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 for assistance.

Monitoring - A COVID-19 Business Continuity Update From Fastly

Questions can be directed to
Mar 16, 04:38 UTC
North America Operational
Ashburn (BWI) Operational
Ashburn (DCA) Operational
Ashburn (IAD) Operational
Ashburn (WDC) Operational
Atlanta (ATL) Operational
Atlanta (FTY) Operational
Atlanta (PDK) Operational
Boston (BOS) Operational
Chicago (CHI) Operational
Chicago (MDW) Operational
Chicago (ORD) Operational
Chicago (PWK) Operational
Columbus (CMH) Operational
Columbus (LCK) Operational
Dallas (DAL) Operational
Dallas (DFW) Operational
Denver (DEN) Operational
Detroit (DTW) Operational
Gainesville (GNV) Operational
Houston (IAH) Operational
Jacksonville (JAX) 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
Sāo Paulo (GRU) Operational
Europe Operational
Amsterdam (AMS) Operational
Copenhagen (CPH) Operational
Dublin (DUB) Operational
Frankfurt (FRA) Operational
Frankfurt (HHN) Operational
Helsinki (HEL) 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
Stockholm (BMA) Operational
Vienna (VIE) Operational
Rome (FCO) Operational
Sofia (SOF) Operational
Asia/Pacific Operational
Auckland (AKL) Operational
Brisbane (BNE) Operational
Dubai (FJR) Operational
Hong Kong (HKG) Operational
Kuala Lumpur (KUL) Operational
Melbourne (MEL) Operational
Osaka (ITM) Operational
Perth (PER) Operational
Singapore (QPG) Operational
Sydney (SYD) Operational
Tokyo (HND) Operational
Tokyo (NRT) Operational
Tokyo (TYO) Operational
Wellington (WLG) Operational
Manila (MNL) Operational
Seoul (ICN) Operational
Dubai (DXB) Operational
Africa Operational
Cape Town (CPT) Operational
Ghana (ACC) Operational
Johannesburg (JNB) Operational
India Operational
Chennai (MAA) Operational
Mumbai (BOM) Operational
New Delhi (DEL) Operational
Hyderabad (HYD) Operational
Kolkata (CCU) Operational
Edge Cloud Services Operational
Fastly API Operational
Fastly Configuration Application Operational
Fastly WAF Operational
Configuration Deployment Operational
DNS Systems Operational
Geolocation Data Operational
Historical Stats ? Operational
Image Optimization Operational
On-the-fly Packager Operational
Purging Operational
Real Time Analytics Operational
Streaming Logs Operational
TLS Provisioning Operational
Nearline Cache Operational
Amsterdam (AMS) Operational
Ashburn (BWI) 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
Degraded Performance
Partial Outage
Major Outage
Past Incidents
Jan 23, 2022

No incidents reported today.

Jan 22, 2022

No incidents reported.

Jan 21, 2022

No incidents reported.

Jan 20, 2022

No incidents reported.

Jan 19, 2022

No incidents reported.

Jan 18, 2022

No incidents reported.

Jan 17, 2022
Resolved - This incident has been resolved.
Jan 17, 04:38 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 17, 01:50 UTC
Investigating - We're investigating possible performance impact affecting the Detroit (DTW) data center. All other locations and services are unaffected
Jan 17, 01:27 UTC
Jan 16, 2022

No incidents reported.

Jan 15, 2022

No incidents reported.

Jan 14, 2022

No incidents reported.

Jan 13, 2022

No incidents reported.

Jan 12, 2022
Resolved - This incident has been resolved.
Jan 12, 23:18 UTC
Monitoring - A fix has been implemented and we are monitoring the results. Impact to customers was minimal.
Jan 12, 22:49 UTC
Investigating - We're investigating elevated errors in Mumbai (BOM), Chennai (MAA), New Delhi (DEL). All other locations and services are unaffected
Jan 12, 21:48 UTC
Resolved - This incident has been resolved.
Jan 12, 00:53 UTC
Update - Fastly engineers have released a new version of Rule ID: 4100050* "Log4j2 - 2.14.1 JNDI possible RCE attempt" for Fastly Legacy WAF. This new version resolves a bug that may have reduced the efficacy of this rule. Fastly Legacy WAF customers are advised to update to the latest version of this rule as soon as possible to ensure the best possible levels of coverage for their accounts.

Strict Enforcement rules for Legacy WAF as well as Fastly 2020 and Signal Sciences Next-Gen WAFs are not affected and do not require any customer action at this time.
Dec 20, 23:43 UTC
Update - Fastly Engineers have released a new version of Log4j Strict Enforcement Rules to increase coverage while reducing false positives for both Fastly 2020 WAF and SignalScience Next-Gen WAF.

There is no action required for customers utilizing this rule in Signal Science implementations, however Fastly 2020 WAF customers must manually activate this new version.

For more information about managing Fastly 2020 WAF rules, please visit
Dec 17, 18:53 UTC
Update - As we continue to monitor the rapidly evolving situation with the log4j vulnerability, our Security Research and Engineering teams have completed several iterations of our Fastly WAF and Signal Sciences Next-Gen WAF CVE rules. Signal Sciences Next-Gen WAF implementations automatically receive updates to rules as they are released without any customer action required. Fastly Legacy and Fastly 2020 WAF implementations require customer action to implement updated rules.

For more information on how to update the legacy Fastly WAF rule set or individual rules in the Fastly 2020 WAF please visit

Legacy Fastly WAF -
Fastly 2020 WAF -

Going forward we will post updates to our status pages as new versions of these rules are made available.

Our efficacy testing has shown that these rules provide excellent coverage in protecting our customers from a wide range of variants and attacks, with minimal false positives.

While these rules are being used widely by a variety of customers with great results, a number of customers have asked for a method to provide more strict coverage, though it increases the risk of false positives and the possibility of blocking a portion of legitimate traffic. To accommodate this request, we have created a second set of, “strict enforcement rules.” These are titled:

Fastly WAFs: Log4j2 - 2.14.1 JNDI possible RCE attempt - strict
Signal Sciences WAF: CVE-2021-44228-STRICT

We recommend only using these rules as a last resort while working to patch your environment, due to the increased risk of blocking legitimate traffic.

Please contact our support teams if you have any questions or need any assistance updating these rules at
Dec 16, 22:12 UTC
Monitoring - Fastly has just published a blog post,

about the Log4j vulnerability. This blog includes background information on the vulnerability, Fastly's observations we've seen so far, and details on how to block exploitation attempts.
Dec 11, 00:42 UTC
Identified - Fastly is aware of a serious vulnerability in log4j. We have developed defenses to assist customers in the mitigation of this vulnerability.

For Sciences Next-Gen WAF customers: You can enable this a new templated rule in the Signal Sciences console by going to Site Rules -> Templated Rules. Look for CVE-2021-44228 and click View. Click Configure. Check the box next to Enabled and click “Update rule”.

For Fastly Legacy WAF customers: please contact the CSOC at for assistance with VCL snippets to protect your CDN services.
Dec 10, 18:07 UTC
Jan 11, 2022
Completed - The scheduled maintenance has been completed.
Jan 11, 11:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 11, 10:30 UTC
Scheduled - On January 11, 2022 from 10:30-11:00 UTC GlobalSign will rotate their Atlas TLS CAs intermediate certificates.

Starting in 2022, GlobalSign Atlas TLS CAs will be updated every quarter, on the second Tuesday of the quarter at 10:30-11:00 UTC

For customers who are using Fastly TLS managed certificates issued by GlobalSign, also known as Fastly TLS Commercial CA, this change will require action on your part if you are using certificate or public key pinning to avoid any impact to your traffic.

For more information on the update from GlobalSign, please refer to the following links:
Jan 7, 02:19 UTC
Jan 10, 2022

No incidents reported.

Jan 9, 2022
Resolved - Fastly Engineers detected a performance impacting event affecting the Brisbane (BNE), Melbourne (MEL), Perth (PER), Seoul (ICN), Sydney (SYD) data centers from approximately 2022-01-09 05:14 UTC to 2022-01-09 06:23 UTC. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Jan 9, 06:47 UTC