We are investigating performance degradation to our Bogota (BOG) 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 Bogota (BOG) POP.

All other locations and services are unaffected.

Engineering has confirmed the impact to Bogota (BOG) POP has been mitigated.

Engineering has confirmed that our Bogota (BOG) POP has been fully restored. Customers may have experienced elevated errors and latency from 20:00 to 21:50 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-19 21:33:33 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 will be adding capacity at our Bogota (BOG) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 28 January 2025 at 06:00 UTC.

Our estimated duration is 4h. 

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please verify that your origin access lists allow the full range of Fastly IP addresses (https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges). Customers with any questions or concerns should contact Fastly’s Support team (support@fastly.com).

The scheduled maintenance has been completed.

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

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.

We are investigating elevated errors to our Bogota (BOG) and Dallas (DFW) Points 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 Bogota (BOG) and Dallas (DFW) POPs. 

All other locations and services are unaffected.

Engineering has confirmed the impact to our Bogota (BOG) and Dallas (DFW) POPs has been mitigated.

Engineering has confirmed that our Bogota (BOG) and Dallas (DFW) POPs have been fully restored. Customers may have experienced backend errors and increased latency from 20:50 to 21:14 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" 

Status Post, Created Date/Time: 2025-01-15 21:16:33 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" 

We are currently investigating performance impacts to our Rio de Janeiro (GIG), Bogota (BOG), Buenos Aires (EZE), Santiago (SCL), and Sao Paulo (GRU) Point of Presence (POP).

All other locations and services are unaffected.

Our engineers have identified the contributing factor and are applying a fix to our Bogota (BOG), Buenos Aires (EZE), Rio de Janeiro (GIG), Santiago (SCL), Sao Paulo (GRU) Point of Presence (POP).

All other locations and services are unaffected.

Engineering has confirmed the impact to Bogota (BOG), Buenos Aires (EZE), Rio de Janeiro (GIG), Santiago (SCL), Sao Paulo (GRU) Point of Presence (POP) has been mitigated.

Engineering has confirmed that Bogota (BOG), Buenos Aires (EZE), Rio de Janeiro (GIG), Santiago (SCL), Sao Paulo (GRU) Point of Presence (POP) has been fully restored. Customers may have experienced increased latency and 5xxx errors from 04:22 to 05:46 UTC.

This incident is resolved.

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

We are investigating elevated errors to our Bogota (BOG) Point of Presence (POP).

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

Engineering has deployed a fix and have confirmed a gradual recovery to our Bogota (BOG) POP. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

Engineering has confirmed that our Bogota (BOG) POP has been fully restored. Customers may have experienced elevated errors and delays from 23:10 to 23:50 UTC.

This incident is resolved.

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

We are investigating elevated errors to our Bogota (BOG) Point of Presence (POP).

Engineering has confirmed the impact to Bogota (BOG) POP has been mitigated.

This event has been resolved.

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

We are investigating elevated errors in our Bogota (BOG) POP.

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

All other locations and services are unaffected.

This event has been resolved.

We are investigating elevated errors to our Bogota (BOG), Fortaleza (FOR), Lima (LIM), and Milan (LIN) Points of Presence (POPs).

Our engineers have identified the contributing factor and are applying a fix to our Milan (LIN), Bogota (BOG), Fortaleza (FOR), Lima (LIM) POPs .

Engineering has confirmed the impact to Milan (LIN), Bogota (BOG), Fortaleza (FOR), Lima (LIM) POPs has been mitigated.

Engineering has confirmed that Milan (LIN), Bogota (BOG), Fortaleza (FOR), Lima (LIM) POPs have been fully restored. Customers may have experienced latency elevated errors from 19:05 to 21:02 UTC.

This incident is resolved.