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 [email protected] for assistance.

All Systems Operational
API Operational
Stats ? Operational
Control Panel Operational
North America Operational
New York (JFK) Operational
Ashburn (IAD) Operational
Atlanta (ATL) Operational
Denver (DEN) Operational
Chicago (ORD) Operational
Miami (MIA) Operational
Dallas (DFW) Operational
San Jose (SJC) Operational
Los Angeles (LAX) Operational
Seattle (SEA) Operational
Boston (BOS) Operational
Toronto (YYZ) Operational
Minneapolis (MSP) Operational
Montreal (YUL) Operational
South America Operational
Sāo Paulo (GRU) Operational
Europe Operational
Frankfurt (FRA) Operational
Amsterdam (AMS) Operational
London (LCY) Operational
London (LHR) Operational
Stockholm (BMA) Operational
Paris (CDG) Operational
Frankfurt (HHN) Operational
Madrid (MAD) Operational
Asia/Pacific Operational
Auckland (AKL) Operational
Wellington (WLG) Operational
Sydney (SYD) Operational
Melbourne (MEL) Operational
Brisbane (BNE) Operational
Perth (PER) Operational
Osaka (ITM) Operational
Tokyo (NRT) Operational
Singapore (SIN) Operational
Hong Kong (HKG) Operational
Dubai (FJR) Operational
South Africa Operational
Johannesburg (JNB) Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
May 9, 2017

No incidents reported today.

May 8, 2017

No incidents reported.

May 7, 2017

No incidents reported.

May 6, 2017

No incidents reported.

May 5, 2017
Traffic rerouted in Johannesburg (JNB)
Resolved - This incident has been resolved.
May 5, 02:22 UTC
Identified - The issue has been identified and a fix is being implemented.
May 4, 16:36 UTC
Investigating - Traffic in JNB has been temporarily rerouted. All other locations and services are unaffected.
May 4, 16:24 UTC
May 3, 2017
Updating required TLS version on Shared Certificates
Completed - After receiving customer feedback, we have decided to postpone further changes to our Shared Certificates this week as part of our TLS deprecation plan. Please contact [email protected] if you have any questions about changes made.
May 3, 22:26 UTC
Scheduled - This week we will be updating our Shared Certificates to require TLS 1.2 as a minimum and dropping 3DES cipher support. Please contact [email protected] if you require TLS 1.0 and 1.1. No updates will be made to Dedicated (Hosted) Certificates.
https://www.fastly.com/blog/phase-two-our-tls-10-and-11-deprecation-plan
May 1, 18:52 UTC
May 2, 2017
Traffic re-routed at Sao Paulo (GRU)
Resolved - This incident has been resolved.
May 2, 18:47 UTC
Update - Engineers are working to return traffic to GRU.
May 2, 18:10 UTC
Identified - The issue has been identified and a fix is being implemented.
May 2, 16:48 UTC
Investigating - Fastly engineers are re-routing traffic at GRU while errors are investigated.
May 2, 16:33 UTC
Degraded Performance in JFK
We experienced degraded performance with our JFK datacenter from 16:48 UTC until 17:20 UTC. Customers may have seen increased error rates in JFK during this timeframe. All other services are unaffected and the issue has since been resolved.
May 2, 17:28 UTC
EU POPs - Elevated Errors
Resolved - This incident has been resolved.
May 2, 15:17 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 2, 15:07 UTC
Identified - The issue has been identified and a fix is being implemented.
May 2, 15:05 UTC
Investigating - Fastly engineers are observing elevated errors from some EU POPs, and are investigating.
May 2, 14:58 UTC
May 1, 2017
Traffic rerouted from Sāo Paulo (GRU)
Resolved - This incident has been resolved.
May 1, 23:43 UTC
Investigating - Traffic in GRU has been temporarily rerouted. All other locations and services are unaffected.
May 1, 23:07 UTC
Apr 30, 2017
Johannesburg (JNB) re-routing
Resolved - This incident has been resolved.
Apr 30, 06:17 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 30, 04:16 UTC
Investigating - We are currently investigating this issue.
Apr 30, 03:37 UTC
ITM (Osaka) - transient errors
We saw elevated errors in ITM ( Osaka Datacenter) from 0340h -> 0348h UTC 30 April 2017.
Apr 30, 03:57 UTC
Apr 29, 2017

No incidents reported.

Apr 28, 2017

No incidents reported.

Apr 27, 2017

No incidents reported.

Apr 26, 2017
Johannesburg (JNB) re-routing
Resolved - This incident has been resolved.
Apr 26, 21:15 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 26, 21:00 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 26, 20:56 UTC
Investigating - investigating issues in Johannesburg datacenter
Apr 26, 20:46 UTC
Degraded Performance for NRT and ITM POPs
Resolved - This incident has been resolved.
Apr 26, 10:43 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 26, 10:38 UTC
Identified - We're currently investigating degraded performance with Japan POPs NRT and ITM. All other services are unaffected.
Apr 26, 10:37 UTC
Apr 25, 2017
Traffic rerouted from LAX
Resolved - This incident has been resolved.
Apr 25, 22:34 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 25, 20:07 UTC
Identified - The issue has been identified and a fix is being implemented
Apr 25, 18:28 UTC
Update - We are continuing to investigate
Apr 25, 16:03 UTC
Investigating - Traffic in LAX has been temporarily rerouted. All other locations and services are unaffected. Customers may experience increased origin load.
Apr 25, 15:46 UTC
← Incident History Powered by StatusPage
About Terms Privacy Contact Support
Copyright 2011-2017 Fastly.com, All Rights Reserved.