Fastly Outage History
Fastly is up right nowPingoru has recorded 144 incidents for Fastly: 144 in the last 12 months and 57 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 43 | 361 of 720 (50%) |
| May 2026 | 12 | 18 of 744 (2%) |
| June 2026 | 18 | 7 of 720 (1%) |
| July 2026 | 13 | 26 of 744 (4%) |
| August 2026 | 18 | 183 of 744 (25%) |
| September 2026 | 16 | 336 of 720 (47%) |
| October 2026 | 21 | 29 of 744 (4%) |
| November 2026 | 1 | 0 of 46 (0%) |
Incidents, newest first
Notice November 2, 2026 Kansas City (MCI) Rerouted Traffic 1h 45m North America, Kansas City (MCI), North America, Platform and 2 more
Started Nov 02, 2026, 08:43 AM UTC· resolved Nov 02, 2026, 10:28 AM UTC
- investigating Nov 02, 2026, 08:43 AM UTC
Traffic in Kansas City (MCI) has been temporarily rerouted. All other locations and services are unaffected.
- resolved Nov 02, 2026, 10:28 AM UTC
This event has been resolved.
Major October 31, 2026 Osaka (ITM) with Possible Impact 2h 17m Asia, Osaka (ITM), Tokyo (NRT), Platform and 1 more
Started Oct 31, 2026, 07:19 PM UTC· resolved Oct 31, 2026, 09:36 PM UTC
- investigating Oct 31, 2026, 07:19 PM UTC
We are investigating an issue causing increased errors and latency for our content delivery service in the Osaka (ITM) and Tokyo (NRT) Points of Presence (POPs). 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.
- investigating Oct 31, 2026, 09:20 PM UTC
Our engineers believe they have identified the contributing factor causing the issue impacting our content delivery service in the ITM and NRT POPs. We are now developing a fix, and we will post a new update once it has been fully implemented and we see signs of recovery. All other products and services remain unaffected by this incident.
- monitoring Oct 31, 2026, 10:18 PM UTC
The fix has been successfully deployed, and we have observed a recovery of our content delivery service in the ITM and NRT POPs. Error rates and latency have returned to nominal levels. Our team will continue to monitor the platform to ensure stability before we resolve this incident.
- monitoring Oct 31, 2026, 10:40 PM UTC
Our engineers have confirmed that our content delivery service in the ITM and NRT POPs has been fully restored. Customers may have experienced increased errors and latency from 19:19 to 21:36 UTC. Service has been fully restored. 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-10-31 20:40:55 UTC
Notice October 29, 2026 Queretaro (QRO) Rerouted Traffic 4h 53m Mexico, Queretaro (QRO), Platform, Platform
Started Oct 29, 2026, 04:01 AM UTC· resolved Oct 29, 2026, 08:54 AM UTC
- investigating Oct 29, 2026, 04:01 AM UTC
Traffic to our Queretaro (QRO) POP is being redirected to nearby POPs due to an upstream provider issue in the region. Customers should see no impact. We will update this post once QRO returns to service.
- resolved Oct 29, 2026, 08:54 AM UTC
This event has been resolved.
Major October 29, 2026 Elevated Errors & Latency for McAllen (MFE) 40m North America, North America, McAllen (MFE), Platform and 1 more
Started Oct 29, 2026, 03:10 AM UTC· resolved Oct 29, 2026, 03:50 AM UTC
- investigating Oct 29, 2026, 03:10 AM UTC
We are investigating elevated errors to our McAllen (MFE) Point of Presence (POP). All other products and services are unaffected by this incident.
- investigating Oct 29, 2026, 03:16 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the McAllen (MFE) 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.
- monitoring Oct 29, 2026, 03:34 AM UTC
Engineering has confirmed the impact to McAllen (MFE) POP has been mitigated.
- resolved Oct 29, 2026, 03:50 AM UTC
This event has been resolved.
Major October 29, 2026 Elevated Errors for Queretaro (QRO) 1h 28m Mexico, Queretaro (QRO), Platform, Platform
Started Oct 29, 2026, 02:04 AM UTC· resolved Oct 29, 2026, 03:32 AM UTC
- investigating Oct 29, 2026, 02:04 AM UTC
We are investigating elevated errors to our Queretaro (QRO) Point of Presence (POP). All other products and services are unaffected by this incident.
- investigating Oct 29, 2026, 02:16 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Queretaro (QRO) 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.
- monitoring Oct 29, 2026, 03:21 AM UTC
Engineering has confirmed the impact to Queretaro (QRO) POP has been mitigated.
- resolved Oct 29, 2026, 03:32 AM UTC
During this incident, customers may have experienced elevated errors and increased latency for requests served through our Queretaro (QRO) POP from 28 October 2026, 23:21 UTC to 29 October 2026, 08:54 UTC. This incident is resolved. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.
Notice October 28, 2026 New York (TSS) Rerouted Traffic 2h 6m North America, New York (TSS), North America, Platform and 1 more
Started Oct 28, 2026, 05:02 AM UTC· resolved Oct 28, 2026, 07:08 AM UTC
- investigating Oct 28, 2026, 05:02 AM UTC
Traffic in New York (TSS) has been temporarily rerouted. All other locations and services are unaffected.
- resolved Oct 28, 2026, 07:08 AM UTC
This event has been resolved.
Major October 27, 2026 Elevated Errors for Compute, Next-Gen WAF (NGWAF) 1h 37m Fanout, Fastly Compute, Config Store, KV Store and 5 more
Started Oct 27, 2026, 11:05 PM UTC· resolved Oct 28, 2026, 12:42 AM UTC
- investigating Oct 27, 2026, 11:05 PM UTC
We are investigating elevated errors to our Compute, Next-Gen WAF (NGWAF) Services
- investigating Oct 28, 2026, 12:34 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Compute, Next-Gen WAF (NGWAF) Services. 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 Oct 28, 2026, 12:35 AM UTC
Engineering has confirmed the impact to Compute, Next-Gen WAF (NGWAF) Services has been mitigated.
- resolved Oct 28, 2026, 12:42 AM UTC
Engineering has confirmed that Compute, Next-Gen WAF (NGWAF) Services has been fully restored. Customers may have experienced intermittent 5xx errors from 23:05 UTC on October 27 to 00:23 UTC on October 28. Service has been fully restored. 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-10-28 00:15:23 UTC
Major October 27, 2026 Cape Town (CPT), Johannesburg (JNB) with Possible Impact 4h 19m Africa, Cape Town (CPT), Johannesburg (JNB), Platform and 1 more
Started Oct 27, 2026, 01:55 PM UTC· resolved Oct 27, 2026, 06:14 PM UTC
- investigating Oct 27, 2026, 01:55 PM UTC
We are investigating an issue causing errors and increased latency for our network services in the Johannesburg (JNB) Point of Presence (POP). Please note that customers in the Cape Town (CPT) POP were temporarily impacted by this issue between 14:35 and 14:54 UTC; however, services in CPT have since fully recovered. 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.
- investigating Oct 27, 2026, 04:09 PM UTC
Our engineers have identified the contributing factor causing the issue impacting our network services in the Johannesburg (JNB) Point of Presence (POP). Our engineers are now developing a fix, and we will post a new update once it has been fully implemented and we see signs of recovery. Customers in the Cape Town (CPT) POP were temporarily impacted between 14:35 and 14:54 UTC. Services in CPT have since fully recovered. All other products and services remain unaffected by this incident.
- monitoring Oct 27, 2026, 05:28 PM UTC
Our engineers have taken steps to recover the affected systems in the Johannesburg (JNB) Point of Presence (POP) and are gradually returning traffic to the site. We are observing a gradual restoration of services, though some customers may continue to experience intermittent issues as the system stabilizes. Customers in the Cape Town (CPT) POP were temporarily impacted between 14:35 and 14:54 UTC. Services in CPT have since fully recovered. Our team is actively monitoring the recovery and will post another update once services are fully restored.
- resolved Oct 27, 2026, 06:54 PM UTC
Our engineers have confirmed that our network services in the Johannesburg (JNB) Point of Presence (POP) have been fully restored. Customers may have experienced errors and increased latency from 13:55 to 17:31 UTC on October 27, 2026. Customers in the Cape Town (CPT) POP were temporarily impacted between 14:35 and 14:54 UTC. Service has been fully restored. Affected customers may have experienced impact to varying degrees and for a shorter duration than stated 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-10-27 15:48:36 UTC
Major October 26, 2026 Content Delivery (CDN) with Possible Impact 2h 21m Streaming, On-the-fly Packager
Started Oct 26, 2026, 04:36 PM UTC· resolved Oct 26, 2026, 06:57 PM UTC
- investigating Oct 26, 2026, 04:36 PM UTC
We are investigating an issue causing 503 errors for customers using On-the-Fly Packaging (OTFP). 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.
- investigating Oct 26, 2026, 06:51 PM UTC
Our engineers believe they have identified the contributing factor causing the issue impacting On-the-Fly Packaging (OTFP). Our engineers are now developing a fix, and we will post a new update once it has been fully implemented and we see signs of recovery. All other products and services remain unaffected by this incident.
- monitoring Oct 26, 2026, 07:05 PM UTC
The fix has been successfully deployed, and we have observed a recovery of On-the-Fly Packaging (OTFP). Error rates and latency have returned to nominal levels. Our team will continue to monitor the platform to ensure stability before we resolve this incident.
- resolved Oct 26, 2026, 07:13 PM UTC
Our engineers have confirmed that On-the-Fly Packaging (OTFP) has been fully restored. Customers may have experienced 503 errors from 16:36 to 18:57 UTC on October 26, 2026. This incident is resolved. Affected customers may have experienced impact to varying degrees and for a shorter duration than stated 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-10-26 18:28:01 UTC
Notice October 22, 2026 Retrospective: Impacted Performance in Mumbai (BOM) 4h 30m Mumbai (BOM), India, Platform, Platform
Started Oct 22, 2026, 07:00 AM UTC· resolved Oct 22, 2026, 11:30 AM UTC
- investigating Oct 22, 2026, 07:00 AM UTC
Fastly Engineers detected a performance impacting event affecting the Mumbai (BOM) data center from 07:00 to 11:00 UTC on October 22, 2026. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
- resolved Oct 22, 2026, 11:30 AM UTC
This event has been resolved.
Notice October 21, 2026 Retrospective: Impacted Performance in Auckland (AKL) 2h Australia / New Zealand, Auckland (AKL), Platform, Platform
Started Oct 21, 2026, 10:20 AM UTC· resolved Oct 21, 2026, 12:20 PM UTC
- investigating Oct 21, 2026, 10:20 AM UTC
Fastly Engineers detected a performance impacting event affecting the Auckland (AKL) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
- resolved Oct 21, 2026, 12:20 PM UTC
During this incident, customers may have experienced elevated errors from 10:20 to 12:20 UTC. This incident is resolved. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.
Notice October 20, 2026 Amsterdam (RTM) Rerouted Traffic 1h 39m Amsterdam (RTM), Platform, Europe, Platform and 1 more
Started Oct 20, 2026, 10:28 PM UTC· resolved Oct 21, 2026, 12:07 AM UTC
- investigating Oct 20, 2026, 10:28 PM UTC
Traffic in Amsterdam (RTM) has been temporarily rerouted. All other locations and services are unaffected.
- resolved Oct 21, 2026, 12:07 AM UTC
This incident has been resolved.
Notice October 20, 2026 Retrospective: Impacted Performance in Curitiba (CWB) 31m South America, Curitiba (CWB), Platform, Platform
Started Oct 20, 2026, 01:33 PM UTC· resolved Oct 20, 2026, 02:04 PM UTC
- investigating Oct 20, 2026, 01:33 PM UTC
Fastly Engineers detected a performance impacting event affecting the Curitiba (CWB) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
- resolved Oct 20, 2026, 02:04 PM UTC
This incident has been resolved.
Major October 13, 2026 Elevated Errors for Singapore (QPG) 1h 36m Asia, Singapore (QPG), Platform, Platform
Started Oct 13, 2026, 02:50 AM UTC· resolved Oct 13, 2026, 04:26 AM UTC
- investigating Oct 13, 2026, 02:50 AM UTC
We are investigating elevated errors to our Singapore (QPG) Point of Presence (POP). All other products and services are unaffected by this incident.
- investigating Oct 13, 2026, 04:05 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Singapore (QPG) 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 Oct 13, 2026, 04:06 AM UTC
Engineering has confirmed the impact to Singapore (QPG) POP has been mitigated.
- resolved Oct 13, 2026, 04:26 AM UTC
Engineering has confirmed that Singapore (QPG) POP has been fully restored. Customers may have experienced elevated errors from 2:50 to 3:53 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-10-13 03:46:16 UTC
Notice October 10, 2026 Retrospective: Impacted Performance in Cape Town (CPT) 45m Africa, Cape Town (CPT), Platform, Platform
Started Oct 10, 2026, 03:12 AM UTC· resolved Oct 10, 2026, 03:57 AM UTC
- investigating Oct 10, 2026, 03:12 AM UTC
Fastly Engineers detected a performance impacting event affecting the Cape Town (CPT) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
- resolved Oct 10, 2026, 03:57 AM UTC
During this incident, customers may have experienced elevated errors from 03:12 to 03:57 UTC. This incident is resolved. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.
Notice October 8, 2026 Shielding Migration: Milan (MXP) to Milan (BGY) 12d 1h Platform, Europe, Platform, Europe and 4 more
Started Oct 08, 2026, 12:10 AM UTC· resolved Oct 20, 2026, 01:17 AM UTC
- investigating Oct 08, 2026, 12:10 AM UTC
Our engineers are conducting scheduled maintenance to decommission the Milan (MXP) POP. This update will help to consolidate our network footprint in the Italy region. To learn more about shielding concepts, please read: https://www.fastly.com/documentation/guides/getting-started/hosts/shielding/ What’s changing? Beginning October 26, 2026, and concluding by November 2, 2026, Fastly will gradually redirect shield traffic for the mxp-milan-it shield location to our Milan (BGY) POP. Services that use mxp-milan-it will continue to reference it, and the redirect will happen automatically. What’s next? What do I have to do? No action is required. You may update your service configuration to select the new shield location (bgy-milan-it) if you do not want Fastly to automatically transition your shielded content. If you elect to change your shield selection, your origin servers may experience a temporary increase in request volume while the cache re-establishes in BGY. If you have any questions or concerns, please contact our Support team through https://support.fastly.com or your account team.
- resolved Oct 20, 2026, 01:17 AM UTC
We’ve identified an additional required action for customers using shielding in Compute services. We’ll be sharing a new status post with updated instructions. Varnish Configuration Language (VCL) services using standard shielding configurations remain unaffected and no action is required.
Notice October 7, 2026 Sambalpur (QAK) Rerouted Traffic 2d 1h Sambalpur (QAK), India, Platform
Started Oct 07, 2026, 10:08 PM UTC· resolved Oct 09, 2026, 11:30 PM UTC
- investigating Oct 07, 2026, 10:08 PM UTC
Traffic in Sambalpur (QAK) has been temporarily rerouted. All other locations and services are unaffected.
- resolved Oct 09, 2026, 11:30 PM UTC
This event has been resolved.
Notice October 7, 2026 Delhi (QAG) Rerouted Traffic 7d 23h Delhi (QAG), Platform, Platform, India and 16 more
Started Oct 07, 2026, 10:05 PM UTC· resolved Oct 15, 2026, 09:41 PM UTC
- investigating Oct 07, 2026, 10:05 PM UTC
Traffic in Delhi (QAG) has been temporarily rerouted. All other locations and services are unaffected.
- resolved Oct 15, 2026, 09:41 PM UTC
This incident has been resolved.
Major October 6, 2026 Elevated Errors for API & Configuration Management 23m Fastly Control Panel, API & Configuration Management, API Services, Configuration Management Services and 32 more
Started Oct 06, 2026, 12:12 AM UTC· resolved Oct 06, 2026, 12:35 AM UTC
- investigating Oct 06, 2026, 12:35 AM UTC
We are investigating elevated errors and latency to our API & Configuration Management All other products and services are unaffected by this incident.
- investigating Oct 06, 2026, 12:42 AM UTC
Our engineers believe they have identified contributing factor causing the issue impacting the API & Configuration Management 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 Oct 06, 2026, 12:44 AM UTC
Engineering have confirmed a gradual recovery to API & Configuration Management. We will continue to monitor until we’ve confirmed that customer and end user experience has been fully restored.
- monitoring Oct 06, 2026, 12:44 AM UTC
Engineering have confirmed a gradual recovery to API & Configuration Management . We will continue to monitor until we’ve confirmed that customer and end user experience has been fully restored.
Major September 30, 2026 Elevated Errors for Object Storage 15h 17m Object Storage, Network Services, Object Storage, Network Services and 1 more
Started Sep 30, 2026, 11:00 PM UTC· resolved Oct 01, 2026, 02:17 PM UTC
- investigating Sep 30, 2026, 11:00 PM UTC
We are investigating an issue causing intermittent failures when uploading objects to Fastly Object Storage in the EU-Central region. 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.
- investigating Oct 01, 2026, 07:55 AM UTC
Our engineers believe they have identified the contributing factor causing the issue impacting Fastly Object Storage. Our engineers are now developing a fix, and we will post a new update once it has been fully implemented and we see signs of recovery. All other products and services remain unaffected by this incident.
- monitoring Oct 01, 2026, 01:45 PM UTC
Engineering has confirmed the impact to Object Storage (EU-Central) has been mitigated. Our team will continue to monitor the platform to ensure stability before we resolve this incident.
- resolved Oct 01, 2026, 02:17 PM UTC
Our engineers have confirmed that Object Storage uploads (EU-Central) have been fully restored. Customers may have experienced upload failures and elevated latency from approximately 23:00 UTC on September 30 to 12:26 UTC on October 1. Service has been fully restored. 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-10-01 10:01:48 UTC
Notice September 22, 2026 Announcing General Availability of Controlled Support Access (CSA) 37d Fastly, Customer Services, Fastly, Fastly and 38 more
Started Sep 22, 2026, 03:02 PM UTC· resolved Oct 29, 2026, 03:07 PM UTC
- investigating Sep 22, 2026, 03:02 PM UTC
Fastly is announcing General Availability on September 29, 2026 of Controlled Support Access (CSA). CSA gives customers more control and visibility over Fastly employee access by requiring customer approval for Fastly write/enforcing access. Approved access is time-bound, auditable, and customer-revocable. Read-only troubleshooting remains available so Fastly can continue diagnosing issues efficiently. CSA is default OFF at General Availability (GA). Customers who want to enable CSA can opt in directly from the Fastly Control Panel. What’s Changing? To learn more, see the Controlled support access documentation. The documentation explains standard CSA requests/grants, customer approval and revocation, audit visibility, and Breakglass emergency access. What’s next? What do I have to do? CSA is disabled by default at GA, meaning no action is required unless you wish to use it. Superusers can enable the feature directly within the Fastly Control Panel. 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.
Notice September 17, 2026 Retrospective: Impacted Performance in Miami (MIA) 4m North America, Miami (MIA), Platform, North America and 15 more
Started Sep 17, 2026, 07:43 PM UTC· resolved Sep 17, 2026, 07:47 PM UTC
- investigating Sep 17, 2026, 07:43 PM UTC
Fastly Engineers detected a performance impacting event affecting the Miami (MIA) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
- resolved Sep 17, 2026, 07:47 PM UTC
During this incident, customers may have experienced elevated errors from 19:43 to 19:47 UTC. This incident is resolved. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.
Major September 16, 2026 Elevated Errors for Support Ticketing System 9h 23m Customer Services, Support Systems, https://support.fastly.com, Chatbot Feature and 35 more
Started Sep 16, 2026, 07:50 AM UTC· resolved Sep 16, 2026, 05:13 PM UTC
- investigating Sep 16, 2026, 07:50 AM UTC
We are investigating an issue caused by a third-party service provider, which is affecting availability of the Support Portal, including the ability to view or create support tickets. Our engineers are actively monitoring the situation and working with the provider to diagnose and resolve the issue. We will provide another update as more information becomes available or within the next hour.
- investigating Sep 16, 2026, 10:35 AM UTC
Our engineers are continuing to investigate the issue impacting the Support Portal, including the ability to view or create support tickets. This has been caused by a third-party service provider outage. We have not yet confirmed the contributing factor has been fully resolved. We'll provide another update as soon as we have more information.
- investigating Sep 16, 2026, 01:00 PM UTC
A fix has been validated by our third-party service provider and is currently being rolled out across all impacted systems. We will post a new update once it has been fully implemented and we see signs of recovery. All other products and services remain unaffected by this incident.
- resolved Sep 16, 2026, 05:13 PM UTC
The third party provider issue affecting availability of the Support Portal has been fully resolved. All Fastly Customer Support services systems have been restored and are operating normally. Ticket processing and standard communication channels are fully functional. We apologize for the inconvenience and appreciate your patience during this interruption to our support channels.
Notice September 15, 2026 Retrospective: Impacted Performance in API Services 7m Fastly Control Panel, API & Configuration Management, API Services, Fastly and 17 more
Started Sep 15, 2026, 06:40 PM UTC· resolved Sep 15, 2026, 06:47 PM UTC
- investigating Sep 15, 2026, 06:40 PM UTC
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.
- resolved Sep 15, 2026, 06:47 PM UTC
During this incident, customers may have experienced elevated errors and increased latency for api.fastly.com from 18:40 to 18:47 UTC. This incident is resolved. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.
Notice September 15, 2026 Retrospective: Impacted Performance in Johannesburg (JNB) 10m Africa, Johannesburg (JNB), Platform, Platform and 11 more
Started Sep 15, 2026, 11:25 AM UTC· resolved Sep 15, 2026, 11:35 AM UTC
- investigating Sep 15, 2026, 11:25 AM UTC
Fastly Engineers detected a performance impacting event affecting the Johannesburg (JNB) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
- resolved Sep 15, 2026, 11:35 AM UTC
During this incident, customers may have experienced elevated 5xx errors and connection resets from 11:25 to 11:35 UTC. This incident is resolved. For more information about this retrospective status post, please reach out to Support through https://support.fastly.com.