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.

Identified - Fastly is aware of a recently disclosed CPU vulnerability known as Retbleed (CVE-2022-29900 and CVE-2022-29901). We are studying the implications of this vulnerability and do not currently believe that exploitation is feasible. Our investigation is ongoing.
Jul 13, 05:46 UTC
Monitoring - A business continuity update from Fastly about the escalating invasion of Ukraine has been posted to our Fastly Blog.

This post can be found here: https://www.fastly.com/blog/business-continuity-amid-the-invasion-of-ukraine

Questions can be directed to support@fastly.com

Mar 2, 03:33 UTC
North America Operational
Ashburn (IAD) Operational
Ashburn (WDC) Operational
Atlanta (ATL) Operational
Atlanta (FTY) Operational
Atlanta (PDK) Operational
Boston (BOS) Operational
Calgary (YYC) Operational
Chicago (CHI) Operational
Columbus (CMH) Operational
Columbus (LCK) Operational
Dallas (DAL) Operational
Dallas (DFW) Operational
Denver (DEN) Operational
Detroit (DTW) Operational
Gainesville (GNV) Operational
Honolulu (HNL) Operational
Houston (IAH) Operational
Kansas City (MCI) Operational
Los Angeles (BUR) Operational
Los Angeles (LGB - LAX/SNA) Operational
Miami (MIA) Operational
Minneapolis (MSP) Operational
Minneapolis (STP) Operational
Montreal (YUL) Operational
New York (LGA) Operational
Newark (EWR) Operational
Palo Alto (PAO) Operational
Phoenix (PHX) Operational
Portland (PDX) Operational
San Jose (SJC) Operational
Seattle (BFI) Operational
Seattle (SEA) Operational
St. Louis (STL) Operational
Toronto (YYZ) Operational
Vancouver (YVR) Operational
South America Operational
Bogota (BOG) Operational
Buenos Aires (EZE) Operational
Curitiba (CWB) Operational
Fortaleza (FOR) Operational
Lima (LIM) Operational
Rio de Janeiro (GIG) Operational
Santiago (SCL) Operational
Sāo Paulo (CGH) Operational
Europe Operational
Amsterdam (AMS) Operational
Brussels (BRU) Operational
Copenhagen (CPH) Operational
Dublin (DUB) Operational
Frankfurt (FRA) Operational
Frankfurt (HHN) Operational
Helsinki (HEL) Operational
Lisbon (LIS) Operational
London (LCY) Operational
London (LHR) Operational
London (LON) Operational
Madrid (MAD) Operational
Manchester (MAN) Operational
Marseille (MRS) Operational
Milan (LIN) Operational
Milan (MXP) Operational
Munich (MUC) Operational
Oslo (OSL) Operational
Paris (CDG) Operational
Rome (FCO) Operational
Sofia (SOF) Operational
Stockholm (BMA) Operational
Vienna (VIE) Operational
Palermo (PMO) Operational
Asia/Pacific Operational
Adelaide (ADL) Operational
Auckland (AKL) Operational
Brisbane (BNE) Operational
Christchurch (CHC) Operational
Dubai (DXB) Operational
Dubai (FJR) Operational
Hong Kong (HKG) Operational
Kuala Lumpur (KUL) Operational
Manila (MNL) Operational
Melbourne (MEL) Operational
Osaka (ITM) Operational
Perth (PER) Operational
Seoul (ICN) Operational
Singapore (QPG) Operational
Sydney (SYD) Operational
Tokyo (HND) Operational
Tokyo (NRT) Operational
Tokyo (TYO) Operational
Wellington (WLG) Operational
Bangkok (BKK) Operational
Africa Operational
Cape Town (CPT) Operational
Ghana (ACC) Operational
Johannesburg (JNB) Operational
India Operational
Chennai (MAA) Operational
Hyderabad (HYD) Operational
Kolkata (CCU) Operational
Mumbai (BOM) Operational
New Delhi (DEL) Operational
Edge Cloud Services Operational
Compute@Edge Operational
Configuration Deployment Operational
DNS Systems Operational
Domain Inspector Operational
Fastly API Operational
Fastly Configuration Application Operational
Fastly WAF Operational
Geolocation Data Operational
Health Checks Operational
Historical Stats ? Operational
Image Optimization Operational
On-the-fly Packager Operational
Origin Inspector Operational
Purging Operational
Real Time Analytics Operational
Streaming Logs Operational
TLS Provisioning Operational
Nearline Cache Operational
Amsterdam (AMS) Operational
Palo Alto (PAO) Operational
Sydney (SYD) Operational
Fastly Systems Operational
Billing System Operational
Customer Support Ticketing System ? Operational
Customer Support Phone System Operational
Customer Support Chat System Operational
Fastly Documentation Site Operational
Fastly Marketing Site Operational
Fastly Status Page Operational
Business Continuity Operational
COVID-19 Operational
Ukraine Invasion ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Capacity Expansion: Miami (MIA) Aug 16, 05:00-09:00 UTC
Update - Please be advised that the time of this maintenance event has changed from August 16th, 08:00 UTC to August 16th, 05:00 UTC
Aug 11, 22:22 UTC
Scheduled - Fastly will be adding capacity at our Miami, United States (MIA) data center. End-users may observe connection resets as traffic is migrated onto new hardware.

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).

Aug 10, 00:10 UTC
Metro Expansion: Frankfurt (FRA) Aug 25, 23:00 - Aug 26, 05:00 UTC
Update - Please be advised that the time of this maintenance event has changed from July 25th, 23:00 UTC to August 25th, 23:00 UTC.
Jul 20, 22:13 UTC
Scheduled - Fastly will be expanding Frankfurt 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 Frankfurt POP (HHN) 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

Jun 14, 22:06 UTC
Metro Expansion: Seattle (BFI) Sep 15, 08:00 - Sep 19, 08:00 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.
Jul 22, 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.
Jul 20, 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

Jun 9, 20:39 UTC
Past Incidents
Aug 14, 2022
Resolved - This incident has been resolved.
Aug 14, 02:53 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 14, 02:48 UTC
Identified - The issue has been identified and a fix is being implemented.
Aug 14, 02:18 UTC
Update - We are continuing to investigate this issue.
Aug 14, 01:51 UTC
Investigating - We're currently investigating performance issues with our TLS provisioning system in the APAC region. All other services are unaffected.
Aug 14, 01:51 UTC
Aug 13, 2022

No incidents reported.

Aug 12, 2022
Resolved - This incident has been resolved.
Aug 12, 16:58 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Aug 12, 16:47 UTC
Identified - The issue has been identified and a fix is being implemented.
Aug 12, 16:39 UTC
Investigating - We're investigating elevated errors in Atlanta (PDK). All other locations and services are unaffected
Aug 12, 16:27 UTC
Aug 11, 2022
Resolved - Fastly Engineers detected a performance impacting event affecting the Hyderabad (HYD) data center from approximately 2022-08-11 11:11 UTC to 2022-08-11 11:38 UTC. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Aug 11, 12:07 UTC
Resolved - Fastly Engineers detected a performance impacting event affecting the Sofia (SOF) data center from approximately 2022-08-11 07:08 UTC to 2022-08-11 07:13 UTC. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Aug 11, 07:34 UTC
Aug 10, 2022

No incidents reported.

Aug 9, 2022

No incidents reported.

Aug 8, 2022
Resolved - All routine checks have been completed. Invoices can be accessed through standard methods.
Aug 8, 19:29 UTC
Update - Fastly Billing has completed our routine checks. As a result of these checks, customers who did not have charges in the month of July may have received an additional email notification confirming a $0.00 balance. There are no further actions to take in response to this notification.
Aug 5, 17:11 UTC
Monitoring - Fastly Billing is currently performing a series of routine checks on our billing process to ensure optimal accuracy for our August 1st billing cycle. As a result of these checks customers may experience a delay receiving their invoice.

There is no impact to production services or traffic.

Aug 1, 20:08 UTC
Resolved - This incident has been resolved.
Aug 8, 17:48 UTC
Identified - The issue has been identified and a fix is being implemented.
Aug 8, 17:36 UTC
Investigating - We are currently investigating performance issues affecting the availability of manage.fastly.com and our API. CDN delivery, stats aggregation, and all other data plane services are unaffected.
Aug 8, 17:23 UTC
Aug 7, 2022

No incidents reported.

Aug 6, 2022

No incidents reported.

Aug 5, 2022
Aug 4, 2022
Resolved - This incident has been resolved.
Aug 4, 21:59 UTC
Investigating - We are currently investigating performance issues affecting the availability of manage.fastly.com and our API. CDN delivery, stats aggregation, and all other data plane services are unaffected.
Aug 4, 21:31 UTC
Completed - The scheduled maintenance has been completed.
Aug 4, 08:18 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 3, 23:00 UTC
Update - 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).

Aug 3, 15:47 UTC
Scheduled - Fastly will be adding capacity at our Madrid, Spain (MAD) data center. End-users may observe connection resets as traffic is migrated onto new hardware.

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).

Jul 29, 23:06 UTC
Aug 3, 2022
Aug 2, 2022

No incidents reported.

Aug 1, 2022
Jul 31, 2022

No incidents reported.