Störungsverlauf von Fastly

1. 15. Juli 2026 um 01:41 UTCupdate

   Wir untersuchen ein Problem, das eine erhöhte Latenz (High Time To First Byte (TTFB)) für unseren Singapore (SIN) Point of Presence (POP) verursacht. Unsere Ingenieure haben Schritte unternommen, um die Auswirkungen zu reduzieren und beobachten Verbesserungen, während sie den beitragenden Faktor weiter untersuchen. Wir werden ein weiteres Update bereitstellen, sobald weitere Informationen verfügbar sind oder innerhalb der nächsten Stunde. Alle anderen Produkte und Dienstleistungen sind von diesem Vorfall nicht betroffen.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 9. Juli 2026 um 01:58 UTCupdate

   This event was resolved and POP fully restored at 01:58 AM earlier today.

1. 7. Juli 2026 um 16:27 UTCupdate

   Our engineers believe they have identified contributing factor causing the issue impacting the Kolkata (CCU) 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.

1. 7. Juli 2026 um 16:17 UTCupdate

   We are investigating reports of intermittent latency and errors impacting customers served through the Kolkata (CCU) Point of Presence. Traffic has been rerouted to nearby regions while our engineers investigate. Customers may experience intermittent impact during this time as traffic stabilizes on alternate paths. Our ability to deliver network services on all other locations, and our ability to security services are not affected by this incident. We will provide another update as more information becomes available.

1. 7. Juli 2026 um 15:55 UTCupdate

   Traffic in Kolkata (CCU) has been temporarily rerouted. All other locations and services are unaffected.

1. 2. Juli 2026 um 19:28 UTCupdate

   Engineering has confirmed the impact to our Palo Alto (PAO) POP has been mitigated.

1. 2. Juli 2026 um 19:16 UTCupdate

   Our engineers believe they have identified contributing factor causing the issue impacting our Palo Alto (PAO) POP. 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.

1. 2. Juli 2026 um 18:34 UTCupdate

   We are investigating elevated errors with Compute at our Palo Alto (PAO) Point of Presence (POP). All other products and services are unaffected by this incident.

1. 30. Juni 2026 um 07:16 UTCupdate

   Traffic in Mumbai (QAI) has been temporarily rerouted. All other locations and services are unaffected.

1. 30. Juni 2026 um 02:50 UTCupdate

   Engineering has deployed a fix and have confirmed a gradual recovery to Buenos Aires (EZE) POP. We will continue to monitor until we’ve confirmed that customer experience has been fully restored. All other networks and services were unaffected by this incident.

1. 30. Juni 2026 um 02:43 UTCupdate

   Our engineers believe they have identified contributing factor causing the issue impacting the Buenos Aires (EZE) 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.

1. 30. Juni 2026 um 02:31 UTCupdate

   We're investigating possible performance impact affecting the Buenos Aires (EZE) data center. All other locations and services are unaffected.

1. 30. Juni 2026 um 01:55 UTCupdate

   Customers may have experienced elevated errors from 01:42 to 01:55 UTC. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.

1. 30. Juni 2026 um 01:50 UTCupdate

   Our engineers believe they have identified contributing factor causing the issue impacting the Next-Gen WAF (NGWAF) 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.

1. 29. Juni 2026 um 23:00 UTCupdate

   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.

1. 24. Juni 2026 um 14:53 UTCupdate

   Traffic in London (QQP) has been temporarily rerouted. All other locations and services are unaffected.

1. 18. Juni 2026 um 18:49 UTCupdate

   We have an update regarding the ongoing Informational affecting Support Ticketing System. Our provider has reported that a contributing factor has been identified and they are working on a fix. As a reminder, Fastly's core edge network and security services remain unaffected. Please continue to email [email protected] for any assistance while our standard support and CRM channels remain impacted. Updated on 18 June 2026 at 18:49 UTC

1. 18. Juni 2026 um 16:48 UTCupdate

   Our engineers have been informed that our Customer Relationship Management (CRM) provider is currently experiencing an incident. As a result, you may experience slightly delayed responses from our Support team while we implement an internal workaround and monitor this provider's incident updates. All other Fastly services remain fully operational. Our network and security products continue to deliver without disruption. We will provide an update if the situation changes.

1. 17. Juni 2026 um 18:33 UTCupdate

   Engineering has confirmed the impact to our Bogota (BOG) POP has been mitigated.

1. 17. Juni 2026 um 18:33 UTCupdate

   Engineering has confirmed the impact to our Lima (LIM) POP has been mitigated.