Intermittent CDN Performance Impact
This incident has been resolved.
Fastly Engineers have completed the deployment of a fix for this issue to all affected cache nodes. We continue to monitor the results.
Fastly Engineers have completed the deployment of a fix for this issue to affected cache nodes in all in APAC and South African POPs, as well as the majority of European POPs.
Fastly Engineers have completed the deployment of a fix for this issue to affected cache nodes in all North and South American POPs.
Fastly has identified an issue that has caused increased 5XX errors for customer origins with a Maximum Segment Size (MSS) higher than 1460 bytes. A fix has been identified and is being deployed to affected cache nodes.
This incident affected: Europe (Amsterdam (AMS), Copenhagen (CPH), Dublin (DUB), Frankfurt (FRA), Frankfurt (HHN), Helsinki (HEL), London (LCY), London (LHR), London (LON), Madrid (MAD), Manchester (MAN), Milan (MXP), Oslo (OSL), Paris (CDG), Stockholm (BMA), Vienna (VIE)), South America (Buenos Aires (EZE), Bogota (BOG), Curitiba (CWB), Rio de Janeiro (GIG), Santiago (SCL), Sāo Paulo (GRU)), South Africa (Cape Town (CPT), Johannesburg (JNB)), Asia/Pacific (Auckland (AKL), Brisbane (BNE), Dubai (FJR), Hong Kong (HKG), Melbourne (MEL), Osaka (ITM), Perth (PER), Singapore (SIN), Sydney (SYD), Tokyo (HND), Tokyo (TYO), Wellington (WLG)), India (Chennai (MAA), Mumbai (BOM), New Delhi (DEL)), and North America (Ashburn (BWI), Ashburn (DCA), Ashburn (IAD), Ashburn (WDC), Atlanta (FTY), Atlanta (PDK), Boston (BOS), Chicago (CHI), Chicago (MDW), Chicago (ORD), Chicago (PWK), Columbus (CMH), Dallas (DAL), Dallas (DFW), Denver (DEN), Houston (IAH), Jacksonville (JAX), Kansas City (MCI), Los Angeles (BUR), Los Angeles (LAX), Miami (MIA), Minneapolis (MSP), Minneapolis (STP), Montreal (YUL), New York (LGA), Newark (EWR), Palo Alto (PAO), San Jose (SJC), Seattle (SEA), St. Louis (STL), Toronto (YYZ), Vancouver (YVR)).