Fly.io Outage History
Fly.io is up right nowPingoru has recorded 194 incidents for Fly.io: 194 in the last 12 months and 74 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 | 12 | 30 of 522 (6%) |
Incidents, newest first
Minor October 20, 2026 Capacity issues in GRU region 6h 59m
Started Oct 20, 2026, 04:54 PM UTC· resolved Oct 20, 2026, 11:53 PM UTC
- identified Oct 20, 2026, 04:54 PM UTC
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.
- resolved Oct 20, 2026, 11:53 PM UTC
We have added host capacity to the region. Machine creates, starts and remote builds in GRU should now be functioning as normal.
Major October 16, 2026 Fly-metrics.net Grafana Dashboard Outage 1h 15m
Started Oct 16, 2026, 06:08 PM UTC· resolved Oct 16, 2026, 07:24 PM UTC
- identified Oct 16, 2026, 06:08 PM UTC
The fly-metrics.net hosted grafana and log search instance is currently unreachable as a result of . 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.
- monitoring Oct 16, 2026, 06:43 PM UTC
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 .
- resolved Oct 16, 2026, 07:24 PM UTC
The [fly-metrics.net](https://fly-metrics.net) hosted Grafana and log search instance is now fully reachable.
Major October 16, 2026 Platform Wide Rolling Host Reboots 12h 52m
Started Oct 16, 2026, 04:22 PM UTC· resolved Oct 17, 2026, 05:15 AM UTC
- identified Oct 16, 2026, 04:22 PM UTC
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.
- identified Oct 16, 2026, 04:50 PM UTC
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.
- identified Oct 16, 2026, 04:59 PM UTC
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.
- identified Oct 16, 2026, 06:01 PM UTC
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.
- identified Oct 16, 2026, 06:35 PM UTC
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.
- identified Oct 16, 2026, 07:10 PM UTC
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.
- identified Oct 16, 2026, 08:00 PM UTC
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.
- identified Oct 16, 2026, 08:41 PM UTC
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.
- identified Oct 16, 2026, 09:11 PM UTC
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.
- identified Oct 16, 2026, 09:41 PM UTC
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.
- identified Oct 16, 2026, 10:27 PM UTC
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.
- identified Oct 16, 2026, 11:15 PM UTC
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.
- identified Oct 17, 2026, 12:05 AM UTC
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
- identified Oct 17, 2026, 12:45 AM UTC
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.
- identified Oct 17, 2026, 01:11 AM UTC
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.
- identified Oct 17, 2026, 01:43 AM UTC
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 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.
- identified Oct 17, 2026, 02:17 AM UTC
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.
- identified Oct 17, 2026, 02:41 AM UTC
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.
- monitoring Oct 17, 2026, 03:48 AM UTC
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
- resolved Oct 17, 2026, 05:15 AM UTC
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
Minor October 15, 2026 Elevated errors creating apps and managing secrets 2h 3m
Started Oct 15, 2026, 09:30 AM UTC· resolved Oct 15, 2026, 11:33 AM UTC
- investigating Oct 15, 2026, 09:30 AM UTC
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.
- monitoring Oct 15, 2026, 09:57 AM UTC
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.
- resolved Oct 15, 2026, 11:33 AM UTC
Between 06:40 and 09:50 UTC some app creation and secrets requests failed or timed out. Running apps and Machines were not affected.
Notice October 15, 2026 Partial FRA network issues –
Started Oct 15, 2026, 02:35 AM UTC· resolved Oct 15, 2026, 02:35 AM UTC
- resolved Oct 15, 2026, 02:55 AM UTC
Subset of hosts in FRA were unavailable due to provider network outage which lasted around 10 minutes
Minor October 13, 2026 Historical logs are currently delayed 4h 24m
Started Oct 13, 2026, 09:25 AM UTC· resolved Oct 13, 2026, 01:50 PM UTC
- identified Oct 13, 2026, 09:25 AM UTC
Our log ingestion pipeline is currently backed up. Historical logs will be delayed while the queue is processed.
- monitoring Oct 13, 2026, 11:09 AM UTC
Logs are caught up and we are monitoring the situation
- resolved Oct 13, 2026, 01:50 PM UTC
This has been resolved
Notice October 11, 2026 Sprite hosting outage –
Started Oct 11, 2026, 11:30 PM UTC· resolved Oct 11, 2026, 11:30 PM UTC
- resolved Oct 12, 2026, 12:47 AM UTC
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.
Critical October 8, 2026 Sprite creates failing 31m
Started Oct 08, 2026, 09:23 PM UTC· resolved Oct 08, 2026, 09:54 PM UTC
- investigating Oct 08, 2026, 09:23 PM UTC
Sprite creates are failing in all regions outside of Europe. We are investigating the cause.
- identified Oct 08, 2026, 09:48 PM UTC
We have identified a potential issue and are applying a fix.
- monitoring Oct 08, 2026, 09:51 PM UTC
Sprite pools are starting to recover and creates are succeeding. We are monitoring the pools as they refill.
- resolved Oct 08, 2026, 09:54 PM UTC
The issue has been resolved.
Major October 8, 2026 LHR network issues 19m
Started Oct 08, 2026, 05:40 AM UTC· resolved Oct 08, 2026, 06:00 AM UTC
- identified Oct 08, 2026, 05:40 AM UTC
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.
- monitoring Oct 08, 2026, 05:53 AM UTC
We have brought BGP back up in LHR and are monitoring recovery.
- resolved Oct 08, 2026, 06:00 AM UTC
This incident has been resolved.
Minor October 6, 2026 Impaired IPv6 connectivity in ORD 3m
Started Oct 06, 2026, 11:59 AM UTC· resolved Oct 06, 2026, 12:02 PM UTC
- identified Oct 06, 2026, 11:59 AM UTC
IPv6 traffic is failing on a subset of machines in ORD. IPv6 connections may fail.
- resolved Oct 06, 2026, 12:02 PM UTC
IPv6 upstream issue was solved.
Critical October 3, 2026 Partial outage in AMS 56m
Started Oct 03, 2026, 08:01 AM UTC· resolved Oct 03, 2026, 08:57 AM UTC
- identified Oct 03, 2026, 08:01 AM UTC
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.
- identified Oct 03, 2026, 08:08 AM UTC
Those hosts are coming back online after a brief interruption. We are assessing the impact on MPG.
- monitoring Oct 03, 2026, 08:19 AM UTC
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.
- monitoring Oct 03, 2026, 08:35 AM UTC
All MPG clusters have recovered. We are monitoring for additional impact.
- resolved Oct 03, 2026, 08:57 AM UTC
All impacted services are operational now.
Minor October 1, 2026 Delayed ingestion of app logs 1h 38m
Started Oct 01, 2026, 01:11 AM UTC· resolved Oct 01, 2026, 02:49 AM UTC
- investigating Oct 01, 2026, 01:11 AM UTC
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.
- identified Oct 01, 2026, 01:39 AM UTC
We've identified the cause of the slowed log ingestion and are working on a fix.
- identified Oct 01, 2026, 02:27 AM UTC
We've resolved the ingestion issue and our systems are processing the backlog of app logs. No logs have been lost.
- monitoring Oct 01, 2026, 02:35 AM UTC
The backlog of app logs has been processed, and we're monitoring the health of the log cluster. No logs were lost.
- resolved Oct 01, 2026, 02:49 AM UTC
This incident has been resolved.
Notice September 29, 2026 GRU Networking Issues –
Started Sep 29, 2026, 07:30 PM UTC· resolved Sep 29, 2026, 07:30 PM UTC
- resolved Sep 29, 2026, 09:12 PM UTC
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.
Critical September 26, 2026 Network outage in AMS region –
Started Sep 26, 2026, 07:53 PM UTC· resolved Sep 26, 2026, 07:53 PM UTC
- identified Sep 26, 2026, 08:10 PM UTC
We are working with our upstream providers to restore connectivity to the AMS region.
- resolved Sep 26, 2026, 08:10 PM UTC
This incident has been resolved.
- monitoring Sep 26, 2026, 08:10 PM UTC
Connectivity is restored and the network is recovering.
Major September 24, 2026 State database issues in GRU 2h
Started Sep 24, 2026, 05:11 PM UTC· resolved Sep 24, 2026, 07:11 PM UTC
- identified Sep 24, 2026, 05:11 PM UTC
We have identified a bug and are working on a fix.
- investigating Sep 24, 2026, 05:11 PM UTC
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
- monitoring Sep 24, 2026, 06:11 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 24, 2026, 07:12 PM UTC
This incident has been resolved.
Major September 24, 2026 Private Networking issues (6PN) 26m
Started Sep 24, 2026, 03:11 PM UTC· resolved Sep 24, 2026, 03:37 PM UTC
- monitoring Sep 24, 2026, 03:11 PM UTC
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.
- investigating Sep 24, 2026, 03:11 PM UTC
We are currently investigating this issue.
- resolved Sep 24, 2026, 04:12 PM UTC
This incident has been resolved
Major September 23, 2026 Partial Sprites outage 7h
Started Sep 23, 2026, 07:12 PM UTC· resolved Sep 24, 2026, 02:12 AM UTC
- identified Sep 23, 2026, 07:12 PM UTC
The issue has been identified and we are rolling out mitigations.
- investigating Sep 23, 2026, 07:12 PM UTC
We are investigating intermittent API failures for users connecting near SJC.
- identified Sep 23, 2026, 09:10 PM UTC
This issue is now occurring on regions other than SJC. We are still working on a fix.
- monitoring Sep 24, 2026, 12:11 AM UTC
We have deployed another potential fix and are monitoring results.
- monitoring Sep 24, 2026, 02:10 AM UTC
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.
- resolved Sep 24, 2026, 03:10 AM UTC
This incident has been resolved.
Major September 23, 2026 Elevated private networking errors 10m
Started Sep 23, 2026, 03:13 PM UTC· resolved Sep 23, 2026, 03:23 PM UTC
- monitoring Sep 23, 2026, 03:13 PM UTC
A fix has been implemented are we are monitoring to ensure recovery.
- investigating Sep 23, 2026, 03:13 PM UTC
We are investigating elevated errors with private networking between machines in some regions.
- resolved Sep 23, 2026, 04:11 PM UTC
This incident has been resolved.
Major September 23, 2026 Upstash unavailability in FRA region 56m
Started Sep 23, 2026, 01:07 PM UTC· resolved Sep 23, 2026, 02:03 PM UTC
- investigating Sep 23, 2026, 01:07 PM UTC
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.
- resolved Sep 23, 2026, 02:13 PM UTC
This incident has been resolved.
- monitoring Sep 23, 2026, 02:13 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 24, 2026, 08:12 AM UTC
**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.
Major September 23, 2026 IPv6 Networking Issues in DFW 5h 3m
Started Sep 23, 2026, 07:12 AM UTC· resolved Sep 23, 2026, 12:15 PM UTC
- identified Sep 23, 2026, 07:12 AM UTC
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.
- investigating Sep 23, 2026, 07:12 AM UTC
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.
- identified Sep 23, 2026, 11:12 AM UTC
We are continuing to work on a fix for this issue.
- resolved Sep 23, 2026, 01:07 PM UTC
This incident has been resolved.
Minor September 15, 2026 Depot builder failures 26m
Started Sep 15, 2026, 05:07 AM UTC· resolved Sep 15, 2026, 05:34 AM UTC
- identified Sep 15, 2026, 05:07 AM UTC
We have identified an issue with deploying via Depot for users connecting through our SYD and JNB regions. Affected customers in these regions can deploy successfully using the --depot=false or --buildkit arguments to flyctl.
- investigating Sep 15, 2026, 05:07 AM UTC
We are investigating reports of Depot builds failing for some customers. Affected customers can deploy successfully using the --depot=false or --buildkit arguments to flyctl.
- monitoring Sep 15, 2026, 05:07 AM UTC
A fix has been implemented and we are monitoring builds. Standard flyctl builds should be working again for customers in all regions.
- resolved Sep 15, 2026, 06:09 AM UTC
This incident has been resolved.
Minor September 12, 2026 Network issues in US West Coast 5m
Started Sep 12, 2026, 10:07 PM UTC· resolved Sep 12, 2026, 10:12 PM UTC
- investigating Sep 12, 2026, 10:07 PM UTC
We are investigating upstream network issues from US West Coast (SJC, LAX). Apps hosted in US West regions may experience higher latency or packet loss, and requests from clients physically located in US West may experience higher latency.
- monitoring Sep 12, 2026, 10:07 PM UTC
Private networking between Fly Machines is resolved, and most outbound connections are healthy. We're continuing to monitor the network, and some issues will still be expected from clients physically located in US West until upstream transit issues are resolved.
- resolved Sep 12, 2026, 11:09 PM UTC
This incident has been resolved.
Major September 2, 2026 Sprites API Partial Outage 1h 37m
Started Sep 02, 2026, 11:03 PM UTC· resolved Sep 03, 2026, 12:41 AM UTC
- investigating Sep 02, 2026, 11:03 PM UTC
We're aware of a problem affecting a subset of Sprites users. We are investigating the source of the issue.
- monitoring Sep 03, 2026, 12:11 AM UTC
Error rates have decreased. We are continuing to monitor the API health.
- resolved Sep 03, 2026, 01:09 AM UTC
This incident has been resolved.
Minor September 2, 2026 Upstream network issues 44m
Started Sep 02, 2026, 03:13 PM UTC· resolved Sep 02, 2026, 03:57 PM UTC
- identified Sep 02, 2026, 03:13 PM UTC
We have put in some temporary mitigations along with our providers. However since the root cause of this issue lies within a bigger upstream transit provider, you may continue to see some elevated latency and connection issues in/around affected regions. We're still working closely with them to resolve the root cause.
- identified Sep 02, 2026, 03:13 PM UTC
We're updating the affected region list to also include SJC since this seems to be a wider upstream issue in US West Coast.
- identified Sep 02, 2026, 03:13 PM UTC
We have observed an upstream network issue in LAX. Connections to some destinations may see elevated latency and packet loss. We're working with our upstream to resolve this issue.
- monitoring Sep 02, 2026, 04:11 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 02, 2026, 04:11 PM UTC
This incident has been resolved.
Major September 2, 2026 API background job queue failure –
Started Sep 02, 2026, 07:44 AM UTC· resolved Sep 02, 2026, 07:44 AM UTC
- resolved Sep 02, 2026, 08:10 AM UTC
This incident has been resolved.
- monitoring Sep 02, 2026, 08:10 AM UTC
A fix has been implemented and we are monitoring the results.
- investigating Sep 02, 2026, 08:10 AM UTC
We are investigating an issue with the background job runner for our API. Actions that require a background job, such as creating apps, assigning IP addresses, or creating/renewing certificates, may fail at this time.