Fastly will be adding capacity at our Frankfurt (FRA) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 15 January 2025 at 02:00 UTC.

Our estimated duration is 3h. 

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

We are investigating elevated errors to our Munich (MUC) 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 Munich (MUC) Point of Presence (POP). 

All other locations and services are unaffected.

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

Engineering has confirmed that our Munich (MUC) Point of Presence (POP) has been fully restored. Customers may have experienced 503 errors from 7:58 to 8:51 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2024-12-16 08:47:00 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 Frankfurt (FRA) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 11 December 2024 at 02: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" 

Fastly Engineers detected a performance impacting event affecting the Munich (MUC) data center. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

This incident has been resolved.

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

We are investigating elevated errors to our London (LCY) and London (LHR) POPs for Compute.

All other products and services are unaffected by this incident.

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

All other products and services are unaffected by this incident.

Engineering has confirmed that London (LCY), London (LHR) POPs has been fully restored. Customers may have experienced latency for Compute from 15:34 to 19:02 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2024-11-14 18:02: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.

Fastly is currently performing extended maintenance on our Milan (LIN) data center from 07 November 2024, 10:34 UTC - 07 November 2024, 13:00 UTC.

During this time frame traffic will remain redirected to neighboring POPs in the region. 

The extended maintenance has been completed.

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

Fastly will be performing scheduled maintenance on our Milan (LIN) data center from 06 November 2024, 23:00 UTC - 07 November 2024, 05:30 UTC.

During this time frame traffic will be redirected to neighboring POPs in the region.

The scheduled maintenance has been completed.

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

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"