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.

Monitoring - A COVID-19 Business Continuity Update From Fastly

https://www.fastly.com/blog/covid-19-update

Questions can be directed to support@fastly.com
Mar 16, 04:38 UTC
North America Operational
Ashburn (BWI) Operational
Ashburn (DCA) Operational
Ashburn (IAD) Operational
Ashburn (WDC) Operational
Atlanta (FTY) Operational
Atlanta (PDK) Operational
Boston (BOS) Operational
Chicago (CHI) Operational
Chicago (MDW) Operational
Chicago (ORD) Operational
Chicago (PWK) Operational
Columbus (CMH) Operational
Columbus (LCK) Operational
Dallas (DAL) Operational
Dallas (DFW) Operational
Denver (DEN) Operational
Houston (IAH) Operational
Jacksonville (JAX) Operational
Kansas City (MCI) Operational
Los Angeles (BUR) Operational
Los Angeles (LGB - LAX/SNA) Operational
Miami (MIA) Operational
Minneapolis (MSP) Operational
Minneapolis (STP) Operational
Montreal (YUL) Operational
New York (LGA) Operational
Newark (EWR) Operational
Palo Alto (PAO) Operational
Phoenix (PHX) Operational
Portland (PDX) Operational
San Jose (SJC) Operational
Seattle (SEA) Operational
St. Louis (STL) Operational
Toronto (YYZ) Operational
Vancouver (YVR) Operational
South America Operational
Bogota (BOG) Operational
Buenos Aires (EZE) Operational
Curitiba (CWB) Operational
Lima (LIM) Operational
Rio de Janeiro (GIG) Operational
Santiago (SCL) Operational
Sāo Paulo (CGH) Operational
Sāo Paulo (GRU) Operational
Europe Operational
Amsterdam (AMS) Operational
Copenhagen (CPH) Operational
Dublin (DUB) Operational
Frankfurt (FRA) Operational
Frankfurt (HHN) Operational
Helsinki (HEL) Operational
London (LCY) Operational
London (LHR) Operational
London (LON) Operational
Madrid (MAD) Operational
Manchester (MAN) Operational
Marseille (MRS) Operational
Milan (MXP) Operational
Munich (MUC) Operational
Oslo (OSL) Operational
Paris (CDG) Operational
Stockholm (BMA) Operational
Vienna (VIE) Operational
Asia/Pacific Operational
Auckland (AKL) Operational
Brisbane (BNE) Operational
Dubai (FJR) Operational
Hong Kong (HKG) Operational
Melbourne (MEL) Operational
Osaka (ITM) Operational
Perth (PER) Operational
Singapore (QPG) Operational
Singapore (SIN) Operational
Sydney (SYD) Operational
Tokyo (HND) Operational
Tokyo (NRT) Operational
Tokyo (TYO) Operational
Wellington (WLG) Operational
Africa Operational
Cape Town (CPT) Operational
Ghana (ACC) Operational
Johannesburg (JNB) Operational
India Operational
Chennai (MAA) Operational
Mumbai (BOM) Operational
New Delhi (DEL) Operational
Edge Cloud Services Operational
Fastly API Operational
Fastly Configuration Application Operational
Fastly WAF Operational
Configuration Deployment Operational
DNS Systems Operational
Geolocation Data Operational
Historical Stats ? Operational
Image Optimization Operational
On-the-fly Packager Operational
Purging Operational
Real Time Analytics Operational
Streaming Logs Operational
TLS Provisioning Operational
Fastly Systems Operational
Billing System Operational
Customer Support Ticketing System ? Operational
Customer Support Phone System Operational
Customer Support Chat System Operational
Fastly Documentation Site Operational
Fastly Marketing Site Operational
Fastly Status Page Operational
Business Continuity Operational
COVID-19 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Fastly engineering teams will be performing maintenance as part of the retirement of Shared and Shared Wildcards TLS certificates, as well as Certificate Procurement, Management, and Hosting beginning June 28th at 12:00 UTC. After this date, TLS management systems for certificate lifecycle management (including ordering, reissuing, and renewal) for Shared and Procured TLS certificates will be unavailable. All certificate and TLS domain management will now be in the Fastly TLS web interface for your TLS domains and certificates, including domains migrated from Shared and Procured TLC certificates.

Fastly has been migrating TLS domains actively since November 2020 and most customers have already completed this process. If you have not already self-migrated or worked with Fastly support to migrate your domains, you will need to complete this before the maintenance begins on June 28th to prevent TLS traffic interruptions.

Update: Start date moved from June 14th, 2021 to June 28th, 2021
Posted on May 6, 20:44 UTC
Control Plane Maintenance Jun 30, 21:00-21:30 UTC
Fastly will be performing scheduled maintenance on the Fastly Application and API. These services will be placed in maintenance mode on 2021-06-30 at 21:00 UTC until 21:30 UTC.

During this scheduled maintenance, customers will not be able to access service configurations through the Fastly App, and service API calls (with the exception of purging), will return a 503 status code. Historical stats, and WAF rule configuration will also be unavailable. Edge delivery, purging (except purge_all), stats aggregation, and all other content delivery services will be unaffected.
Posted on May 26, 13:26 UTC
Changes to Fastly IP Address Space Jul 6, 00:00 - Jul 7, 00:00 UTC
On July 6, 2021, Fastly will remove some of our public IP addresses which are currently advertised as being used to retrieve content from customer origins. We recommend removing them from any appropriate access lists as soon as possible.

The IP addresses are being removed from the following existing block:
Today’s block: 146.75.0.0/16
Starting July 6, 2021 will become: 146.75.0.0/17

Because the IP addresses have never been used by Fastly for origin connections, customers who wish to do so may update their origin access control lists to the new, smaller block immediately without impacting Fastly’s ability to retrieve content from their origins.

The Fastly IP API endpoint has been updated to reflect this change to help alert customers who use it to monitor for Fastly IP address changes. You can find information about accessing the list of Fastly’s IPs with this API here:

https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges

If you need any clarification or have any concerns regarding this change, please contact Fastly Support through https://support.fastly.com or by emailing support@fastly.com.
Posted on May 20, 21:32 UTC
As part of Fastly’s continuing network expansions, we’re excited to announce two changes to our billing regions:

- A new point of presence (POP) in Seoul, South Korea (ICN) with a concurrent launch of the new South Korea billing region. The South Korea billing region rates will be the same as our current (South) Africa billing region rates.
- The current Brazil billing region will be merged into the current South America billing region with no change to the current South America billing region’s rates.

Fastly’s standard billing rates are located at https://www.fastly.com/pricing

No action is required if you intend to send traffic through the new POP in Seoul at the South Korea billing region rate and to send traffic to the Brazil POPs at the South America billing region rate.

To give customers time to decide whether to take advantage of these changes, we are giving a minimum of 45 days notice before implementing them. Starting no sooner than Aug 2, 2021, customers who have not opted out of the South Korea or South America billing regions will be subject to their respective billing rates on the traffic served from these POPs. Opt-out requests received after July 26, 2021 cannot be guaranteed to go into effect before these changes go live. To opt out of Fastly billing regions, contact support@fastly.com.
Posted on Jun 15, 20:33 UTC
Past Incidents
Jun 24, 2021

No incidents reported today.

Jun 23, 2021
Completed - The scheduled maintenance has been completed.
Jun 23, 00:00 UTC
Update - Scheduled maintenance is still in progress. We will provide updates as necessary.
Jun 16, 00:58 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 15, 00:01 UTC
Scheduled - Fastly will be performing scheduled maintenance on our Amsterdam, (AMS) data center from 2021-06-15 to 2021-06-23. Each night during traffic low periods in the region, from 00:00 to 02:00 UTC, end users may observe connection resets as traffic is migrated onto new hardware.
Jun 14, 12:29 UTC
Jun 22, 2021
Resolved - This incident has been resolved.
Jun 22, 16:08 UTC
Identified - We're investigating elevated errors in Rio de Janeiro (GIG). All other locations and services are unaffected
Jun 22, 14:33 UTC
Completed - The scheduled maintenance has been completed.
Jun 22, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 21, 16:00 UTC
Scheduled - As part of Fastly’s continuing network expansions, we’re excited to announce a new point of presence (POP) in Accra, Ghana (ACC). Concurrently, we will be launching the new Africa billing region which will replace the current South Africa billing region and will include this new POP in Ghana as well as the existing POPs in the current South Africa billing region. The Africa billing region rates will be the same as our current South Africa billing region rates. Fastly’s standard billing rates are located at https://www.fastly.com/pricing.

No action is required if you intend to send traffic through the new POP in Ghana at the Africa billing region rates.

To give customers time to decide whether to take advantage of this new POP, we are giving 45 days notice before sending traffic to the new POP. Starting June 21, 2021, customers who have not opted out of the Africa billing region will be subject to the Africa billing region billing rates on the traffic served from this new POP. Opt-out requests received after June 7, 2021 cannot be guaranteed to go into effect before the POP goes live. To opt out of the Africa billing region POPs, contact support@fastly.com.
May 4, 17:21 UTC
Resolved - This incident has been resolved.
Jun 22, 15:22 UTC
Identified - We're investigating elevated errors in Los Angeles (LGB). All other locations and services are unaffected
Jun 22, 14:48 UTC
Jun 21, 2021
Completed - The scheduled maintenance has been completed.
Jun 21, 18:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 21, 15:02 UTC
Scheduled - As part of Fastly’s global network expansion, we will be adding a Ghana, West Africa (ACC) data center to Fastly's Africa network.

Traffic served by our ACC data center will be aggregated into our Africa region for billing and stats purposes. We expect that some traffic currently served by our data centers in neighboring regions will shift to ACC. As such, some customers may see a change in their bills. Fastly’s standard billing rates are located at https://www.fastly.com/pricing.
Jun 18, 20:06 UTC
Jun 20, 2021

No incidents reported.

Jun 19, 2021

No incidents reported.

Jun 18, 2021
Completed - The scheduled maintenance has been completed.
Jun 18, 07:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 17, 23:00 UTC
Scheduled - Fastly will be adding capacity at our Cape Town, South Africa (CPT) data center. End-users may observe connection resets as traffic is migrated onto new hardware.

In order for customers who use this POP as an Origin Shield to leverage new cache nodes for an expanded cache footprint, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf 7 days after this maintenance window closes.

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. 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). Customers with any questions or concerns should contact Fastly’s Support team (support@fastly.com).
Jun 16, 16:07 UTC
Jun 17, 2021
Jun 16, 2021
Jun 15, 2021
Jun 14, 2021
Resolved - Fastly Engineers detected a performance impacting event affecting the availability of manage.fastly.com and API from approximately 2021-06-14 19:45 UTC to 2021-06-14 20:12 UTC. CDN delivery, stats aggregation, and all other data plane services were unaffected. The issue has been resolved and we are monitoring performance closely.
Jun 14, 20:51 UTC
Completed - The scheduled maintenance has been completed.
Jun 14, 03:36 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 14, 00:00 UTC
Scheduled - Fastly will be adding capacity at our Amsterdam, Netherlands (AMS) data center. End-users may observe connection resets as traffic is migrated onto new hardware.

In order for customers who use this POP as an Origin Shield to leverage new cache nodes for an expanded cache footprint, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf 7 days after this maintenance window closes.

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. 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). Customers with any questions or concerns should contact Fastly’s Support team (support@fastly.com).
Jun 9, 21:41 UTC
Jun 13, 2021

No incidents reported.

Jun 12, 2021

No incidents reported.

Jun 11, 2021

No incidents reported.

Jun 10, 2021
Resolved - Fastly Engineers detected a performance impacting event affecting the Los Angeles (BUR) & Vancouver (YVR) data centers from approximately 2021-06-10 04:14 UTC to 2021-06-10 04:19 UTC. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Jun 10, 04:31 UTC