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.

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 Chennai (MAA), New Delhi (DEL), Amsterdam (AMS), Johannesburg (JNB) Points of Presence (POPs).

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.

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

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" 

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" 

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

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.

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

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" 

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

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

All other locations and services are unaffected.

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.

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

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.

Traffic in Johannesburg (JNB) has been temporarily rerouted.

All other locations and services are unaffected.

This event 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 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.