Atlanta (PDK)

17 November 2025, 02:02 UTC
Platform North America Atlanta (PDK)
 
17 November 2025, 02:02 UTC

We are investigating elevated errors to our Atlanta (PDK) Point of Presence (POP).

All other products and services are unaffected by this incident.

 
17 November 2025, 02:44 UTC

Our engineers believe they have identified contributing factor causing the issue impacting the Atlanta (PDK) Point of Presence (POP).

We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery.

All other products and services are unaffected by this incident.

 
17 November 2025, 02:57 UTC

Engineering has confirmed the impact to Atlanta (PDK) POP has been mitigated.

 
17 November 2025, 04:59 UTC

This event has been resolved.

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

Status Post, Created Date/Time: 2025-11-17 02:38:06 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.


Platform North America Atlanta (PDK) Dallas (DFW)
 
29 January 2025, 17:38 UTC

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.

Platform North America Atlanta (PDK)
 
18 November 2024, 05:00 UTC

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

 
18 November 2024, 13:00 UTC

The scheduled maintenance has been completed.

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

Platform North America Atlanta (PDK)
 
04 November 2024, 05:00 UTC

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

 
04 November 2024, 13:00 UTC

The scheduled maintenance has been completed.

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

05 September 2024, 19:48 UTC
Platform North America Europe Asia South America Oceania Africa Amsterdam (AMS) Adelaide (ADL) Bogota (BOG) Cape Town (CPT) Auckland (AKL) Buenos Aires (EZE) Ghana (ACC) Ashburn (IAD) Brussels (BRU) Brisbane (BNE) Curitiba (CWB) Johannesburg (JNB) Copenhagen (CPH) Christchurch (CHC) Bangkok (BKK) Fortaleza (FOR) Atlanta (ATL) Dublin (DUB) Melbourne (MEL) Lima (LIM) Frankfurt (FRA) Perth (PER) Atlanta (PDK) Frankfurt (HHN) Rio de Janeiro (GIG) Boston (BOS) Helsinki (HEL) Sydney (SYD) Santiago (SCL) Calgary (YYC) Chennai (MAA) London (LCY) Wellington (WLG) Sāo Paulo (CGH) Chicago (CHI) London (LON) Sao Paulo (GRU) London (LHR) Lisbon (LIS) Dubai (FJR) Dubai (DXB) Madrid (MAD) Fujairah (FJR) Chicago (ORD) Manchester (MAN) Hong Kong (HKG) Marseille (MRS) Columbus (CMH) Hyderabad (HYD) Milan (LIN) Columbus (LCK) Milan (MXP) Oslo (OSL) Dallas (DFW) Munich (MUC) Denver (DEN) Detroit (DTW) Kolkata (CCU) Gainesville (GNV) Paris (CDG) Honolulu (HNL) Paris (PAR) Rome (FCO) Kuala Lumpur (KUL) Houston (IAH) Sofia (SOF) Stockholm (BMA) Manila (MNL) Kansas City (MCI) Mumbai (BOM) Vienna (VIE) Los Angeles (BUR) Los Angeles (LAX) New Delhi (DEL) Osaka (ITM) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) Seoul (ICN) New York (NYC) Singapore (QPG) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Tokyo (HND) Seattle (BFI) Tokyo (NRT) Tokyo (TYO) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
05 September 2024, 19:48 UTC

We are investigating elevated errors to our Platform delivery services.

 
05 September 2024, 21:44 UTC

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

 
05 September 2024, 22:01 UTC

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

 
05 September 2024, 23:00 UTC

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

 
05 September 2024, 23:34 UTC

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.

 
06 September 2024, 00:48 UTC

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

Platform North America Europe Amsterdam (AMS) Ashburn (IAD) Brussels (BRU) Copenhagen (CPH) Atlanta (ATL) Dublin (DUB) Frankfurt (FRA) Atlanta (PDK) Frankfurt (HHN) Boston (BOS) Helsinki (HEL) Calgary (YYC) London (LCY) Chicago (CHI) London (LON) London (LHR) Lisbon (LIS) Madrid (MAD) Chicago (ORD) Manchester (MAN) Marseille (MRS) Columbus (CMH) Milan (LIN) Columbus (LCK) Milan (MXP) Oslo (OSL) Dallas (DFW) Munich (MUC) Denver (DEN) Detroit (DTW) Gainesville (GNV) Paris (CDG) Honolulu (HNL) Paris (PAR) Rome (FCO) Houston (IAH) Sofia (SOF) Stockholm (BMA) Kansas City (MCI) Vienna (VIE) Los Angeles (BUR) Los Angeles (LAX) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
23 July 2024, 12:48 UTC

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.

 
23 July 2024, 14:29 UTC

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.

 
23 July 2024, 16:37 UTC

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.

 
23 July 2024, 23:52 UTC

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

Platform North America Atlanta (PDK)
 
24 May 2024, 22:29 UTC

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.

06 January 2024, 03:17 UTC
Platform North America Atlanta (PDK)
 
06 January 2024, 03:17 UTC

We are investigating elevated errors to our Atlanta (PDK) Point of Presence (POP).

 
06 January 2024, 04:34 UTC

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

 
06 January 2024, 05:39 UTC

This event has been resolved.

21 December 2023, 10:00 UTC
Platform North America Atlanta (PDK)
 
21 December 2023, 10:00 UTC

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.

 
21 December 2023, 14:00 UTC

The scheduled maintenance has been completed.

28 November 2023, 05:00 UTC
Platform North America Atlanta (ATL) Atlanta (PDK)
 
28 November 2023, 05:00 UTC

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.

 
05 December 2023, 05:00 UTC

The scheduled maintenance has been completed.