On the 30th of June 2025 at 19:00 UTC, Fastly released new options for fine-tuned control over user access and permissions within the Fastly Control Panel. This release is a part of our continued effort to optimize the efficiency and effectiveness of our platform.
What’s Changed?
This update introduces two enhancements to help you manage user access and Transport Layer Security (TLS) related permissions more effectively:
New user roles:
We've added TLS Viewer and TLS Admin roles to give you more granular control over TLS configurations.
These roles allow you to assign TLS-specific access without granting broader platform permissions.
Improved roles visibility in the UI:
The Active Users view in the User Management UI now includes a Role column, making it easier to see and audit what roles are assigned to each user.
Both new TLS user roles are now available for adding a new user account or configuring user roles and permissions for current users accounts.
What’s next? What do I have to do?
Nothing. Our engineers have initiated the maintenance to our Fastly Application, and there is no anticipated action or impact for our customers. Customers now have additional options to customize their new and existing user permissions. Rest assured that Fastly has not updated any existing permissions as a result of this maintenance. Customers may review and adjust their own preferences at their own pace.
Customers with any questions or concerns may engage with our Support team through https://support.fastly.com.
The scheduled maintenance has been completed.
All subscribers can review our initial post here.
To offer feedback on our status page, click "Give Feedback"
Fastly Engineers detected a performance impacting event affecting our service configuration endpoints API.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Fastly Engineers detected a performance impacting event affecting the Houston (IAH) data center.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Traffic in Honolulu (HNL) has been temporarily rerouted.
All other locations and services are unaffected.
Traffic in Honolulu (HNL) has been temporarily rerouted.
All other locations and services are unaffected.
On the 23rd of June 2026 at 20:16 UTC, Fastly released an update that included a bug fix to our Fastly API. This bug impacted the order of paginated results from the GET /service-authorizations endpoint, which could cause inconsistent results to be returned.
What’s Changing?
This change has introduced altered behavior in the API. If no sort parameter has been provided in the request, the results will now default to sorting by ID.
What’s next? What do I have to do?
Nothing. There is no anticipated action or impact for our customers.
Customers with any questions or concerns may engage with our Support team through https://support.fastly.com or by contacting your designated account management team members.
We are investigating elevated errors to our Brussels (BRU) Point of Presence (POP).
All other products and services are unaffected by this incident.
Our engineers have identified the contributing factor and are developing a fix to our Brussels (BRU) POP.
All other locations and services are unaffected.
Engineering has confirmed the impact to our Brussels (BRU) POP has been mitigated.
Engineering has confirmed that our Brussels (BRU) POP has been fully restored. Customers may have experienced request timeouts to the KV store within Fastly's Compute service, and increased cache misses from the 23rd of June at 12:30 to the 27th of June at 18:12 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-06-27 16:33:20 UTC
Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.
Fastly Engineers detected a performance impacting event affecting the Manchester (MAN) data center.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Traffic in Ghana (ACC) has been temporarily rerouted.
All other locations and services are unaffected.
The Fastly support chat system is currently experiencing performance issues. We are working to restore service, but communications may be interrupted or delayed for a subset of customers.
How will I be able to reach Support?
Our customers will be able to contact support through t he Fastly Support Portal (https://support.fastly.com/s/) or by sending an email to support@fastly.com.
All other products and services are unaffected.
Our engineers have identified the contributing factor and are developing a fix to our Support Chat System.
This incident does not affect our ability to deliver network or security services.
Engineering has confirmed the impact to our Support Chat System has been mitigated.
Engineering has confirmed that our Support Chat System has been fully restored. Customers may have experienced issues creating new Fastly Support cases via chat from 19:10 to 20:36 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-06-20 20:06:29 UTC
Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.