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.
Fastly Engineers detected a performance impacting event affecting the Compute@Edge services in IAD 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.
The scheduled maintenance has been completed.
Fastly will be migrating customers shielding in Sāo Paulo (CGH) to Sāo Paulo (GRU).
As part of this expansion, customers utilizing shielding in the neighboring Edge Cloud Platform 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 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.