Is Fly.io down?

Last checked 1m ago
Current status
Fly.io is up

No incidents right now.

  • Official status page: status.fly.io
  • Checked every 5 minutes
  • 25 components tracked

Fly.io is operational right now. Last checked 1m ago; the most recent incident resolved 18h ago.

Real-time Fly.io status, recent outages, and incident history: pulled directly from Fly.io's official status page at status.fly.io every 5 minutes. Pingoru tracks 25 Fly.io services and has captured 85 incidents in the last 90 days (98.00% uptime). Get email, Slack, Discord, or webhook alerts the moment Fly.io reports a new incident, free for 3 monitors, no credit card.

Users who monitor Fly.io also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 8,000+ providers
Fly.io uptime 98.00% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 28m
    Started Oct 30, 2026, 08:24 PM UTC · Resolved Oct 30, 2026, 09:52 PM UTC
    Timeline · 4 updates
    • 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.

    • identified · Oct 30, 2026, 09:07 PM UTC

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

    • monitoring · Oct 30, 2026, 09:23 PM UTC

      We have implemented a fix and are monitoring results.

    • resolved · Oct 30, 2026, 09:52 PM UTC

      Image pull times in IAD have returned to normal.

    Latest: Image pull times in IAD have returned to normal.

  2. Resolved –
    Started Oct 29, 2026, 10:00 PM UTC · Resolved Oct 29, 2026, 10:00 PM UTC
    Timeline · 1 update
    • resolved · Oct 29, 2026, 10:52 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.

    Latest: 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/incide…

  3. Resolved 48m
    Started Oct 29, 2026, 08:40 PM UTC · Resolved Oct 29, 2026, 09:28 PM UTC
    Timeline · 4 updates
    • investigating · Oct 29, 2026, 08:40 PM UTC

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

    • identified · Oct 29, 2026, 08:49 PM UTC

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

    • identified · Oct 29, 2026, 09:19 PM UTC

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

    • resolved · Oct 29, 2026, 09:28 PM UTC

      The incident has been resolved.

    Latest: The incident has been resolved.

  4. Resolved 4h 48m
    Started Oct 29, 2026, 11:01 AM UTC · Resolved Oct 29, 2026, 03:49 PM UTC
    Timeline · 2 updates
    • 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`

    • resolved · Oct 29, 2026, 03:49 PM UTC

      The ARN WireGuard gateways are up

    Latest: The ARN WireGuard gateways are up

  5. Resolved 6h 5m
    Started Oct 26, 2026, 02:34 PM UTC · Resolved Oct 26, 2026, 08:40 PM UTC
    Timeline · 7 updates
    • 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.

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

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

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

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

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

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

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

See the full Fly.io outage history

73 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Fly.io outage history →

Or sign up free to get alerts when Fly.io breaks · 10 free monitors · No credit card

Incident record

Since April 2026 · Statuspage by Atlassian · 25 components checked every 5 minutes
202incidents recorded
202last 12 months
78last 90 days
3 hourstypical duration, 12 months

The longest incident in the last year, Machines failing to start in DFW on March 20, 2026, ran for 3 days. 13 maintenance windows announced in the same period.

Most affected components, last 12 months

  • Deployments21
  • Machines API18
  • Dashboard15
  • ORD - Chicago, Illinois (US)13
  • Customer Applications10

Latest incidents

  • Slow image pulls delaying Machine starts in IAD October 30, 2026 · 88 minutes · degraded service

    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…

  • Elevated Depot Failures October 29, 2026 · under a minute · notice

    Between 22:00 and 22:30 UTC, we saw elevated errors provisioning Depot hosted Builders due to [an upstream incident impacting Depot's control…

  • Elevated issues with the Machines API October 29, 2026 · 48 minutes · degraded service

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

Outage history

Past 90 days · 78 incidents View full outage history →