Fastly will be expanding Sāo Paulo (CGH) into a Metro POP. End-users may observe connection resets as traffic is migrated onto new hardware.

As part of this expansion, customers utilizing shielding in the neighboring Sāo Paulo (CGH) will be migrated to the new Metro POP. Once this maintenance window closes, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf after 14 days.

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin.

Action for Fastly Customers:

1. Please verify that all origins allow the full range of Fastly IP addresses (https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges), as this list is updated periodically. Failure to verify origin access lists will result in origin connection disruption. 
2. Customers with any questions or concerns should contact their dedicated technical account team or Fastly’s Support team at (support@fastly.com).

For more information on Metro POPs: https://developer.fastly.com/learning/concepts/pop/#metro-pops

Fastly will be migrating Atlanta (ATL and FTY) shield customers to Atlanta (PDK).

As part of this migration, customers utilizing shielding in Atlanta (ATL and FTY) will be migrated to Atlanta (PDK). Once this maintenance window closes, customers can either apply a new shield at a time of their choosing, or their shielding configuration will be updated to Atlanta (PDK) on their behalf after 14 days.

Customers may observe additional origin traffic as new cache nodes retrieve content from origin.

Action for Fastly Customers:

1. 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. Failure to verify origin access lists will result in origin connection disruption.

2. Customers with any questions or concerns should contact their dedicated technical account team or Fastly's Support team at (support@fastly.com).

Fastly will be adding capacity at our Houston (IAH) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 03 October 2023 at 05: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).

We're investigating possible performance impact affecting the Buenos Aires (EZE) data center.

All other locations and services are unaffected

This issue has been identified and a fix is being implemented. 

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are aware of a possible issue and are working to determine the scope and impact.

Update: Our investigations confirmed that there were no external impacts to our customer services or end user experiences. We've changed this status from "degraded performance" to "informational".

Our Engineering team had identified an internal issue that had risk for customer impact. Our Acute Incident Response teams have deployed a fix and are monitoring the results. 

Our network availability and all other locations were unaffected by this incident. Customers and their end users should not have seen impact as a result of this incident. 

This incident has been resolved.

We're investigating elevated errors in Columbus (CMH).

All other locations and services are unaffected

Fastly Engineering has identified a third party service provider issue that caused elevated latency and increased errors for customers within the Columbus (CMH) Point of Presence (POP). Engineering has rerouted customer traffic around the impacted region and services be gradually restoring across our network. 

We will continue to monitor the actions of the third party service provider and will resolve our status post once we've seen full recovery from the provider.

Update: An earlier status post: https://www.fastlystatus.com/incident/376077 has been closed. As the elevated errors observed when access our Control Plane (manage.fastly.com) and API services has been correlated to the third party service provider issue identified within this status post.

This incident has resolved.

During this incident, customers would have experienced increased latency and elevated 5xx errors in our Columbus (CMH) POP, as well as, elevated errors when attempting to access configuration management and API services through our Control Plane from 18:40 to 21:30 UTC.

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

Fastly Engineering has confirmed that our network availability and Control Plane services have been fully restored.

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.

Fastly will be performing scheduled maintenance on our Houston (IAH) data center from 19 September 2023, 06:00 UTC - 19 September 2023, 12:00 UTC.

During this time frame traffic will be redirected to neighboring POPs in the region.

Scheduled maintenance is currently in progress. We have extended completion time to 15:00 UTC.

Scheduled maintenance is currently in progress. We have extended completion time to 17:00 UTC.

Scheduled maintenance is currently in progress. We have extended completion time to 19:00 UTC.

The scheduled maintenance has been completed.

We're investigating elevated errors in Ashburn (IAD).

All other locations and services are unaffected

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

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

All other locations and services are unaffected.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.