- Detected by Pingoru
- Jun 17, 2026, 05:05 PM UTC
- Resolved
- Jun 17, 2026, 07:10 PM UTC
- Duration
- 2h 5m
Affected: South AmericaBogota (BOG)South AmericaPlatformPlatformBogota (BOG)South AmericaPlatform
Timeline · 4 updates
-
investigating Jun 17, 2026, 05:05 PM UTC
We are investigating elevated errors to our Bogota (BOG) Point of Presence (POP). All other products and services are unaffected by this incident.
-
investigating Jun 17, 2026, 06:13 PM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Bogota (BOG) 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 Jun 17, 2026, 06:33 PM UTC
Engineering has confirmed the impact to our Bogota (BOG) POP has been mitigated.
-
resolved Jun 17, 2026, 07:10 PM UTC
Engineering has confirmed that our Bogota (BOG) POP has been fully restored. Customers may have experienced elevated errors and increased latency from 17:05 to 17:51 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-06-17 17:30:29 UTC
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 05:05 PM UTC
- Resolved
- Jun 17, 2026, 07:43 PM UTC
- Duration
- 2h 38m
Affected: South AmericaLima (LIM)PlatformSouth AmericaLima (LIM)Platform
Timeline · 4 updates
-
investigating Jun 17, 2026, 05:05 PM UTC
We are investigating elevated errors to our Lima (LIM) Point of Presence (POP). All other products and services are unaffected by this incident.
-
investigating Jun 17, 2026, 06:12 PM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Lima (LIM) 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 Jun 17, 2026, 06:33 PM UTC
Engineering has confirmed the impact to our Lima (LIM) POP has been mitigated.
-
resolved Jun 17, 2026, 07:43 PM UTC
Engineering has confirmed that our Lima (LIM) POP has been fully restored. Customers may have experienced elevated errors and increased latency from 17:05 to 17:51 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-06-17 18:00:00 UTC
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2026, 07:25 PM UTC
- Resolved
- Jun 11, 2026, 07:40 PM UTC
- Duration
- 15m
Affected: AsiaHong Kong (HKG)PlatformPlatformPlatformPlatform
Timeline · 2 updates
-
investigating Jun 11, 2026, 07:25 PM UTC
Traffic in Hong Kong (HKG) has been temporarily rerouted. All other locations and services are unaffected.
-
resolved Jun 11, 2026, 07:40 PM UTC
This event has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2026, 03:01 PM UTC
- Resolved
- Jun 11, 2026, 04:01 PM UTC
- Duration
- 1h
Affected: AsiaHong Kong (HKG)PlatformPlatformPlatformPlatform
Timeline · 3 updates
-
investigating Jun 11, 2026, 03:01 PM UTC
Fastly Engineers detected a performance impacting event affecting the Hong Kong (HKG) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
-
resolved Jun 11, 2026, 03:20 PM UTC
This event has been resolved.
-
resolved Jun 11, 2026, 04:01 PM UTC
This event has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 06, 2026, 10:00 PM UTC
- Resolved
- Jun 06, 2026, 11:56 PM UTC
- Duration
- 1h 56m
Affected: Howrah (QAC)PlatformPlatformIndiaIndiaHowrah (QAC)PlatformPlatform
Timeline · 2 updates
-
investigating Jun 06, 2026, 10:00 PM UTC
Traffic in Howrah (QAC) has been temporarily rerouted. All other locations and services are unaffected.
-
resolved Jun 06, 2026, 11:56 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 06, 2026, 12:50 AM UTC
- Resolved
- Jun 06, 2026, 02:25 AM UTC
- Duration
- 1h 35m
Affected: North AmericaAtlanta (PDK)Dallas (DFW)Denver (DEN)Miami (MIA)Minneapolis (MSP)Newark (EWR)PlatformNorth AmericaPlatformNorth AmericaAtlanta (PDK)Dallas (DFW)Denver (DEN)Miami (MIA)Minneapolis (MSP)Newark (EWR)PlatformNorth AmericaPlatformNorth America
Timeline · 5 updates
-
investigating Jun 06, 2026, 01:00 AM UTC
We are investigating elevated errors to our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), Newark (EWR) Points of Presence (POPs) All other products and services are unaffected by this incident.
-
investigating Jun 06, 2026, 01:06 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), Newark (EWR) status page components. 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.
-
investigating Jun 06, 2026, 01:53 AM UTC
The fix has been successfully deployed, and we have observed a recovery to only our DFW, DEN, MSP, and EWR POPs. Error rates and latency have returned to nominal levels and we are monitoring stability at these locations. Our engineers have identified an additional contributing factor and are developing an adjusted mitigation strategy to our MIA and PDK POPs specifically. All other locations and services are unaffected.
-
monitoring Jun 06, 2026, 02:14 AM UTC
Engineering has confirmed the impact to our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), and Newark (EWR) Points of Presence (POPs) has been mitigated.
-
resolved Jun 06, 2026, 02:25 AM UTC
Engineering has confirmed that our our Atlanta (PDK), Dallas (DFW), Denver (DEN), Miami (MIA), Minneapolis (MSP), and Newark (EWR) POPs have been fully restored. Customers may have experienced increased latency from 00:50 to 01:50 UTC at our DFW, DEN, MSP, and EWR POPs and from 00:50 to 02:13 UTC at our PDK and MIA POPs. 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-06-06 01:01:14 UTC
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2026, 12:00 PM UTC
- Resolved
- Jun 05, 2026, 12:52 PM UTC
- Duration
- 52m
Affected: AsiaSingapore (SIN)PlatformPlatformPlatformPlatform
Timeline · 2 updates
-
investigating Jun 05, 2026, 12:00 PM UTC
Fastly Engineers detected a performance impacting event affecting the Singapore (SIN) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
-
resolved Jun 05, 2026, 12:52 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2026, 08:00 AM UTC
- Resolved
- Jun 04, 2026, 09:25 AM UTC
- Duration
- 1h 25m
Affected: North AmericaHouston (IAH)PlatformNorth AmericaPlatformNorth AmericaHouston (IAH)PlatformNorth AmericaPlatformNorth America
Timeline · 2 updates
-
investigating Jun 04, 2026, 08:00 AM UTC
Traffic in Houston (IAH) has been temporarily rerouted. All other locations and services are unaffected.
-
resolved Jun 04, 2026, 09:25 AM UTC
This event has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2026, 03:03 PM UTC
- Resolved
- Jun 02, 2026, 04:36 PM UTC
- Duration
- 1h 33m
Affected: South AmericaFortaleza (FOR)PlatformSouth AmericaFortaleza (FOR)PlatformPlatformSouth AmericaPlatform
Timeline · 2 updates
-
investigating Jun 02, 2026, 03:03 PM UTC
Traffic in Fortaleza (FOR) has been temporarily rerouted. All other locations and services are unaffected.
-
resolved Jun 02, 2026, 04:36 PM UTC
This event has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 01:38 AM UTC
- Resolved
- May 28, 2026, 02:29 AM UTC
- Duration
- 51m
Affected: South AmericaFortaleza (FOR)PlatformSouth AmericaFortaleza (FOR)PlatformPlatformSouth AmericaPlatform
Timeline · 2 updates
-
investigating May 28, 2026, 01:38 AM UTC
We are investigating elevated errors to our Fortaleza (FOR) Point of Presence (POP). All other products and services are unaffected by this incident.
-
resolved May 28, 2026, 02:29 AM UTC
This event has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 06:50 AM UTC
- Resolved
- May 22, 2026, 12:10 PM UTC
- Duration
- 5h 20m
Affected: Web DeliveryImage OptimizationNetwork ServicesWeb DeliveryImage Optimization
Timeline · 4 updates
-
investigating May 22, 2026, 09:53 AM UTC
We're currently investigating performance issues with our Image Optimization service in Europe. All other services are unaffected.
-
investigating May 22, 2026, 10:20 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Image Optimization 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 22, 2026, 10:24 AM UTC
Engineering has confirmed the impact to Image Optimization service has been mitigated.
-
resolved May 22, 2026, 12:10 PM UTC
This incident has been resolved. Image Optimization services in Europe are fully restored and operating normally. Customers may have experienced intermittent errors and elevated latency between 06:50 UTC and 10:02 UTC on May 22, 2026. We apologize for any disruption this may have caused and thank you for your patience. 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-22 09:55:16 UTC
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 09:29 PM UTC
- Resolved
- May 21, 2026, 09:35 PM UTC
- Duration
- 6m
Affected: North AmericaAshburn (IAD)PlatformNorth AmericaPlatformNorth AmericaPlatformNorth AmericaPlatformNorth America
Timeline · 2 updates
-
investigating May 21, 2026, 09:29 PM UTC
Fastly Engineers detected a performance impacting event affecting the Ashburn (IAD) data center.
-
resolved May 21, 2026, 09:35 PM UTC
The issue causing temporary unhealthy cache nodes was resolved, and services were fully restored. Our engineers confirmed that all cache nodes returned to a healthy state. Customers may have experienced impact between 21:29 UTC and 21:35 UTC (approximately 6 minutes). All other services and locations were unaffected by this event.
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 06:35 PM UTC
- Resolved
- May 20, 2026, 08:19 PM UTC
- Duration
- 1h 44m
Affected: Fastly ApplicationAPI & Configuration ManagementAPI ServicesFastlyFastly ApplicationAPI & Configuration ManagementAPI Services
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- May 17, 2026, 01:27 AM UTC
- Resolved
- May 17, 2026, 03:26 AM UTC
- Duration
- 1h 59m
Affected: AsiaAmbala (QAA)PlatformAsiaAmbala (QAA)PlatformPlatform
Timeline · 3 updates
-
investigating May 17, 2026, 01:51 AM UTC
Traffic in Ambala (QAA) has been temporarily rerouted. All other locations and services are unaffected.
-
investigating May 17, 2026, 02:59 AM UTC
Update: The responding escalation manager erroneously marked the incorrect status page component in their original post which caused the wrong title to appear within customer support chat and email threads. This was corrected to display the proper component (Ambala (QAA)). All other components, locations and services were unaffected by this event.
-
resolved May 17, 2026, 03:26 AM UTC
Engineering has confirmed that Ambala (QAA) POP has been fully restored. Customers may have experienced elevated intermittent errors or periods of latency while traffic was rerouted from 01:27 to 03:26 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-05-17 01:53:50 UTC
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 06:06 AM UTC
- Resolved
- May 13, 2026, 07:15 AM UTC
- Duration
- 1h 9m
Affected: Domain ManagementTLS ProvisioningNetwork ServicesDomain ManagementTLS Provisioning
Timeline · 4 updates
-
investigating May 13, 2026, 06:54 AM UTC
We are investigating elevated errors to our TLS Provisioning feature.
-
investigating May 13, 2026, 07:01 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the TLS Provisioning 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.
-
monitoring May 13, 2026, 07:12 AM UTC
Engineering has confirmed the impact to TLS Provisioning service has been mitigated.
-
resolved May 13, 2026, 07:15 AM UTC
Engineering has confirmed that our TLS Provisioning service has been fully restored. Customers may have experienced errors and timeouts when using the TLS provisioning API from 06:06 to 07:12 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-05-13 06:55:15 UTC
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 01:49 PM UTC
- Resolved
- May 12, 2026, 01:59 PM UTC
- Duration
- 10m
Affected: Domain ManagementTLS ProvisioningNetwork ServicesDomain ManagementTLS Provisioning
Timeline · 2 updates
-
investigating May 12, 2026, 01:49 PM UTC
Fastly Engineers detected a performance impacting event affecting the TLS Provisioning service. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
-
resolved May 12, 2026, 01:59 PM UTC
This event has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 10, 2026, 07:25 PM UTC
- Resolved
- May 10, 2026, 10:33 PM UTC
- Duration
- 3h 8m
Affected: Fastly ApplicationAPI & Configuration ManagementAPI ServicesConfiguration Management ServicesDomain ManagementTLS ProvisioningFastlyFastly ApplicationAPI & Configuration ManagementAPI ServicesNetwork ServicesDomain ManagementTLS Provisioning
Timeline · 2 updates
-
investigating May 10, 2026, 07:25 PM UTC
From 10 May 2026, 19:25 UTC to 10 May 2026, 22:35 UTC, we experienced an issue affecting the availability of our TLS management and Fastly DDoS Protection APIs. During this time, customers may have experienced errors and timeouts when using the TLS management API and the Fastly DDoS Protection API. Customers accessing TLS and network subscription management via manage.fastly.com were also affected. CDN delivery, stats aggregation, and all other data plane services were unaffected. The issue has been resolved and all services are operating normally.
-
resolved May 10, 2026, 10:35 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 06:38 PM UTC
- Resolved
- May 07, 2026, 01:05 AM UTC
- Duration
- 6h 27m
Affected: North AmericaNew York (TSS)PlatformNorth AmericaNew York (TSS)PlatformNorth America
Timeline · 2 updates
-
investigating May 06, 2026, 06:38 PM UTC
Traffic in New York (TSS) has been temporarily rerouted. All other locations and services are unaffected.
-
resolved May 07, 2026, 01:05 AM UTC
This event has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 04:42 AM UTC
- Resolved
- May 06, 2026, 05:59 AM UTC
- Duration
- 1h 17m
Affected: Next-Gen WAF (NGWAF)
Timeline · 4 updates
-
investigating May 06, 2026, 04:42 AM UTC
Next-Gen WAF (NGWAF) services are currently experiencing a delay in new rule propagation. Existing rules and functionality are unaffected.
-
investigating May 06, 2026, 05:38 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Next-Gen WAF (NGWAF) rule propagation. 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 06, 2026, 05:43 AM UTC
A fix has been deployed for the issue impacting Next-Gen WAF (NGWAF) new rule propagation. We are observing a gradual restoration of services, though some customers may continue to experience intermittent issues as the system stabilizes. Our team is actively monitoring the recovery and will post another update once services are fully restored.
-
resolved May 06, 2026, 05:59 AM UTC
Engineering has confirmed that Next-Gen WAF (NGWAF) new rule propagation has been fully restored. Customers may have experienced new rules not applying from 04:42 to 06:30 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: 0001-01-01 00:00:00 UTC
Read the full incident report →
- 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
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 →
