Johannesburg (JNB)
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.
We're investigating possible performance impact affecting the Amsterdam (AMS), Milan (MXP), Sofia (SOF), Fujairah (FJR), Osaka (ITM), Singapore (QPG), Tokyo (NRT), Tokyo (TYO), Los Angeles (BUR), Paris (PAR), Singapore (SIN), Amsterdam (RTM) data center.
All other locations and services are unaffected.
Our engineers are continuing to investigate confirmed periods of increased latency and elevated errors to Amsterdam (AMS), Frankfurt (FRA), London (LCY), London (LON), Marseille (MRS), Sofia (SOF), Fujairah (FJR), Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Tokyo (NRT), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Rio de Janeiro (GIG), Cape Town (CPT), Johannesburg (JNB), Los Angeles (BUR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Los Angeles (HHR), Singapore (SIN) POPs.
Our engineers believe they have identified contributing factor causing the issue impacting the Amsterdam (AMS), Frankfurt (FRA), London (LCY), London (LON), Marseille (MRS), Sofia (SOF), Fujairah (FJR), Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Tokyo (NRT), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Rio de Janeiro (GIG), Cape Town (CPT), Johannesburg (JNB), Los Angeles (BUR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Los Angeles (HHR), Singapore (SIN) POPs.
We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery.
Engineering has confirmed the impact to Amsterdam (AMS), Frankfurt (FRA), London (LCY), London (LON), Marseille (MRS), Sofia (SOF), Fujairah (FJR), Kuala Lumpur (KUL), Manila (MNL), Osaka (ITM), Tokyo (NRT), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Rio de Janeiro (GIG), Cape Town (CPT), Johannesburg (JNB), Los Angeles (BUR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Los Angeles (HHR), Singapore (SIN) POPs has been mitigated and services are fully restored.
Engineering has confirmed that all POPs have been fully restored. Customers may have experienced elevated errors from 13:35 UTC to 14:15 UTC, a duration of 40 minutes on the 11th of December 2025. This incident is resolved.
Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-12-11 14:34:14 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.
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.
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.
We are investigating elevated errors to our Johannesburg (JNB) Point of Presence (POP).
All other products and services are unaffected by this incident.
Our engineers have identified the contributing factor and are developing a fix to our Johannesburg (JNB) POP.
(All other locations and services are unaffected.)
Engineering has confirmed the impact to Johannesburg (JNB) POP has been mitigated.
This event has been resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-07-17 11:04:32 UTC
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 the Johannesburg (JNB) data center.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
We are investigating elevated errors to our Johannesburg (JNB) Point of Presence (POP).
Traffic engineering has been performed in the region to minimize possible impact while we continue to research into this incident.
Our engineers have identified a power outage that caused the impact our engineers observed in our Johannesburg (JNB) POP.
We have contacted a local Third Party Service Provider who has restored power and our engineers have begun to mitigate the POP.
Customers will continue to see their traffic rerouted to surrounding regions until the POP has been fully restored and traffic can be returned to their typical routes. All other products and services remain unaffected by this event.
Engineering has confirmed the impact to our JNB POP has been mitigated.
Our Network Engineering team will gradually return traffic as part of our standard traffic engineering best practices.
This incident has been resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-05-10 12:52:12 UTC
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 elevated errors to our Cape Town (CPT), Johannesburg (JNB) Points of Presence (POPs).
All other products and services are unaffected by this incident.
Our engineers have identified the contributing factor and are applying a fix to our Cape Town (CPT), Johannesburg (JNB) POPs.
All other locations and services are unaffected.
Engineering has confirmed the impact to our Cape Town (CPT), Johannesburg (JNB) POPs has been mitigated.
Engineering has confirmed that our Cape Town (CPT), Johannesburg (JNB) POPs have been fully restored. Customers may have experienced elevated errors and latency from 20:02 to 20:30 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-03-11 20:13:51 UTC
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 elevated errors to our Hyderabad (HYD), Manila (MNL), Bogota (BOG), Johannesburg (JNB), Singapore (SIN) POPs for Compute Services and the Fastly Application.
All other products and services are unaffected by this incident.
Our engineers have identified the contributing factor and are applying a fix to our Hyderabad (HYD), Manila (MNL), Bogota (BOG), Johannesburg (JNB), Singapore (SIN) POPs for Compute Services.
All other locations and services are unaffected.
Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Hyderabad (HYD), Manila (MNL), Bogota (BOG), Johannesburg (JNB), Singapore (SIN) POPs for Compute services.
All other locations and services are unaffected.
Engineering has deployed a fix and have confirmed a gradual recovery to our Hyderabad (HYD), Manila (MNL), Bogota (BOG), Johannesburg (JNB), Singapore (SIN) POPs and Fastly Application service. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.
After further investigation, Engineering observed impact to our Tokyo (NRT), Tokyo (TYO), and Osaka (ITM) POPs.
Engineering has confirmed that Hyderabad (HYD), Manila (MNL), Osaka (ITM), Tokyo (NRT), Tokyo (TYO), Bogota (BOG), Fastly Application, Johannesburg (JNB), Singapore (SIN) POPs and service have been fully restored. Compute customers may have experienced errors for requests that utilized geolocation as well as login issues with the Fastly Application from the 28th of January at 04:21 to 18:30 UTC.
Affected customers may have experienced impact to varying degrees and to a shorter duration than set forth above.
As the fix was deployed Engineering made additional adjustments to address impact observed to our Tokyo (NRT), Tokyo (TYO), and Osaka (ITM) POPs. Customer during this time may have experienced an increase in error rates from the 28th of January at 23:00 to the 29th of January 05:00 UTC.
Affected customers may have experienced impact to varying degrees and to a shorter duration than set forth above.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-01-28 09:30:53 UTC
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.