Fastly incident

CDN Global Performance Impact

Major Resolved View vendor source →

Fastly experienced a major incident on April 16, 2026 affecting North America and Ashburn (IAD) and 1 more component, lasting 1h 16m. The incident has been resolved; the full update timeline is below.

Started
Apr 16, 2026, 05:13 PM UTC
Resolved
Apr 16, 2026, 06:29 PM UTC
Duration
1h 16m
Detected by Pingoru
Apr 16, 2026, 05:13 PM UTC

Affected components

North AmericaAshburn (IAD)Atlanta (PDK)Boston (BOS)Calgary (YYC)Chicago (CHI)Dallas (DFW)Denver (DEN)Detroit (DTW)Gainesville (GNV)

Update timeline

  1. investigating Apr 16, 2026, 05:13 PM 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.

  2. investigating Apr 16, 2026, 06:22 PM 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.

  3. monitoring Apr 16, 2026, 06:28 PM 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.

  4. resolved Apr 16, 2026, 06:29 PM 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