We're investigating possible performance impact affecting the Frankfurt (FRA) data center.

All other locations and services are unaffected.

Our engineers believe they have identified contributing factor causing the issue impacting the Frankfurt (FRA) status page component.

We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery.

All other products and services are unaffected by this incident.

Engineering has confirmed the impact to Frankfurt (FRA) POP has been mitigated.

Engineering has confirmed that Frankfurt (FRA) POP has been fully restored. Customers may have experienced an increase in latency on Time to First Byte (TTFB) metrics from 14:13 to 17:27 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-10-17 14:51:01 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 Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), and Amsterdam (RTM) Points of Presence (POPs).

All other products and services are unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting our  Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), and Amsterdam (RTM) POPs .

We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery.

All other products and services are unaffected by this incident.

Our engineers have identified an additional  contributing factor and are developing an adjusted mitigation strategy to our Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), and Amsterdam (RTM) POPs.

All other locations and services are unaffected.

Engineering has deployed a fix and have confirmed a gradual recovery to our Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), and Amsterdam (RTM) POPs.  We will continue to monitor until we’ve confirmed that the customer  experience has been fully restored.

All other locations and services are unaffected.

Engineering has confirmed that our Brussels (BRU), Frankfurt (FRA), Chicago (CHI), Dallas (DFW), and Amsterdam (RTM) POPs have been fully restored. Customers may have experienced increased latency or elevated timeout errors from 11:30 on the 10th of October 2025 to 00:30 on the 11th of October 2025 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-10-10 21:10:07 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 30 September 2025 at 23:30 UTC.

Our estimated duration is 2h. 

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 at https://support.fastly.com.

The scheduled maintenance has been completed.

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

We're currently investigating performance impacts in Europe.

All other locations and services are unaffected.

Our engineers have identified the contributing factor and are developing a fix to our Europe POPs.

All other locations and services are unaffected.

Engineering has confirmed the impact to Europe POPs has been mitigated.

Engineering has confirmed that Europe POPs has been fully restored. Customers may have experienced latency from 17:08 to 18:00 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-09-15 17:35:41 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 Frankfurt (FRA) data center.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Fastly will be adding capacity at our Sofia (SOF) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 10 September 2025 at 01:30 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 at https://support.fastly.com.

The scheduled maintenance has been completed.

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

Fastly will be adding capacity at our Paris (PAR) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 19 August 2025 at 17:30 UTC.

Our estimated duration is 11h 30m. 

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 at https://support.fastly.com.

The scheduled maintenance has been completed.

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

Fastly engineers identified and resolved an unusual traffic event affecting our Munich (MUC) and Frankfurt (FRA) Points of Presence (POPs).

From 12:36 to 12:48 UTC (approximately 12 minutes), customers using compute services within the MUC and FRA POPs may have experienced elevated 503 error responses and increased latency during the impact window.

Our engineers responded with standard incident response best practices, and all impacted compute services should now be fully restored for our customers.

Fastly will be adding capacity at our Dublin (DUB) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 30 July 2025 at 00: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 at https://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 Brussels (BRU) Point of Presence (POP).

All other products and services are unaffected by this incident.

Our engineers have identified the contributing factor and are developing a fix to our Brussels (BRU) POP.

All other locations and services are unaffected.

Engineering has confirmed the impact to our Brussels (BRU) POP has been mitigated.

Engineering has confirmed that our Brussels (BRU) POP has been fully restored. Customers may have experienced request timeouts to the KV store within Fastly's Compute service, and increased cache misses from the 23rd of June at 12:30 to the 27th of June at 18:12 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-06-27 16:33:20 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.