Subscribe to UpdatesSubscribe
Get email notifications whenever Fly.io creates, updates or resolves an incident.
Get text message notifications whenever Fly.io creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get webhook notifications whenever Fly.io creates an incident, updates an incident, resolves an incident or changes a component status.
Visit our support site.
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Scheduled Maintenance
Network maintenance in IAD Jun 14, 2026 04:00-12:00 UTC
An upstream provider is performing network maintenance on a subset of hosts in IAD on 2026-06-14, from 04:00 UTC to 12:00 UTC. A loss of connectivity for up to 1 hour is possible within the scheduled maintenance window.
Posted on Jun 05, 2026 - 14:30 UTC
Posted on Jun 05, 2026 - 14:30 UTC
Past Incidents
Jun 6, 2026
No incidents reported today.
Jun 5, 2026
No incidents reported.
Jun 4, 2026
Resolved -
We have restored the degraded Consul cluster. All affected functionality is now working correctly: Unmanaged Postgres and LiteFS with dynamic leases.
Jun 4, 17:03 UTC
Jun 4, 17:03 UTC
Monitoring -
We have restored the degraded Consul cluster and are monitoring for stability. All affected functionality should now be working correctly: Unmanaged Postgres and LiteFS with dynamic leases.
Jun 4, 16:02 UTC
Jun 4, 16:02 UTC
Identified -
One of our Consul clusters is in degraded state due to a failed node. This can cause issues with LiteFS primary node selection, Unmanaged Postgres (14.x and older *only*), and creation of new Unmanaged Postgres clusters.
Impact is limited to these legacy products and does not affect deployments, running Fly applications in general, or Managed Postgres clusters.
Jun 4, 13:44 UTC
Impact is limited to these legacy products and does not affect deployments, running Fly applications in general, or Managed Postgres clusters.
Jun 4, 13:44 UTC
Jun 3, 2026
No incidents reported.
Jun 2, 2026
No incidents reported.
Jun 1, 2026
Resolved -
This incident has been resolved.
Jun 1, 18:43 UTC
Jun 1, 18:43 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 1, 18:35 UTC
Jun 1, 18:35 UTC
Investigating -
We're currently investigating an issue affecting flyctl ssh console functionality and machines' OIDC tokens.
Jun 1, 18:33 UTC
Jun 1, 18:33 UTC
Completed -
The scheduled maintenance has been completed.
Jun 1, 07:05 UTC
Jun 1, 07:05 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 1, 04:00 UTC
Jun 1, 04:00 UTC
Scheduled -
An upstream provider is performing network maintenance on a subset of hosts in IAD on 2026-06-01, from 04:00 UTC (00:00am local time) to 12:00 UTC (8:00am local time). A loss of connectivity for up to 1 hour is possible within the scheduled maintenance window.
May 31, 12:56 UTC
May 31, 12:56 UTC
May 31, 2026
Resolved -
This incident has been resolved.
May 31, 10:52 UTC
May 31, 10:52 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 31, 07:03 UTC
May 31, 07:03 UTC
Investigating -
We're working with our upstream providers to investigate an IPv6 networking failure in ORD.
May 31, 06:34 UTC
May 31, 06:34 UTC
May 30, 2026
Resolved -
This incident has been resolved.
May 30, 13:37 UTC
May 30, 13:37 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 30, 13:32 UTC
May 30, 13:32 UTC
Identified -
Due to an upstream provider issue, Private Networking (6PN) is currently degraded in SYD region. Communication between Machines in SYD region and Machines in other regions may fail at this time. Newly created Machines in SYD may fail to sync to other regions (may not show up in Machines API List endpoint, or state may be incorrect).
Additionally, TLS certificate resolution and Machines API authentication may currently be degraded in the SYD region.
We are working with our upstream providers to resolve this issue.
May 30, 13:29 UTC
Additionally, TLS certificate resolution and Machines API authentication may currently be degraded in the SYD region.
We are working with our upstream providers to resolve this issue.
May 30, 13:29 UTC
Resolved -
This incident has been resolved.
May 30, 04:21 UTC
May 30, 04:21 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 30, 03:37 UTC
May 30, 03:37 UTC
Identified -
We identified the issue and are working on a fix.
May 30, 03:13 UTC
May 30, 03:13 UTC
Investigating -
We're investigating an increase in deployment errors affecting some users. At this time, creating or updating Machines may erroneously fail with the message: "We require your billing information, please add it at https://fly.io/dashboard//billing".
May 30, 02:42 UTC
May 30, 02:42 UTC
May 29, 2026
Resolved -
This incident has been resolved.
May 29, 19:45 UTC
May 29, 19:45 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 29, 19:21 UTC
May 29, 19:21 UTC
Identified -
We are aware of increased latency and connection drops for clients located near Chicago (ORD) and are currently working on a fix.
May 29, 19:09 UTC
May 29, 19:09 UTC
Resolved -
This incident has been resolved.
May 29, 16:50 UTC
May 29, 16:50 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 29, 10:22 UTC
May 29, 10:22 UTC
Investigating -
We are currently investigating increased latency and dropped connections in ORD (Chicago).
May 29, 06:59 UTC
May 29, 06:59 UTC
Resolved -
This incident has been resolved.
May 29, 01:27 UTC
May 29, 01:27 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 29, 01:00 UTC
May 29, 01:00 UTC
Investigating -
We are currently investigating increased latency and dropped connections in ORD (Chicago).
May 29, 00:42 UTC
May 29, 00:42 UTC
May 28, 2026
Resolved -
This incident has been resolved.
May 28, 23:07 UTC
May 28, 23:07 UTC
Update -
We are continuing to monitor for any further issues.
May 28, 22:34 UTC
May 28, 22:34 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 28, 22:33 UTC
May 28, 22:33 UTC
Identified -
We're still seeing connection issues originating from SJC/LAX/West Coast US and are still investigating.
May 28, 22:25 UTC
May 28, 22:25 UTC
Monitoring -
We have implemented a mitigation for the issue and are monitoring for stability. This issue happened on the edge hosts in SJC, which means that any traffic near/around SJC would have been affected during the incident. We will provide a more detailed write-up on our Infra Log (https://fly.io/infra-log/) later once we have a better picture of the entire incident.
May 28, 21:56 UTC
May 28, 21:56 UTC
Investigating -
We are currently investigating increased latency in SJC.
May 28, 21:08 UTC
May 28, 21:08 UTC
May 27, 2026
Resolved -
This incident has been resolved.
May 27, 12:52 UTC
May 27, 12:52 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 27, 12:13 UTC
May 27, 12:13 UTC
Identified -
Due to an upstream provider issue, Private Networking (6PN) is currently degraded in SYD region. Communication between Machines in SYD region and Machines in other regions may fail at this time. Newly created Machines in SYD may fail to sync to other regions (may not show up in Machines API List endpoint, or state may be incorrect).
Additionally, TLS certificate resolution and Machines API authentication may currently be degraded in the SYD region.
We are working with our upstream providers to resolve this issue.
May 27, 11:54 UTC
Additionally, TLS certificate resolution and Machines API authentication may currently be degraded in the SYD region.
We are working with our upstream providers to resolve this issue.
May 27, 11:54 UTC
Resolved -
This incident has been resolved.
May 27, 04:36 UTC
May 27, 04:36 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 27, 04:07 UTC
May 27, 04:07 UTC
Investigating -
We are investigating elevated API Latency. Users may see delays or errors creating apps, as well as on some dashboard pages.
May 27, 03:50 UTC
May 27, 03:50 UTC
May 26, 2026
Resolved -
This incident has been resolved.
May 26, 19:06 UTC
May 26, 19:06 UTC
Identified -
The EWR region is low on available host capacity. Creating new machines, or starting currently stopped/suspended machines, may fail at this time.
We are working on provisioning new host capacity in the region. Please consider using nearby regions such as ord if possible.
May 26, 17:34 UTC
We are working on provisioning new host capacity in the region. Please consider using nearby regions such as ord if possible.
May 26, 17:34 UTC
May 25, 2026
No incidents reported.
May 24, 2026
Resolved -
This incident has been resolved.
May 24, 23:07 UTC
May 24, 23:07 UTC
Monitoring -
Network performance has been restored and we're continuing to monitor.
May 23, 02:14 UTC
May 23, 02:14 UTC
Investigating -
We're currently looking into this issue.
May 23, 01:01 UTC
May 23, 01:01 UTC
May 23, 2026