Expert incident response for Fly.io

Our founding team picks up your incident, and Polylane's agents dig through your logs, metrics, traces and code with them.

Real engineers who've carried the pager The team has been on-call at Cloudflare, Webflow, Groq, Twilio, and Robinhood. They've been where you are right now.
Multi-cloud incident response Polylane investigates incidents across AWS, Cloudflare, Vercel, Kubernetes and the rest of your stack, from the edge to the database.
Unified context & investigation Logs, metrics, traces, deploys and code in one context graph. Connect in minutes, not weeks.
Least-privilege access New cloud accounts connect read-only, with scoped credentials. Nothing in production changes unless you allow it.

My app on Fly.io is down. What should I do?

Check status.flyio.net first. If Fly reports nothing, run fly status and fly logs: a 502 usually means your app isn't listening on the internal_port from fly.toml or its machines are failing health checks, and an out-of-memory kill shows up in the logs. If the errors started with a deploy, redeploy the previous image, then fix forward.

1 Check Fly's status status.flyio.net lists incidents by region and service. If your regions show one, the problem is upstream.
2 Read the machines and logs fly status shows machine state and failing checks, and fly logs the errors. "Out of memory: Killed process" means a machine needs more memory, or your app is leaking it.
3 Line it up with your last change fly releases lists recent deploys. Setting a secret creates a new release too, so it counts as a change.
4 Roll back, then dig in Fly has no rollback command: find the last good release's image with fly releases --image and redeploy it with fly deploy --image.

Guides for the errors you're seeing

How we resolve active incidents

1 Rapid onboarding A Polylane engineer reaches out, connects Polylane to your clouds, code and telemetry, and confirms what's affected.
2 Investigation & mitigation Polylane's agents investigate across logs, metrics, traces and recent changes, and an engineer works with you on the right mitigation.
3 Remediation, validation & monitoring The fix lands in your repo for your team to review. Polylane checks that things are back to normal and keeps watching every deploy after it.

Why teams choose Polylane

Every cloud in one graph AWS, Cloudflare, Vercel, Kubernetes and more, mapped into one context graph with your code.

Connected in minutes Connect with OAuth or the CLI. No agents to install, no code changes.

Real engineers on the other end Your report goes straight to the people who build Polylane.

Evidence for every claim Every finding links to the log line, metric or deploy behind it.

You stay in control Read-only by default. Nothing writes to production unless you allow it, and you can switch it off at any time.

Works with your coding agents Claude Code, Cursor and other agents reach Polylane over MCP, so they can dig in with you.

“So far @polylane is very cool! Even more that it's finding issues, creating fixes and then working with @pullfrogai in PR's to improve it even more.”

Ben @nurodev

Common questions

Is Fly.io down or is it my app?

Check status.flyio.net. If your regions show no incident, run fly status and fly logs to see whether your machines are crashing or failing checks.

Why is my Fly.io app returning 502 errors?

Fly's proxy got no response from your app: it isn't listening on the internal_port from fly.toml, it's listening on localhost instead of 0.0.0.0, or its machines are crashing or failing health checks.

How do I roll back on Fly.io?

Redeploy an earlier image: fly releases --image lists each release's image, and fly deploy --image deploys it again.

Who will help me with a Fly.io incident?

Our founding team, engineers who have carried the pager for production systems at scale, working with Polylane's agents across your Fly apps, code and telemetry.