Expert incident response for Vercel
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.
We're on it.
Your report is with the team. Keep an eye on your inbox, we'll reply there.
My app on Vercel is down. What should I do?
Check vercel-status.com first. If Vercel reports nothing, open the Runtime Logs for your production deployment: FUNCTION_INVOCATION_FAILED means a function threw, and FUNCTION_INVOCATION_TIMEOUT means it ran past its maximum duration. If the errors started with your latest deployment, use Instant Rollback to put the previous one back, then fix forward.
- 1 Check Vercel's status vercel-status.com lists incidents by product. If one matches what you see, the problem is upstream.
- 2 Read the function error
FUNCTION_INVOCATION_FAILED(500) means your function threw.FUNCTION_INVOCATION_TIMEOUT(504) means it ran past its maximum duration, usually waiting on a slow database or API. - 3 Line it up with your last deployment Compare when the errors started with your deployments list. A new environment variable or dependency counts as a change too.
- 4 Roll back, then dig in Instant Rollback in the dashboard, or
vercel rollback, puts the previous production deployment back. Then read the Runtime Logs and check what your functions call.
Guides for the errors you're seeing
- How to reduce Vercel Function cold starts
- Fix “Cannot find module axios/dist/node/axios.cjs” on Vercel
- Fix “TypeError: fetch failed” on Vercel and Next.js
- Fix Vercel “FUNCTION_INVOCATION_FAILED” 500 errors
- Fix Vercel “MIDDLEWARE_INVOCATION_FAILED” errors
- How to debug Vercel function timeouts
- Vercel 504 Gateway Timeout on Serverless Functions: Causes and Fixes
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
“just 2 hours after signing up for @polylane it prevented a potential problem in production. I changed the request body schema for an API endpoint and if I would've just merged it, one of our dashboard pages would've crashed until the API was fully deployed too. Pretty simple mistake, but I forgot this time. polylane didn't”
Andreas Thomas Co-founder & CTO at Unkey Common questions
Is Vercel down or is it my app?
Check vercel-status.com. If it shows no incident for the products you use, open your deployment's Runtime Logs: the error code there tells you whether your function threw or timed out.
What does FUNCTION_INVOCATION_TIMEOUT mean?
Your function ran longer than its maximum duration, so Vercel stopped it and returned a 504. Find what it was waiting on, usually a database query or an upstream API, before raising the limit. More in our 504 guide.
How do I roll back a deployment on Vercel?
Use Instant Rollback on the production deployment in the dashboard, or run vercel rollback from the CLI.
Who will help me with a Vercel incident?
Our founding team, engineers who have carried the pager for production systems at scale, working with Polylane's agents across your Vercel projects, code and telemetry.