Hi Sbullocks,

Since static assets work but every function hangs until timeout, I’d separate “Vercel can route to a function” from “your new runtime code is waiting forever.”

First, deploy one tiny endpoint that does not import anything shared from the app:

1
// app/api/ping/route.ts
2
export const dynamic = "force-dynamic"
3

4
export async function GET() {
5
  return Response.json({ ok: true, time: Date.now() })
6
}
7

If that works, the platform/function routing is fine and I’d look at the changes from the rate-limiting commit: middleware, shared auth helpers, Redis/KV/database clients, external fetches, or env vars that are now awaited before returning a response.

If that tiny endpoint also hangs, check whether it is really included in the latest deployment and inspect logs outside the dashboard:

1
vercel inspect <deployment-url> --logs
2
vercel logs <deployment-url> --since 1h
3

For the affected routes, I’d also add timing around each awaited operation:

1
console.time("rate-limit")
2
await checkRateLimit()
3
console.timeEnd("rate-limit")
4

5
console.time("upstream")
6
const res = await fetch(url, { signal: AbortSignal.timeout(10000) })
7
console.timeEnd("upstream")
8

A very common cause after adding rate limiting is a server-side call waiting on a missing/incorrect Production env var or an upstream service that is reachable locally but not from the deployed function. The key signal is whether the function logs stop before or after the rate-limit / external API call.

Vercel has a useful slow-function debugging command here:

https://vercel.com/docs/functions/debug-slow-functions

vercel.com

Debugging slow Vercel Functions

Diagnose and fix slow Vercel Functions using CLI tools, logs, and timing analysis.

Can you share the first log line before the hang and whether the isolated /api/ping route returns immediately?