Skip to content
Edge returns 429 "rate limited" to low-volume proxied Vercel traffic (2026-11-10 14:21–14:47 UTC)
tafactoryny-sketch
OP

9 days ago

For about 26 minutes on 2026-11-10 (14:21–14:47 UTC), the Railway edge returned HTTP 429 with the body rate limited to requests for our API service. The requests never reached our application.

Setup: our frontend runs on Vercel (Pro). Every API request from end users goes through a Vercel external rewrite to the public domain above, so Railway sees all our traffic coming from a small set of Vercel egress IPs, never from end users' IPs. No browser reaches the Railway domain directly.

Edge settings on this service: Under Attack Mode is not active, CDN Caching is off, and no Edge Rules are configured. We therefore assume the 429s came from the edge's built-in per-source-IP limiter.

Error messages

Status 429, response body rate limited.

125 requests were throttled. They covered GET and POST, many endpoints, two custom domains, and one internal cron endpoint.

In the same minutes, other requests succeeded (200/201/307), so the service was healthy and the throttling looks per-source.

Our application never returns 429 on these routes. Its own limiters answer 400 with a different message.

Vercel's firewall action on every throttled request was allow.

We saw zero 429s in the 23 hours outside this window.

Logs

We have no Railway-side logs for these requests because they were rejected at the edge. These figures come from Vercel's request logs. The full redacted list (timestamp, method, path template, Vercel edge region, Vercel request id) is attached as CSV.

Volume was low. Total proxied traffic peaked at about 515 requests per 10 minutes. The busiest single Vercel edge region (cle1) sent at most about 87 requests in one minute (~1.5 req/s), and that region received 80 of the 429s.

429 count per minute (UTC, 2026-11-10):

14:21 8 14:22 3 14:25 1 14:28 4 14:30 3 14:31 2 14:32 4

14:33 3 14:34 7 14:35 7 14:36 21 14:37 8 14:38 3 14:39 8

14:40 16 14:41 4 14:45 3 14:46 15 14:47 5

All proxied traffic by status (UTC, 10-minute windows):

window 200 201 307 429

14:00 79 3 1 0

14:10 146 0 13 0

14:20 515 1 98 16

14:30 302 7 45 66

14:40 149 1 43 43

14:50 15 0 0 0

429 by Vercel edge region: cle1 80, iad1 23, sfo1 11, hkg1 11.

Sample Vercel request ids: t7rm8-1794320490189-430325095d26, 6fmbh-1794320493969-8eb4dad9c691, ssj72-1794322054541-ff28556242e5

Questions

Please confirm what produced these 429s. Was it the built-in per-source-IP limiter?

What is the threshold and window of that limiter?

How can we stop it from throttling our legitimate proxied traffic? For example: raise the limit for this service, allowlist Vercel's egress IPs, or let requests that carry a specific secret request header (which we set on every proxied request) bypass the limiter.

Solved

1 Reply

Railway
BOT

9 days ago

The per-domain limits we publish for the edge are about 11,000 HTTP requests per second, 10,000 concurrent connections, and 10,000 requests per connection (Specs & Limits). Your peak of roughly 1.5 req/s from one Vercel region is far below those, and we have not been able to confirm from our side what returned these 429s, so we can't give you a threshold or window for a per-source-IP limit.

There is no setting on your plan to raise edge limits per service. Edge rules can match on client IP or on a request header (such as your proxy secret header) with an Allow action, but an Allow rule only skips your later edge rules; we have not verified that it exempts requests from platform-level limits, so it shouldn't be relied on as a fix for this.

To trace the throttled requests on our side, could you share the X-Railway-Request-Id and X-Railway-Edge response headers from any of the 429 responses (Vercel may have captured response headers in its logs), and confirm which Railway service the two custom domains are attached to?


Status changed to Awaiting User Response Railway • 9 days ago


Railway
BOT

2 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 1 day ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...