Fastly will be adding capacity at our Atlanta (PDK) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 18 November 2024 at 05:00 UTC.

Our estimated duration is 8h. 

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 Atlanta (PDK) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 04 November 2024 at 05:00 UTC.

Our estimated duration is 8h. 

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" 

We are investigating elevated errors to our Platform delivery services.

Our engineers are continuing to investigate the impact to our Platform delivery services.

Our engineers have identified the contributing factor and are applying a fix to our Platform delivery services.

Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Platform delivery services.

Engineering has deployed a fix and have confirmed a gradual recovery to our Platform delivery service. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

Engineering has confirmed that our Platform delivery services have been fully restored. Customers may have experienced elevated errors and latency. In addition, Compute customers may have also experienced delayed configuration deployments from the 5th of September at 19:48 to the 6th of September at 00:48 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" 

At approximately 08:00 UTC our engineers began to investigate a large traffic event impacting performance within our Europe and North America regions. 

Standard traffic engineering practices have been deployed in response to this event, in an effort to reduce the potential impact to our customers within the regions. Customer may continue to see elevated errors and latency as mitigation efforts continue to be deployed.

All other products and services are unaffected by this incident.

Our engineers are implementing adjusted mitigation strategies in our North America and Europe regions to continue to balance traffic and manage performance.

Error rates and latency have improved, although customers may still experience intermittent periods of performance impact as traffic engineering continues to be deployed.

Engineering has implemented mitigation strategies and has confirmed a gradual recovery in our North America and Europe regions. 

We are closely monitoring performance in these regions as a top priority as this event continues and will provide a final update once customer and end user experience has been fully restored.

Engineering has confirmed that Europe and North America regions have been fully restored. Customers may have experienced elevated errors and latency from 08:00 to 16:37 UTC.

This incident is resolved.

Affected customers would 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" 

Fastly Engineers detected a performance impacting event affecting the Atlanta (PDK) 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 Atlanta (PDK) Point of Presence (POP).

Our engineers have identified the contributing factor and are developing a fix for our Atlanta (PDK) POP.

This event has been resolved.

Fastly will be performing a scheduled maintenance on our Atlanta (PDK) data center on 12/21/2023 from 10:00AM UTC through 14:00 UTC.

During this maintenance, a portion of traffic will be redirected to neighboring POPs in the region. Additionally, customers may experience increased origin traffic.

The scheduled maintenance has been completed.

Fastly will be expanding Atlanta (ATL) into the Atlanta (PDK) Metro POP starting on 2023-11-28 at 05:00 UTC. End-users may observe connection resets as traffic is migrated onto new hardware.

When this change is applied, customers may observe additional origin traffic as new cache nodes in the Atlanta (PDK) Metro POP retrieve content from origin.

The scheduled maintenance has been completed.

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).

The scheduled maintenance has been completed.

Fastly will be expanding Atlanta (PDK) 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 Atlanta (PDK) 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

The scheduled maintenance has been completed.