Fly.io logo
ALL SYSTEMS OPERATIONAL

Fly.io systems
are operational.

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

Last checked: 2 min ago · 0 user reports (24h) · Trusted by 30,000+ teams

Report an outage
  • ALL SYSTEMS OPERATIONAL

    Fly.io is up and running.

    Last incident resolved 14 hours ago


    No active incidents at this time. Noticed something? Let us know →
  • 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?

    Report an outage
  • 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

    60

    Since Feb 2026

  • Major / Critical

    26

    26 high-impact incidents

  • Minor Incidents

    34

    Avg. 0.4 per day

  • Median Resolution

    1h 39m

    P95: 16h 9m

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
Degraded networking in North America
Jun 24, 2026 · 1:42 AM 5h 15m
Minor
Resolved
Details →
Network issues in SIN, NRT
Jun 22, 2026 · 8:15 PM 1h 40m
Major
Resolved
Details →
SIN, NRT network issues
Jun 22, 2026 · 5:10 PM 2h 38m
Major
Resolved
Details →
Log search unavailable
Jun 19, 2026 · 6:05 PM 3h 47m
Minor
Resolved
Details →
Network Issues in SIN
Jun 17, 2026 · 3:21 AM 1h 33m
Major
Resolved
Details →
Macaroon Auth + Machines API Issues
Jun 15, 2026 · 3:03 PM 1h 37m
Critical
Resolved
Details →
MPG cluster provisioning is broken
Jun 15, 2026 · 6:20 AM 18m
None
Resolved
Details →
Elevated Sprites error rates in SIN
Jun 12, 2026 · 2:35 AM 1h 54m
Major
Resolved
Details →
Increased network latency in North America
Jun 11, 2026 · 1:16 AM 9h 56m
Minor
Resolved
Details →
Ingress Traffic issues in GRU
Jun 10, 2026 · 7:39 PM 13m
Major
Resolved
Details →

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 60 incidents, of which 26 were major or critical. The median resolution time is 1h 39m.

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