Expert incident response for Cloudflare

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 Cloudflare is down. What should I do?

Check cloudflarestatus.com first. If Cloudflare reports nothing in your region, the error code tells you where to look: 520 to 526 come from your origin server behind Cloudflare, and 1101 or 1102 come from your Worker. If the errors started with a deploy, roll it back with wrangler rollback, then find the cause in Workers Logs or wrangler tail.

1 Check Cloudflare's status cloudflarestatus.com lists incidents by service and data centre. If your region shows one, the problem is upstream: watch it and tell your users.
2 Read the error code 520 to 526 mean Cloudflare got no good response from your origin: it's down (521), timing out (522, 524), unreachable (523) or failing TLS (525, 526). 1101 means your Worker threw an uncaught exception, 1102 that it ran out of CPU or memory.
3 Line it up with your last change Compare when the errors started with your latest Worker deploy, DNS change or configuration change. wrangler deployments list shows recent Worker versions.
4 Roll back, then dig in wrangler rollback restores the previous Worker version. Then read the exception in Workers Logs or live with wrangler tail, and check bindings like D1, KV, Durable Objects and Hyperdrive.

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.

“there was something wrong with our docs deployment, and Polylane automatically found and notified us about it... insane stuff @boristane”

Dhravya Shah Founder & CEO at Supermemory

Common questions

Is Cloudflare down or is it my app?

Check cloudflarestatus.com first. If it shows no incident for your region, look at the error code: 52x errors point at your origin server and 1101 or 1102 point at your Worker code, so the fix is on your side.

What does Cloudflare error 522 mean?

Cloudflare couldn't open a connection to your origin server in time. The origin is usually down, overloaded, or blocking Cloudflare's IP ranges at a firewall.

How do I roll back a Cloudflare Worker?

Run wrangler rollback to restore the previous version, or pick an earlier version under Deployments in the Cloudflare dashboard.

Who will help me with a Cloudflare incident?

Our founding team. Boris, our founder, built and led the observability team for Cloudflare Workers after Cloudflare acquired his company, Baselime.