Fastly incident

Update to waitlist disconnect response codes

Resolved after 12 days 23 hours, affecting Customer Services and General Updates and 1 more, on September 2, 2026.

investigating Sep 02, 2026, 05:05 PM UTC

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.

Started
Sep 02, 2026, 05:05 PM UTC
Resolved
Sep 15, 2026, 05:00 PM UTC
Duration
12d 23h
Detected by Pingoru
Sep 02, 2026, 05:05 PM UTC

Affected components

Customer ServicesGeneral UpdatesFastlyFastlyCustomer ServicesFastlyFastlyFastlyCustomer ServicesCustomer Services

Update timeline

  1. investigating Sep 02, 2026, 05:05 PM UTC

    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.

  2. resolved Sep 15, 2026, 05:00 PM UTC

    This event has been resolved.

Your product runs on more than Fastly

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →