We are investigating elevated errors to our Ashburn (IAD), Boston (BOS), Buenos Aires (EZE), Chicago (CHI), Columbus (CMH), Miami (MIA), Santiago (SCL) Point of Presence (POP).

All other products and services are unaffected by this incident.

Our engineers have identified the contributing factor and are applying a fix for our Ashburn (IAD), Boston (BOS), Buenos Aires (EZE), Chicago (CHI), Columbus (CMH), Miami (MIA), and Santiago (SCL) POP.

Our engineers have identified an additional contributing factor and are applying an adjusted mitigation strategy to Buenos Aires (EZE), Santiago (SCL), Ashburn (IAD), Boston (BOS), Chicago (CHI), Columbus (CMH), Miami (MIA) POPs.

All other locations and services are unaffected.

Engineering has confirmed the impact to Buenos Aires (EZE), Santiago (SCL), Ashburn (IAD), Boston (BOS), Chicago (CHI), Columbus (CMH), Miami (MIA) POPs has been mitigated.

Engineering has confirmed that Buenos Aires (EZE), Santiago (SCL), Ashburn (IAD), Boston (BOS), Chicago (CHI), Columbus (CMH), Miami (MIA) POPs has been fully restored. Customers may have experienced elevated errors and increased latency from 00:25 to 01:45 UTC.

This incident is resolved.

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

To offer feedback on our status page, click "Give Feedback" 

Status Post, Created Date/Time: 2025-04-03 00:51:46 UTC 

Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.

Traffic in St. Louis (STL) has been temporarily rerouted.

All other locations and services are unaffected.

Fastly will be adding capacity at our Newark (EWR) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 11 March 2025 at 06: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).

The scheduled maintenance has been completed.

To offer feedback on our status page, click "Give Feedback" 

Fastly will be adding capacity at our Denver (DEN) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 06 March 2025 at 13: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).

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Fastly Engineering has extended the scheduled maintenance and is currently in progress. We will provide updates as necessary.

The scheduled maintenance has been completed.

To offer feedback on our status page, click "Give Feedback" 

Fastly Engineers detected a performance impacting event affecting the Columbus (LCK), Minneapolis (STP) data centers.

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

Fastly Engineers detected a performance impacting event affecting the Atlanta (PDK), Dallas (DFW) data centers.

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

Fastly will be performing scheduled maintenance on our Seattle (BFI) data center from 23 January 2025, 09:00 UTC - 23 January 2025, 13:00 UTC.

During this time frame traffic in BFI will be operating with reduced capacity and some traffic will be redirected to neighboring POPs in the region.

The scheduled maintenance has been completed.

To offer feedback on our status page, click "Give Feedback" 

Fastly Engineers detected a performance impacting event affecting the Seattle (BFI) data center.

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

We are investigating elevated errors to our Bogota (BOG) and Dallas (DFW) Points of Presence (POP).

All other products and services are unaffected by this incident.

Our engineers have identified the contributing factor and are applying a fix to our Bogota (BOG) and Dallas (DFW) POPs. 

All other locations and services are unaffected.

Engineering has confirmed the impact to our Bogota (BOG) and Dallas (DFW) POPs has been mitigated.

Engineering has confirmed that our Bogota (BOG) and Dallas (DFW) POPs have been fully restored. Customers may have experienced backend errors and increased latency from 20:50 to 21:14 UTC.

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

This incident is resolved.

To offer feedback on our status page, click "Give Feedback" 

Status Post, Created Date/Time: 2025-01-15 21:16:33 UTC 

Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.

Traffic in Los Angeles (LAX) has been temporarily rerouted. All other locations and services are unaffected.

This event has been resolved.

To offer feedback on our status page, click "Give Feedback" 

Status Post, Created Date/Time: 2025-01-14 00:13:21 UTC 

Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.