We're investigating possible performance impact affecting the Frankfurt (FRA), Milan (LIN), Munich (MUC) data centers.

All other locations and services are unaffected

Our engineers have identified the contributing factor and are applying a fix to our Frankfurt (FRA), Milan (LIN), Munich (MUC) POPs.

All other locations and services are unaffected.

Engineering has confirmed the impact to Frankfurt (FRA), Milan (LIN), Munich (MUC) POPs has been mitigated.

All other locations and services are unaffected.

Engineering has confirmed that Frankfurt (FRA), Milan (LIN), Munich (MUC) POPs has been fully restored. Customers may have experienced elevated errors and increased latency from 18:53 to 20:41 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 will be adding capacity at our Manchester (MAN) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 17 September 2024 at 01: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 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" 

Fastly Engineers detected a performance impacting event affecting the Frankfurt (FRA) 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 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 London (LCY), London (LHR) Points of Presence (POPs).

Our engineers have identified the contributing factor and are applying a fix to our London (LCY), London (LHR) POPs.

Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our London (LCY), London (LHR) POPs.

Engineering has confirmed the impact to our London (LCY), London (LHR) POPs has been mitigated.

Engineering has confirmed that our London (LCY), London (LHR) POPs have been fully restored. Customers may have experienced elevated errors and latency from 08:41 to 18:29 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 Paris (PAR), Paris (CDG) Points of Presence (POPs).

Our engineers have identified the contributing factor and are applying a fix to our Paris (PAR), Paris (CDG) POPs.

Engineering has confirmed the impact to Paris (PAR), Paris (CDG) POPs has been mitigated.

Engineering has confirmed that Paris (PAR), Paris (CDG) POPs have been fully restored. Customers may have experienced latency and elevated errors from 18:35 to 19:14 UTC.

This incident is resolved.

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

At approximately 08:00 UTC our engineers began to investigate a large traffic event impacting performance within our Europe and North America regions. 

Standard traffic engineering practices have been deployed in response to this event, in an effort to reduce the potential impact to our customers within the regions. Customer may continue to see elevated errors and latency as mitigation efforts continue to be deployed.

All other products and services are unaffected by this incident.

Our engineers are implementing adjusted mitigation strategies in our North America and Europe regions to continue to balance traffic and manage performance.

Error rates and latency have improved, although customers may still experience intermittent periods of performance impact as traffic engineering continues to be deployed.

Engineering has implemented mitigation strategies and has confirmed a gradual recovery in our North America and Europe regions. 

We are closely monitoring performance in these regions as a top priority as this event continues and will provide a final update once customer and end user experience has been fully restored.

Engineering has confirmed that Europe and North America regions have been fully restored. Customers may have experienced elevated errors and latency from 08:00 to 16:37 UTC.

This incident is resolved.

Affected customers would 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 will be adding capacity at our Paris (CDG) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 04 July 2024 at 03:00 UTC.

Our estimated duration is 6h. 

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).

This planned capacity expansion has been postponed and will now begin on 17 July 2024 at 03:00 UTC.

The scheduled maintenance has been completed.

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

Fastly will be adding capacity at our London (LHR) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 09 July 2024 at 23: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"