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.

We are investigating elevated errors to our Houston (IAH) Point of Presence (POP).

All other products and services are unaffected by this incident.

Our engineers believe they have identified the contributing factor causing the issue impacting the  Houston (IAH) 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 Houston (IAH) POP has been mitigated.

This event has been resolved.

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

Status Post, Created Date/Time: 2025-10-01 01:26:10 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 Newark (EWR) 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 Newark (EWR) POP.

All other locations and services are unaffected.

Engineering has confirmed the impact to Newark (EWR) POP has been mitigated.

Engineering has confirmed that Newark (EWR) POP has been fully restored. Customers may have experienced elevated errors from 17:30 UTC Sunday 28 September to 01:00 UTC Monday 29 September.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-09-29 01:05:16 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 performance impacting events affecting the Ashburn (IAD) 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 Miami (MIA) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 26 September 2025 at 21: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" 

As part of Fastly's ongoing global network expansion, we are announcing the addition of our new data center in New York (TSS). 

This facility will initially launch as a limited availability deployment on the 9th of September 2025, meaning not all customer traffic will be routed through this new location during this initial phase.

Our estimated duration is 4 hours, starting at 18:00 UTC on Sept-9th. 

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 [Public IP List | Fastly Documentation]. 

Customers with any questions or concerns may engage with our Support team through [Fastly Support] or by contacting your designated account management team members.

The scheduled maintenance has been completed.

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

We are investigating elevated errors to our KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs).

All other products and services are unaffected by this incident.

Our engineers have identified the contributing factor and are developing a fix for the KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs)

All other locations and services are unaffected.

Engineering has confirmed the impact to  the KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs) has been mitigated.

Engineering has confirmed that the impact to the KV Store at our Singapore (QPG), Singapore (SIN), San Jose (SJC), and Palo Alto (PAO) Points of Presence (POPs) has been fully restored. Customers may have experienced elevated errors and latency from 20:34 to 22:37 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2025-08-20 22:26:51 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 Houston (IAH) data center.

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

Traffic in Honolulu (HNL) has been temporarily rerouted.

All other locations and services are unaffected.

Traffic in Honolulu (HNL) has been temporarily rerouted.

All other locations and services are unaffected.