Flightcontrol Outage History

Started Nov 04, 2026, 05:01 AM UTC· resolved Nov 04, 2026, 05:15 AM UTC

1. identified Nov 04, 2026, 05:01 AM UTC

   One of our upstream providers is performing emergency network maintenance on a subset of hosts in ORD. Some machines in ORD may be unreachable during the incident. A small subset of MPG clusters are running with reduced HA due to their replicas being on the affected hosts.

2. resolved Nov 04, 2026, 05:15 AM UTC

   The affected hosts are back online

Read the full incident report →

Started Nov 02, 2026, 12:34 PM UTC· resolved Nov 02, 2026, 01:35 PM UTC

1. investigating Nov 02, 2026, 12:34 PM UTC

   We're currently investigating an elevated level of machine start failures. Workaround in the meantime would be to replace affected machines : https://docs.fly.io/apps/trouble-host-unavailable#apps-with-one-machine-and-no-volumeswith a new one: fly machine clone

2. resolved Nov 02, 2026, 01:35 PM UTC

   We have fixed the underlying issue caused failed Machine starts in ARN

Read the full incident report →

Started Nov 02, 2026, 11:19 AM UTC· resolved Nov 02, 2026, 11:57 AM UTC

1. investigating Nov 02, 2026, 11:19 AM UTC

   We are performing an emergency network maintenance in IAD region. Machines on a subset of hosts will be unreachable for a few minutes starting from the publication of this incident.

2. resolved Nov 02, 2026, 11:57 AM UTC

   This maintenance is complete.

Read the full incident report →

Started Nov 01, 2026, 06:50 PM UTC· resolved Nov 01, 2026, 09:00 PM UTC

1. identified Nov 01, 2026, 06:50 PM UTC

   We are working to resolve an issue with outbound IPv4 connectivity failures affecting machines with in the ARN, JNB, and GRU regions.

2. identified Nov 01, 2026, 07:24 PM UTC

   We have identified the issue and are working to resolve in the affected regions. Newly created static egress IPs may continue to see problems while we roll out fixes.

3. monitoring Nov 01, 2026, 08:24 PM UTC

   We've rolled out fixes to the affected regions and are monitoring for any additional issues.

4. resolved Nov 01, 2026, 09:00 PM UTC

   We've fixed affected regions and everything is back to normal.

Read the full incident report →

Started Oct 30, 2026, 08:24 PM UTC· resolved Oct 30, 2026, 09:52 PM UTC

1. investigating Oct 30, 2026, 08:24 PM UTC

   We are investigating slow image pulls within Fly Machines in IAD. Newly created or updated Machines are taking longer to start, which may cause deployments to time out. Machines start successfully after the delay. Consider creating Machines in alternate regions, if possible, or running fly deploy --wait-timeout 10m to give Machines up to 10 minutes to prepare images and start.

2. identified Oct 30, 2026, 09:07 PM UTC

   We have identified the cause of the issue and are working on a fix.

3. monitoring Oct 30, 2026, 09:23 PM UTC

   We have implemented a fix and are monitoring results.

4. resolved Oct 30, 2026, 09:52 PM UTC

   Image pull times in IAD have returned to normal.

Read the full incident report →

Started Oct 29, 2026, 10:00 PM UTC· resolved Oct 29, 2026, 10:00 PM UTC

1. resolved Oct 29, 2026, 10:00 PM UTC

   Between 22:00 and 22:30 UTC, we saw elevated errors provisioning Depot hosted Builders due to an upstream incident impacting Depot's control plane: https://status.depot.dev/incidents/01M64NVFDKM930PX39YM4275DN. During this time customers may have seen deploys fail with an internal error message. Depot resolved the incident and deploys using Depot hosted builders are working as normal again.

Read the full incident report →

Started Oct 29, 2026, 08:40 PM UTC· resolved Oct 29, 2026, 09:28 PM UTC

1. investigating Oct 29, 2026, 08:40 PM UTC

   We're currently investigating degraded performance with the Machines API.

2. identified Oct 29, 2026, 08:49 PM UTC

   We've identified the problem and are working on a fix.

3. identified Oct 29, 2026, 09:19 PM UTC

   We're continuing to work on a fix to resolve this incident.

4. resolved Oct 29, 2026, 09:28 PM UTC

   The incident has been resolved.

Read the full incident report →

Started Oct 29, 2026, 11:01 AM UTC· resolved Oct 29, 2026, 03:49 PM UTC

1. identified Oct 29, 2026, 11:01 AM UTC

   The ARN WireGuard gateways are currently unreachable. You can specify a different region in the meantime via fly wireguard create region

2. resolved Oct 29, 2026, 03:49 PM UTC

   The ARN WireGuard gateways are up

Read the full incident report →

Started Oct 26, 2026, 02:34 PM UTC· resolved Oct 26, 2026, 08:40 PM UTC

1. investigating Oct 26, 2026, 02:34 PM UTC

   We are investigating reports of elevated networking issues between our network and AWS IPs. We are working to determine the source of the issue.

2. investigating Oct 26, 2026, 02:54 PM UTC

   Our initial investigations indicate connection errors are occuring the return path from AWS IPs. We are escalating the issue with AWS and continuing to investigate. Customers seeing issues are encouraged to also contact AWS support or their AWS hosted vendors support with details of the connection errors and their fly machine IPs.

3. identified Oct 26, 2026, 03:15 PM UTC

   We are continuing to see connectivity issues from AWS IPs to a subset of our hosts. From our investigation these connections appear to be being blocked from the AWS side. We are continuing to work with our upstream networking partners and AWS on remediation. In the meantime impacted customers are recommended to allocate app-scoped static egress IPs using fly ips allocate-egress.

4. identified Oct 26, 2026, 04:26 PM UTC

   We are continuing to work with our upstream networking partners and AWS on remediation. Impacted customers are recommended to allocate app-scoped static egress IPs using fly ips allocate-egress. Customers seeing issues are encouraged to also contact AWS support or their AWS hosted vendors support with details of the connection errors and their fly machine IPs.

5. identified Oct 26, 2026, 06:08 PM UTC

   AWS has implemented changes to unblock connections from their network from reaching our machines. We are seeing connectivity starting to resume on a host-by-host basis as these changes take effect.

6. identified Oct 26, 2026, 07:23 PM UTC

   Connectivity from AWS to Fly.io on impacted hosts is continuing to recover. Approximately 80% of the hosts that were seeing connectivity issues are fully recovered at this time.

7. resolved Oct 26, 2026, 08:40 PM UTC

   This incident has been resolved, connectivity from AWS to all of our hosts is back to normal.

Read the full incident report →

Started Oct 26, 2026, 01:50 AM UTC· resolved Oct 26, 2026, 04:24 AM UTC

1. identified Oct 26, 2026, 01:50 AM UTC

   A subset of hosts in IAD region are experiencing elevated packet loss due to congestion at an upstream provider. We are working with the provider to resolve this issue. Apps hosted in IAD region may experience packet loss at this time.

2. resolved Oct 26, 2026, 04:24 AM UTC

   The congestion affecting our upstream provider has been resolved. We are observing a return to normal levels of networking performance in IAD region.

Read the full incident report →

Started Oct 25, 2026, 10:46 AM UTC· resolved Oct 25, 2026, 11:02 AM UTC

1. investigating Oct 25, 2026, 10:46 AM UTC

   Control plane operations such as resizing or changing plans will fail. MPG cluster availability isn't affected.

2. monitoring Oct 25, 2026, 10:58 AM UTC

   MPG control plane in IAD is accepting writes again. We are monitoring for additional impact.

3. resolved Oct 25, 2026, 11:02 AM UTC

   Control plane operations in IAD, including resizing and changing plans, are working normally again.

Read the full incident report →

Started Oct 22, 2026, 06:00 PM UTC· resolved Oct 22, 2026, 06:00 PM UTC

1. resolved Oct 22, 2026, 06:00 PM UTC

   Between ~18:00 - 18:10 UTC today we saw degraded edge performance across multiple regions. Customers may have noticed elevated numbers of dropped connections or longer than usual connection times reaching their apps during this period. A fix was applied and edge performance is back to normal levels.

Read the full incident report →

Started Oct 20, 2026, 04:54 PM UTC· resolved Oct 20, 2026, 11:53 PM UTC

1. 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.

2. 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.

Read the full incident report →

Started Oct 16, 2026, 06:08 PM UTC· resolved Oct 16, 2026, 06:43 PM UTC

1. 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 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. 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 https://status.flyio.net/incidents/01M52RAWMVC0NKEBRDKC3VXT3K.

3. 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.

Read the full incident report →

Started Oct 16, 2026, 04:22 PM UTC· resolved Oct 17, 2026, 03:48 AM UTC

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. 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.

8. 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.

9. 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.

10. 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.

11. 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.

12. 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.

13. 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

14. 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.

15. 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.

16. 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 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. 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.

18. 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.

19. 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 https://fly.io/status

20. 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 https://fly.io/status

Read the full incident report →

Started Oct 15, 2026, 09:30 AM UTC· resolved Oct 15, 2026, 11:33 AM UTC

1. 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.

2. 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.

3. 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.

Read the full incident report →

Started Oct 15, 2026, 02:35 AM UTC· resolved Oct 15, 2026, 02:35 AM UTC

1. resolved Oct 15, 2026, 02:35 AM UTC

   Subset of hosts in FRA were unavailable due to provider network outage which lasted around 10 minutes

Read the full incident report →

Started Oct 13, 2026, 09:25 AM UTC· resolved Oct 13, 2026, 11:09 AM UTC

1. 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.

2. monitoring Oct 13, 2026, 11:09 AM UTC

   Logs are caught up and we are monitoring the situation

3. resolved Oct 13, 2026, 01:50 PM UTC

   This has been resolved

Read the full incident report →

Started Oct 11, 2026, 11:30 PM UTC· resolved Oct 11, 2026, 11:30 PM UTC

1. resolved Oct 11, 2026, 11:30 PM 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.

Read the full incident report →

Started Oct 08, 2026, 09:23 PM UTC· resolved Oct 08, 2026, 09:51 PM UTC

1. investigating Oct 08, 2026, 09:23 PM UTC

   Sprite creates are failing in all regions outside of Europe. We are investigating the cause.

2. identified Oct 08, 2026, 09:48 PM UTC

   We have identified a potential issue and are applying a fix.

3. 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.

4. resolved Oct 08, 2026, 09:54 PM UTC

   The issue has been resolved.

Read the full incident report →

Started Oct 08, 2026, 05:40 AM UTC· resolved Oct 08, 2026, 06:00 AM UTC

1. 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.

2. monitoring Oct 08, 2026, 05:53 AM UTC

   We have brought BGP back up in LHR and are monitoring recovery.

3. resolved Oct 08, 2026, 06:00 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 06, 2026, 11:00 AM UTC· resolved Oct 06, 2026, 12:02 PM UTC

1. identified Oct 06, 2026, 11:59 AM UTC

   IPv6 traffic is failing on a subset of machines in ORD. IPv6 connections may fail.

2. resolved Oct 06, 2026, 12:02 PM UTC

   IPv6 upstream issue was solved.

Read the full incident report →

Started Oct 03, 2026, 08:01 AM UTC· resolved Oct 03, 2026, 08:35 AM UTC

1. 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.

2. 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.

3. 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.

4. monitoring Oct 03, 2026, 08:35 AM UTC

   All MPG clusters have recovered. We are monitoring for additional impact.

5. resolved Oct 03, 2026, 08:57 AM UTC

   All impacted services are operational now.

Read the full incident report →

Started Oct 01, 2026, 01:11 AM UTC· resolved Oct 01, 2026, 02:35 AM UTC

1. 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.

2. identified Oct 01, 2026, 01:39 AM UTC

   We've identified the cause of the slowed log ingestion and are working on a fix.

3. 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.

4. 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.

5. resolved Oct 01, 2026, 02:49 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 29, 2026, 07:30 PM UTC· resolved Sep 29, 2026, 07:30 PM UTC

1. resolved Sep 29, 2026, 07:30 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.

Read the full incident report →