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
| Unavailable, see "Current Incidents" for more information.
This issue has been identified and a fix is being implemented.
With the recently announced news that Silicon Valley Bank (SVB) has been taken over by the FDIC, Fastly would like to reassure that while we do have a relationship with SVB, our financial exposure is not material. There should be no disruption to the normal operations of our services.
We are transitioning our banking relationship from SVB to another financial institution. Fastly has updated our payment instructions and customers will receive a message containing directions about how to process upcoming payments.
Customers may verify this request by contacting us at support@fastly.com.
Fastly products and all other services are unaffected.
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 issue has been identified and a fix is being implemented.
This incident has been resolved.
During this incident, customers could not make Varnish or Compute@Edge changes to their Fastly services through the administrative control panel. Additionally, the Fastly UI and API were unavailable, impacting API dependent capabilities such as purge_all, viewing/changing service configurations, etc.
CDN delivery and Fastly network availability were unaffected.
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.
With the recently announced news that Silicon Valley Bank (SVB) has been taken over by the FDIC, Fastly would like to reassure that while we do have a relationship with SVB, our financial exposure is not material. There should be no disruption to the normal operations of our services.
We are transitioning our banking relationship from SVB to another financial institution. Fastly has updated our payment instructions and customers will receive a message containing directions about how to process upcoming payments.
Customers may verify this request by contacting us at support@fastly.com.
Fastly products and all other services are unaffected.
This incident has been resolved.
The scheduled maintenance has been completed.
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).
Fastly will be migrating customers shielding in Dallas (DAL) to Dallas (DFW).
Customers can either apply a new shield in advance, or their shielding configuration will be updated to Dallas (DFW) 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:
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. Access the Fastly App and modify your service's shield: https://docs.fastly.com/en/guides/shielding#enabling-shielding.
3. 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 Palo Alto, California (PAO) shield customers to Santa Clara, California (SJC).
As part of this migration, customers utilizing shielding in Palo Alto, California (PAO) will be migrated to Santa Clara, California (SJC). 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 Santa Clara, California (SJC) 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).
Thank you!
Fastly is announcing the end of life (EOL) schedule for our Fastly WAF (Legacy and WAF 2020). This will allow us to focus more of our resources on the replacement product, the Fastly Next-Gen WAF, which is an enhanced offering.
We’re looking forward to helping you transition to this product as soon as you are able.
- The official EOL for the Fastly WAF is April 30th, 2023 at 00:00 UTC.
The product will continue to be supported until this date.
We’re happy to help you get you started with a proof-of-concept (POC) evaluation of our Next-Gen WAF so you can see how the two solutions compare. To get started, contact us via email at waftransition@fastly.com.
Click here to access a filterable version of our full incident history. Includes full incident history for Fastly, Fanout and Signal Sciences.