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
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
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
New POP: Madrid Jan 25, 00:00-02:00 UTC
As part of Fastly’s global network expansion, we’re excited to let you know that we will be adding a Madrid, Spain (MAD) point of presence (POP) to Fastly's European network.

If you have questions, please contact support@fastly.com
Posted on Jan 18, 20:59 UTC
Past Incidents
Jan 20, 2017

No incidents reported today.

Jan 19, 2017
Resolved - This incident has been resolved.
Jan 19, 14:01 UTC
Identified - The issue has been identified and a fix is being implemented.
Jan 19, 13:39 UTC
Investigating - We're currently investigating degraded performance with our SJC POP. All other services are unaffected.
Jan 19, 13:25 UTC
Jan 18, 2017

No incidents reported.

Jan 17, 2017

No incidents reported.

Jan 16, 2017

No incidents reported.

Jan 15, 2017

No incidents reported.

Jan 14, 2017
Resolved - We have fully resolved the issue.
Jan 14, 23:24 UTC
Investigating - We're currently investigating degraded performance with our Historical Stats service. All other services are unaffected.
Jan 14, 22:40 UTC
Jan 13, 2017
Resolved - This incident has been resolved.
Jan 13, 19:37 UTC
Monitoring - We've currently mitigated degraded performance with our GRU datacenter, and are monitoring the results. All other services are unaffected.
Jan 13, 18:28 UTC
Jan 12, 2017
Completed - The scheduled maintenance has been completed.
Jan 12, 02:41 UTC
Verifying - Verification is currently underway for the maintenance items.
Jan 12, 02:39 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 12, 02:30 UTC
Scheduled - Fastly engineering will be performing maintenance on the Fastly control panel and APIs. They will be placed in maintenance mode for less than 15 minutes between 0230-0330 UTC, January 12th. Customers may see errors from app.fastly.com and manage.fastly.com as well as API endpoints on api.fastly.com. Purge by URL and surrogate key purges through API will not be affected. CDN delivery, stats aggregation, and all other content delivery services will be unaffected.
Jan 9, 23:32 UTC
Jan 11, 2017

No incidents reported.

Jan 10, 2017

No incidents reported.

Jan 9, 2017

No incidents reported.

Jan 8, 2017

No incidents reported.

Jan 7, 2017

No incidents reported.

Jan 6, 2017

No incidents reported.