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 been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This scheduled maintenance has been completed.
[Update]
A retrospective of this maintenance did reflect that there was a service with a misconfiguration from 18:47 UTC to 19:27 UTC, during which customers may have experienced TLS API related errors.
All other services were unaffected by this change.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Fastly will be adding capacity at our Atlanta (ATL) data center. End-users may observe connection resets as traffic is migrated onto new hardware, starting on 07 February 2023 at 05:00 UTC.
- Our estimated duration is 240 minutes
In order for customers who use this POP as an Origin Shield to leverage new cache nodes for an expanded cache footprint, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf 7 days after this maintenance window closes.
When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. 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). Customers with any questions or concerns should contact Fastly’s Support team (support@fastly.com).
Fastly will be adding capacity at our Kansas City (MCI) data center. End-users may observe connection resets as traffic is migrated onto new hardware, starting on 07 February 2023 at 06:00 UTC.
- Our estimated duration is 240 minutes
In order for customers who use this POP as an Origin Shield to leverage new cache nodes for an expanded cache footprint, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf 7 days after this maintenance window closes.
When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. 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). Customers with any questions or concerns should contact Fastly’s Support team (support@fastly.com).
Fastly will be adding capacity at our Atlanta (ATL) data center. End-users may observe connection resets as traffic is migrated onto new hardware, starting on 08 February 2023 at 05:00 UTC.
- Our estimated duration is 240 minutes
In order for customers who use this POP as an Origin Shield to leverage new cache nodes for an expanded cache footprint, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf 7 days after this maintenance window closes.
When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. 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). Customers with any questions or concerns should contact Fastly’s Support team (support@fastly.com).
Fastly will be adding capacity at our Atlanta (ATL) data center. End-users may observe connection resets as traffic is migrated onto new hardware, starting on 09 February 2023 at 05:00 UTC.
- Our estimated duration is 240 minutes
In order for customers who use this POP as an Origin Shield to leverage new cache nodes for an expanded cache footprint, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf 7 days after this maintenance window closes.
When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. 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). Customers with any questions or concerns should contact Fastly’s Support team (support@fastly.com).
On March 7th, 2023, Rapid7 will formally retire their Logentries product. As a result, Fastly will be completely removing the associated Logentries integration on the same date. We strongly advise all customers to replace their Logentries integration with a different logging integration (https://docs.fastly.com/en/guides/integrations#_logging-endpoints) in advance of this end-of-life date.
If you have a paid plan from Rapid7, you can choose to retain your Logentries data by following Rapid7’s archiving instructions (https://docs.logentries.com/docs/aws-s3-archiving).
Fastly will be migrating Paris (CDG) shield customers to Paris (PAR).
As part of this migration, customers utilizing shielding in Paris (CDG) will be migrated to Paris (PAR). 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 Paris (PAR) 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).
Fastly will be migrating customers shielding in Los Angeles (LGB) to Los Angeles (BUR).
Customers can either apply a new shield in advance, or their shielding configuration will be updated to Los Angeles (BUR) on their behalf during the maintenance.
When this change is applied, customers may observe additional origin traffic as cache nodes retrieve content from origin.
Action for Fastly Customers:
- 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.
- Access the Fastly App and modify your service's shield: https://docs.fastly.com/en/guides/shielding#enabling-shielding.
- Customers with any questions or concerns should contact their dedicated technical account team or Fastly’s Support team at (support@fastly.com).
Click here to access a filterable version of our full incident history. Includes full incident history for Fastly, Fanout and Signal Sciences.