Cape Town (CPT)

Platform Africa Cape Town (CPT) Johannesburg (JNB)
 
27 October 2026, 13:55 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.

 
27 October 2026, 16:09 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.

 
27 October 2026, 17:28 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.



 
27 October 2026, 18:54 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  

Platform Africa Cape Town (CPT)
 
10 October 2026, 03:12 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.

Platform North America Europe Asia South America Africa Amsterdam (AMS) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Buenos Aires (EZE) Johannesburg (JNB) Fujairah (FJR) Fortaleza (FOR) Rio de Janeiro (GIG) Frankfurt (FRA) Kuala Lumpur (KUL) Manila (MNL) Sao Paulo (GRU) Osaka (ITM) London (LCY) London (LON) Singapore (SIN) Marseille (MRS) Tokyo (NRT) Los Angeles (HHR) Los Angeles (BUR) Los Angeles (LAX) Paris (PAR) Sofia (SOF)
 
11 December 2025, 13:35 UTC

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.

 
11 December 2025, 14:39 UTC

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.

 
11 December 2025, 14:41 UTC

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. 

 
11 December 2025, 15:23 UTC

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.

 
11 December 2025, 15:35 UTC

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 


Platform Africa Cape Town (CPT) Johannesburg (JNB)
 
11 March 2025, 20:02 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.


 
11 March 2025, 20:25 UTC

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.

 
11 March 2025, 20:30 UTC

Engineering has confirmed the impact to our Cape Town (CPT), Johannesburg (JNB) POPs has been mitigated.

 
11 March 2025, 20:46 UTC

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.


05 September 2024, 19:48 UTC
Platform North America Europe Asia Australia / New Zealand South America Africa Amsterdam (AMS) Adelaide (ADL) Seoul (ICN) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Auckland (AKL) Ghana (ACC) Ashburn (IAD) Dubai (FJR) Brisbane (BNE) Dubai (DXB) Buenos Aires (EZE) Johannesburg (JNB) Brussels (BRU) Christchurch (CHC) Fujairah (FJR) Curitiba (CWB) Copenhagen (CPH) Hong Kong (HKG) Melbourne (MEL) Fortaleza (FOR) Dublin (DUB) Perth (PER) Lima (LIM) Atlanta (PDK) Sydney (SYD) Rio de Janeiro (GIG) Boston (BOS) Frankfurt (FRA) Kuala Lumpur (KUL) Santiago (SCL) Calgary (YYC) Wellington (WLG) Chicago (CHI) Helsinki (HEL) Manila (MNL) Sao Paulo (GRU) Osaka (ITM) London (LCY) London (LHR) London (LON) Chicago (ORD) Chennai (MAA) Singapore (QPG) Columbus (CMH) Lisbon (LIS) Madrid (MAD) Dallas (DFW) Denver (DEN) Manchester (MAN) Detroit (DTW) Marseille (MRS) Tokyo (NRT) Tokyo (TYO) Honolulu (HNL) Hyderabad (HYD) Milan (LIN) Houston (IAH) Milan (MXP) Oslo (OSL) Kansas City (MCI) Munich (MUC) Los Angeles (BUR) Los Angeles (LAX) Paris (PAR) Rome (FCO) Kolkata (CCU) Sofia (SOF) Stockholm (BMA) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Vienna (VIE) Montreal (YUL) Newark (EWR) Mumbai (BOM) New York (LGA) New York (NYC) Palo Alto (PAO) New Delhi (DEL) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
05 September 2024, 19:48 UTC

We are investigating elevated errors to our Platform delivery services.

 
05 September 2024, 21:44 UTC

Our engineers are continuing to investigate the impact to our Platform delivery services.

 
05 September 2024, 22:01 UTC

Our engineers have identified the contributing factor and are applying a fix to our Platform delivery services.

 
05 September 2024, 23:00 UTC

Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Platform delivery services.

 
05 September 2024, 23:34 UTC

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.

 
06 September 2024, 00:48 UTC

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" 

14 March 2024, 14:35 UTC
Platform Africa Cape Town (CPT)
 
14 March 2024, 14:35 UTC

Traffic in Cape Town (CPT) has been temporarily rerouted.

All other locations and services are unaffected.

18 August 2023, 08:01 UTC
Platform Africa Cape Town (CPT) Ghana (ACC) Johannesburg (JNB)
 
18 August 2023, 08:01 UTC

We're currently investigating performance impacts in Africa.

All other locations and services are unaffected.

 
18 August 2023, 10:06 UTC

A fix has been implemented and we are monitoring the results.

 
18 August 2023, 11:04 UTC

This issue has been identified as a regional 3rd party undersea cable issue. Fastly Engineers have mitigated impact.

This incident has been resolved.

15 August 2023, 10:10 UTC
Platform Africa Cape Town (CPT) Ghana (ACC) Johannesburg (JNB)
 
15 August 2023, 10:10 UTC

We're currently investigating performance impacts in Africa.

All other locations and services are unaffected.

 
15 August 2023, 13:18 UTC
This issue has been identified as a regional 3rd party undersea cable issue. Fastly Engineers are continuing efforts to mitigate impact where possible.
 
15 August 2023, 15:25 UTC

A fix has been implemented and we are monitoring the results.

 
15 August 2023, 16:14 UTC

This incident has been resolved.

19 January 2023, 23:05 UTC
Platform North America Europe Asia Australia / New Zealand South America Africa Amsterdam (AMS) Adelaide (ADL) Seoul (ICN) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Auckland (AKL) Ghana (ACC) Ashburn (IAD) Dubai (FJR) Brisbane (BNE) Dubai (DXB) Buenos Aires (EZE) Johannesburg (JNB) Brussels (BRU) Christchurch (CHC) Fujairah (FJR) Curitiba (CWB) Copenhagen (CPH) Hong Kong (HKG) Melbourne (MEL) Fortaleza (FOR) Dublin (DUB) Perth (PER) Lima (LIM) Atlanta (PDK) Sydney (SYD) Rio de Janeiro (GIG) Boston (BOS) Frankfurt (FRA) Kuala Lumpur (KUL) Santiago (SCL) Calgary (YYC) Wellington (WLG) Chicago (CHI) Helsinki (HEL) Manila (MNL) Sao Paulo (GRU) Osaka (ITM) London (LCY) London (LHR) London (LON) Chicago (ORD) Chennai (MAA) Singapore (QPG) Columbus (CMH) Lisbon (LIS) Madrid (MAD) Dallas (DFW) Denver (DEN) Manchester (MAN) Detroit (DTW) Marseille (MRS) Tokyo (NRT) Tokyo (TYO) Honolulu (HNL) Hyderabad (HYD) Milan (LIN) Houston (IAH) Milan (MXP) Oslo (OSL) Kansas City (MCI) Munich (MUC) Los Angeles (BUR) Los Angeles (LAX) Paris (PAR) Rome (FCO) Kolkata (CCU) Sofia (SOF) Stockholm (BMA) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Vienna (VIE) Montreal (YUL) Newark (EWR) Mumbai (BOM) New York (LGA) New York (NYC) Palo Alto (PAO) New Delhi (DEL) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
19 January 2023, 23:05 UTC

We're currently investigating potential impact to performance with our CDN services.

 
19 January 2023, 23:06 UTC

A fix has been implemented and we are monitoring the results.

 
19 January 2023, 23:48 UTC
On the 19th of January at 23:00 UTC a configuration change was deployed which impacted performance to global CDN delivery. Fastly Engineering reverted the change resulting in immediate recovery at 23:06 UTC. Fastly's Customer Incident Response team is currently preparing a Fastly Service Advisory of today's incident, and will be made available to Fastly Customers.
 
20 January 2023, 00:48 UTC

This incident has been resolved.

Platform Africa Cape Town (CPT) Johannesburg (JNB)
 
14 November 2022, 17:52 UTC

We're investigating elevated errors in Cape Town (CPT),Johannesburg (JNB).

All other locations and services are unaffected

 
14 November 2022, 17:59 UTC

A fix has been implemented and we are monitoring the results.