API & Configuration Management
We are investigating elevated errors to our Fastly Application services. Customers may experience an error when attempting to access their Fastly Control Panel.
Our ability to serve Network and Security services are not affected by this event.
We continue to investigate this event as a high priority, responding engineers have confirmed that the Security Console & API is also impacted. Customers attempting to access their Signal Sciences Dashboards will experience an error when attempting to log in.
Engineering has confirmed the impact to our Fastly Application and Security Console & API has been mitigated. Customers who were logged in at the onset of this incident may be required to log back in order to obtain access.
Our ability to deliver existing Network and Security services to our customers was not affected by this incident. Full duration of possible impact will be provided in our final update. Engineers and acute incident response teams are monitoring to ensure no further impact.
Engineering has confirmed that both the Fastly Application and Security Console have been fully restored. Customers may have experienced an error when attempting to access these systems and their control panels from 21:51 to 22:12 UTC.
Our engineers did confirm with acute incident responders that api.fastly.com was not affected by this incident.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-07-11 22:08:11 UTC
Note: Our Customer Escalation Management team have updated 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.
On the 9th of July 2025, Fastly released an update to introduce Automated User Lifecycle Management. This update included provisioning, deprovisioning, and real-time updates via System for Cross-domain Identity Management (SCIM) which are now available via the Fastly Control Panel for all Fastly services for customers using Okta.
What’s Changing?
This update will enable:
- Reduction in Human Errors: Reduction in overhead associated with manually managing users within the applications.
- Automated User Management: SCIM integration improves security by ensuring that user management is restricted to and inherited from the Identity Provider (IdP), reducing the risk of manual errors.
- Comprehensive Audit Logs: Detailed logging of all SCIM-related activities supports compliance requirements for user activity monitoring and reporting.
- Reduced Manual Intervention: Automating user provisioning and deprovisioning minimizes the risk of human error in account management
- Improved Security Posture: Improve security posture for Fastly and you, by ensuring all user management is restricted/inherited from an IdP.
- SCIM 2.0 Compatibility: Adherence to SCIM 2.0 specifications ensures interoperability and compliance with industry standards for identity management.
To learn more about why we have made this change please read our Automating user management documentation.
What’s next? What do I have to do?
Nothing. All actions taken during this planned release belong to Fastly.
Contact Information
Customers with any questions or concerns may engage with our Security team through security@fastly.com or by contacting our Support team at https://support.fastly.com.
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.
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 seeing increased errors across multiple Fastly services that utilize a common third party service provider, unrelated to Fastly's Edge Cloud Network.
Fastly has launched acute incident response practices to investigate into this issue further in an effort to reduce the impact to our customers.
As our engineers determine the scope of impact our Customer Escalation Management team will be updating the impacted components on this status post.
We're aware of an ongoing Google Cloud incident, detailed on their status page, which is affecting several Fastly services. Customers may be experiencing increased latency due to impact to our KV Store.
Specifically, those trying to access their control plane via manage.fastly.com might notice that several key Observability features are not loading, including Billing, Historical Stats, Log Explorer & Insights, Origin Inspector, Real-Time Log Streaming, and Real-time Analytics. You may also find it difficult to engage with API endpoints. Additionally, customers might see elevated errors when accessing Fastly webpages and documented resources.
Our engineers are working to restore these services as a high priority and we will provide more information shortly.
You can monitor the Google Cloud incident here:
We've confirmed that customers won't receive status post notifications through their Support Slack channels during this incident.
However, we want to assure you that your ability to request a support case through our Support Slack services remains unaffected. You can still open new support cases as needed.
Google Cloud has communicated that they have successfully deployed mitigations to the majority of their services. We are now observing a gradual recovery of Fastly services.
We will continue to monitor this situation with the highest priority until all Fastly and customer services are fully restored.
We have continued to monitor the Google Cloud Status Page for the latest information by the third party service provider.
Incident Update: Full Recovery and Root Cause Identified
Current Status: Resolved
We're confirming that all services impacted during yesterday's incident have fully recovered. Our teams continuously monitored the situation and verified the stability of all affected systems.
Root Cause Analysis
Our investigation has confirmed that the increased errors and latency across our KV Store, control plane, and certain Observability features were a direct result of the Google Cloud disruption on the 12th of June 2025.
Google has publicly shared a post-mortem regarding the incident. It includes specific information about the root cause—an invalid automated quota update to their API management system—along with their mitigation strategies and steps they're taking for future prevention.
Next Steps
For a comprehensive understanding of the incident's origin, mitigation, and Google's preventative measures, we encourage customers to review the official Google Cloud Status Page. This provides a full breakdown from their perspective.
Additionally, our Product and Engineering teams will thoroughly review all Google Cloud Platform (GCP) reports to determine mitigation strategies and ensure they are adopted as part of our long-term preventive measures to ensure our systems are more resilient to third-party outages of this kind in the future.
We appreciate your patience and understanding as we worked through this third-party event. Our focus remains on providing reliable and high-performance services.
On the 30th of June 2025 at 19:00 UTC, Fastly will release 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 Changing?
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 will be available on the 30th of June 2025 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 prepared upcoming maintenance to our Fastly Application, and there is no anticipated action or impact for our customers. Customers will have additional options to customize their new and existing user permissions. Rest assured that Fastly is not updating 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.
On the day of the release a subsequent post will be shared as an announcement, and will include a link to updated material on our docs.fastly.com webpage.
To offer feedback on our status page, click "Give Feedback"
As part of our ongoing commitment to account security and alignment with industry standard best practices, we’re strengthening our password policy across our Fastly Application and Next-Gen WAF (NGWAF) Console product offerings.
Fastly will be performing maintenance on the Fastly Control Panel on the 19th of May 2025 from 14:00 to 14:30 UTC (~30 minute duration).
What’s Changing?
Beginning on the 19th of May 2025, any user who creates a new account or resets their password in the Fastly Application will be required to choose a password that is at least 12 characters long including letters, numbers, and special characters. This change will affect the Sign Up, Create Account, and Reset Password experiences on our website.
This change will help maintain account security and provides significant benefits to our users, including:
- Longer passwords are more secure and significantly reduce the risk of brute‑force or guessing attacks
- A minimum length of 12 characters meets the current recommended industry security standard
- Safeguards your data against unauthorized access and protects user accounts
This new password requirement condition will be displayed in real time as a password is entered into any password field on the website. Users attempting to submit a password with fewer than 12 characters, including Application Programming Interface (API) or Terraform requests to Create or Reset a password, will fail.
This change will not impact existing account passwords and will only apply to new account passwords or when a password reset is requested.
What’s next? What do I have to do?
If you have an integration using our Fastly API or Terraform modules to automate account creation or password resets, you’ll need to update your code and configurations to enforce the new 12 character minimum requirement.
Remember that all passwords associated with your Fastly account are case sensitive.
Your account will continue to operate as expected and all other products and services remain unaffected by this maintenance.
Contact Information
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.The scheduled maintenance has been completed.
To offer feedback on our status page, click "Give Feedback"
We are currently investigating performance issues affecting the availability of new customer signups, invitation acceptances, and SSO configurations. CDN delivery, stats aggregation, and all other data plane services are unaffected.
Our engineers have identified the contributing factor and are developing a fix to our Fastly Application service.
All other locations and services are unaffected.
Engineering has confirmed the impact to Fastly Application service has been mitigated.
Engineering has confirmed that Fastly Application
service
has been fully restored. Customers may have experienced
performance issues affecting the availability of new customer signups, invitation acceptances, and SSO configurations
from 18:50 to 19:58
UTC.
This incident is resolved.
To offer feedback on our status page, click " Give Feedback "
Status Post, Created Date/Time: 2025-05-13 19:37:09 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 have confirmed a performance impacting event that affected the API Services. Customers may have experienced a 410 error code with a plan to apply changes to services in Terraform from 14:17 to 16:22 UTC.
All other services were unaffected. The issue has been resolved and we are monitoring performance closely.