Cape Town (CPT)
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.
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.
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.
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.
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.
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
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 Platform delivery services.
Our engineers are continuing to investigate the impact to our Platform delivery services.
Our engineers have identified the contributing factor and are applying a fix to our Platform delivery services.
Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Platform delivery services.
Engineering has deployed a fix and have confirmed a gradual recovery to our Platform delivery service. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.
Engineering has confirmed that our Platform delivery services have been fully restored. Customers may have experienced elevated errors and latency. In addition, Compute customers may have also experienced delayed configuration deployments from the 5th of September at 19:48 to the 6th of September at 00:48 UTC.
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"
Traffic in Cape Town (CPT) has been temporarily rerouted.
All other locations and services are unaffected.
We're currently investigating performance impacts in Africa.
All other locations and services are unaffected.
A fix has been implemented and we are monitoring the results.
This issue has been identified as a regional 3rd party undersea cable issue. Fastly Engineers have mitigated impact.
This incident has been resolved.
We're currently investigating performance impacts in Africa.
All other locations and services are unaffected.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're currently investigating potential impact to performance with our CDN services.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're investigating elevated errors in Cape Town (CPT),Johannesburg (JNB).
All other locations and services are unaffected
A fix has been implemented and we are monitoring the results.