Africa

17 December 2024, 16:52 UTC
Platform Africa Ghana (ACC)
 
17 December 2024, 16:52 UTC

Traffic in Ghana (ACC) has been temporarily rerouted.

All other locations and services are unaffected.

17 December 2024, 09:43 UTC
Platform Africa Ghana (ACC)
 
17 December 2024, 09:43 UTC

Traffic in Ghana (ACC) has been temporarily rerouted.

All other locations and services are unaffected.

12 December 2024, 06:50 UTC
Platform Africa Ghana (ACC)
 
12 December 2024, 06:50 UTC

Traffic in Ghana (ACC) has been temporarily rerouted.

All other locations and services are unaffected.

02 December 2024, 14:16 UTC
Platform Africa Ghana (ACC)
 
02 December 2024, 14:16 UTC

Traffic in Ghana (ACC) has been temporarily rerouted.

All other locations and services are unaffected.

22 November 2024, 16:54 UTC
Platform Africa Ghana (ACC)
 
22 November 2024, 16:54 UTC

Traffic in Ghana (ACC) has been temporarily rerouted.

All other locations and services are unaffected.

16 November 2024, 05:20 UTC
Platform Africa Ghana (ACC)
 
16 November 2024, 05:20 UTC

Traffic in Ghana (ACC) has been temporarily rerouted.

All other locations and services are unaffected.

Platform Africa Johannesburg (JNB)
 
22 September 2024, 15:35 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.

Platform Europe Asia Africa Amsterdam (AMS) Chennai (MAA) Johannesburg (JNB) New Delhi (DEL)
 
16 September 2024, 17:10 UTC

We are investigating elevated errors to our Chennai (MAA), New Delhi (DEL), Amsterdam (AMS), Johannesburg (JNB) Points of Presence (POPs).

 
16 September 2024, 18:26 UTC

Our engineers have identified the contributing factor and are applying a fix to our Amsterdam (AMS) Point of Presence (POP).

Fastly's Engineering team has confirmed that the impact has been mitigated for our Chennai (MAA), New Delhi (DEL), and Johannesburg (JNB) POPs.

 
16 September 2024, 18:43 UTC

Engineering has confirmed the impact to our Amsterdam (AMS) Point of Presence (POP) has been mitigated.

 
16 September 2024, 19:09 UTC

Engineering has confirmed that our Chennai (MAA), New Delhi (DEL), Amsterdam (AMS), and Johannesburg (JNB) Points of Presence (POPs) have been fully restored. Customers may have experienced an increase in errors and latency from 17:10 to 18:45 UTC.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

This incident is resolved.

To offer feedback on our status page, click "Give Feedback

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

Platform Africa Johannesburg (JNB)
 
23 August 2024, 15:58 UTC

We are investigating elevated errors to our Johannesburg (JNB) Point of Presence (POP).

 
23 August 2024, 16:40 UTC

Our engineers have identified the contributing factor and are applying a fix our Johannesburg (JNB) Point of Presence (POP). 

All other locations and services are unaffected.

 
23 August 2024, 16:58 UTC

Engineering has confirmed the impact to our Johannesburg (JNB) Point of Presence (POP) has been mitigated.

 
23 August 2024, 17:08 UTC

Engineering has confirmed that our Johannesburg (JNB) Point of Presence (POP) has been fully restored. Customers may have experienced increased latency and 5xx errors from 15:58 to 16:37 UTC.

This incident is resolved.

To offer feedback on our status page, click "Give Feedback