Fly.io logo
ALL SYSTEMS OPERATIONAL

Fly.io systems
are operational.

Pulsetic detects outages before the provider officially reports them. Monitoring since Feb 2026 · 118 incidents caught

Last checked: just now · 0 user reports (24h) · Trusted by 30,000+ teams

  • ALL SYSTEMS OPERATIONAL

    Fly.io is up and running.

    Last incident resolved 32 minutes ago


    No active incidents at this time. Noticed something?
  • User Reports: Last 24 Hours

    0 reports

    Bars represent 20-min intervals. Occasional spikes may reflect individual issues, not widespread outages.

  • Outage Map

    No reports yet

    Reports by region (last 24h)

    No reports in the last 24h
  • Recent User Reports

    Live

    Latest 50 reports from the last 48 hours

  • Top reported issues

    Click an issue to upvote it and help us better indicate the service status.

    Service outage 0
    Degraded performance 0
    Error messages 0
    Timeouts / no response 0
    Authentication issues 0
    Network / connectivity issues 0
    Feature not working 0
    API errors 0
    Billing or usage issues 0
    Other 0

    Have a different problem?

  • Issue breakdown

    0 total votes

    Distribution of reported issues over the last 24 hours.

    Service outage 0%
    Degraded performance 0%
    Error messages 0%
    Timeouts / no response 0%
    Authentication issues 0%
    Network / connectivity issues 0%
    Feature not working 0%
    API errors 0%
    Billing or usage issues 0%
    Other 0%

Last 90 days

90-Day Health Summary

  • Total Incidents

    69

    Since Feb 2026

  • Major / Critical

    30

    30 high-impact incidents

  • Minor Incidents

    39

    Avg. 0.4 per day

  • Median Resolution

    1h 38m

    P95: 13h 10m

Fly.io Response Time, ms

By Continent
Location List

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
MPG creation is failing in GRU due to lack of capacity
Aug 4, 2026 · 7:03 PM 8h 19m
Major
Resolved
Details →
Certificate issuance delays
Aug 4, 2026 · 2:53 PM 9h 4m
Minor
Resolved
Details →
Inbound connection failure to Fly Apps
Aug 3, 2026 · 3:16 PM 3h 33m
Critical
Resolved
Details →
Managed Postgres v2 control plane issues in iad
Aug 1, 2026 · 5:01 PM 1h 28m
Minor
Resolved
Details →
Capacity issues in CDG
Jul 31, 2026 · 4:44 PM 3h 27m
None
Resolved
Details →
Outbound email issues
Jul 31, 2026 · 1:34 PM 1h 16m
Minor
Resolved
Details →
Increased API latency
Jul 29, 2026 · 12:41 PM 44m
Minor
Resolved
Details →
High number of 5XX on the Machines API and dashboard
Jul 20, 2026 · 7:10 AM 9h 59m
Critical
Resolved
Details →
Egress IPv6 issues in BOM
Jul 19, 2026 · 3:48 AM 1h 4m
Minor
Resolved
Details →
Brief Flycast / MPG interruption in YYZ
Jul 17, 2026 · 6:30 PM < 1m
None
Resolved
Details →

How do they compare?

Alternatives to Fly.io

Teams monitoring Fly.io also watch

Other Monitored Services

Get alerted the moment Fly.io goes down.

No credit card · free plan · 2-minute setup

Common questions

Frequently Asked Questions

  • Is Fly.io down today?

    Check the status badge at the top of this page for the current status. Pulsetic polls the official status page every few minutes and cross-references with user reports to give you the most accurate picture.

  • How often does Fly.io go down?

    Based on our 90-day data, we've detected 69 incidents, of which 30 were major or critical. The median resolution time is 1h 38m.

  • How are outages detected?

    Pulsetic polls the official status page every few minutes from multiple global locations. Crowdsourced user reports provide an additional early-warning signal, often surfacing issues before the official monitors catch them.

  • Is it down for everyone or just me?

    The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.

  • What does "never acknowledged" mean?

    "Never acknowledged" means Pulsetic detected a real service disruption, confirmed by multiple user reports, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.