New York (LGA)

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.

Platform North America New York (LGA)
 
17 September 2026, 05:00 UTC

Fastly will be adding capacity at our New York (LGA) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 17 September 2026 at 05:00 UTC.

Our estimated duration is 5h. 

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.

 
17 September 2026, 10:00 UTC

The scheduled maintenance has been completed.


Platform North America New York (LGA)
 
16 September 2026, 05:00 UTC

Fastly will be adding capacity at our New York (LGA) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 16 September 2026 at 05:00 UTC.

Our estimated duration is 5h. 

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.

 
16 September 2026, 10:00 UTC

The 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 Ashburn (IAD) Atlanta (PDK) Boston (BOS) Calgary (YYC) Detroit (DTW) Los Angeles (LAX) Miami (MIA) Montreal (YUL) New York (LGA) San Jose (SJC) Toronto (YYZ)
 
28 March 2026, 00:55 UTC

We are investigating elevated errors to multiple Points of Presence:  Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), Los Angeles (LAX)

Customers may experience intermittent periods of increased latency and elevated errors while we investigate into the contributing factors causing this impact.

 
28 March 2026, 01:39 UTC

Our engineers believe they have identified contributing factor causing the issue impacting the Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), Los Angeles (LAX) status page component.

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.

 
28 March 2026, 01:54 UTC

Engineering has deployed a fix and have confirmed recovery to Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), Los Angeles (LAX) POPs. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

All other services were unaffected by this incident.


 
28 March 2026, 01:59 UTC

Our engineers have confirmed that our Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Detroit (DTW), Miami (MIA), Montreal (YUL), New York (LGA), San Jose (SJC), Toronto (YYZ), and Los Angeles (LAX) Points of Presence have been fully restored.

Customers may have experienced intermittent periods of increased latency and elevated errors from March 28, 2026 at 00:55 to 01:33 UTC.

This incident is resolved. Affected customers would 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-03-28 01:16:07 UTC  

15 December 2025, 13:07 UTC
Platform North America New York (LGA)
 
15 December 2025, 13:07 UTC

Traffic in New York (LGA) has been temporarily rerouted.

All other locations and services are unaffected.

05 September 2024, 19:48 UTC
Platform North America Europe Asia Australia / New Zealand South America Africa Amsterdam (AMS) Adelaide (ADL) Seoul (ICN) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Auckland (AKL) Ghana (ACC) Ashburn (IAD) Dubai (FJR) Brisbane (BNE) Dubai (DXB) Buenos Aires (EZE) Johannesburg (JNB) Brussels (BRU) Christchurch (CHC) Fujairah (FJR) Curitiba (CWB) Copenhagen (CPH) Hong Kong (HKG) Melbourne (MEL) Fortaleza (FOR) Dublin (DUB) Perth (PER) Lima (LIM) Atlanta (PDK) Sydney (SYD) Rio de Janeiro (GIG) Boston (BOS) Frankfurt (FRA) Kuala Lumpur (KUL) Santiago (SCL) Calgary (YYC) Wellington (WLG) Chicago (CHI) Helsinki (HEL) Manila (MNL) Sao Paulo (GRU) Osaka (ITM) London (LCY) London (LHR) London (LON) Chicago (ORD) Chennai (MAA) Singapore (QPG) Columbus (CMH) Lisbon (LIS) Madrid (MAD) Dallas (DFW) Denver (DEN) Manchester (MAN) Detroit (DTW) Marseille (MRS) Tokyo (NRT) Tokyo (TYO) Honolulu (HNL) Hyderabad (HYD) Milan (LIN) Houston (IAH) Milan (MXP) 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) Minneapolis (STP) Vienna (VIE) Montreal (YUL) Newark (EWR) Mumbai (BOM) New York (LGA) New York (NYC) Palo Alto (PAO) New Delhi (DEL) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) 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 New York (LGA)
 
14 August 2024, 08:00 UTC

Fastly will be adding capacity at our New York (LGA) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 14 August 2024 at 08:00 UTC.

Our estimated duration is 10h. 

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

 
14 August 2024, 19:00 UTC

The scheduled maintenance has been completed.

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

Platform North America Europe Amsterdam (AMS) Ashburn (IAD) Brussels (BRU) Copenhagen (CPH) Dublin (DUB) Atlanta (PDK) Boston (BOS) Frankfurt (FRA) Calgary (YYC) Chicago (CHI) Helsinki (HEL) London (LCY) London (LHR) London (LON) Chicago (ORD) Columbus (CMH) Lisbon (LIS) Madrid (MAD) Dallas (DFW) Denver (DEN) Manchester (MAN) Detroit (DTW) Marseille (MRS) Honolulu (HNL) Milan (LIN) Houston (IAH) Milan (MXP) Oslo (OSL) Kansas City (MCI) Munich (MUC) Los Angeles (BUR) Los Angeles (LAX) Paris (PAR) Rome (FCO) Sofia (SOF) Stockholm (BMA) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Vienna (VIE) 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"