Fly.io Status · History · Incident #6831

RESOLVED

HTTP/2 traffic disruptions

Minor · Started Aug 31, 2026 · 3:30 PM

  • Duration

    < 1m

  • Severity

    Minor

  • Detection lead

  • User reports

Summary

HTTP/2 traffic disruptions

A configuration update caused temporary failures for incoming HTTP/2 traffic for Fly Machines located on a subset of hosts for a few minutes. This incident has since been resolved. Managed Postgres depends on HTTP/2 and some control plane ops may have been affected as well. However, downstream Postgres connections were unlikely to have been affected by this since they do not use the HTTP2 handler.


  • Started

    Aug 31, 2026 · 3:30 PM

  • Resolved

    Aug 31, 2026 · 3:30 PM

  • Duration

    < 1m

  • Severity

    None

Event timeline

How this incident unfolded

  • Resolved

    Aug 31 · 3:42 PM Fly.io

    A configuration update caused temporary failures for incoming HTTP/2 traffic for Fly Machines located on a subset of hosts for a few minutes. This incident has since been resolved. Managed Postgres depends on HTTP/2 and some control plane ops may have been affected as well. However, downstream Postgres connections were unlikely to have been affected by this since they do not use the HTTP2 handler.

Get alerted before the next Fly.io outage.

Pulsetic catches degradations minutes before vendors acknowledge them.