Hosting / Edge compute / Fly.io

Fly.io

OPERATIONAL

Since Sep 2026 · 25 incidents · status.flyio.net · checked just now

CompareStatus page
GradeFLast 90 days
DPRODBSHIP

Overview

30d90d1y
Admitted uptimeTime not covered by a Sev 1 the provider posted itself. A best case.
98.126%Grade F
IncidentsEverything posted on the status page except scheduled maintenance.
204 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
13h 30m
Median fixMedian time to resolve. Half of incidents were fixed faster.
57m
LongestLongest single incident, start to resolved.
12h 53m
Since lastTime since the last counted incident was resolved.
43h 27m

By area

DProduction
13INCIDENTS
22h 49mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 30d
SEV 1Sep 24, 2026 · 27mPrivate Networking issues (6PN)
SEV 1Sep 23, 2026 · 10mElevated private networking errors
SEV 1Sep 26, 2026 · 0mNetwork outage in AMS region
Worse. 16 in the last 6 months, 0 in the 6 before.
BShipping
8INCIDENTS
25h 35mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 30d
SEV 2Oct 8, 2026 · 31mSprite creates failing
SEV 3Sep 23, 2026 · 7h 01mPartial Sprites outage
SEV 3Oct 20, 2026 · 6h 59mCapacity issues in GRU region
Worse. 10 in the last 6 months, 0 in the 6 before.
CleanSev 3–4Sev 1–2No data

What it costs

One small production web app, per month512 MB app on all month, 1M requests, 100 GB out, commercial use, one seat. Cheapest plan that runs it.
Pay as you go1 of 8 cheaper · Cloudflare: cheaper, same grade
$5.69/mo
shared-cpu-1x, 512 MB, cheapest region$3.69
100 GB egress at $0.02/GB (North America, Europe)$2

docs.fly.io · checked Oct 22, 2026 · Wrong price?

Trend, last 12 months

Worse. 25 in the last 6 months, 0 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss4
Sev 2 · BleedingProd degraded or partly down10
Sev 3 · Can't shipCan't deploy, build or manage it3
Sev 4 · PapercutDocs, status page, slow dashboard3
1 security incident

When it breaks

Start times, last 12 months, UTC.

What breaks

No components named in the last 12 months.

Communication

Updates eachStatus page updates per incident, on average.
3.9Last 12 months
Update gapMedian time between status page updates during an incident.
30mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 17Sev 1–2

Incident history

Show all 25
Oct 20, 20266h 59mSEV 3
Capacity issues in GRU regionCreating and starting Machines and remote builds in the GRU region failed for about seven hours due to low host capacity; other regions were not mentioned.AI-graded · regional
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · REGIONAL · MEDIUM CONFIDENCE
    Creating and starting Machines and remote builds in the GRU region failed for about seven hours due to low host capacity; other regions were not mentioned.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 16:54 UTC · identified
    We're experiencing low host capacity in GRU. Creating or starting Machines in the region may fail at this time. Remote builders in GRU are also impacted. We're actively provisioning additional capacity. As a temporary remediation, customers may consider creating resources in EWR or IAD.
  2. 23:53 UTC · resolved
    We have added host capacity to the region. Machine creates, starts and remote builds in GRU should now be functioning as normal.
Source
Oct 16, 20261h 16mSEV 4
Fly-metrics.net Grafana Dashboard OutageThe hosted Grafana and log search instance at fly-metrics.net was unreachable from about 18:08 to 19:24 UTC on October 16 because the host it runs on was under maintenance. Telemetry shipping via Fly Telemetry and the log shipper stayed available. The instance was restored once the host maintenance finished.AI-graded
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · GLOBAL · MEDIUM CONFIDENCE
    The hosted Grafana dashboard and log search at fly-metrics.net was unreachable for about 75 minutes; telemetry shipping continued working.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 18:08 UTC · identified
    The fly-metrics.net hosted grafana and log search instance is currently unreachable as a result of <https://status.flyio.net/incidents/01M52RAWMVC0NKEBRDKC3VXT3K>. It will return once the host it is on is out of maintenance, approximately 20 minutes. Logs and Metrics shipped to other sources using things like Fly Telemetry or the Fly Log shipper continue to be available, only the hosted Grafana viewer is unavailable at this time.
  2. 18:43 UTC · monitoring
    The [fly-metrics.net](https://fly-metrics.net) hosted Grafana and log search instance should now be reachable again. We're continuing to monitor for any issues as a result of <https://status.flyio.net/incidents/01M52RAWMVC0NKEBRDKC3VXT3K>.
  3. 19:24 UTC · resolved
    The [fly-metrics.net](https://fly-metrics.net) hosted Grafana and log search instance is now fully reachable.
Source
Oct 16, 202612h 53mSEV 1 · SECURITY
Platform Wide Rolling Host RebootsFly.io rebooted hosts fleet-wide over about 11 hours to mitigate kernel vulnerability PwnEscape (CVE-2026-99999). Machines and volumes on each host were unavailable for 15-20 minutes, with multiple hosts per region down at once. Managed Postgres saw elevated primary-standby switchovers and some clusters stayed offline. Restarts finished and the platform was declared normal, though a few hosts remained degraded.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 1 · GLOBAL · HIGH CONFIDENCE · SECURITY
    Rolling host reboots across all regions took Machines offline for 15-20 minutes each over about 11 hours; some hosts stayed degraded afterward.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
20 updates
  1. 16:22 UTC · identified
    We will be imminently applying rolling restarts across all hosts in our fleet for a critical maintenance. Customer Machines, volumes, and MPG cluster instances on each host will be unavailable while their host reboots. Each host will be unavailable for 15 - 20 minutes during the restart, and multiple hosts in a region may be down at once. Users should expect a period of downtime or disruption for their apps, especially if they are running on a single machine. We are aiming for the highest possible uptime during the rollout, while ensuring this is completed quickly. We will provide a further update once we begin the restart process.
  2. 16:50 UTC · identified
    We are beginning the rolling restart process of all hosts, beginning with the YYZ region. Machines, volumes, and MPG instances on hosts being rebooted will be unavailable for approximately 15-20 minutes during the restart. We will provide further updates as the rollout progresses.
  3. 16:59 UTC · identified
    Rolling host restarts are beginning in all regions. Machines, volumes, and MPG instances will be unavailable for approximately 15-20 minutes when their hosts are restarted during this process. Users should expect a period of disruption or downtime for their apps during this, especially if they are running on a single machine. We will provide further updates as the rollout progresses.
  4. 18:01 UTC · identified
    Host restarts are continuing in phases across all regions. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with larger regions taking the longest to complete. Rollout phases were scheduled to minimize impact to Managed Postgres Clusters within those regions, however MPG users will likely see elevated primary <> standby switchovers during this period. We will provide further updates on progress as the rollout continues.
  5. 18:35 UTC · identified
    Host restarts are continuing in phases across all regions, with the first phase nearly complete. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with larger regions taking the longest to complete. Rollout phases were scheduled to minimize impact to Managed Postgres Clusters within those regions; however, MPG users will likely see elevated primary <> standby switchovers during this period. We will continue to provide updates on progress as the rollout continues.
  6. 19:10 UTC · identified
    Host restarts are continuing in phases across all regions, with the second phase nearly complete - at this point, roughly 25% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with larger regions taking the longest to complete. Rollout phases were scheduled to minimize impact to Managed Postgres Clusters within those regions; however, MPG users will likely see elevated primary <> standby switchovers during this period. We will continue to provide updates on progress as the rollout continues.
  7. 20:00 UTC · identified
    Host restarts are continuing in phases across all regions - at this point, roughly 40% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with larger regions taking the longest to complete. In general, Fly Machines should return to whatever state they were in prior to the host reboot, unless the Machine's restart policy says otherwise. Rollout phases were scheduled to minimize impact to Managed Postgres Clusters within those regions; however, MPG users will likely see elevated primary <> standby switchovers during this period. We will continue to provide updates on progress as the rollout continues.
  8. 20:41 UTC · identified
    Host restarts are continuing in phases across all regions - at this point, roughly 50% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with larger regions taking the longest to complete. In general, Fly Machines should return to whatever state they were in prior to the host reboot, unless the Machine's restart policy says otherwise. Rollout phases were scheduled to minimize impact to Managed Postgres Clusters within those regions; however, MPG users will likely see elevated primary <> standby switchovers during this period. We will continue to provide updates on progress as the rollout continues.
  9. 21:11 UTC · identified
    Host restarts are continuing in phases across all regions - at this point, roughly 65% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with larger regions taking the longest to complete. In general, Fly Machines should return to whatever state they were in prior to the host reboot, unless the Machine's restart policy says otherwise. Rollout phases were scheduled to minimize impact to Managed Postgres Clusters within those regions; however, MPG users will likely see elevated primary <> standby switchovers during this period. We will continue to provide updates on progress as the rollout continues.
  10. 21:41 UTC · identified
    Host restarts are continuing in phases across all regions - at this point, roughly 70% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with larger regions taking the longest to complete. In general, Fly Machines should return to whatever state they were in prior to the host reboot, unless the Machine's restart policy says otherwise. Rollout phases were scheduled to minimize impact to Managed Postgres Clusters within those regions; however, MPG users will likely see elevated primary <> standby switchovers during this period. We will continue to provide updates on progress as the rollout continues.
  11. 22:27 UTC · identified
    Host restarts are continuing in phases across all regions - at this point, roughly 80% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with larger regions taking the longest to complete. In general, Fly Machines should return to whatever state they were in prior to the host reboot, unless the Machine's restart policy says otherwise. Rollout phases were scheduled to minimize impact to Managed Postgres Clusters within those regions; however, MPG users will likely see elevated primary <> standby switchovers during this period. We will continue to provide updates on progress as the rollout continues.
  12. 23:15 UTC · identified
    Host restarts are continuing in phases across all regions - at this point, roughly 85% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with larger regions taking the longest to complete. In general, Fly Machines should return to whatever state they were in prior to the host reboot, unless the Machine's restart policy says otherwise. Rollout phases were scheduled to minimize impact to Managed Postgres Clusters within those regions; however, MPG users will likely see elevated primary <> standby switchovers during this period. We will continue to provide updates on progress as the rollout continues.
  13. 00:05 UTC · identified
    Host restarts are continuing in phases across all regions - at this point, roughly 90% of all hosts across the fleet have been restarted. Only a subset of hosts in each region will be down at each time. We expect this process to take multiple hours to complete in full, with larger regions taking the longest to complete. In general, Fly Machines should return to whatever state they were in prior to the host reboot, unless the Machine's restart policy says otherwise. Rollout phases were scheduled to minimize impact to Managed Postgres Clusters within those regions; however, MPG users will likely see elevated primary <> standby switchovers during this period. We
  14. 00:45 UTC · identified
    As a mitigation measure for PwnEscape (Linux Kernel CVE-2026-99999), host restarts are continuing in phases across all regions. At this point, more than 90% of the fleet has been restarted. The remaining hosts are expected to be restarted over the next 2h30m. Only a subset of hosts in each region will be down at each time. In general, Fly Machines should return to whatever state they were in prior to the host reboot, unless the Machine's restart policy says otherwise. MPG users will likely see elevated primary <> standby switchovers during this period. Impacted MPG clusters are being attended to by the team. We will continue to provide updates on progress as the rollout continues.
  15. 01:11 UTC · identified
    As a mitigation measure for PwnEscape (Linux Kernel CVE-2026-99999), host restarts are continuing in phases across all regions. At this point, more than 90% of the fleet has been restarted. The remaining hosts are expected to be restarted over the next 2h. Only a subset of hosts in each region will be down at each time. In general, Fly Machines should return to whatever state they were in prior to the host reboot, unless the Machine's restart policy says otherwise. MPG users will likely see elevated primary <> standby switchovers during this period. Impacted MPG clusters are being attended to by the team. We will continue to provide updates on progress as the rollout continues.
  16. 01:43 UTC · identified
    As a mitigation measure for PwnEscape (Linux Kernel CVE-2026-99999), host restarts are continuing in phases across all regions. At this point, more than 95% of the fleet has been restarted. The remaining hosts are expected to be restarted over the next 1h40m. Only a subset of hosts in each region will be down at each time. In general, Fly Machines should return to whatever state they were in prior to the host reboot, unless the Machine's restart policy says otherwise. MPG users will likely see elevated primary <> standby switchovers during this period. Impacted MPG clusters are being attended to by the team. We will continue to provide updates on progress as the rollout continues.
  17. 02:17 UTC · identified
    As a mitigation measure for PwnEscape (Linux Kernel CVE-2026-99999), host restarts are continuing in phases across all regions. At this point, more than 95% of the fleet has been restarted. The remaining hosts are expected to be restarted over the next 1h30m. Only a subset of hosts in each region will be down at each time. In general, Fly Machines should return to whatever state they were in prior to the host reboot, unless the Machine's restart policy says otherwise. MPG users will likely see elevated primary <> standby switchovers during this period. Impacted MPG clusters are being attended to by the team. We will continue to provide updates on progress as the rollout continues.
  18. 02:41 UTC · identified
    As a mitigation measure for PwnEscape (Linux Kernel CVE-2026-99999), host restarts are continuing in phases across all regions. At this point, more than 95% of the fleet has been restarted. The remaining hosts are expected to be restarted over the next 30m. Only a subset of hosts in each region will be down at each time. In general, Fly Machines should return to whatever state they were in prior to the host reboot, unless the Machine's restart policy says otherwise. MPG users will likely see elevated primary <> standby switchovers during this period. Impacted MPG clusters are being attended to by the team. We will continue to provide updates on progress as the rollout continues.
  19. 03:48 UTC · monitoring
    All host restarts have been completed and we are monitoring the fleet health. A small number of hosts remain degraded or offline for apps and for MPG. Those impacted can see this status on the personalized status page viewable at <https://fly.io/status>
  20. 05:15 UTC · resolved
    All host restarts have been completed and the platform is operating normally. A small number of hosts remain degraded or offline for apps and for MPG. Those impacted can see further updates on the personalized status page viewable at <https://fly.io/status>
Source
Oct 15, 20262h 04mSEV 3
Elevated errors creating apps and managing secretsSome app creation, secrets changes and app deletions via flyctl, the Machines API and dashboard returned 500 or 503 errors or timed out. Running apps and Machines were not affected. A fix was applied and error rates returned to normal, and the incident was resolved after about two hours.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · SUBSET · HIGH CONFIDENCE
    Creating apps, setting or removing secrets, and some app deletions failed or timed out; running Machines were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 09:30 UTC · investigating
    We’re seeing elevated error rates and slow responses for some operations that create or change data. Creating new apps, setting or removing secrets, and some app deletions are affected. You may see 500 or 503 errors from `flyctl`, the Machines API, or the dashboard. Apps and Machines that are already running are not affected. Starting, stopping and reading existing Machines are working normally. We’re investigating and will post another update within 30 minutes.
  2. 09:57 UTC · monitoring
    We’ve applied a fix for the elevated errors affecting app creation and secrets management. Error rates and response times have returned to normal. We’re continuing to monitor to confirm the issue is fully resolved.
  3. 11:33 UTC · resolved
    Between 06:40 and 09:50 UTC some app creation and secrets requests failed or timed out. Running apps and Machines were not affected.
Source
Oct 15, 20260mSEV 2
Partial FRA network issuesSev 2 from the incident title (no components listed)
1 update
  1. 02:35 UTC · resolved
    Subset of hosts in FRA were unavailable due to provider network outage which lasted around 10 minutes
Source
Oct 13, 20264h 25mSEV 4
Historical logs are currently delayedHistorical log delivery lagged for about four hours due to a backed-up ingestion pipeline; live serving was not described as affected.AI-graded
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE
    Historical log delivery lagged for about four hours due to a backed-up ingestion pipeline; live serving was not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 09:25 UTC · identified
    Our log ingestion pipeline is currently backed up. Historical logs will be delayed while the queue is processed.
  2. 11:09 UTC · monitoring
    Logs are caught up and we are monitoring the situation
  3. 13:50 UTC · resolved
    This has been resolved
Source
Oct 12, 20260mSEV 2
Sprite hosting outageSev 2 from the incident title (no components listed)
1 update
  1. 23:30 UTC · resolved
    From approximately 2026-10-11 23:30 UTC through 2026-10-12 00:45 UTC some or all hosted sprites on the *.sprites.app subdomain were unavailable due to a certificate error. As of 00:45 UTC this incident has been resolved.
Source
Oct 8, 202631mSEV 2
Sprite creates failingSprite creates failed in all regions outside Europe from 21:23 to 21:54 UTC on October 8. Fly.io identified a potential issue and applied a fix, after which sprite pools recovered and creates succeeded. The incident was resolved at 21:54 UTC.AI-graded · regional
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Sprite creation failed in all regions outside Europe for about 30 minutes; European regions were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 21:23 UTC · investigating
    Sprite creates are failing in all regions outside of Europe. We are investigating the cause.
  2. 21:48 UTC · identified
    We have identified a potential issue and are applying a fix.
  3. 21:51 UTC · monitoring
    Sprite pools are starting to recover and creates are succeeding. We are monitoring the pools as they refill.
  4. 21:54 UTC · resolved
    The issue has been resolved.
Source
Oct 8, 202620mSEV 2
LHR network issuesBGP announcements failed in the London region, breaking anycast and static egress IPs for about 20 minutes; traffic rerouted to nearby regions.AI-graded · regional
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    BGP announcements failed in the London region, breaking anycast and static egress IPs for about 20 minutes; traffic rerouted to nearby regions.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 05:40 UTC · identified
    We are working to resolve an issue with our BGP announcements in LHR (London, UK) region. Regional anycast and static egress IPs are currently not functional and anycast traffic is being rerouted to nearby regions.
  2. 05:53 UTC · monitoring
    We have brought BGP back up in LHR and are monitoring recovery.
  3. 06:00 UTC · resolved
    This incident has been resolved.
Source
Oct 6, 20263mSEV 2
Impaired IPv6 connectivity in ORDIPv6 traffic failed on a subset of machines in the ORD region for about three minutes before an upstream fix.AI-graded · one location
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    IPv6 traffic failed on a subset of machines in the ORD region for about three minutes before an upstream fix.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 11:59 UTC · identified
    IPv6 traffic is failing on a subset of machines in ORD. IPv6 connections may fail.
  2. 12:02 UTC · resolved
    IPv6 upstream issue was solved.
Source
Oct 3, 202657mSEV 2
Partial outage in AMSSome hosts in the AMS region went offline from about 08:01 to 08:19 UTC, making some machines unavailable and causing Managed Postgres control plane operations to fail. Hosts recovered by 08:19; some MPGv1 clusters may have been degraded until the control plane recovered. All MPG clusters were recovered by 08:35 and the incident was resolved at 08:57 UTC. No cause was given.AI-graded · regional
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Some hosts and machines in the AMS region went offline for under an hour, and Managed Postgres control planes there failed.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
5 updates
  1. 08:01 UTC · identified
    Some of our hosts are offline in AMS. Control plane for Managed Postgres v1 and v2 in AMS is unavailable as a result of this. MPG clusters should remain online but any control plane ops will fail. Some machines in AMS are also unavailable.
  2. 08:08 UTC · identified
    Those hosts are coming back online after a brief interruption. We are assessing the impact on MPG.
  3. 08:19 UTC · monitoring
    All hosts are back online. MPGv2 control plane is fully operational now. Some MPGv1 clusters in AMS might be degraded while MPGv1's control plane recovers.
  4. 08:35 UTC · monitoring
    All MPG clusters have recovered. We are monitoring for additional impact.
  5. 08:57 UTC · resolved
    All impacted services are operational now.
Source
Oct 1, 20261h 38mSEV 4
Delayed ingestion of app logsFly.io log ingestion was delayed across all regions from about 01:11 to 02:49 UTC on 2026-10-01. New logs from machines were not visible during this time, though past logs remained available. The cause was identified and fixed, and the backlog was processed. The provider said no logs were lost.AI-graded
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · GLOBAL · HIGH CONFIDENCE
    Delayed app log ingestion across all regions for about 98 minutes; past logs stayed available and no logs were lost.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
5 updates
  1. 01:11 UTC · investigating
    We're investigating delayed ingestion of app logs across all regions. New logs from machines may not be visible, but past logs are still available.
  2. 01:39 UTC · identified
    We've identified the cause of the slowed log ingestion and are working on a fix.
  3. 02:27 UTC · identified
    We've resolved the ingestion issue and our systems are processing the backlog of app logs. No logs have been lost.
  4. 02:35 UTC · monitoring
    The backlog of app logs has been processed, and we're monitoring the health of the log cluster. No logs were lost.
  5. 02:49 UTC · resolved
    This incident has been resolved.
Source
Sep 29, 20260mSEV 2
GRU Networking IssuesSev 2 from the incident title (no components listed)
1 update
  1. 19:30 UTC · resolved
    We observed networking issues affecting a subset of our hosts in GRU from 19:37 UTC through 19:59 UTC. This affected platform operations requiring leases, private networking, and internet connectivity to some endpoints.
Source
Sep 26, 20260mSEV 1
Network outage in AMS regionSev 1 from the incident title (no components listed)
3 updates
  1. 19:31 UTC · identified
    We are working with our upstream providers to restore connectivity to the AMS region.
  2. 19:46 UTC · monitoring
    Connectivity is restored and the network is recovering.
  3. 19:53 UTC · resolved
    This incident has been resolved.
Source
Sep 24, 20262h 00mSEV 2
State database issues in GRUA migration of Fly.io's distributed state database caused problems in the GRU region. Apps kept running, but creating or updating machines could fail, and connections to GRU apps or from nearby clients could fail. A bug was identified, a fix was deployed, and the incident was resolved about two hours after it started.AI-graded · regional
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Machine creation and updates failed in the GRU region for about two hours, and connections to GRU apps may have failed; apps kept running.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 16:31 UTC · investigating
    We are investigating issues in GRU related to a migration of our distributed state database. Apps continue to run, but creating or updating machines in GRU region may fail. Connections to apps in GRU, or connections from clients near GRU region, may fail at this time
  2. 16:58 UTC · identified
    We have identified a bug and are working on a fix.
  3. 17:27 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  4. 19:11 UTC · resolved
    This incident has been resolved.
Source
Sep 24, 202627mSEV 1
Private Networking issues (6PN)Sev 1 from the incident title (no components listed)
3 updates
  1. 14:51 UTC · investigating
    We are currently investigating this issue.
  2. 15:01 UTC · monitoring
    A fix has been implemented and we are seeing private networking error rates return to normal. We are continuing to monitor to ensure full recovery.
  3. 15:37 UTC · resolved
    This incident has been resolved
Source
Sep 23, 20267h 01mSEV 3
Partial Sprites outageFly.io's Sprites API had intermittent failures starting near SJC, later spreading to other regions. Creating, connecting to and managing Sprites often errored. Fixes were deployed over several hours; performance largely recovered by 01:43 UTC, and the incident was resolved at 02:12 UTC on September 24.AI-graded · regional
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · REGIONAL · MEDIUM CONFIDENCE
    Sprites API requests failed intermittently for creating, connecting to and managing Sprites, starting near SJC and spreading to other regions for about 7 hours.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
6 updates
  1. 18:44 UTC · investigating
    We are investigating intermittent API failures for users connecting near SJC.
  2. 18:47 UTC · identified
    The issue has been identified and we are rolling out mitigations.
  3. 20:26 UTC · identified
    This issue is now occurring on regions other than SJC. We are still working on a fix.
  4. 23:59 UTC · monitoring
    We have deployed another potential fix and are monitoring results.
  5. 01:43 UTC · monitoring
    Sprites API performance has largely recovered and most users should no longer see errors creating, connecting to, or managing Sprites. We're still seeing a small number of intermittent errors and are investigating them before resolving this incident.
  6. 02:12 UTC · resolved
    This incident has been resolved.
Source
Sep 23, 202610mSEV 1
Elevated private networking errorsSev 1 from the incident title (no components listed)
3 updates
  1. 14:47 UTC · investigating
    We are investigating elevated errors with private networking between machines in some regions.
  2. 14:56 UTC · monitoring
    A fix has been implemented are we are monitoring to ensure recovery.
  3. 15:23 UTC · resolved
    This incident has been resolved.
Source
Sep 23, 202656mSEV 2
Upstash unavailability in FRA regionFrom about 12:00 to 13:05 UTC, some clients got connection timeouts to Redis databases hosted in or routed through the fra and gig regions. A planned Upstash rolling upgrade left replicas out of service and returned them to routing before they were ready. Fixes planned include safer replica return and upgrade checks.AI-graded · regional
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · HIGH CONFIDENCE
    Redis connection timeouts hit databases in the fra and gig regions for about an hour; some clients were affected, others were not.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 12:42 UTC · investigating
    We are investigating an issue affecting Upstash services in the fra region. Customers may experience connection failures or service unavailability. We are working with Upstash to identify the cause and restore service. We’ll provide an update as soon as we have more information.
  2. 13:08 UTC · monitoring
    A fix has been implemented and we are monitoring the results.
  3. 14:03 UTC · resolved
    This incident has been resolved.
  4. 07:22 UTC · resolved
    **Impact** From about 12:00 to 13:05 UTC, some clients got connection timeouts to their Redis databases. Affected were databases hosted in fra or gig, and clients whose connections were routed through fra or gig, even if their database is hosted in another region. **What happened** During a planned rolling upgrade, replicas in fra and gig did not finish draining and were left out of service. They were returned to Fly routing before they were ready to accept connections. Connections routed to them then timed out. **What we're changing** • We will be adding tooling to return a replica to service safely after maintenance. • We will be adding safety checks to our upgrade process. • We will make the upgrade procedure more resilient to errors like this one.
Source
Sep 23, 20265h 03mSEV 2
IPv6 Networking Issues in DFWMachines on a subset of hosts in the DFW region had inbound and outbound IPv6 connectivity problems, caused by regional maintenance at an upstream internet transit provider. IPv4 was not impacted. The incident started at 07:12 UTC and was resolved at 12:15 UTC on 2026-09-23.AI-graded · regional
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    IPv6 inbound and outbound connectivity failed for machines on a subset of DFW hosts for about five hours; IPv4 was unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 06:18 UTC · investigating
    We are investigating IPv6 connectivity issues on a subset of hosts in DFW region. Machines on impacted hosts may see inbound/outbound connectivity issues over IPv6. IPv4 connectivity is not impacted.
  2. 06:52 UTC · identified
    One of the internet transit providers upstream of the affected hosts is performing regional maintenance, which is expected to complete at 10:00AM UTC. IPv6 connectivity to and from destinations using that transit may be impacted during this time window.
  3. 10:52 UTC · identified
    We are continuing to work on a fix for this issue.
  4. 12:15 UTC · resolved
    This incident has been resolved.
Source

Peers, 90 days

Compare
HerokuGrade A+100.00% up0 incidentsMTTR –$7/moNetlifyGrade B100.00% up17 incidentsMTTR 34m~$20/moRenderGrade C100.00% up13 incidentsMTTR 1h 35m$21.25/moVercelGrade C100.00% up23 incidentsMTTR 47m~$20/moDigitalOceanGrade F100.00% up18 incidentsMTTR 4h 02m$6/moFly.ioGrade F99.38% up25 incidentsMTTR 44m$5.69/moCloudflareGrade F100.00% up54 incidentsMTTR 1h 13m~$5/moRailwayGrade F98.31% up27 incidentsMTTR 55m~$12/mo

README badge

Fly.io's live grade, for your README.

Fly.io grade badge
[![fly on downagain.dev](https://downagain.dev/badge/fly.svg)](https://downagain.dev/p/fly)