Between approximately 16:59 and 17:12 UTC on August 20, 2026, some customers experienced difficulty accessing the manage.fastly.com dashboard, including blank pages and login issues.

This incident did not impact API endpoints on api.fastly.com.

This issue has been fully resolved and all customers should now have normal access to manage.fastly.com. We apologize for any disruption this may have caused.

Our engineering team has identified the contributing factor and is implementing measures to prevent recurrence.

Fastly will be performing scheduled maintenance on our Month to Date API Services from 20 August 2026, 12:00 UTC - 28 August 2026, 01:00 UTC (7d 13h).

During this time the Month to Date API service will be inaccessible and our customers will not receive spend alerts during this maintenance window. Once completed, the Month to Date page will fully restored with no impact to your invoice. 

We are investigating elevated errors to our API & Configuration Management service

All other products and services are unaffected by this incident.

Our engineers believe they have identified the contributing factor causing elevated 5xx errors and slowness impacting api.fastly.com and manage.fastly.com.

Our engineers are actively working on a fix. We will provide another update within the hour.

Our engineers have deployed a fix and are actively monitoring for improvements. We have not observed any additional errors since the fix was applied.

We will provide a further update once we've confirmed full resolution, or within the next hour.

We are investigating a reoccurrence of the issue causing elevated 5xx errors and slowness for api.fastly.com and manage.fastly.com.

Our engineers are actively working to diagnose the contributing factor and prevent further recurrence.

We will provide another update as more information becomes available or within the next hour.

Following the reoccurrence, our engineers have redeployed a fix and are actively monitoring for improvements. We have not observed any additional errors since the fix was applied.

We will provide a further update once we've confirmed full resolution, or within the next hour.

This incident has been resolved. Between 06:20 and 09:27 UTC, customers may have experienced elevated 5xx errors and slowness for api.fastly.com and manage.fastly.com. Our engineers identified the contributing factor and applied a fix, and normal service has been confirmed for an extended monitoring period.

We apologize for any disruption this may have caused. If you continue to experience issues, please reach out to support.

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 an issue causing elevated 503 errors and slowness affecting api.fastly.com and manage.fastly.com. Our engineers are actively working to diagnose the contributing factor.

We will provide another update as more information becomes available.

We have observed a recovery of our API and configuration management services (api.fastly.com and manage.fastly.com).

Error rates and response times have returned to nominal levels.

Our engineers are continuing to monitor the platform closely to ensure stability before we resolve this incident.

All other products and services are unaffected by this incident.

Engineering has confirmed that api.fastly.com and manage.fastly.com have been fully restored.

Customers may have experienced possible errors, including elevated 503 responses and slow or failed access, from 06:03 to 07:37 UTC.This incident is resolved.

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

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

All 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 Services.

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

The AI Assistant within the Fastly Control Panel will be temporarily unavailable while it undergoes maintenance.

Maintenance window ends: Monday, July 6 at 11:00 p.m. UTC (4:00 p.m. PDT)

This maintenance will not affect your Network or Security services, nor your access to the Fastly Control Panel.  Your ability to manage service configurations, API services, and observability features will remain fully accessible throughout the window. 

We'll post an update here once the assistant is back online.

The scheduled maintenance has been completed.

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 investigating elevated errors with product enablements in our Fastly Application. 

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.

All other products and services are unaffected by this incident.

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 failures with enablement, disablement, and configuration operations, as well as enablement checks from 17:25 to 18:22 UTC.

This incident is resolved.

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 an issue causing errors and timeouts for customers using the Fastly API (api.fastly.com).

Our engineers are actively working to diagnose the contributing factor. We will provide another update as more information becomes available or within the next hour.

All other products and services are unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting the  API 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 API Services has been mitigated.

Our engineers have confirmed that the Fastly API (api.fastly.com) has been fully restored. Customers may have experienced elevated 503 errors, increased timeouts, or failures on API calls and Terraform builds from approximately 18:35 to 19:37 UTC.

As a side effect of the API degradation, the following areas were also impacted during this period:

• Next-Gen WAF (NGWAF) rule and configuration updates may have been delayed in taking effect
• Fastly account sign-up may have experienced disruptions
• Fastly Support Portal functionality may have been affected

Service has been fully restored. Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

This incident is resolved.

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.