Fastly’s network has built-in redundancies and automatic failover routing to ensure optimal performance and uptime. But when a network issue does arise, we think our customers deserve clear, transparent communication so they can maintain trust in our service and our team. Notices will be posted here when we re-route traffic, upgrade hardware, or in the extremely rare case our network isn’t serving traffic. If you are experiencing issues and do not see a notice posted, please email support@fastly.com for assistance.

Metro Expansion: Seattle (BFI)
Scheduled Maintenance Report for Fastly
Update
Please be advised that the time of this maintenance event has been extended until October 7th, 08:00 UTC.
Posted Sep 28, 2022 - 19:46 UTC
Update
Scheduled maintenance is still in progress. We will provide updates as necessary.
Posted Sep 28, 2022 - 19:05 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Sep 28, 2022 - 08:00 UTC
Update
Please be advised that the time of this maintenance event has changed from September 15th, 08:00 UTC to September 28th, 08:00 UTC.
Posted Sep 09, 2022 - 22:25 UTC
Update
Please be advised that the time of this maintenance event has changed from August 26th, 08:00 UTC to September 15th, 08:00 UTC.
Posted Jul 22, 2022 - 16:11 UTC
Update
Please be advised that the time of this maintenance event has changed from August 4th, 08:00 UTC to August 26th, 08:00 UTC.
Posted Jul 20, 2022 - 22:19 UTC
Scheduled
Fastly will be expanding Seattle into a Metro POP. End-users may observe connection resets as traffic is migrated onto new hardware.

As part of this expansion, customers utilizing shielding in the neighboring Seattle POPs (BFI, SEA) will be migrated to the new Metro POP. Once this maintenance window closes, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf after 14 days.
When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin.

Action for Fastly Customers:
1. Please be sure to check that your origin access lists allow the full range of Fastly IP addresses: https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges. Failure to verify origin access lists will result in origin connection disruption.
2. Customers with any questions or concerns should contact their dedicated technical account team or Fastly’s Support team at (support@fastly.com).

For more information on Metro POPs: https://developer.fastly.com/learning/concepts/pop/#metro-pops
Posted Jun 09, 2022 - 20:39 UTC
This scheduled maintenance affects: North America (Seattle (BFI), Seattle (SEA)).