Flightcontrol Outage History

Flightcontrol is up right now

Pingoru has recorded 195 incidents for Flightcontrol: 195 in the last 12 months and 75 in the last 90 days.

Source: status.flyio.net

195incidents recorded
195last 12 months
75last 90 days
3 hourstypical duration
Incidents per month
02040AprMayJunJulAugSepOct13
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct5%
Pingoru began tracking Flightcontrol in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20261379 of 720 (11%)
May 202629114 of 744 (15%)
June 202622100 of 720 (14%)
July 20261834 of 744 (5%)
August 20263334 of 744 (5%)
September 20262625 of 720 (3%)
October 20261330 of 575 (5%)

Incidents, newest first

Major May 19, 2026 Logs issues in IAD 1h 40m Logs, Metrics

Started May 19, 2026, 07:16 PM UTC· resolved May 19, 2026, 08:56 PM UTC

  1. investigating May 19, 2026, 07:16 PM UTC

    We are investigating an issue with logs and metrics in IAD region. New logs and metrics from machines in IAD region may be missing, but past logs/metrics are still accessible. Apps continue to run.

  2. resolved May 19, 2026, 08:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 19, 2026 Proxy issues in SIN region 44m Management Plane - SIN, SIN - Singapore

Started May 19, 2026, 11:15 AM UTC· resolved May 19, 2026, 12:00 PM UTC

  1. investigating May 19, 2026, 11:15 AM UTC

    We are investigating issues with fly-proxy on a subset of hosts in the Singapore region. Apps are still running, but requests to/from some apps may fail, and some Managed Postgres clusters may be inaccessible.

  2. monitoring May 19, 2026, 11:22 AM UTC

    A fix has been implemented and we are seeing proxy performance in SIN return to normal. All Managed Postgres clusters in the region are reachable. We are continuing to monitor to ensure stable recovery.

  3. resolved May 19, 2026, 12:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 16, 2026 Some Managed Postgres clusters in FRA are unreachable 2h 25m Management Plane - FRA

Started May 16, 2026, 12:45 PM UTC· resolved May 16, 2026, 03:10 PM UTC

  1. investigating May 16, 2026, 12:45 PM UTC

    We are currently investigating this issue.

  2. investigating May 16, 2026, 12:45 PM UTC

    We are continuing to investigate this issue.

  3. identified May 16, 2026, 01:22 PM UTC

    The issue has been identified and a fix is being implemented.

  4. identified May 16, 2026, 01:40 PM UTC

    Some of unreachable clusters are showing recovery. We are still fixing the root cause.

  5. monitoring May 16, 2026, 02:03 PM UTC

    All affected clusters have recovered

  6. resolved May 16, 2026, 03:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 15, 2026 fly ssh console returns error 500 55m

Started May 15, 2026, 04:29 PM UTC· resolved May 15, 2026, 05:24 PM UTC

  1. identified May 15, 2026, 04:29 PM UTC

    A problem with our vault used to issue temporary certificates for SSH sessions is causing calls to `fly ssh console` and `fly console` to return error 500. Our team has identified the cause and is deploying a fix.

  2. monitoring May 15, 2026, 04:40 PM UTC

    We've deployed a fix and are monitoring as error rates normalize. `fly ssh console` should be working now.

  3. resolved May 15, 2026, 05:24 PM UTC

    This issue has been resolved, fly ssh console invocations are now working correctly.

Read the full incident report →

Major May 11, 2026 log search unavailable 45m Logs

Started May 11, 2026, 08:02 PM UTC· resolved May 11, 2026, 08:48 PM UTC

  1. investigating May 11, 2026, 08:02 PM UTC

    Log search in Grafana is currently unavailable. You may see `failed to make http request: 503` errors when accessing logs from fly-metrics.net at this time. App logs are still available using the `fly logs` command and in the Fly.io dashboard.

  2. monitoring May 11, 2026, 08:32 PM UTC

    A fix has been implemented and we are monitoring the results. Logs should again be available through Log search in Grafana.

  3. resolved May 11, 2026, 08:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 11, 2026 Upstash Redis Outage 4h 4m Upstash for Redis

Started May 11, 2026, 02:36 PM UTC· resolved May 11, 2026, 06:41 PM UTC

  1. investigating May 11, 2026, 02:36 PM UTC

    We are working with Upstash to investigate issues with their Fly hosted Redis service. Users may see degraded or failing connections connecting to their Upstash Redis databases at this time.

  2. investigating May 11, 2026, 03:04 PM UTC

    We are continuing to work with Upstash on this issue.

  3. investigating May 11, 2026, 05:31 PM UTC

    We are continuing to work with Upstash on this issue. We have received reports of partial recovery for some users, however we are still seeing higher levels of degraded or failing connections connecting to Upstash Redis databases at this time.

  4. monitoring May 11, 2026, 06:26 PM UTC

    A fix has been implemented and we are seeing Upstash Redis connectivity return to normal across all regions. We continuing to monitor to ensure stable recovery.

  5. resolved May 11, 2026, 06:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 8, 2026 Certificate Issuance failing due to LetsEncrypt Outage 2h 24m SSL/TLS Certificate Provisioning

Started May 08, 2026, 06:45 PM UTC· resolved May 08, 2026, 09:09 PM UTC

  1. identified May 08, 2026, 08:25 PM UTC

    Due to a service outage at LetsEncrypt, creating new certificates with `fly certs add` is failing. Existing certificates and `*.fly.dev` preview certificates are not impacted. For additional details please see LetsEncrypt's statuspage https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/69fe2d6698ca07050eb4b1b3

  2. monitoring May 08, 2026, 09:02 PM UTC

    We are seeing recovery and certificates are now issuing normally. We are continuing to monitor to ensure full recovery.

  3. resolved May 08, 2026, 09:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 7, 2026 Connectivity issues in SJC 38m SJC - San Jose, California (US)

Started May 07, 2026, 05:49 PM UTC· resolved May 07, 2026, 06:28 PM UTC

  1. investigating May 07, 2026, 05:49 PM UTC

    Some hosts in SJC are currently experiencing an upstream network issue. Apps running on these hosts may be temporarily unavailable.

  2. monitoring May 07, 2026, 06:18 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 07, 2026, 06:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 7, 2026 Intermittent machines issues in BOM 1h 51m BOM - Mumbai, India

Started May 07, 2026, 10:16 AM UTC· resolved May 07, 2026, 12:08 PM UTC

  1. identified May 07, 2026, 10:16 AM UTC

    Creation and updating of machines in BOM are affected. Some metrics and logs for resources in BOM may be delayed.

  2. resolved May 07, 2026, 12:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 6, 2026 Elevated error rates on List Machines endpoint 34m Machines API

Started May 06, 2026, 12:06 AM UTC· resolved May 06, 2026, 12:41 AM UTC

  1. investigating May 06, 2026, 12:06 AM UTC

    We are currently investigating this issue.

  2. resolved May 06, 2026, 12:41 AM UTC

    We mitigated the problem. The issue only affected apps having machines in the sin region.

Read the full incident report →

Major May 5, 2026 Errors Setting/Updating Secrets 35m Machines API

Started May 05, 2026, 01:18 PM UTC· resolved May 05, 2026, 01:53 PM UTC

  1. investigating May 05, 2026, 01:18 PM UTC

    We are currently investigating this issue.

  2. investigating May 05, 2026, 01:19 PM UTC

    We are continuing to investigate this issue.

  3. investigating May 05, 2026, 01:22 PM UTC

    Creation of new apps or changing secrets on existing apps fails

  4. investigating May 05, 2026, 01:22 PM UTC

    Creation of new apps or changing secrets on existing apps fails

  5. resolved May 05, 2026, 01:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 28, 2026 flyctl deploy creating new app instances 49m Deployments

Started Apr 28, 2026, 11:50 PM UTC· resolved Apr 29, 2026, 12:40 AM UTC

  1. investigating Apr 28, 2026, 11:50 PM UTC

    We're investigating an issue where fly deploy is creating new Fly machine instances rather than updating existing ones, leading to apps with a mixed state. We're currently investigating the issue. As a workaround, please try removing the "processes = [ "app" ]" line from your fly.toml configuration file and redeploying - this should resolve the issue in the meantime.

  2. identified Apr 29, 2026, 12:07 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 29, 2026, 12:31 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 29, 2026, 12:40 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 24, 2026 Slow machines operations in IAD region 45m IAD - Ashburn, Virginia (US)

Started Apr 24, 2026, 10:45 PM UTC· resolved Apr 24, 2026, 11:31 PM UTC

  1. investigating Apr 24, 2026, 10:45 PM UTC

    We are currently investigating the issue. Only a portion of machines within the region are impacted.

  2. investigating Apr 24, 2026, 10:58 PM UTC

    We are deploying a partial mitigation while we continue investigating.

  3. investigating Apr 24, 2026, 11:18 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Apr 24, 2026, 11:19 PM UTC

    Network packet loss has returned to normal levels. We are monitoring the Machines API for stability.

  5. resolved Apr 24, 2026, 11:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 23, 2026 Errors when adding or editing Github integrations for deployments 1h 20m Dashboard

Started Apr 23, 2026, 03:05 PM UTC· resolved Apr 23, 2026, 04:26 PM UTC

  1. investigating Apr 23, 2026, 03:05 PM UTC

    We're investigating reports of "500" errors when trying to add a new Github integration or edit an existing Github integration in Fly.io/dashboard. This only affects "Launch an app from Github" or trying to change settings for an app set up this way. Existing integrations continue to work normally. It does not affect deploys done with `flyctl` or existing, running apps.

  2. identified Apr 23, 2026, 03:22 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Apr 23, 2026, 03:22 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Apr 23, 2026, 03:39 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Apr 23, 2026, 04:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 23, 2026 Errors (5xx, timeouts) in Fly.io dashboard 33m Dashboard

Started Apr 23, 2026, 11:17 AM UTC· resolved Apr 23, 2026, 11:50 AM UTC

  1. investigating Apr 23, 2026, 11:17 AM UTC

    We are investigating issues with web dashboard.

  2. identified Apr 23, 2026, 11:35 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 23, 2026, 11:45 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 23, 2026, 11:50 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 20, 2026 Increased latency in SIN 3h 9m SIN - Singapore

Started Apr 20, 2026, 02:29 PM UTC· resolved Apr 20, 2026, 05:38 PM UTC

  1. identified Apr 20, 2026, 03:29 PM UTC

    We are currently working on resolving increased latencies in our Singapore region.

  2. resolved Apr 20, 2026, 05:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 17, 2026 TLS certificate issues 1d 7h SSL/TLS Certificate Provisioning

Started Apr 17, 2026, 01:06 PM UTC· resolved Apr 18, 2026, 08:42 PM UTC

  1. investigating Apr 17, 2026, 01:06 PM UTC

    We are investigating an issue with the Vault server that stores TLS certificates. Provisioning new TLS certificates may fail, and connecting to domains whose existing certificate has not yet been cached may fail.

  2. monitoring Apr 17, 2026, 03:34 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 18, 2026, 08:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 15, 2026 Network issues in SYD 23h 51m

Started Apr 15, 2026, 11:08 AM UTC· resolved Apr 16, 2026, 10:59 AM UTC

  1. investigating Apr 15, 2026, 11:08 AM UTC

    We're currently investigating some networking issues in SYD. This is affecting a number of our central services.

  2. monitoring Apr 15, 2026, 11:40 AM UTC

    We've identified the issue and applied a fix. All services should be working as normal.

  3. resolved Apr 16, 2026, 10:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 12, 2026 Heightened latency in ORD 4h 12m

Started Apr 12, 2026, 06:50 PM UTC· resolved Apr 12, 2026, 11:03 PM UTC

  1. investigating Apr 12, 2026, 06:50 PM UTC

    We are currently investigating heightened network latency in ORD.

  2. monitoring Apr 12, 2026, 07:26 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 12, 2026, 11:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 10, 2026 Managed Postgres control plane instability in NRT (Tokyo) 3h 5m Management Plane - NRT

Started Apr 10, 2026, 06:42 PM UTC· resolved Apr 10, 2026, 09:48 PM UTC

  1. investigating Apr 10, 2026, 06:42 PM UTC

    We are investigating instability in the MPG control plane in the NRT (Toyko, Japan) region causing unexpected cluster failovers. Clusters return to health shortly after, but some users with clusters in NRT may see dropped connections or degraded performance at this time.

  2. identified Apr 10, 2026, 08:13 PM UTC

    The issue has been identified and a fix is being implemented. Users with clusters in NRT may continue to see instability at this time

  3. monitoring Apr 10, 2026, 08:32 PM UTC

    A fix has been implemented and we are seeing MPG performance in NRT normalize. We are continuing to monitor to ensure a stable recovery

  4. resolved Apr 10, 2026, 09:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 9, 2026 Unavailable hosts in ORD region 45m ORD - Chicago, Illinois (US)

Started Apr 09, 2026, 07:29 PM UTC· resolved Apr 09, 2026, 08:14 PM UTC

  1. investigating Apr 09, 2026, 07:29 PM UTC

    Some hosts in our Chicago (ORD) region are currently inaccessible. We are working with our provider to resolve this issue. To see if you are affected, please visit the personalized status page: https://fly.io/status A small amount of Managed Postgres clusters may also be inaccessible at this time.

  2. resolved Apr 09, 2026, 08:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 9, 2026 Managed Postgres Control Plane Issues in SYD 1h 39m Management Plane - SYD

Started Apr 09, 2026, 03:50 AM UTC· resolved Apr 09, 2026, 05:30 AM UTC

  1. investigating Apr 09, 2026, 03:50 AM UTC

    We are investigating elevated control plane issues for Managed Postgres clusters in SYD. The majority of clusters appear to be running fine, but new creates, backup restores, and upgrades may show errors or take longer than usual to complete. Some clusters will have seen a failover event from primary to standby.

  2. identified Apr 09, 2026, 04:12 AM UTC

    We are seeing an improvement in control plane performance in the SYD region. Some clusters in the region currently are showing degraded standby nodes and we are working to bring those back to full health.

  3. monitoring Apr 09, 2026, 05:20 AM UTC

    Control plane operations in SYD have returned to normal and all clusters are healthy at this time. We're continuing to monitor to ensure stable recovery.

  4. resolved Apr 09, 2026, 05:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 7, 2026 GraphQL API / Dashboard Issues 3h 8m Dashboard

Started Apr 07, 2026, 03:08 PM UTC· resolved Apr 07, 2026, 06:17 PM UTC

  1. investigating Apr 07, 2026, 03:08 PM UTC

    We are investigating issues with our GraphQL API and web dashboard

  2. identified Apr 07, 2026, 03:17 PM UTC

    We have restored GraphQL and dashboard availability, but some actions (e.g. app state updates) may still be delayed.

  3. monitoring Apr 07, 2026, 03:39 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 07, 2026, 06:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 29, 2026 Low Capacity in SIN and AMS regions 1h 1m AMS - Amsterdam, Netherlands, Sprites, SIN - Singapore

Started Mar 29, 2026, 03:00 PM UTC· resolved Mar 29, 2026, 04:01 PM UTC

  1. identified Mar 29, 2026, 03:00 PM UTC

    We are currently investigating elevated errors when creating and starting machines in the SIN and AMS regions. Choosing other regions to create or deploy may help in the meantime

  2. identified Mar 29, 2026, 03:13 PM UTC

    This may also affect: - Remote builders in AMS and SIN regions, which could currently be experiencing degraded performance or failures. - Sprites starting from a cold state, which may experience failures in starting

  3. identified Mar 29, 2026, 03:19 PM UTC

    We are currently investigating capacity issues in SIN and AMS regions that are affecting: - Machine Create and Start events - Deployments, due to affected, degraded Remote Builders - Sprite startup from cold state

  4. monitoring Mar 29, 2026, 03:33 PM UTC

    We've freed up additional room in the SIN and AMS regions and are monitoring capacity.

  5. monitoring Mar 29, 2026, 03:35 PM UTC

    We've freed up additional room in the SIN and AMS regions and are monitoring capacity.

  6. resolved Mar 29, 2026, 04:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 27, 2026 Low capacity in IAD 3h 42m Deployments, IAD - Ashburn, Virginia (US)

Started Mar 27, 2026, 06:08 PM UTC· resolved Mar 27, 2026, 09:51 PM UTC

  1. investigating Mar 27, 2026, 06:08 PM UTC

    We're currently investigating capacity issues in IAD that is preventing machine starts (machine creates are currently unaffected). This may result in deploys failing to complete (even for apps outside of the IAD region). As a workaround, using legacy Fly builders explicitly located in another region (i.e., `FLY_REMOTE_BUILDER_REGION=lhr fly deploy --depot=false --recreate-builder`) may help in the meantime.

  2. investigating Mar 27, 2026, 06:47 PM UTC

    We're continuing to evaluate our options for increasing short-term capacity in the IAD region.

  3. identified Mar 27, 2026, 07:21 PM UTC

    We've brought some additional capacity online in IAD and are seeing improvements, and we're continuing to work on adding more and freeing up additional room.

  4. monitoring Mar 27, 2026, 09:09 PM UTC

    With the additional capacity we've brought online, machine start failure rates in IAD have now recovered. We'll continue to monitor IAD capacity.

  5. resolved Mar 27, 2026, 09:51 PM UTC

    This incident has been resolved.

Read the full incident report →