- Detected by Pingoru
- May 01, 2026, 02:49 PM UTC
- Resolved
- May 01, 2026, 10:19 PM UTC
- Duration
- 7h 30m
Affected: Object StorageNetwork ServicesObject Storage
Timeline · 8 updates
-
investigating May 01, 2026, 04:25 PM UTC
We're currently investigating performance impacts in for US-East, US-West and EU-Central with Object Storage. All other locations and services are unaffected.
-
investigating May 01, 2026, 04:31 PM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Object Storage 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.
-
monitoring May 01, 2026, 04:33 PM UTC
Engineering has confirmed the impact to Object Storage service has been mitigated.
-
monitoring May 01, 2026, 04:50 PM UTC
Engineering has deployed a fix and have confirmed a gradual recovery to Object Storage service. We will continue to monitor until we’ve confirmed that customer and end user experience has been fully restored. All other products and services are unaffected by this incident.
-
investigating May 01, 2026, 06:13 PM UTC
Our engineers have identified an additional contributing factor and are developing an adjusted mitigation strategy for our Object Storage. All other locations and services are unaffected.
-
investigating May 01, 2026, 08:24 PM UTC
A fix has been deployed to our Object Storage. Our engineers are continuing to research the contributing factors to verify that no further actions are required. We will provide another update once our investigation is complete. All other locations and services are unaffected.
-
monitoring May 01, 2026, 10:16 PM UTC
Engineering has confirmed the impact to our Object Storage has been mitigated.
-
resolved May 01, 2026, 10:19 PM UTC
Engineering has confirmed that Object Storage has been fully restored. Customers may have experienced elevated errors from 14:59 to 20:58 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. Status Post, Created Date/Time: 2026-05-01 16:29:34 UTC
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 08:05 AM UTC
- Resolved
- Apr 29, 2026, 11:23 AM UTC
- Duration
- 3h 18m
Affected: Fastly ApplicationAPI & Configuration ManagementAPI ServicesFastlyFastly ApplicationAPI & Configuration ManagementAPI Services
Timeline · 5 updates
-
investigating Apr 29, 2026, 08:05 AM UTC
We are currently investigating performance issues affecting the availability of our API. CDN delivery, stats aggregation, and all other data plane services are unaffected.
-
investigating Apr 29, 2026, 10:38 AM UTC
Our engineers are continuing to investigate issues affecting our API Services.
-
investigating Apr 29, 2026, 10:47 AM UTC
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.
-
monitoring Apr 29, 2026, 11:03 AM UTC
Engineering has confirmed the impact to our API Services has been mitigated.
-
resolved Apr 29, 2026, 11:23 AM UTC
Engineering has confirmed that our API Services has been fully restored. Customers may have experienced elevated 429 errors and limited functionality from 08:05 to 11:55 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. Status Post, Created Date/Time: 2026-04-29 09:39:30 UTC
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 04:00 PM UTC
- Resolved
- Apr 28, 2026, 08:00 PM UTC
- Duration
- 4h
Affected: Fastly ApplicationAPI & Configuration ManagementAPI ServicesConfiguration Management ServicesNotification CenterFastlyFastly ApplicationAPI & Configuration ManagementAPI Services
Timeline · 2 updates
-
investigating Apr 28, 2026, 04:00 PM UTC
On April 28, 2026, at 16:00 UTC, Fastly released an update to our Fastly Application introducing a compliance reporting download option providing seamless self-service options helping customers meet their audit and compliance needs. What’s Changing? This update will help provide large enterprises and regulated-adjacent organizations who require predictable configuration behavior and exportable proof of their compliance posture. Key Benefits Self-serve report downloads: Customers can now directly download essential compliance reports—including GDPR, SOC2, HIPAA, PCI, and ISO 27001—as PDFs directly from the UI. Enhanced operational efficiency: This self-serve model eliminates the need for support threads and/or escalations, allowing teams to gather necessary evidence details asynchronously. You can learn more on our blog post: Introducing Compliance Audit Reports What’s next? What do I have to do? Nothing. All actions taken during this update belong to Fastly and 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.
-
resolved Apr 28, 2026, 08:00 PM UTC
This event has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 09:42 PM UTC
- Resolved
- Apr 25, 2026, 04:21 PM UTC
- Duration
- 18h 39m
Affected: Object StorageFastly ComputeKV StoreNetwork ServicesObject Storage
Timeline · 4 updates
-
investigating Apr 24, 2026, 09:42 PM UTC
We are investigating elevated errors to our KV Store, Object Storage service for Asia Pacific (APAC) and South Asia regions. All other products and services are unaffected by this incident.
-
investigating Apr 25, 2026, 02:05 PM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the KV Store, Object Storage for Asia Pacific (APAC) and South Asia regions. 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.
-
monitoring Apr 25, 2026, 02:35 PM UTC
Engineering has confirmed the impact to KV Store, Object Storage service for Asia Pacific (APAC) and South Asia regions has been mitigated.
-
resolved Apr 25, 2026, 04:21 PM UTC
Engineering has confirmed that KV Store, Object Storage service for Asia Pacific (APAC) and South Asia regions has been fully restored. Customers may have experienced increased latency observed when accessing KV Store and Object Storage from 14:42 UTC on April 24, 2026 to 14:49 UTC on April 25, 2026 . 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. Status Post, Created Date/Time: 2026-04-25 16:19:58 UTC
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 09:42 PM UTC
- Resolved
- Apr 24, 2026, 09:42 PM UTC
- Duration
- —
Affected: Object StorageFastly ComputeKV StoreNetwork ServicesObject Storage
Timeline · 1 update
-
resolved Apr 24, 2026, 09:42 PM UTC
This incident post has been superseded, please refer to the updated post here: https://www.fastlystatus.com/incident/378503
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 06:07 PM UTC
- Resolved
- Apr 24, 2026, 06:20 PM UTC
- Duration
- 13m
Affected: Fastly ApplicationAPI & Configuration ManagementAPI ServicesConfiguration Management ServicesFastlyFastlyFastly ApplicationAPI & Configuration ManagementAPI Services
Timeline · 2 updates
-
investigating Apr 24, 2026, 06:07 PM UTC
Fastly Engineers detected a performance impacting event affecting our API & Configuration Management service. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
-
resolved Apr 24, 2026, 06:20 PM UTC
During this incident, customers may have experienced delayed VCL deployment activations from 18:07 to 18:20 UTC. This incident is resolved. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 01:23 PM UTC
- Resolved
- Apr 24, 2026, 04:55 PM UTC
- Duration
- 3h 32m
Affected: AsiaDhanbad (QAM)Raipur (RPR)PlatformAsia
Timeline · 2 updates
-
investigating Apr 24, 2026, 01:23 PM UTC
Traffic in Dhanbad (QAM), Raipur (RPR) has been temporarily rerouted. All other locations and services are unaffected.
-
resolved Apr 24, 2026, 04:55 PM UTC
This event has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 10:22 PM UTC
- Resolved
- Apr 23, 2026, 10:32 PM UTC
- Duration
- 10m
Affected: AsiaTokyo (NRT)PlatformAsia
Timeline · 2 updates
-
investigating Apr 23, 2026, 10:22 PM UTC
Fastly Engineers detected a performance impacting event affecting the Tokyo (NRT) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
-
resolved Apr 23, 2026, 10:32 PM UTC
This event has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 05:47 PM UTC
- Resolved
- Apr 23, 2026, 07:07 PM UTC
- Duration
- 1h 20m
Affected: Security Console & APIDashboard Data
Timeline · 4 updates
-
investigating Apr 23, 2026, 05:47 PM UTC
We are investigating elevated errors to Dashboard Data in our Next Gen-WAF (NGWAF) Dashboard. All other products and services are unaffected by this incident.
-
investigating Apr 23, 2026, 06:59 PM UTC
Our engineers believe they have identified contributing factor causing the issue impacting Dashboard Data for our NGWAF Dashboard. 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.
-
monitoring Apr 23, 2026, 07:03 PM UTC
Engineering has confirmed the impact to Dashboard Data for our NGWAF Dashboard has been mitigated.
-
resolved Apr 23, 2026, 07:07 PM UTC
Engineering has confirmed that Dashboard Data for our NGWAF Dashboard has been fully restored. From 17:47 to 18:57 UTC, customers may have experienced elevated 5xx errors, degraded performance, blank graphs or the inability to perform searches. Additionally, attempts to view queries from various sites may have failed returning an "Invalid search query" error message. 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. Status Post, Created Date/Time: 2026-04-23 18:37:49 UTC
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 06:31 PM UTC
- Resolved
- Apr 22, 2026, 08:51 PM UTC
- Duration
- 2h 20m
Affected: AsiaVaranasi (VNS)PlatformAsia
Timeline · 2 updates
-
investigating Apr 22, 2026, 06:31 PM UTC
Fastly Engineers detected a performance impacting event affecting the Varanasi (VNS) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
-
resolved Apr 22, 2026, 08:51 PM UTC
During this incident, customers may have experienced elevated errors from 18:34 to 20:51 UTC. This incident is resolved. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 06:07 AM UTC
- Resolved
- Apr 22, 2026, 07:15 AM UTC
- Duration
- 1h 8m
Affected: Fastly ApplicationAPI & Configuration ManagementAPI ServicesConfiguration Management ServicesFastlyFastlyFastly ApplicationAPI & Configuration ManagementAPI Services
Timeline · 2 updates
-
investigating Apr 22, 2026, 06:07 AM UTC
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.
-
resolved Apr 22, 2026, 07:15 AM UTC
Engineering has confirmed that API & Configuration Management service has been fully restored. Customers may have experienced issues using API services and accessing manage.fastly.com from 06:07 to 07:15 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. Status Post, Created Date/Time: 2026-04-22 07:35:20 UTC
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 05:35 PM UTC
- Resolved
- Apr 21, 2026, 09:16 PM UTC
- Duration
- 3h 41m
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 04:32 PM UTC
- Resolved
- Apr 21, 2026, 09:16 PM UTC
- Duration
- 4h 44m
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 10:47 PM UTC
- Resolved
- Apr 21, 2026, 09:16 PM UTC
- Duration
- 22h 29m
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 08:39 AM UTC
- Resolved
- Apr 21, 2026, 09:16 PM UTC
- Duration
- 1d 12h
Read the full incident report →
- Detected by Pingoru
- Apr 19, 2026, 03:35 PM UTC
- Resolved
- Apr 21, 2026, 09:16 PM UTC
- Duration
- 2d 5h
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 09:18 PM UTC
- Resolved
- Apr 21, 2026, 09:16 PM UTC
- Duration
- 3d 23h
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 12:55 PM UTC
- Resolved
- Apr 21, 2026, 09:16 PM UTC
- Duration
- 4d 8h
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 08:00 AM UTC
- Resolved
- Apr 21, 2026, 09:16 PM UTC
- Duration
- 4d 13h
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 03:00 AM UTC
- Resolved
- Apr 21, 2026, 09:16 PM UTC
- Duration
- 4d 18h
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 06:29 PM UTC
- Resolved
- Apr 21, 2026, 09:16 PM UTC
- Duration
- 5d 2h
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 01:12 AM UTC
- Resolved
- Apr 21, 2026, 09:16 PM UTC
- Duration
- 6d 20h
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 02:17 AM UTC
- Resolved
- Apr 21, 2026, 09:16 PM UTC
- Duration
- 7d 18h
Read the full incident report →
- Detected by Pingoru
- Apr 12, 2026, 12:00 PM UTC
- Resolved
- Apr 21, 2026, 09:16 PM UTC
- Duration
- 9d 9h
Read the full incident report →
- Detected by Pingoru
- Apr 10, 2026, 09:00 AM UTC
- Resolved
- Apr 21, 2026, 09:16 PM UTC
- Duration
- 11d 12h
Read the full incident report →