Expert incident response for Modal

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 Modal is failing. What should I do?

Check status.modal.com first. If Modal reports nothing, read the app's logs in the dashboard or with modal app logs: a container out of memory needs a larger memory request, and a function that hits its timeout needs a longer timeout or less work per call. If the errors started with a deploy, roll back with modal app rollback, then fix forward.

1 Check Modal's status status.modal.com lists incidents. If one matches what you see, the problem is upstream.
2 Read the app logs The dashboard shows each function call with its logs and errors, or run modal app logs. Out-of-memory and timeout errors name the function that hit them.
3 Line it up with your last deploy Compare when the errors started with your latest modal deploy. A changed image, dependency or secret counts as a change too.
4 Roll back, then dig in modal app rollback redeploys the app's previous version, and adding a version such as v3 picks an earlier one. Then fix forward with what the logs showed.

Guides for the errors you're seeing

Modal container out of memory: find the cause and fix it

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.

“It fixed something like 5 mins in after we set it up. It not only helps with on-call investigations, it's also pro-active about improving issues in CI, like flaky tests, hardening against transient errors, etc. Great product!”

Vitor Balocco Runlayer, on Product Hunt

Common questions

Is Modal down or is it my app?

Check status.modal.com. If it shows no incident, the app's logs show which function fails and why.

Why is my Modal container running out of memory?

The function needs more memory than it requested. Raise its memory request, or hold less in memory per call. More in our guide.

How do I roll back a Modal deployment?

Run modal app rollback APP for the previous version, or modal app rollback APP v3 for a specific earlier one.

Who will help me with a Modal incident?

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