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

Jun 08
Jun 07
Jun 06
Jun 05
Jun 04
Jun 03
Jun 02
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)
Ontario (YYZ)
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)
Dubai (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
08 June 2023, 05:04 UTC
Edge Cloud Platform North America Seattle (BFI)
08 June 2023, 05:42 UTC
[closed]

This incident has been resolved.

Compute API & Configuration Management Configuration Deployment Fastly Application Fastly API
07 June 2023, 23:05 UTC
[closed]

This incident has been resolved.

06 June 2023, 15:29 UTC
Edge Cloud Platform Europe Lisbon (LIS)
06 June 2023, 19:02 UTC
[closed]

This incident has been resolved.

02 June 2023, 16:13 UTC
Edge Cloud Platform Asia Osaka (ITM)
02 June 2023, 18:11 UTC
[closed]

This incident has been resolved.

Last Month
31 May 2023, 14:15 UTC
Customer Services Support Ticketing System
31 May 2023, 14:50 UTC
[closed]

This incident has been resolved.

31 May 2023, 10:14 UTC
Edge Cloud Platform Asia Dubai (FJR)
31 May 2023, 20:04 UTC
[closed]

This incident has been resolved.

28 May 2023, 21:35 UTC
Edge Cloud Platform South America Santiago (SCL)
29 May 2023, 00:49 UTC
[closed]

This incident has been resolved.

Edge Cloud Platform North America Seattle (BFI)
26 May 2023, 08:59 UTC
[closed]

This incident has been resolved.

Compute Compute@Edge
25 May 2023, 17:54 UTC
[closed]

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.

Edge Cloud Platform North America Atlanta (ATL) Atlanta (PDK)
24 May 2023, 02:51 UTC
[closed]

This incident has been resolved.

Scheduled Maintenance (Last 15 Days)

Last Month
24 May 2023, 06:00 UTC
Edge Cloud Platform North America New York (LGA)
24 May 2023, 11:00 UTC
[closed]

The scheduled maintenance has been completed.

31 May 2023, 06:00 UTC
Edge Cloud Platform South America Sao Paulo (GRU)
31 May 2023, 20:41 UTC
[closed]

The scheduled maintenance has been completed.

This Month
Edge Cloud Platform South America Sao Paulo (GRU) Sāo Paulo (CGH)
19 June 2023, 17:00 UTC
[upcoming]

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:

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

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