We're investigating possible performance impact affecting the Tokyo (TYO) data center.

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

Engineering has confirmed the impact to our Tokyo (TYO) POP has been mitigated.

Engineering has confirmed that Tokyo (TYO) POP has been fully restored. Customers may have experienced latency from 3:04 to 3:25 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" 

Status Post, Created Date/Time: 2025-02-12 03:31:29 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 Tokyo (TYO) 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 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 Tokyo (TYO) 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 Tokyo (TYO) Point of Presence (POP). 

All other products and services are unaffected by this incident.

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

All other locations and services are unaffected.

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

Engineering has confirmed that our Tokyo (TYO) Point of Presence (POP) has been fully restored. Customers may have experienced increased 5xx errors and latency from 3:00 to 3:40 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2024-12-18 03:37:38 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" 

Fastly Engineers detected a performance impacting event affecting the Dublin (DUB) 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 Melbourne (MEL), Seoul (ICN), Tokyo (TYO), Los Angeles (BUR) Points of Presence (POPs).

Our engineers have identified the contributing factor and are applying a fix to our Melbourne (MEL), Seoul (ICN), Tokyo (TYO), Los Angeles (BUR) POPs.

Engineering has confirmed the impact to Melbourne (MEL), Seoul (ICN), Tokyo (TYO), Los Angeles (BUR) POPs has been mitigated.

Engineering has confirmed that Melbourne (MEL), Seoul (ICN), Tokyo (TYO), Los Angeles (BUR) POPs have been fully restored. Customers may have experienced elevated errors and latency from 17:38 to 18:13 UTC.

This incident is resolved.

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

We are aware of a possible issue and are working to determine the scope and impact.

Update: Our investigations confirmed that there were no external impacts to our customer services or end user experiences. We've changed this status from "degraded performance" to "informational".

Our Engineering team had identified an internal issue that had risk for customer impact. Our Acute Incident Response teams have deployed a fix and are monitoring the results. 

Our network availability and all other locations were unaffected by this incident. Customers and their end users should not have seen impact as a result of this incident. 

This incident has been resolved.

Traffic in Tokyo (TYO) has been temporarily rerouted.

All other locations and services are unaffected.

This incident has been resolved.