Fastly Engineers detected a performance impacting event affecting logins for new users in the Fastly Application.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

We are investigating an issue preventing new account creation on the Fastly platform. This issue began on January 21, 2026, at 17:51 UTC. 

New customers are currently unable to sign up for an account. Consequently, these customers cannot log in to the Support Portal. 

This issue does not affect network or security services for existing customers. Additionally, existing customers can log in to our support systems as normal. 

If you are unable to create an account, please email us at support@fastly.com.

Fastly Engineers detected a performance impacting event affecting our API Services.

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 availability of manage.fastly.com.

CDN delivery, stats aggregation, and all other data plane services were unaffected.

The issue has been resolved and we are monitoring performance closely.

Fastly Engineers detected a performance impacting event affecting our API Services.

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 our API & Configuration Management services

All data centers and other network services were unaffected. The issue has been resolved and we are monitoring performance closely.

We are investigating elevated errors to our Fastly Application.  Customers may experience an error when attempting to access Fastly Next-Gen WAF (NGWAF) configuration pages.

All other products and services are unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting the Fastly Application status page component.

We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery.

Our ability to deliver Network and Security products, along with API services for our Fastly Application are not affected by this incident.

Engineering has confirmed the impact to the Fastly Application has been mitigated.

Engineering has confirmed that Fastly Application has been fully restored. Customers may have experienced elevated errors in our NGWAF settings and configuration webpages from 15:42 to 17:19 UTC.

This incident is resolved.

To offer feedback on our status page, click "Give Feedback" 

Status Post, Created Date/Time: 2025-11-10 17:15: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.

Fastly Engineers detected a performance impacting event affecting the availability of manage.fastly.com and API.

CDN delivery, stats aggregation, and all other data plane services were unaffected.

The issue has been resolved and we are monitoring performance closely.

We are currently investigating performance issues affecting the availability of manage.fastly.com. CDN delivery, stats aggregation, and all other data plane services are unaffected.

Our engineers believe they have identified contributing factor causing the issue impacting the Fastly Application status page component.

We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery.

All other products and services are unaffected by this incident.

Engineering has confirmed the impact to the Fastly Application service has been mitigated.

Engineering has confirmed that the Fastly Application service has been fully restored. Customers may have experienced the following issues: 4xx errors, redirect loops or inability to initiate new login sessions  from 13:56  to 14:21 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

To offer feedback on our status page, click " Give Feedback " 

Status Post, Created Date/Time: 2025-10-22 14:20:19 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're investigating possible performance impact affecting our Configuration Management Services.

All other locations and services are unaffected.

Our engineers believe they have identified contributing factor causing the issue impacting the Configuration Management Services status page component.

We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery.

All other products and services are unaffected by this incident.

Engineering has confirmed the impact to our Configuration Management Services has been mitigated.

Engineering has confirmed that our Configuration Management Services has been fully restored. Customers may have experienced delays in deploying new and existing VCL versions from 15:18 to 16:31 UTC.

This incident is resolved.

To offer feedback on our status page, click "Give Feedback" 

Status Post, Created Date/Time: 2025-10-14 16:10:26 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.