Flightcontrol Outage History
Flightcontrol is up right nowPingoru has recorded 195 incidents for Flightcontrol: 195 in the last 12 months and 75 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 13 | 79 of 720 (11%) |
| May 2026 | 29 | 114 of 744 (15%) |
| June 2026 | 22 | 100 of 720 (14%) |
| July 2026 | 18 | 34 of 744 (5%) |
| August 2026 | 33 | 34 of 744 (5%) |
| September 2026 | 26 | 25 of 720 (3%) |
| October 2026 | 13 | 30 of 571 (5%) |
Incidents, newest first
Critical July 20, 2026 High number of 5XX on the Machines API and dashboard 9h 59m Dashboard, Machines API
Started Jul 20, 2026, 07:10 AM UTC· resolved Jul 20, 2026, 05:09 PM UTC
- investigating Jul 20, 2026, 07:10 AM UTC
Existing machines are unaffected. We are investigating the issue.
- investigating Jul 20, 2026, 07:48 AM UTC
We are continuing to investigate this issue.
- identified Jul 20, 2026, 07:51 AM UTC
We've identified an internal service providing authentication to our Machines API has failed, our team is currently looking at our options for restoring this service. Existing Machines/Apps will continue to run as normal. Thank you for your patience.
- identified Jul 20, 2026, 07:52 AM UTC
We've identified an internal service providing authentication to our Machines API has failed, our team is currently looking at our options for restoring this service. Existing Machines/Apps will continue to run as normal. Thank you for your patience.
- monitoring Jul 20, 2026, 08:02 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jul 20, 2026, 09:14 AM UTC
Some Managed Postgres v1 clusters are degraded. We are working on fixing them. Managed Postgres v2 is unaffected.
- monitoring Jul 20, 2026, 01:34 PM UTC
We are still working on fixing degraded Managed Postgres clusters.
- resolved Jul 20, 2026, 05:09 PM UTC
This incident has been resolved.
Minor July 19, 2026 Egress IPv6 issues in BOM 1h 4m BOM - Mumbai, India
Started Jul 19, 2026, 03:48 AM UTC· resolved Jul 19, 2026, 04:52 AM UTC
- identified Jul 19, 2026, 03:48 AM UTC
We have identified an upstream issue that is preventing egress IPv6 addresses in BOM from reaching parts of the internet, and we're currently working with an upstream provider to resolve this issue. Normal IPv6 addresses remain unaffected.
- resolved Jul 19, 2026, 04:52 AM UTC
This incident has been resolved.
Notice July 17, 2026 Brief Flycast / MPG interruption in YYZ –
Started Jul 17, 2026, 06:30 PM UTC· resolved Jul 17, 2026, 06:30 PM UTC
- resolved Jul 17, 2026, 07:13 PM UTC
A bad deployment momentarily caused issues with Flycast connectivity, and, by extension, MPG, in our YYZ region. The deployment was immediately rolled back and connectivity was restored shortly after.
Minor July 16, 2026 App creation failing 22m Machines API
Started Jul 16, 2026, 11:54 AM UTC· resolved Jul 16, 2026, 12:17 PM UTC
- identified Jul 16, 2026, 11:54 AM UTC
An issue with our Machines API is causing app creations to fail in some cases. We are working on a fix.
- resolved Jul 16, 2026, 12:17 PM UTC
This incident has been resolved.
Minor July 16, 2026 Edge proxy issues 2h 10m Customer Applications
Started Jul 16, 2026, 11:34 AM UTC· resolved Jul 16, 2026, 01:44 PM UTC
- investigating Jul 16, 2026, 11:34 AM UTC
We are investigating increased connection latency and "connection reset" errors from our edge proxy. Apps continue to run, but requests may experience increased connection latency or fail at this time.
- monitoring Jul 16, 2026, 12:27 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 16, 2026, 01:44 PM UTC
This incident has been resolved.
Major July 14, 2026 Partial outage in SJC 2h 7m SJC - San Jose, California (US)
Started Jul 14, 2026, 02:51 PM UTC· resolved Jul 14, 2026, 04:59 PM UTC
- identified Jul 14, 2026, 02:51 PM UTC
A subset of hosts in SJC are currently offline. Some apps may be unreachable at this time.
- monitoring Jul 14, 2026, 03:53 PM UTC
A fix has been implemented and we are monitoring the results. Apps should be reachable at this point in time.
- resolved Jul 14, 2026, 04:59 PM UTC
This incident has been resolved.
Minor July 13, 2026 Some DFW hosts offline 33m DFW - Dallas, Texas (US)
Started Jul 13, 2026, 10:25 PM UTC· resolved Jul 13, 2026, 10:58 PM UTC
- investigating Jul 13, 2026, 10:25 PM UTC
A subset of hosts in DFW are currently offline, and we're investigating the issue.
- monitoring Jul 13, 2026, 10:36 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 13, 2026, 10:58 PM UTC
This incident has been resolved.
Minor July 9, 2026 Registry performance issues 31m Deployments
Started Jul 09, 2026, 03:33 PM UTC· resolved Jul 09, 2026, 04:04 PM UTC
- identified Jul 09, 2026, 03:33 PM UTC
The fly.io registry is currently experiencing capacity constraints that reduced performance and may lead to temporary high latency or failed pushes. We are currently working to add capacity and restore service.
- monitoring Jul 09, 2026, 03:55 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 09, 2026, 04:04 PM UTC
This incident has been resolved.
Minor July 9, 2026 Delays starting Depot Builders in IAD 56m Deployments, Remote Builds
Started Jul 09, 2026, 03:21 PM UTC· resolved Jul 09, 2026, 04:18 PM UTC
- identified Jul 09, 2026, 03:21 PM UTC
We have identified an issue causing delays or failures when starting depoting builders located in the IAD region. Customers with builders in IAD may see delays or timeouts starting builds during `fly deploy`. We are working on a fix. In the meantime customers can trigger a fly-hosted builder based deploy with `fly deploy --depot=false`. You can also change your builder region away from IAD via the `settings` tab of your Fly dashboard. We recommend DFW or ORD as alternate builder regions at this time. Please note, your builder region can differ from the region your machines are in.
- monitoring Jul 09, 2026, 03:43 PM UTC
A fix has been implemented and we are seeing improvements in builder performance, latency, and error rates. We are continuing to monitor for a full recovery. Customers still seeing issues can trigger a fly-hosted builder based deploy with `fly deploy --depot=false`.
- resolved Jul 09, 2026, 04:18 PM UTC
This incident has been resolved.
Major July 3, 2026 Partial Outage in ORD 1h 11m Management Plane - ORD, ORD - Chicago, Illinois (US)
Started Jul 03, 2026, 05:00 PM UTC· resolved Jul 03, 2026, 06:11 PM UTC
- investigating Jul 03, 2026, 05:00 PM UTC
We are investigating an issue with one of our upstream providers in ORD. Machines across a subset of hosts may be unreachable or not running correctly. Deploys with machines on these hosts may fail at this time. Some Managed Postgres clusters in ORD region may be unavailable or see connectivity issues at this time.
- identified Jul 03, 2026, 05:02 PM UTC
We've identified the issue as a networking hardware failure impacting a subset of hosts at one of our Upstream providers in ORD. We are working with our provider to restore connectivity.
- monitoring Jul 03, 2026, 05:49 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 03, 2026, 06:11 PM UTC
This incident has been resolved.
Major July 3, 2026 Partial outage in ORD 5h 48m Management Plane - ORD, ORD - Chicago, Illinois (US)
Started Jul 03, 2026, 12:11 AM UTC· resolved Jul 03, 2026, 05:59 AM UTC
- investigating Jul 03, 2026, 12:11 AM UTC
We are investigating an issue with one of our upstream providers in ORD. Machines across a subset of hosts may be unreachable or not running correctly. Deploys with machines on these hosts may fail at this time. Some Managed Postgres clusters in ORD region may be unavailable at this time.
- identified Jul 03, 2026, 12:29 AM UTC
We've identified and reported power issues with one of our upstream providers in ORD. We're waiting for an update from our upstream for a resolution. Some Managed Postgres clusters in ORD will be unavailable due to placement.
- identified Jul 03, 2026, 12:54 AM UTC
Our provider has advised us their facilities team is working on restoring the power, we'll provide another update as soon as we learn more.
- identified Jul 03, 2026, 02:59 AM UTC
Power restoration work in a subset of ORD is still in progress and impact remains ongoing for a subset of hosts and some Managed Postgres clusters.
- identified Jul 03, 2026, 04:21 AM UTC
Power restoration is ongoing and we're making sure the hosts are healthy before starting customer workloads to avoid issues. Customer impact remains and updates to come.
- monitoring Jul 03, 2026, 04:41 AM UTC
Customer workloads are now starting and we're monitoring the affected hosts. Affected Managed Postgres instances will be investigated.
- resolved Jul 03, 2026, 05:59 AM UTC
This incident has been resolved.
Critical July 2, 2026 Errors issuing new SSL certificates 1h 39m SSL/TLS Certificate Provisioning
Started Jul 02, 2026, 09:38 PM UTC· resolved Jul 02, 2026, 11:18 PM UTC
- investigating Jul 02, 2026, 09:38 PM UTC
We are currently investigating errors when issuing new SSL certificates for hostnames.
- identified Jul 02, 2026, 10:26 PM UTC
The issue has been identified and we are awaiting a fix.
- monitoring Jul 02, 2026, 10:50 PM UTC
A fix has been implemented upstream and certificates are being issued successfully. We will continue to monitor.
- resolved Jul 02, 2026, 11:18 PM UTC
This incident has been resolved.
Notice July 2, 2026 Performance issues in NTR (Tokyo) 11m Corrosion, NRT - Tokyo, Japan
Started Jul 02, 2026, 08:05 AM UTC· resolved Jul 02, 2026, 08:17 AM UTC
- investigating Jul 02, 2026, 08:05 AM UTC
A single host in the NTR region is experiencing some performance issues. The issue has been identified and our engineers are working on a resolution.
Minor July 1, 2026 Static Egress IPv6 issues in NRT 50m NRT - Tokyo, Japan
Started Jul 01, 2026, 01:06 PM UTC· resolved Jul 01, 2026, 01:57 PM UTC
- investigating Jul 01, 2026, 01:06 PM UTC
We are investigating issues with static egress IPv6 addresses in NRT region. Apps using static egress IPs may experience connectivity failures to some destinations.
- monitoring Jul 01, 2026, 01:44 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 01, 2026, 01:57 PM UTC
This incident has been resolved.
Major July 1, 2026 Elevated API Errors 1h 35m Dashboard
Started Jul 01, 2026, 06:14 AM UTC· resolved Jul 01, 2026, 07:50 AM UTC
- investigating Jul 01, 2026, 06:14 AM UTC
We are investigating elevated errors with our GraphQL API and background job processing
- identified Jul 01, 2026, 06:27 AM UTC
The cause of the errors has been identified and we are working on a fix.
- identified Jul 01, 2026, 07:05 AM UTC
A fix has been put in place, and we are no longer seeing elevated API errors. Some dashboard actions will be delayed while background processing catches up.
- monitoring Jul 01, 2026, 07:26 AM UTC
Background jobs have caught up and the API is fully operational. We are continuing to monitor service health.
- resolved Jul 01, 2026, 07:50 AM UTC
This incident has been resolved.
Minor June 30, 2026 Egress IP issues in SIN and NRT 18m NRT - Tokyo, Japan, SIN - Singapore
Started Jun 30, 2026, 01:45 PM UTC· resolved Jun 30, 2026, 02:03 PM UTC
- identified Jun 30, 2026, 01:45 PM UTC
We are aware of egress IP issues in SIN and NRT and are working on a fix. Some machines in SIN and NRT using egress IPs may temporarily lose connectivity or otherwise see degraded performance.
- monitoring Jun 30, 2026, 01:49 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 30, 2026, 02:03 PM UTC
This incident has been resolved.
Major June 29, 2026 Delayed Metrics 1d 21h Metrics
Started Jun 29, 2026, 01:03 AM UTC· resolved Jun 30, 2026, 10:19 PM UTC
- investigating Jun 29, 2026, 01:03 AM UTC
We are investigating issues with customer facing metrics in the fly-metrics.net dashboard. Users may see delayed or missing metrics at this time.
- identified Jun 29, 2026, 01:46 AM UTC
We've identified an issue on multiple hosts causing delayed metric ingestion into our hosted fly-metrics.net dashboards. We are working on a fix.
- identified Jun 29, 2026, 02:58 AM UTC
We are continuing to see delayed metric exports from a number of hosts. Users will see delayed or missing metrics for machines on impacted hosts at this time.
- identified Jun 29, 2026, 05:34 AM UTC
We are continuing to see delayed metrics due to resource contention on a subset of metrics ingestion hosts, and we are working to rebalance ingestion traffic and reduce the backlog.
- identified Jun 29, 2026, 08:43 AM UTC
We are still in the process of increasing the metrics cluster throughput to catch up with metric backlog.
- identified Jun 29, 2026, 03:56 PM UTC
Metric ingestion is still delayed for some customers. We’re seeing gradual improvement and continue to monitor the situation while the system catches up.
- identified Jun 29, 2026, 08:02 PM UTC
Backlogged metrics data is still being processed, continue to monitor the situation while the system catches up.
- identified Jun 30, 2026, 12:58 AM UTC
Backlogged metrics are still being processed and ingestion delays persist for some customers, but we’re continuing to see gradual improvement as the backlog continues to drain.
- identified Jun 30, 2026, 05:17 AM UTC
Backlogged metrics are still being processed and ingestion delays persist for some customers
- identified Jun 30, 2026, 04:50 PM UTC
Backlogged metrics are still being processed. We're bringing extra processing capacity online to speed up the process.
- identified Jun 30, 2026, 07:58 PM UTC
Almost all metrics have caught up aside from a small handful in `sin` and `syd`. We're continuing to monitor and expect these to complete in the next few hours.
- resolved Jun 30, 2026, 10:19 PM UTC
This incident has been resolved.
Major June 28, 2026 Metrics currently experiencing issues 13h 10m Metrics
Started Jun 28, 2026, 08:10 AM UTC· resolved Jun 28, 2026, 09:20 PM UTC
- investigating Jun 28, 2026, 08:10 AM UTC
We are currently investigating an issue with our metrics cluster.
- resolved Jun 28, 2026, 09:20 PM UTC
This incident has been resolved.
Major June 26, 2026 IPv6 Connectivity Issues in EWR 1h 30m EWR - Secaucus, NJ (US)
Started Jun 26, 2026, 10:17 PM UTC· resolved Jun 26, 2026, 11:48 PM UTC
- investigating Jun 26, 2026, 10:17 PM UTC
One of our upstream providers is experiencing IPv6 network connectivity problems in EWR. Apps with machines on affected hosts may have impacted connectivity to certain IPv6 destinations while they investigate and resolve this issue.
- monitoring Jun 26, 2026, 11:14 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 26, 2026, 11:48 PM UTC
This incident has been resolved.
Minor June 25, 2026 Deploys defaulting to Fly-hosted Builders 1h 56m Deployments
Started Jun 25, 2026, 01:41 PM UTC· resolved Jun 25, 2026, 03:38 PM UTC
- investigating Jun 25, 2026, 01:41 PM UTC
We are investigating delays provisioning Depot backed builders for deploys. We have switched the default `fly deploy` strategy to use fly hosted builders at this time. Users can still trigger a depot based deploy with `fly deploy --depot=true`
- monitoring Jun 25, 2026, 03:08 PM UTC
We are seeing improvements in Depot builder provision times and are switching the default deploy strategy back to them. We will continue to monitor builder performance closely. Users with a preference can trigger a Fly builder based deploy with `fly deploy --depot=false` or use `fly deploy --depot=true` to force a depot-based deployment.
- resolved Jun 25, 2026, 03:38 PM UTC
This incident has been resolved.
Minor June 25, 2026 Elevated control plane latency 3h 7m BOM - Mumbai, India, NRT - Tokyo, Japan
Started Jun 25, 2026, 12:11 PM UTC· resolved Jun 25, 2026, 03:18 PM UTC
- investigating Jun 25, 2026, 12:11 PM UTC
We're addressing elevated control plane latency and saturation affecting the BOM and NRT regions. Apps with machines in this region might experience longer response times and possible timeouts (502 errors).
- identified Jun 25, 2026, 01:20 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jun 25, 2026, 01:48 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 25, 2026, 03:18 PM UTC
This incident has been resolved.
Minor June 24, 2026 Degraded networking in North America 5h 15m EWR - Secaucus, NJ (US), IAD - Ashburn, Virginia (US), LAX - Los Angeles, California (US), ORD - Chicago, Illinois (US) and 2 more
Started Jun 24, 2026, 01:42 AM UTC· resolved Jun 24, 2026, 06:57 AM UTC
- investigating Jun 24, 2026, 01:42 AM UTC
We are currently investigating degraded network performance between sites in NA due to an upstream incident
- identified Jun 24, 2026, 02:04 AM UTC
Most networking is largely healthy between primary North American regions. Some Machines may see ongoing packet loss and higher latency communicating with other Machines on certain routes. We're continuing to monitor the backbone health upstream.
- identified Jun 24, 2026, 03:42 AM UTC
Some 6PN Private Networking traffic remains impacted into and out of our LAX region, pending upstream resolution.
- resolved Jun 24, 2026, 06:57 AM UTC
This incident has been resolved.
Major June 22, 2026 Network issues in SIN, NRT 1h 40m NRT - Tokyo, Japan, SIN - Singapore
Started Jun 22, 2026, 08:15 PM UTC· resolved Jun 22, 2026, 09:56 PM UTC
- identified Jun 22, 2026, 08:15 PM UTC
Our upstream provider is continuing to experience network issues in SIN and NRT regions. Apps running in those regions may be unreachable or experience high packet loss at this time.
- resolved Jun 22, 2026, 09:56 PM UTC
This incident has been resolved.
Major June 22, 2026 SIN, NRT network issues 2h 38m NRT - Tokyo, Japan, SIN - Singapore
Started Jun 22, 2026, 05:10 PM UTC· resolved Jun 22, 2026, 07:48 PM UTC
- investigating Jun 22, 2026, 05:10 PM UTC
We are investigating an upstream network issue in the SIN (Singapore) region. Apps may be unreachable or have higher packet loss.
- identified Jun 22, 2026, 05:24 PM UTC
Our upstream provider has identified the issue and is working on a fix. Apps running in NRT (Tokyo) region may also have issues reaching certain destinations at this time.
- monitoring Jun 22, 2026, 05:44 PM UTC
A fix has been implemented and we are monitoring the results.
- identified Jun 22, 2026, 06:33 PM UTC
We are continuing to experience network issues with an upstream provider in SIN and NRT regions.
- resolved Jun 22, 2026, 07:48 PM UTC
This incident has been resolved.
Minor June 19, 2026 Log search unavailable 3h 47m Logs
Started Jun 19, 2026, 06:05 PM UTC· resolved Jun 19, 2026, 09:53 PM UTC
- investigating Jun 19, 2026, 06:05 PM UTC
We are investigating an issue causing application log search to be unavailable. This is affecting the Fly Metrics log search panels, and historical application logs initially returned from the `fly logs` command. Streaming logs using `fly logs`, the Live Logs page in the dashboard, and Fly Log Shipper services continue to work as expected.
- investigating Jun 19, 2026, 06:10 PM UTC
Log search is available; however, new app logs since ~1 hour ago are missing and new logs are not being ingested. We are continuing to investigate.
- monitoring Jun 19, 2026, 06:19 PM UTC
We've applied a fix for this issue. Historical logs are currently backfilling. We will post an update once logs have finished backfilling and current logs are being ingested normally.
- resolved Jun 19, 2026, 09:53 PM UTC
Most queued historical logs have been ingested and should now be available through log search. Log ingestion rates have returned to normal levels.