Is Fly.io Down Right Now?
Fly.io is a developer PaaS for running Docker containers globally. Outages are region-specific — check your deployment region before assuming a full outage.
Updated May 2026
📡 Monitor your APIs — know when they go down before your users do
Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.
Affiliate link — we may earn a commission at no extra cost to you
How to Check If Fly.io Is Down
- 1. Visit status.flyio.net — check your specific region (iad, ord, lax, fra, sin, etc.)
- 2. Run
fly status --app your-app-nameto see machine states - 3. Check community.fly.io for real-time developer reports
- 4. Run
fly logs --app your-app-nameto see recent error messages
Fly.io Service Components
Fly Machines
Docker containers on bare metal globally. Each machine is independent.
Region-specific outages are most common here
Fly Postgres
Self-managed Postgres on Fly Machines. Primary/replica via Patroni.
This is YOUR Postgres, not a managed service
Tigris (Object Storage)
S3-compatible globally-distributed object storage.
Check status separately from compute
Monitor your Fly.io apps — know before your users do
Better Stack checks your Fly.io endpoints every 30 seconds across multiple global regions. Get Slack/email/SMS alerts instantly when any region fails.
Try Better Stack Free →Fly.io Error Reference
fly deploy: Error: error creating a new machine
Cause: No capacity in the region or Fly.io infrastructure issue
Fix: Try fly deploy --region ord (or another region); check status.flyio.net for your region
machine failed to start: exit status 1
Cause: App crashes on startup — missing env vars, port mismatch, or OOM
Fix: Run fly logs --app your-app; ensure app listens on $PORT or fly.toml internal_port; check fly scale show
health checks failed (max attempts exceeded)
Cause: App not responding on health check path within timeout
Fix: Check fly.toml [[services.http_checks]] path and timeout; ensure your app starts in <30 seconds
FATAL: password authentication failed (Fly Postgres)
Cause: DATABASE_URL secret incorrect or Postgres machine down
Fix: Run fly postgres status --app your-postgres; check fly secrets list for DATABASE_URL
error connecting to Flycast / private networking
Cause: WireGuard tunnel not active or DNS resolution failed
Fix: Run fly wireguard status; run flyctl doctor to diagnose; use .internal hostnames not IPs
volume has no space left (OOM or disk)
Cause: Fly Volume is full
Fix: Run fly volumes list --app your-app; create a new larger volume; consider Tigris for object storage
Fly.io Debugging Cheat Sheet
# Check app status and machines fly status --app your-app fly machines list --app your-app # View live logs fly logs --app your-app # SSH into a running machine fly ssh console --app your-app # Check resource usage (CPU/RAM) fly scale show --app your-app # Scale up RAM if OOMKilled fly scale memory 512 --app your-app # Check Fly Postgres health fly postgres status --app your-postgres-app # Connect to Postgres directly fly postgres connect --app your-postgres-app # Check secrets fly secrets list --app your-app # Diagnose WireGuard/networking flyctl doctor # Deploy to a specific region fly deploy --region iad --app your-app
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Fly.io goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Fly.io + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial
Related Developer Platform Guides
Frequently Asked Questions
Is Fly.io down right now?
To check if Fly.io is down, visit status.flyio.net (Fly.io's official status page). Fly.io reports status by region — check your specific deployment region (iad, ord, lax, fra, sin, etc.). Also check the Fly.io Community forums (community.fly.io) where incidents are often discussed in real time. Fly.io outages are typically region-specific: if your app is in iad (US East) and there's an incident in fra (EU), your app is likely unaffected.
Why is my Fly.io deployment failing?
Fly.io deployment failures (flyctl deploy errors) have several causes: (1) Build errors — the Docker image build failed; check build logs with fly logs --app your-app, (2) Machine startup failure — your container crashes on start; check machine logs with fly machines list then fly machine status <machine-id>, (3) Health check failing — your app is not responding on the configured port within the timeout; check your fly.toml [[services]] health check config, (4) No available capacity in the region — try adding --region with an alternate region, (5) Fly.io platform incident — check status.flyio.net. Run fly status --app your-app to see machine states.
Why is my Fly Postgres database down or unreachable?
Fly Postgres is self-managed PostgreSQL running on Fly Machines — it is NOT a managed database service. When Fly Postgres is "down": (1) Check if the Postgres app machines are running: fly machines list --app your-postgres-app, (2) Postgres machines can fail to start if the volume is full — run fly volumes list and check usage, (3) The primary machine may have failed; run fly postgres status --app your-postgres-app to see if failover is needed, (4) For connection issues from your app: use the internal Fly DNS address (yourapp.internal), not the public URL — internal networking is more reliable, (5) Connection string: check DATABASE_URL secret is set correctly with fly secrets list --app your-app.
Why are my Fly.io machines not starting or crashing immediately?
Fly Machines that crash immediately (OOMKilled, exit code 1) are usually caused by: (1) Out of Memory — the default 256MB RAM is too low for many apps; increase with fly scale memory 512 --app your-app, (2) Missing environment variables or secrets — check fly secrets list --app your-app and ensure DATABASE_URL, PORT, and other required vars are set, (3) Wrong entrypoint — Docker CMD or ENTRYPOINT is misconfigured for the Fly environment, (4) Port mismatch — your app must listen on the port specified in fly.toml internal_port (default 8080), (5) Volume not mounted — check that persistent volumes are attached if your app expects data at a specific path.
What are the best Fly.io alternatives when it is down?
Best Fly.io alternatives when it's down: (1) Render (render.com) — similar developer PaaS, managed Postgres, free tier available; deploy via git push, (2) Railway (railway.app) — one-click deploys from GitHub, managed databases, usage-based pricing, (3) Heroku — classic PaaS, simpler but higher cost at scale, (4) DigitalOcean App Platform — managed PaaS with global CDN, (5) Google Cloud Run — serverless containers, pay-per-request, global regions. For database specifically: Neon (serverless Postgres) or Supabase as drop-in alternatives to Fly Postgres.