Johannesburg (JNB)

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

Platform Africa Johannesburg (JNB)
 
11 May 2024, 12:59 UTC

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

 
11 May 2024, 13:49 UTC

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

All other locations and services are unaffected.

 
11 May 2024, 14:32 UTC

Our engineers have identified an additional contributing factor and are applying an adjusted mitigation strategy to Johannesburg (JNB) (POP).

All other locations and services are unaffected.

 
11 May 2024, 19:09 UTC

Engineering has confirmed the impact to Johannesburg (JNB) (POP) has been mitigated.

 
11 May 2024, 20:12 UTC

Engineering has confirmed that Johannesburg (JNB) (POP) has been fully restored. Traffic was rerouted to neighboring POPs to minimize potential impact during this incident, traffic has since been returned to Johannesburg (JNB) (POP). Customers may have observed elevated errors and degraded performance from 12:18 to 12:25 UTC. 

This incident is resolved.


Platform Africa Johannesburg (JNB)
 
01 May 2024, 12:45 UTC

Traffic in Johannesburg (JNB) has been temporarily rerouted.

All other locations and services are unaffected.

 
01 May 2024, 19:00 UTC

This event has been resolved.

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.

Platform Africa Johannesburg (JNB)
 
08 August 2023, 18:03 UTC

We're investigating possible performance impact affecting the Johannesburg (JNB) data center.

All other locations and services are unaffected

 
08 August 2023, 18:08 UTC

This incident has been resolved.

19 January 2023, 23:05 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)
 
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.