To ensure the highest security and best performance for our customers, Fastly’s network has built-in redundancies and automatic failover routing. We continuously monitor the status of our global network and all related services, but in the event of scheduled maintenance or an unplanned performance impact, we think our customers deserve clear, transparent communication so they can maintain trust in our service and our teams. 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.
Current Status
| Normal
For the History Grid below, the color and icon indicators utilized, represent the most severe event posted within the date displayed. Click the ＋ icon next to each section to see the status recorded for that date, and hover your mouse over a status icon within the history grid, if an event was posted, for a pop-up to appear with the relative summary.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has resolved.
During this incident, customers would have experienced increased latency and elevated 5xx errors in our Columbus (CMH) POP, as well as, elevated errors when attempting to access configuration management and API services through our Control Plane from 18:40 to 21:30 UTC.
Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.
Fastly Engineering has confirmed that our network availability and Control Plane services have been fully restored.
The customer impact associated with this status post is a direct result of the third party service provider issue that is covered in this status post link: https://www.fastlystatus.com/incident/376079
All remaining status post updates will be consolidated into the link provided above. We are effectively closing this post in order to reduce dual notifications for our subscribers.
Fastly Engineers detected a performance impacting event affecting the Seattle (BFI) data center.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
This incident has been resolved.
The scheduled maintenance has been completed.
Fastly will be adding capacity at our Houston (IAH) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 03 October 2023 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 (support@fastly.com).
Fastly will be migrating Atlanta (ATL and FTY) shield customers to Atlanta (PDK).
As part of this migration, customers utilizing shielding in Atlanta (ATL and FTY) will be migrated to Atlanta (PDK). Once this maintenance window closes, customers can either apply a new shield at a time of their choosing, or their shielding configuration will be updated to Atlanta (PDK) on their behalf after 14 days.
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).
Fastly will be expanding Sāo Paulo (CGH) 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 Sāo Paulo (CGH) 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:
- Please verify that all origins allow the full range of Fastly IP addresses (https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges), as this list is updated periodically. Failure to verify origin access lists will result in origin connection disruption.
- 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
Click here to access a filterable version of our full incident history. Includes full incident history for Fastly, Fanout and Signal Sciences.