Ashburn (IAD)
Fastly will be performing scheduled maintenance on our Ashburn (IAD) data center from 25 September 2026, 03:00 UTC - 25 September 2026, 11:00 UTC.
End-users may observe connection resets as traffic is migrated onto new hardware.
The scheduled maintenance has been completed.
Fastly will be performing scheduled maintenance on our Ashburn (IAD) data center from 24 September 2026, 03:00 UTC - 24 September 2026, 11:00 UTC.
During this time frame traffic will be redirected to neighboring POPs in the region.
The scheduled maintenance has been completed.
Fastly will be adding capacity at our Ashburn (IAD) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 23 September 2026 at 04:30 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.
Fastly will be performing scheduled maintenance on our Ashburn (IAD) data center from 21 September 2026, 17:30 UTC - 23 September 2026, 17:30 UTC.
During this time frame traffic will be redirected to neighboring sites within the Ashburn (IAD) data center or from POPs within the region.
Fastly will be adding capacity at our Ashburn (IAD) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 17 September 2026 at 05: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.
Fastly will be adding capacity at our Ashburn (IAD) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 28 August 2026 at 06:00 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.
We have identified an issue that caused elevated error rates (HTTP 429/503) and timeouts for Object Storage in the Frankfurt (FRA), Ashburn (IAD) Points of Presence (POP)s.
All other products and services are unaffected by this incident.
Fastly will be adding capacity at our Ashburn (IAD) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 1st July 2026 at 04: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.
Fastly Engineers detected a performance impacting event affecting the Ashburn (IAD) data center.
We are investigating elevated errors to our Ashburn (IAD).
All other products and services are unaffected by this incident.
Engineering has confirmed the impact to Ashburn (IAD) PoP has been mitigated.
Our engineers have confirmed that traffic routing through our Ashburn (IAD) POP has been fully restored. Because a software defect caused brief node crashes, customers routing traffic through the affected nodes may have experienced a temporary increase in 5xx errors and dropped connections from 15:55 to 22:10 UTC on April 20, 2026.
This incident is resolved.
Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.