Is Fly.io Down?

Fly.io: Operational

No, Fly.io is up. All systems operational.

checked 56s ago·All Systems Operational·Official Fly.io status page →

Fly.io components

AMS - Amsterdam, NetherlandsOperational
Fly Machine .internal DNSOperational
Usage Metrics APIOperational
Upstash for RedisOperational
Customer ApplicationsOperational
Management Plane - ORDOperational
Stripe API ConnectionOperational
DashboardOperational
ARN - Stockholm, SwedenOperational
Fly Machine External DNSOperational
Management Plane - IADOperational
Machines APIOperational
Management Plane - FRAOperational
*.flyio.net NameserversOperational
Management Plane - GRUOperational
Persistent Storage (Volumes)Operational
BOM - Mumbai, IndiaOperational
Management Plane - LAXOperational
flydns.netOperational
DeploymentsOperational
CDG - Paris, FranceOperational
Management Plane - SYDOperational
Remote BuildsOperational
Management Plane - AMSOperational
DFW - Dallas, Texas (US)Operational
LogsOperational
Management Plane - LHROperational
MetricsOperational
EWR - Secaucus, NJ (US)Operational
Management Plane - NRTOperational

What is Fly.io?

Fly.io is a platform for deploying applications close to users by running containerized workloads across a global network of regions. Developers use it to launch full-stack apps, databases via Fly Postgres, and background workers without managing traditional server infrastructure. It is widely used by individual developers, startups, and teams who want low-latency global deployments with a relatively simple CLI-driven workflow.

Signs Fly.io is having problems

  • flyctl deploy hangs or returns a timeout error mid-deployment, with machines failing to reach the running state
  • HTTP requests to a deployed app return 502 Bad Gateway or connection refused errors despite the app appearing healthy locally
  • Fly Postgres connections are refused or existing connections are dropped, causing database-dependent apps to crash
  • flyctl commands such as fly status or fly logs return API errors or take unusually long to respond, indicating a control plane issue

Find out when your own services go down

You can check Fly.io here — but a heartbeat monitor tells you the moment your API, website, or cron job stops responding, so you hear about your own downtime before your users do.

Frequently asked questions

How can I tell if Fly.io is down?

Check the official Fly.io status page at https://status.flyio.net for real-time incident reports and component health. You can also run flyctl status on your app to distinguish a platform-wide issue from a problem specific to your deployment. Community discussion on the Fly.io forum often surfaces incidents quickly as well.

Where is the official Fly.io status page?

The official status page is https://status.flyio.net. It lists the health of individual components such as the API, builders, Fly Postgres, and specific regions, and it publishes incident updates and post-mortems.

Does Fly.io publish post-mortems for outages?

Yes. Fly.io has a practice of publishing detailed incident post-mortems on their status page and community forum. These typically explain the root cause, the timeline, and steps taken to prevent recurrence, making them useful reading for teams evaluating platform reliability.

How do I get alerted when my own services go down, regardless of the platform?

Platform status pages only tell you about the infrastructure layer. If you want to know the moment your specific app stops responding, a heartbeat monitor pings your service on a schedule and alerts you immediately when it misses a check. CronJobPro offers this kind of uptime monitoring independently of whatever hosting platform you use.

Not affiliated with or endorsed by Fly.io. Status data is sourced from Fly.io's official status page (status.flyio.net); for critical incidents, always verify at the official source. All trademarks are property of their respective owners.