Chicago (CHI)

18 November 2026, 01:50 UTC
Platform North America Ashburn (IAD) Atlanta (PDK) Boston (BOS) Calgary (YYC) Chicago (CHI) Chicago (ORD) Columbus (CMH) Dallas (DFW) Denver (DEN) Detroit (DTW) Honolulu (HNL) Houston (IAH) Jacksonville (JAX) Kansas City (MCI) Los Angeles (HHR) Los Angeles (BUR) Los Angeles (LAX) McAllen (MFE) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) New York (TSS) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
18 November 2026, 01:50 UTC

We're investigating possible performance impact affecting the North America data centers.

All other locations and services are unaffected.

 
18 November 2026, 03:51 UTC

Our engineers have identified the contributing factor causing the issue impacting our services in North America.

Mitigation actions are in progress, and we are seeing early signs of improvement. We will post a new update once recovery is confirmed.

All other products and services remain unaffected by this incident.

 
18 November 2026, 03:57 UTC

Engineering has deployed a fix and have confirmed a gradual recovery to North America POPs. We will continue to monitor until we’ve confirmed that customer and end user experience has been fully restored.

All other networks and services were unaffected by this incident.

 
18 November 2026, 04:07 UTC

Engineering has confirmed that North America POPs have been fully restored. Customers may have experienced elevated errors and latency from 1:50 to 3:34 UTC.

This incident is resolved.

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


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.

Status Post, Created Date/Time:   2026-11-18 02:57:01 UTC  

Platform North America Asia Australia / New Zealand Auckland (AKL) Ashburn (IAD) Dubai (DXB) Atlanta (PDK) Boston (BOS) Chicago (CHI) Columbus (CMH) Dallas (DFW) Denver (DEN) Detroit (DTW) Jacksonville (JAX) Los Angeles (HHR) Los Angeles (BUR) Los Angeles (LAX) Miami (MIA) Minneapolis (MSP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Portland (PDX) San Jose (SJC) Seattle (BFI) Toronto (YYZ)
 
04 November 2026, 01:04 UTC

Between 00:21 UTC and 00:24 UTC on November 4, 2026, we experienced a performance impact to the  Auckland (AKL), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Chicago (CHI), Columbus (CMH), Dallas (DFW), Denver (DEN), Detroit (DTW) , Dubai (DXB),  Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Newark (EWR), Palo Alto (PAO), Portland (PDX), San Jose (SJC), Seattle (BFI), Toronto (YYZ), New York (NYC), Los Angeles (LAX), Los Angeles (HHR), Jacksonville (JAX) Point of Presence (POPs).

During this time, customers may have experienced elevated errors and latency.

The issue has been resolved, and all services are operating normally. No other POPs or services were affected.

12 September 2026, 07:30 UTC
Platform North America Chicago (CHI)
 
12 September 2026, 07:30 UTC

Fastly will be performing scheduled maintenance on our Chicago (CHI) data center from 12 September 2026, 07:30 UTC - 12 September 2026, 12:00 UTC.

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

 
12 September 2026, 12:00 UTC
This scheduled maintenance has been completed.
Platform North America Chicago (CHI)
 
10 September 2026, 10:02 UTC

Between 10:02 UTC and 10:45 UTC on September 10, 2026, we experienced an issue with our delivery service at our Chicago (CHI) Point of Presence (POP).

During this time, customers may have experienced intermittent errors on requests routed through this POP.

The issue has been resolved, and all services are operating normally.

Platform North America Asia Chicago (CHI) Columbus (CMH) Tokyo (NRT) Los Angeles (HHR) Los Angeles (BUR) Los Angeles (LAX) Phoenix (PHX) Toronto (YYZ)
 
23 August 2026, 01:06 UTC

Between 01:06 UTC and 01:51 UTC on August 23, 2026, Fastly Engineers detected a performance impacting event affecting the Tokyo (NRT), Chicago (CHI), Columbus (CMH), Los Angeles (BUR), Phoenix (PHX), Toronto (YYZ), Los Angeles (LAX), Los Angeles (HHR) Points of Presence (POPs).

During this time, customers with traffic routed through these locations may have experienced elevated error rates or latency. All other data centers and services were unaffected.

The issue has been resolved and we are monitoring performance closely.

22 August 2026, 01:20 UTC
Platform North America Chicago (CHI)
 
22 August 2026, 01:20 UTC

We are investigating elevated errors to our Chicago (CHI) Point of Presence (POP).

All other products and services are unaffected by this incident.

 
22 August 2026, 04:06 UTC

We have identified the cause of elevated latency affecting a subset of edge POPs served by our Chicago (CHI) shield.

Engineers are actively working on a mitigation. We understand how critical this service is to your operations and apologize for the disruption.

All other products and services are unaffected by this incident.

 
22 August 2026, 04:28 UTC

Engineering has confirmed the impact to the subset of edge POPs served by our Chicago (CHI) shield has been mitigated.

 
22 August 2026, 04:42 UTC

Engineering has confirmed that a subset of edge POPs served by our Chicago (CHI) shield has been fully restored. Customers may have experienced elevated latency from 01:20 to 04:05 UTC.

This incident is resolved.




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.

Status Post, Created Date/Time:   2026-08-22 04:06:19 UTC  

Platform North America Chicago (CHI)
 
04 June 2026, 05:00 UTC

Fastly will be adding capacity at our Chicago (CHI) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 04 June 2026 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 at https://support.fastly.com.

 
04 June 2026, 09:00 UTC
This scheduled maintenance has been completed.
16 April 2026, 17:13 UTC
Platform North America Europe Asia Australia / New Zealand South America Africa Amsterdam (AMS) Seoul (ICN) Bangkok (BKK) Bogota (BOG) Ghana (ACC) Ashburn (IAD) Amsterdam (RTM) Brasilia (BSB) Dubai (DXB) Buenos Aires (EZE) Brussels (BRU) Christchurch (CHC) Fujairah (FJR) Copenhagen (CPH) Melbourne (MEL) Fortaleza (FOR) Dublin (DUB) Lima (LIM) Atlanta (PDK) Sydney (SYD) Rio de Janeiro (GIG) Boston (BOS) Frankfurt (FRA) Santiago (SCL) Calgary (YYC) Sydney (WSI) Wellington (WLG) Chicago (CHI) Helsinki (HEL) Sao Paulo (GRU) London (LCY) London (LON) Singapore (QPG) Lisbon (LIS) Madrid (MAD) Dallas (DFW) Denver (DEN) Manchester (MAN) Detroit (DTW) Tokyo (NRT) Honolulu (HNL) Milan (BGY) Hyderabad (HYD) Milan (LIN) Houston (IAH) Milan (MXP) Jacksonville (JAX) Oslo (OSL) Kansas City (MCI) Munich (MUC) Los Angeles (BUR) Los Angeles (LAX) Paris (PAR) Rome (FCO) Kolkata (CCU) Sofia (SOF) Stockholm (BMA) Miami (MIA) Minneapolis (MSP) Montreal (YUL) Mumbai (BOM) New York (LGA) New Delhi (DEL) Phoenix (PHX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
16 April 2026, 17:13 UTC

We are investigating elevated errors to our Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL), Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Dublin (DUB), Frankfurt (FRA), Helsinki (HEL), Lisbon (LIS), London (LCY), London (LON), Madrid (MAD), Manchester (MAN), Milan (LIN), Milan (MXP), Munich (MUC), Oslo (OSL), Rome (FCO), Sofia (SOF), Stockholm (BMA), Christchurch (CHC), Dubai (DXB), Fujairah (FJR), Melbourne (MEL), Seoul (ICN), Singapore (QPG), Sydney (SYD), Tokyo (NRT), Wellington (WLG), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG), Santiago (SCL), Ghana (ACC), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Chicago (CHI), Dallas (DFW), Denver (DEN), Detroit (DTW), Gainesville (GNV), Honolulu (HNL), Houston (IAH), Kansas City (MCI), Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Phoenix (PHX), San Jose (SJC), Seattle (BFI), St. Louis (STL), Toronto (YYZ), Vancouver (YVR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Sydney (WSI), Amsterdam (RTM), Jacksonville (JAX), Milan (BGY), Brasilia (BSB) Points of Presence (POPs).

All other products and services are unaffected by this incident.

 
16 April 2026, 18:22 UTC

Our engineers believe they have identified contributing factor causing the issue impacting our Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL), Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Dublin (DUB), Frankfurt (FRA), Helsinki (HEL), Lisbon (LIS), London (LCY), London (LON), Madrid (MAD), Manchester (MAN), Milan (LIN), Milan (MXP), Munich (MUC), Oslo (OSL), Rome (FCO), Sofia (SOF), Stockholm (BMA), Christchurch (CHC), Dubai (DXB), Fujairah (FJR), Melbourne (MEL), Seoul (ICN), Singapore (QPG), Sydney (SYD), Tokyo (NRT), Wellington (WLG), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG), Santiago (SCL), Ghana (ACC), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Chicago (CHI), Dallas (DFW), Denver (DEN), Detroit (DTW), Gainesville (GNV), Honolulu (HNL), Houston (IAH), Kansas City (MCI), Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Phoenix (PHX), San Jose (SJC), Seattle (BFI), St. Louis (STL), Toronto (YYZ), Vancouver (YVR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Sydney (WSI), Amsterdam (RTM), Jacksonville (JAX), Milan (BGY), Brasilia (BSB) POPs.

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.

 
16 April 2026, 18:28 UTC

Engineering has confirmed the impact to our Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL), Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Dublin (DUB), Frankfurt (FRA), Helsinki (HEL), Lisbon (LIS), London (LCY), London (LON), Madrid (MAD), Manchester (MAN), Milan (LIN), Milan (MXP), Munich (MUC), Oslo (OSL), Rome (FCO), Sofia (SOF), Stockholm (BMA), Christchurch (CHC), Dubai (DXB), Fujairah (FJR), Melbourne (MEL), Seoul (ICN), Singapore (QPG), Sydney (SYD), Tokyo (NRT), Wellington (WLG), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG), Santiago (SCL), Ghana (ACC), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Chicago (CHI), Dallas (DFW), Denver (DEN), Detroit (DTW), Gainesville (GNV), Honolulu (HNL), Houston (IAH), Kansas City (MCI), Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Phoenix (PHX), San Jose (SJC), Seattle (BFI), St. Louis (STL), Toronto (YYZ), Vancouver (YVR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Sydney (WSI), Amsterdam (RTM), Jacksonville (JAX), Milan (BGY), Brasilia (BSB) POPs has been mitigated.

 
16 April 2026, 18:29 UTC

Engineering has confirmed that our Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL), Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Dublin (DUB), Frankfurt (FRA), Helsinki (HEL), Lisbon (LIS), London (LCY), London (LON), Madrid (MAD), Manchester (MAN), Milan (LIN), Milan (MXP), Munich (MUC), Oslo (OSL), Rome (FCO), Sofia (SOF), Stockholm (BMA), Christchurch (CHC), Dubai (DXB), Fujairah (FJR), Melbourne (MEL), Seoul (ICN), Singapore (QPG), Sydney (SYD), Tokyo (NRT), Wellington (WLG), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG), Santiago (SCL), Ghana (ACC), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Chicago (CHI), Dallas (DFW), Denver (DEN), Detroit (DTW), Gainesville (GNV), Honolulu (HNL), Houston (IAH), Kansas City (MCI), Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Phoenix (PHX), San Jose (SJC), Seattle (BFI), St. Louis (STL), Toronto (YYZ), Vancouver (YVR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Sydney (WSI), Amsterdam (RTM), Jacksonville (JAX), Milan (BGY), Brasilia (BSB) POPs  have been fully restored.

Customers may have experienced elevated 5xx errors from 17:13  to 17:45  UTC.

This incident is resolved.



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.

Status Post, Created Date/Time:    2026-04-16 18:21:26 UTC    

Platform North America Chicago (CHI)
 
26 March 2026, 23:09 UTC

Fastly Engineers detected a performance impacting event affecting the Chicago (CHI) data center.

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

Platform North America Europe Frankfurt (FRA) Chicago (CHI) London (LCY) London (LHR) Lisbon (LIS) Detroit (DTW) Paris (PAR) Rome (FCO)
 
29 November 2025, 20:13 UTC

We are investigating elevated errors to our Frankfurt (FRA), Lisbon (LIS), London (LCY), Rome (FCO), Chicago (CHI), Detroit (DTW), Paris (PAR) Points of Presence (POPs)

All other products and services are unaffected by this incident.

 
29 November 2025, 20:52 UTC

Our engineers believe they have identified contributing factor causing the issue impacting our Frankfurt (FRA), Lisbon (LIS), London (LCY), Rome (FCO), Chicago (CHI), Detroit (DTW), Paris (PAR) POPs.

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.

 
29 November 2025, 21:27 UTC

Engineering has confirmed the impact to our Frankfurt (FRA), Lisbon (LIS), London (LCY), Rome (FCO), Chicago (CHI), Detroit (DTW), Paris (PAR) POPs has been mitigated.

 
29 November 2025, 21:52 UTC

Engineering has confirmed that our Frankfurt (FRA), Lisbon (LIS), London (LCY), Rome (FCO), Chicago (CHI), Detroit (DTW), Paris (PAR) POPs  have been fully restored. Customers may have experienced elevated errors and increased latency  from 20:13  to 21:20  UTC.

This incident is resolved.

12/12 A retrospective into this incident identified that London (LHR) had also experienced elevated errors and increased periods of latency as a result of this incident. Component has been added to reflect accurate data.

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

Status Post, Created Date/Time: 2025-11-29 20:35:29 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.