Fastly

Fastly is updating how a subset of client disconnects are reported for Delivery (Varnish) Services. Previously, these disconnects returned a 503 (Service Unavailable) response code. As part of a fix for an issue affecting our ERROR-WAIT handling, we changed this behavior so a subset of these disconnects now return a 499 (Client Closed Request) and will have an ERROR-DISCONNECT state. This change will be rolling out gradually over the next few weeks.  What you may notice: You may see an increase in 499 response codes and a corresponding decrease in 503 response codes for waitlist disconnects in your logs and dashboards. This is expected and does not indicate a new issue with your service. What you need to do: If you have monitoring, alerting, or automation that treats 503s and 499s differently, review your configuration to confirm it accounts for this change. If you have questions, contact your Fastly support team.

Fastly is updating how a subset of client disconnects are reported for Delivery (Varnish) Services. Previously, these disconnects returned a 503 (Service Unavailable) response code. As part of a fix for an issue affecting our ERROR-WAIT handling, we changed this behavior so a subset of these disconnects now return a 499 (Client Closed Request) and will have an ERROR-DISCONNECT state. This change will be rolling out gradually over the next few weeks.  What you may notice: You may see an increase in 499 response codes and a corresponding decrease in 503 response codes for waitlist disconnects in your logs and dashboards. This is expected and does not indicate a new issue with your service. What you need to do: If you have monitoring, alerting, or automation that treats 503s and 499s differently, review your configuration to confirm it accounts for this change. If you have questions, contact your Fastly support team.

We're investigating possible performance impact affecting the Los Angeles (LAX), Los Angeles (HHR) Points of Presence (POPs).All other locations and services are unaffected.

We are investigating elevated errors to our Manila (MNL) Point of Presence (POP) affecting customers with backends in the us-east-1 region. All other products and services are unaffected by this incident. We will provide another update as more information becomes available or within the next hour.

We are investigating an issue causing Next-Gen WAF (NGWAF) dashboard to display blank or missing performance data for some customers. This is a visible issue only - NGWAF protection and services are no impacted. Our engineers are actively working to diagnose the contributing factor. We will provide another update as more information becomes available or within the hour All other products and services are unaffected by this incident

We are investigating elevated errors to our Chicago (CHI) Point of Presence (POP).All other products and services are unaffected by this incident.

We are investigating a small number of requests receiving an empty response body where content is expected. Impact is limited to requests that use Streaming Miss and are eligible for HTTP response revalidation.All other products and services are unaffected by this incident.

Our engineers have identified a contributing factor causing reduced cache-hit performance for a subset of cache infrastructure serving Compute customers. Affected customers may see temporarily elevated origin load.A fix is being deployed to the affected nodes. Due to the scope of the change, full deployment will take some time. We will post updates as the rollout progresses.All other products and services remain unaffected by this incident.

We are investigating increased latency for purging at our Purging, Minneapolis (STP), Ranchi (IXR), Mumbai (QAI), Surat (STV), Ambala (QAV), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL), LA - Santa Clara (RHV), LA - West Florida (VNC), LA - Salt Lake City (BTF), LA - Denver (APA), LA - Pompano (PPM), LA - Richmond (RIC), LA - Nashville (BNA), LA - Memphis (MEM), LA - Pittsburgh (PIT), LA - Roseville (STP) Points of Presence (POPs). All other products and services are unaffected by this incident.

We are investigating elevated errors to our API & Configuration Management serviceAll other products and services are unaffected by this incident.