Welcome to Fastly's Status Page

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

History Grid Indicators

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.

Color indicators for completed statuses Color indicator for active statuses
Normal Informational Maintenance Degraded Unavailable Investigating Identified Monitoring
Normal: Everything is operating normally. No events or incidents related to network or service components have been identified or announced. Informational: We’ve posted information for general awareness. No network or service components are impacted. Maintenance: We’ve scheduled or are actively performing maintenance on the Fastly global network or one of its service components. Degraded: We’ve identified something that has caused a degradation of a portion of the Fastly network or service component. Customer services are being delivered but at reduced capacity. Unavailable: A portion of our network or specific service component is not currently operational or available. Investigating: We've observed or received a report of something that's impacting the performance of our network or a service component. We are actively investigating this event. Identified: An investigation identified the cause of an event or problem and a fix for it is being implemented. Monitoring: A fix has been deployed for an event or problem that is now resolved. The impacted network or service components are now stable and being monitored for continued health.

History Grid

Oct 02
Oct 01
Sep 30
Sep 29
Sep 28
Sep 27
Sep 26
Edge Cloud Platform Edge Cloud Platform
North America
Ashburn (IAD)
Ashburn (WDC)
Atlanta (ATL)
Atlanta (FTY)
Atlanta (PDK)
Boston (BOS)
Calgary (YYC)
Chicago (CHI)
Columbus (CMH)
Columbus (LCK)
Dallas (DAL)
Dallas (DFW)
Denver (DEN)
Detroit (DTW)
Gainesville (GNV)
Honolulu (HNL)
Houston (IAH)
Kansas City (MCI)
Los Angeles (BUR)
Los Angeles (LGB)
Miami (MIA)
Minneapolis (MSP)
Minneapolis (STP)
Montreal (YUL)
New York (NYC)
New York (LGA)
Newark (EWR)
Palo Alto (PAO)
Phoenix (PHX)
Portland (PDX)
San Francisco San Francisco
San Jose (SJC)
Seattle (BFI)
St. Louis (STL)
Toronto (YYZ)
Vancouver (YVR)
Europe
Amsterdam (AMS)
Brussels (BRU)
Copenhagen (CPH)
Dublin (DUB)
Frankfurt (FRA)
Frankfurt (HHN)
Helsinki (HEL)
Lisbon (LIS)
London London
London (LCY)
London (LHR)
London (LON)
Madrid (MAD)
Manchester (MAN)
Marseille (MRS)
Milan (LIN)
Milan (MXP)
Munich (MUC)
Oslo (OSL)
Palermo (PMO)
Paris (PAR)
Rome (FCO)
Sofia (SOF)
Stockholm (BMA)
Vienna (VIE)
Asia
Chennai (MAA)
Bangkok (BKK)
Dubai (DXB)
Fujairah (FJR)
Hong Kong (HKG)
Hyderabad (HYD)
Kolkata (CCU)
Kuala Lumpur (KUL)
Manila (MNL)
Mumbai (BOM)
Osaka (ITM)
New Delhi (DEL)
Seoul (ICN)
Singapore Singapore
Singapore (QPG)
Tokyo (HND)
Tokyo (NRT)
Tokyo (TYO)
South America
Bogota (BOG)
Buenos Aires (EZE)
Curitiba (CWB)
Fortaleza (FOR)
Lima (LIM)
Rio de Janeiro (GIG)
Santiago (SCL)
Sao Paulo (GRU)
Sāo Paulo (CGH)
Oceania
Adelaide (ADL)
Auckland (AKL)
Brisbane (BNE)
Christchurch (CHC)
Melbourne (MEL)
Perth (PER)
Sydney (SYD)
Wellington (WLG)
Africa
Cape Town (CPT)
Johannesburg (JNB)
Ghana (ACC)
Compute Compute
API & Configuration Management
Configuration Deployment
Fastly Application
Fastly API
Compute@Edge
DNS Systems
Fanout Fanout
Fanout Control Panel Fanout Control Panel
Edge Cloud Services
Fastly Public IPs
Geolocation Data
Image Optimization
Purging
On-the-fly Packager
TLS Provisioning
Security Security
Agents and Module Agents and Module
Agent Downloads Agent Downloads
Rule and IP List updates Rule and IP List updates
Rule Processing Rule Processing
Console and API Console and API
Data Services Data Services
Dashboard Data Dashboard Data
MOWD MOWD
Rate Limiting and Alerts Rate Limiting and Alerts
Requests Requests
Signals Dashboard Signals Dashboard
Cloud WAF Cloud WAF
NGWAF@Edge NGWAF@Edge
Fastly WAF (Legacy)
Observability Observability
Domain Inspector
Health Checks
Historical Stats
Origin Inspector
Real Time Analytics
Streaming Logs
Customer Services Customer Services
Business Continuity
COVID-19
Ukraine Invasion
Billing System
Support Ticketing System
Support Phone System
Support Chat System
https://docs.fastly.com/
https://www.fastly.com/
https://www.signalsciences.com/ https://www.signalsciences.com/
https://fanout.io/ https://fanout.io/
Status Page
Status Page (legacy)
Third Party Service Provider Third Party Service Provider
General Updates General Updates

Filters

Incidents (Last 15 Days)

This Month
Edge Cloud Platform South America Buenos Aires (EZE)
01 October 2023, 18:51 UTC
[closed]

This incident has been resolved.

Last Month
Compute API & Configuration Management Configuration Deployment
27 September 2023, 19:56 UTC
[closed]

This incident has been resolved.

25 September 2023, 23:29 UTC
Edge Cloud Platform Asia Tokyo (TYO)
26 September 2023, 03:27 UTC
[closed]

This incident has been resolved.

21 September 2023, 12:38 UTC
Compute API & Configuration Management Configuration Deployment Fastly Application Fastly API
21 September 2023, 13:27 UTC
[closed]

This incident has been resolved.

20 September 2023, 21:01 UTC
Edge Cloud Platform North America Columbus (CMH)
20 September 2023, 23:36 UTC
[closed]

This incident has resolved.

During this incident, customers would have experienced increased latency and elevated 5xx errors in our Columbus (CMH) POP, as well as, elevated errors when attempting to access configuration management and API services through our Control Plane from 18:40 to 21:30 UTC.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

Fastly Engineering has confirmed that our network availability and Control Plane services have been fully restored.

Compute API & Configuration Management Configuration Deployment Fastly Application Fastly API
20 September 2023, 22:08 UTC
[closed]

The customer impact associated with this status post is a direct result of the third party service provider issue that is covered in this status post link: https://www.fastlystatus.com/incident/376079 

All remaining status post updates will be consolidated into the link provided above. We are effectively closing this post in order to reduce dual notifications for our subscribers.

Edge Cloud Platform North America Seattle (BFI)
20 September 2023, 08:00 UTC
[closed]

Fastly Engineers detected a performance impacting event affecting the Seattle (BFI) data center.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

19 September 2023, 16:59 UTC
Security Console and API Dashboard Data
19 September 2023, 23:06 UTC
[closed]

This incident has been resolved.

Scheduled Maintenance (Last 15 Days)

Last Month
19 September 2023, 06:00 UTC
Edge Cloud Platform North America Houston (IAH)
19 September 2023, 19:18 UTC
[closed]

The scheduled maintenance has been completed.

This Month
Edge Cloud Platform North America Houston (IAH)
03 October 2023, 05:00 UTC
[upcoming]

Fastly will be adding capacity at our Houston (IAH) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 03 October 2023 at 05:00 UTC.

Our estimated duration is 4h. 

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please verify 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).

09 October 2023, 09:00 UTC
Edge Cloud Platform North America Atlanta (ATL) Atlanta (FTY) Atlanta (PDK)
09 October 2023, 09:00 UTC
[upcoming]

Fastly will be migrating Atlanta (ATL and FTY) shield customers to Atlanta (PDK).

As part of this migration, customers utilizing shielding in Atlanta (ATL and FTY) will be migrated to Atlanta (PDK). 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 Atlanta (PDK) on their behalf after 14 days.

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

24 October 2023, 05:00 UTC
Edge Cloud Platform South America Sāo Paulo (CGH)
24 October 2023, 05:00 UTC
[upcoming]

Fastly will be expanding Sāo Paulo (CGH) 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 Sāo Paulo (CGH) 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 verify that all origins allow the full range of Fastly IP addresses (https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges), as this list is updated periodically. 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

Click here to access a filterable version of our full incident history. Includes full incident history for Fastly, Fanout and Signal Sciences.