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

Apr 19
Apr 18
Apr 17
Apr 16
Apr 15
Apr 14
Apr 13
Edge Cloud Platform Edge Cloud Platform
North America
Ashburn (IAD)
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 (LAX)
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 Services
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
Global POP Network (SEV1/0)
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)
Business Continuity
COVID-19
Ukraine Invasion
Third Party Service Provider Third Party Service Provider
General Updates General Updates

Filters

Incidents (Last 15 Days)

This Month
Compute API & Configuration Management Configuration Deployment Fastly Application Fastly API
18 April 2024, 15:59 UTC

Engineering has confirmed that our API and Configuration Management services and access to our Fastly Application has been fully restored. Customers may have experienced elevated errors when attempting to access manage.fastly.com and failed Configuration propagation and API services during this incident from 14:08 to 15:37 UTC.

Our network availability and all other services were unaffected by this incident.

This incident is resolved.

18 April 2024, 13:49 UTC

A significant update from Let’s Encrypt, one of our integrated Certification Authorities (CA), may affect how customers access your website. On June 6th, 2024, Let’s Encrypt end-users on very old devices or software may receive insecure warnings or be blocked from accessing your applications. 


To protect your customer experience, we encourage you to confirm which CA you’re using. If it’s Lets Encrypt and serving this type of traffic is a hard requirement, consider changing your TLS subscription to Certainly.


Learn more about the change and how to confirm your CA here. Our customer support team is here to help if you have any additional questions. You can reach us at https://support.fastly.com


We are dedicated to providing all our customers a secure and reliable online experience. We appreciate your attention to this matter and your continued trust in us. Thank you for your understanding and cooperation.


17 April 2024, 20:45 UTC
Edge Cloud Platform Europe Milan (LIN)
17 April 2024, 21:00 UTC

Engineering has confirmed that our Milan (LIN) Point of Presence (POP) has been fully restored. Customers may have experienced degraded performance from 20:45 to 21:00 UTC.

This incident is resolved.

Edge Cloud Platform South America Buenos Aires (EZE) Fortaleza (FOR) Lima (LIM) Rio de Janeiro (GIG)
17 April 2024, 21:45 UTC

Engineering has confirmed that our Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG) Point of Presence (POP)s has been fully restored. Customers may have experienced degraded performance from 19:15 to 21:45 UTC.

This incident is resolved.

Observability Domain Inspector Origin Inspector
15 April 2024, 23:05 UTC

Engineering has confirmed that impact to the Domain Inspector and Origin Inspector metrics has been fully restored. Customers may have experienced degraded service for Fastly Alerts from 21:42 to 23:05 UTC.

This incident is resolved.

Security Console and API Data Services Dashboard Data
11 April 2024, 09:00 UTC
Security NGWAF@Edge
11 April 2024, 16:17 UTC

Engineering has confirmed that NGWAF@Edge has been fully restored. Customers may have experienced errors in new Edge WAF deployments within our NGWAF Services from 09:00 to 16:04 UTC.

This incident is resolved.

Customer Services Status Page
10 April 2024, 13:54 UTC

On the 26th of April 2024 we will release an update to our status page, https://www.fastlystatus.com. 

During this update, there will be no disruption to our status page or our ability to notify our customers of maintenance or service status updates. Rest assured that your existing notification preferences will remain unchanged. However, new components will be displayed as a result of this change. We kindly encourage you to review your preferences to ensure that the updates will be valuable to you and your developer teams.



Edge Cloud Platform South America Lima (LIM)
10 April 2024, 05:02 UTC

Fastly Engineers detected a performance impacting event affecting the Lima (LIM) data center.

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

09 April 2024, 18:02 UTC
Compute API & Configuration Management Fastly API
09 April 2024, 18:33 UTC

Engineering has confirmed that Fastly API services has been fully restored. Customers would have experienced intermittent periods of latency in accessing our secret store for NGWAF console services.

In addition, our manage.fastly.com Website and API authentication may have resulted in varying degrees of timeout and/or increased latency as a result of this incident from 18:02 to 18:33 UTC. (~31 minutes)

This incident is resolved.

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

Scheduled Maintenance (Last 15 Days)

This Month
Edge Cloud Platform South America Santiago (SCL)
17 April 2024, 10:00 UTC

The scheduled maintenance has been completed.

Upcoming May 2024
Edge Cloud Platform Europe Milan (LIN)
02 May 2024, 00:00 UTC
[upcoming]

Fastly will be adding capacity at our Milan (LIN) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 02 May 2024 at 00: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).

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