---
title: "504 Gateway Timeout in Vercel"
canonical: "https://lemwatch.com/http-status-codes/504/in-vercel"
platform: "Vercel"
last_verified: "2026-08-11"
source: "https://lemwatch.com"
---

# HTTP 504 Gateway Timeout in Vercel

**Platform** — Vercel — serverless deployment platform for Next.js and edge apps.

**Where it surfaces** — Vercel's Edge Network, serverless function logs, or the deployment dashboard.

## Cause on this platform

A serverless function exceeded the max duration (10s on Hobby, 60s on Pro, 900s on Enterprise) or the edge middleware timed out (25s hard cap).

## Fix on this platform

Move long tasks to a queue (Vercel Queues, Inngest, QStash), stream the response, or upgrade the function's `maxDuration` in `vercel.json`.

## Log signature

```
[GET] /api/report status=504
FUNCTION_INVOCATION_TIMEOUT
```

## Generic reference

A proxy or gateway server didn't receive a response from the upstream server in time — the "slow backend" failure mode that's different from 502 (broken backend).

_Canonical HTML page: https://lemwatch.com/http-status-codes/504/in-vercel_