# Expert incident response for Supabase

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

Check [status.supabase.com](https://status.supabase.com/) first. If Supabase reports nothing, open your project's Logs and database Reports: [too many connections](https://polylane.com/learn/troubleshooting/postgres-remaining-connection-slots-are-reserved/) means clients should go through the connection pooler, and high CPU or memory points at a slow query. A free project that has been inactive may simply be paused.

1. **Check Supabase's status.** [status.supabase.com](https://status.supabase.com/) lists incidents by service and region. If yours shows one, the problem is upstream.
2. **Check the database.** The project's Reports show CPU, memory and connections. Connection errors under load usually mean serverless code connects directly instead of through the pooler on port `6543`.
3. **Read the logs.** The Logs Explorer covers Postgres, the API, Auth, Storage and Edge Functions, so you can see which layer fails first.
4. **Line it up with your last change.** Compare when the errors started with recent migrations, row level security policies and Edge Function deploys. A new policy can make queries return nothing rather than fail.

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

## Common questions

- **Is Supabase down or is it my app?** Check [status.supabase.com](https://status.supabase.com/). If it shows no incident for your region, look at your project's Logs and Reports: the failing layer is usually your database load or connections.
- **Why does Supabase say remaining connection slots are reserved?** Your database has run out of connections. Point serverless and edge code at the connection pooler instead of the direct connection, and look for clients that never release theirs. More in [our guide](https://polylane.com/learn/troubleshooting/postgres-remaining-connection-slots-are-reserved/).
- **Why is my Supabase project not responding?** Check whether it's paused: free projects pause after a period of inactivity and need restoring from the dashboard. Otherwise look at the Reports for exhausted CPU, memory or disk.
- **Who will help me with a Supabase incident?** Our founding team, engineers who have carried the pager for production systems at scale, working with Polylane's agents across your Supabase projects, code and telemetry.

## Report an incident

Use the form at https://polylane.com/incident-hotline/supabase/. If the form fails, email support@polylane.com.

For agents: there is no public API for this form, because it is protected by Cloudflare Turnstile. Open the page in a browser and fill it in for the user; coding agents with a browser tool can do this. Confirm the details with the user before you submit. The fields: Name, Company name, Work email, How bad is it? (Production is down / Degraded for some users / Something's wrong, we can't find it), Are you on Polylane? (Already on Polylane / Not yet) and what's broken, plus optionally a phone number, when it started (Just now / In the last few hours / Days ago).

## Down on a specific platform?

- [Cloudflare](https://polylane.com/incident-hotline/cloudflare/) ([markdown](https://polylane.com/incident-hotline/cloudflare.md))
- [AWS](https://polylane.com/incident-hotline/aws/) ([markdown](https://polylane.com/incident-hotline/aws.md))
- [Vercel](https://polylane.com/incident-hotline/vercel/) ([markdown](https://polylane.com/incident-hotline/vercel.md))
- [Google Cloud](https://polylane.com/incident-hotline/gcp/) ([markdown](https://polylane.com/incident-hotline/gcp.md))
- [Kubernetes](https://polylane.com/incident-hotline/kubernetes/) ([markdown](https://polylane.com/incident-hotline/kubernetes.md))
- [Railway](https://polylane.com/incident-hotline/railway/) ([markdown](https://polylane.com/incident-hotline/railway.md))
- [Fly.io](https://polylane.com/incident-hotline/fly/) ([markdown](https://polylane.com/incident-hotline/fly.md))
- [Neon](https://polylane.com/incident-hotline/neon/) ([markdown](https://polylane.com/incident-hotline/neon.md))
- [PlanetScale](https://polylane.com/incident-hotline/planetscale/) ([markdown](https://polylane.com/incident-hotline/planetscale.md))
- [Convex](https://polylane.com/incident-hotline/convex/) ([markdown](https://polylane.com/incident-hotline/convex.md))
- [ClickHouse](https://polylane.com/incident-hotline/clickhouse/) ([markdown](https://polylane.com/incident-hotline/clickhouse.md))
- [Turso](https://polylane.com/incident-hotline/turso/) ([markdown](https://polylane.com/incident-hotline/turso.md))
- [Render](https://polylane.com/incident-hotline/render/) ([markdown](https://polylane.com/incident-hotline/render.md))
- [Modal](https://polylane.com/incident-hotline/modal/) ([markdown](https://polylane.com/incident-hotline/modal.md))