Is Fly.io down?

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

No incidents right now.

Get alerts when Fly.io breaks →

Free · no credit card

Official status page: https://status.fly.io · Polled every 5 minutes · 53 components tracked

Real-time Fly.io status, recent outages, and incident history — pulled directly from Fly.io's official status page at https://status.fly.io every 5 minutes. Pingoru tracks 53 Fly.io services and has captured 50 incidents in the last 90 days (98.46% uptime). Get email, Slack, Discord, or webhook alerts the moment Fly.io reports a new incident — free for 5 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 6,000+ providers
Fly.io uptime 98.46% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. flyctl deploy creating new app instances
    Resolved 49m
    Started Apr 28, 2026, 11:50 PM UTC · Resolved Apr 29, 2026, 12:40 AM UTC
    Deployments
    4 updates · show timeline
    • investigating · Apr 28, 2026, 11:50 PM UTC

      We're investigating an issue where fly deploy is creating new Fly machine instances rather than updating existing ones, leading to apps with a mixed state. We're currently investigating the issue. As a workaround, please try removing the "processes = [ "app" ]" line from your fly.toml configuration file and redeploying - this should resolve the issue in the meantime.

    • identified · Apr 29, 2026, 12:07 AM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Apr 29, 2026, 12:31 AM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Apr 29, 2026, 12:40 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Slow machines operations in IAD region
    Resolved 45m
    Started Apr 24, 2026, 10:45 PM UTC · Resolved Apr 24, 2026, 11:31 PM UTC
    IAD - Ashburn, Virginia (US)
    5 updates · show timeline
    • investigating · Apr 24, 2026, 10:45 PM UTC

      We are currently investigating the issue. Only a portion of machines within the region are impacted.

    • investigating · Apr 24, 2026, 10:58 PM UTC

      We are deploying a partial mitigation while we continue investigating.

    • investigating · Apr 24, 2026, 11:18 PM UTC

      We are continuing to investigate this issue.

    • monitoring · Apr 24, 2026, 11:19 PM UTC

      Network packet loss has returned to normal levels. We are monitoring the Machines API for stability.

    • resolved · Apr 24, 2026, 11:31 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Errors when adding or editing Github integrations for deployments
    Resolved 1h 20m
    Started Apr 23, 2026, 03:05 PM UTC · Resolved Apr 23, 2026, 04:26 PM UTC
    Dashboard
    5 updates · show timeline
    • investigating · Apr 23, 2026, 03:05 PM UTC

      We're investigating reports of "500" errors when trying to add a new Github integration or edit an existing Github integration in Fly.io/dashboard. This only affects "Launch an app from Github" or trying to change settings for an app set up this way. Existing integrations continue to work normally. It does not affect deploys done with `flyctl` or existing, running apps.

    • identified · Apr 23, 2026, 03:22 PM UTC

      The issue has been identified and a fix is being implemented.

    • identified · Apr 23, 2026, 03:22 PM UTC

      We are continuing to work on a fix for this issue.

    • monitoring · Apr 23, 2026, 03:39 PM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Apr 23, 2026, 04:26 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Errors (5xx, timeouts) in Fly.io dashboard
    Resolved 33m
    Started Apr 23, 2026, 11:17 AM UTC · Resolved Apr 23, 2026, 11:50 AM UTC
    Dashboard
    4 updates · show timeline
    • investigating · Apr 23, 2026, 11:17 AM UTC

      We are investigating issues with web dashboard.

    • identified · Apr 23, 2026, 11:35 AM UTC

      The issue has been identified and a fix is being implemented.

    • monitoring · Apr 23, 2026, 11:45 AM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Apr 23, 2026, 11:50 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Fly.io outage history

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

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 13 incidents
  • flyctl deploy creating new app instances Resolved
    Started Apr 28, 2026, 11:50 PM UTC · Resolved Apr 29, 2026, 12:40 AM UTC · 49m
  • Slow machines operations in IAD region Resolved
    Started Apr 24, 2026, 10:45 PM UTC · Resolved Apr 24, 2026, 11:31 PM UTC · 45m
  • Errors when adding or editing Github integrations for deployments Resolved
    Started Apr 23, 2026, 03:05 PM UTC · Resolved Apr 23, 2026, 04:26 PM UTC · 1h 20m
  • Errors (5xx, timeouts) in Fly.io dashboard Resolved
    Started Apr 23, 2026, 11:17 AM UTC · Resolved Apr 23, 2026, 11:50 AM UTC · 33m
  • Increased latency in SIN Resolved
    Started Apr 20, 2026, 02:29 PM UTC · Resolved Apr 20, 2026, 05:38 PM UTC · 3h 9m
  • TLS certificate issues Resolved
    Started Apr 17, 2026, 01:06 PM UTC · Resolved Apr 18, 2026, 08:42 PM UTC · 1d 7h
  • Network issues in SYD Resolved
    Started Apr 15, 2026, 11:08 AM UTC · Resolved Apr 16, 2026, 10:59 AM UTC · 23h 51m
  • Heightened latency in ORD Resolved
    Started Apr 12, 2026, 06:50 PM UTC · Resolved Apr 12, 2026, 11:03 PM UTC · 4h 12m

See Fly.io in your Pingoru dashboard

Monitor Fly.io alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Fly.io to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Fly.io incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Fly.io or see every provider at once.

Maintenance calendar

Scheduled Fly.io maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Fly.io status change, one inbox

Pingoru watches Fly.io's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Fly.io reports on 53 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Fly.io alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Fly.io maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Fly.io services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Fly.io from the same account, with per-user notification preferences for any monitor.

Get notified on Fly.io status changes

Pingoru watches Fly.io's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Fly.io free

Monitor Fly.io along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Fly.io and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Fly.io uptime & incident history

See 90 days of Fly.io uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Fly.io uptime history

Frequently asked questions

What is Fly.io's uptime?
Over the last 90 days, Fly.io reported 98.46% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.fly.io — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Fly.io's uptime history rolling forward in real time.
Has Fly.io had outages in 2026?
Yes — Fly.io has had 50 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Fly.io outage?
The most recent Fly.io incident was "flyctl deploy creating new app instances", which started on April 28, 2026 and was resolved on April 29, 2026. Pingoru captured this directly from https://status.fly.io. See the full incident card above for affected components and the update timeline.
How often does Fly.io have outages?
Based on the last 90 days, Fly.io averages 16.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Fly.io's status page?
Fly.io's official status page is https://status.fly.io. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Fly.io down right now?
Fly.io is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Fly.io reports a change. Current status is based on 53 tracked services.
How does Pingoru know if Fly.io is down?
We read https://status.fly.io directly, using Fly.io's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Fly.io has an outage?
Create a free Pingoru account and add Fly.io as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Fly.io's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Fly.io incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Fly.io issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Fly.io status?
We use Fly.io's own status page at https://status.fly.io. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked Fly.io components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Fly.io's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Fly.io free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →