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 support@fastly.com for assistance.

All Systems Operational
API Operational
Stats ? Operational
Configuration 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
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
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
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Sep 28, 2016

No incidents reported today.

Sep 27, 2016

No incidents reported.

Sep 26, 2016

No incidents reported.

Sep 25, 2016

No incidents reported.

Sep 24, 2016

No incidents reported.

Sep 23, 2016
Resolved - This incident has been resolved.
Sep 23, 03:42 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Sep 22, 23:33 UTC
Identified - The Fastly helpdesk system is currently experiencing connectivity problems. We are working with external parties to restore service, but communications may be interrupted or delayed. In the interim, our support team is reachable through the #fastly irc room on the Freenode network (https://webchat.freenode.net/).
Sep 22, 23:12 UTC
Sep 21, 2016

No incidents reported.

Sep 20, 2016
Resolved - This incident has been resolved.
Sep 20, 12:38 UTC
Monitoring - This issue has been mitigated and is being actively monitored
Sep 20, 11:40 UTC
Investigating - Fastly is investigating elevated error rates from our LHR POP.
Sep 20, 11:08 UTC
Resolved - This incident has been resolved.
Sep 20, 06:40 UTC
Update - The affected backbone provider has confirmed that they have stabilized services. Fastly Engineering will be re-introducing this backbone provider into our network over the next few hours while closely monitoring for any abnormalities. A final update will be issued upon completion.
Sep 20, 01:13 UTC
Update - Due to the scope of the impacted service provider, we have deployed additional routing changes to mitigate degradation to end user networks
Sep 19, 20:22 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Sep 19, 19:10 UTC
Update - Fastly has routed around the affected backbone provider. We are monitoring the situation.
Sep 19, 19:00 UTC
Identified - The issue has been identified and a fix is being implemented.
Sep 19, 19:00 UTC
Investigating - Fastly is currently investigating a backbone event on the US West Coast.
Sep 19, 18:47 UTC
Sep 18, 2016

No incidents reported.

Sep 17, 2016

No incidents reported.

Sep 16, 2016

No incidents reported.

Sep 15, 2016

No incidents reported.

Sep 14, 2016
Resolved - Log delivery to the Logentries collection service is working normally
Sep 14, 17:48 UTC
Investigating - We're currently investigating streaming logs delivery degradation to the Logentries log collection service.
Sep 14, 16:30 UTC
Resolved - Retrospective - At approximately 05:30 UTC, September 14th, maintenance activities in our Chicago (ORD) and Dallas (DFW) POPs may have caused a temporary increase in requests to customer origins. No further impact is expected.
Sep 14, 17:00 UTC
Identified - Due to maintenance, customers shielding in our Chicago (ORD) and Dallas (DFW) may have experienced increased origin load. Object delivery is unaffected.
Sep 14, 16:35 UTC