HTTP/2 traffic disruptions
Aug 31, 15:30 UTCAug 31, 15:30 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
Fly.io, 90 days
48 incidents
Affected
Not listed by the vendor.
Final update
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.
Timeline
- Resolved · Aug 31, 15:30 UTC
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.
More from Fly.io
Full historyGitHub connections reset - sign in with GitHub again to restore GitHub deployslasted 3h 37mLAX region outagelasted 2dIntermittent errors pushing images to Fly.io Registrylasted 0mIPv6 egress issues on a subset of IAD hostslasted 23mEmergency network maintenance on a subset of hosts in ORDlasted 14mElevated Machine start failures in ARNlasted 1h 1m