API Services
Fastly will be performing maintenance on our platform system on the 22nd of April 2025 from 00:00 to 01:00 UTC (~60m duration).
What’s Changing?
We're making improvements to make the Fastly platform even more resilient, secure, and reliable.
- We are introducing general security updates to our authentication infrastructure
- We are improving system availability so that future maintenance of the Authentication Platform can be performed without impacting availability.
What’s next? What do I have to do?
Nothing. All actions taken during this planned maintenance belong to Fastly. During this time, customers may experience:
- Temporary inability to log in to the Fastly App (manage.fastly.com)
- Temporary inability to log in to the Signal Science (SigSci) console (dashboard.signalsciences.net)
- Possible navigation issues in the apps due to token refresh interruptions.
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.
What’s Changing?
Fastly will be conducting planned maintenance on both the Fastly Control Panel (https://manage.fastly.com/) and the Signal Science (SigSci) console (https://dashboard.signalsciences.net/) as a part of our ongoing effort to enhance customer account security and ensure we are following security best practices on our platform.
We will permanently reduce the account session timeout during this maintenance. Instead of three hours, sessions will now expire after 30 minutes of inactivity.
These changes will take effect immediately on the 15th of April 2025 at 14:00 UTC.
For security purposes, all active user sessions will be terminated after 30 minutes of inactivity, and users will be directed to the login page. This change applies to all Fastly account types and roles, and any unsaved activity may be lost after the 30-minute idle period.
You can learn more about session timeouts in our Managing users documentation.
This maintenance will have no impact on our ability to deliver Network or Security services to our customers.
What’s next? What do I have to do?
Nothing. All actions taken during this planned maintenance belong to Fastly and there are no anticipated actions 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.
The scheduled maintenance has been completed.
To offer feedback on our status page, click "Give Feedback"
Fastly Engineers detected an event affecting the Fastly Application Audit Logs.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
We are investigating elevated errors to our Fastly Application.
All other products and services are unaffected by this incident.
Our engineers are continuing to investigate the login functionality of our Fastly Application.
Our engineers have identified the contributing factor and are applying a fix to our Fastly Application.
All other locations and services are unaffected.
Engineering has confirmed the impact to our Fastly Application has been mitigated.
Engineering has confirmed that our Fastly Application has been fully restored. Customers may have experienced one or more of the following issues including: 4xx errors, redirect loops, inability to initiate new login sessions, or forced termination of active user sessions from 19:24 to 22:51 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-03-13 21:02:27 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.
We are investigating elevated errors to our Fastly Application.
All other products and services are unaffected by this incident.
Our engineers have identified the contributing factor and are applying a fix to our Fastly Application.
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 an error when attempting to access their control panel through manage.fastly.com and increased latency and errors when using API Services as a result of this incident from 00:20 to 00:58 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-03-07 00:41:27 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 an availability impacting event affecting the Fastly Application service.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
We are investigating elevated errors to our API & Configuration Management services.
All other products and services are unaffected by this incident.
Our engineers have identified the contributing factor and are applying a fix to our API & Configuration Management services.
All other locations and services are unaffected.
Engineering has confirmed the impact to our API & Configuration Management has been mitigated.
Engineering has confirmed that our API & Configuration Management services have been fully restored. Customers may have experienced elevated errors from 7:15 to 7:58 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-02-04 08:12:42 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.
On the 29th of January 2025 we will be launching a new account-switching experience that is part of our continuous efforts to strengthen our security processes.
Customers who have our multi-account user access feature enabled are anticipated to be impacted by our implementation and the below message describes how this change applies to your services.
What’s Changing?
We are deploying a re-authentication step to our account services that will trigger when users switch between Fastly accounts within the Fastly Application. This change applies to all user accounts and access levels.
To learn more about this change please read our Managing multiple accounts documentation.
Why does it matter?
The best part? You don't have to do a thing! This change is all about enhancing security practices and ensuring that all shared information is protected under our non-disclosure agreements. Users will need to re-authenticate when switching between their different accounts within the Fastly Application.
This effort will help to better secure your accounts in the interim as we continue to develop a smoother and more seamless long term account-switching experience.
Your account will continue to operate as expected and all other products and services remain unaffected by this change.
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.
We are investigating elevated errors to our Hyderabad (HYD), Manila (MNL), Bogota (BOG), Johannesburg (JNB), Singapore (SIN) POPs for Compute Services and the Fastly Application.
All other products and services are unaffected by this incident.
Our engineers have identified the contributing factor and are applying a fix to our Hyderabad (HYD), Manila (MNL), Bogota (BOG), Johannesburg (JNB), Singapore (SIN) POPs for Compute Services.
All other locations and services are unaffected.
Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Hyderabad (HYD), Manila (MNL), Bogota (BOG), Johannesburg (JNB), Singapore (SIN) POPs for Compute services.
All other locations and services are unaffected.
Engineering has deployed a fix and have confirmed a gradual recovery to our Hyderabad (HYD), Manila (MNL), Bogota (BOG), Johannesburg (JNB), Singapore (SIN) POPs and Fastly Application service. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.
After further investigation, Engineering observed impact to our Tokyo (NRT), Tokyo (TYO), and Osaka (ITM) POPs.
Engineering has confirmed that Hyderabad (HYD), Manila (MNL), Osaka (ITM), Tokyo (NRT), Tokyo (TYO), Bogota (BOG), Fastly Application, Johannesburg (JNB), Singapore (SIN) POPs and service have been fully restored. Compute customers may have experienced errors for requests that utilized geolocation as well as login issues with the Fastly Application from the 28th of January at 04:21 to 18:30 UTC.
Affected customers may have experienced impact to varying degrees and to a shorter duration than set forth above.
As the fix was deployed Engineering made additional adjustments to address impact observed to our Tokyo (NRT), Tokyo (TYO), and Osaka (ITM) POPs. Customer during this time may have experienced an increase in error rates from the 28th of January at 23:00 to the 29th of January 05:00 UTC.
Affected customers may have experienced impact to varying degrees and to a shorter duration than set forth above.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-01-28 09:30:53 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.
We are investigating elevated errors to our Fastly Application service.
Our engineers have identified the contributing factor and are applying 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 5xx errors and issues when they attempted to enable or access purchased products from 18:00 to 19:16 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-01-22 19:21:56 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.