Dallas (DFW)
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 Engineers detected a performance impacting event affecting the Atlanta (PDK), Dallas (DFW) data centers.
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 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.
Fastly will be adding capacity at our Dallas (DFW) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 21 November 2024 at 05:00 UTC.
Our estimated duration is 13h.
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 will be adding capacity at our Dallas (DFW) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 20 November 2024 at 05:00 UTC.
Our estimated duration is 11h.
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 will be adding capacity at our Dallas (DFW) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 22 October 2024 at 03:00 UTC.
Our estimated duration is 7h.
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 will be adding capacity at our Dallas (DFW) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 11 October 2024 at 05:00 UTC.
Our estimated duration is 5h.
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 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"
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 Dallas (DFW) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 17 November 2023 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.