15 days ago
My service web-production-4e7a5.up.railway.app (project: adequate-tenderness, service: web) is returning 429 with body rate limited on every request — including a plain GET /health with essentially no real traffic — and this is blocking real inbound Twilio WebSocket connections (error 31920 on Twilio's side, handshake never completes).
What I've confirmed:
Billing is current, no usage limits reached ($0.75 of $5 Hobby plan)
status.railway.com shows Fully Operational, no active incidents
Manually redeployed the service — issue persists after redeploy
Response headers: server: railway-hikari, x-hikari-trace: atl1.mwdw, x-railway-edge: atl1
Example failing request:
curl -I https://web-production-4e7a5.up.railway.app/health
HTTP/2 429
content-type: text/plain; charset=utf-8
content-length: 12
This is affecting real production phone calls from customers. Can you check if this domain/deployment is stuck in an edge-level rate-limit or block state? Happy to provide the exact service ID or deployment ID if needed.
1 Replies
15 days ago
Your service has Under Attack Mode enabled (set to stay on until manually disabled). While active, it turns away all non-browser traffic, which includes curl requests and Twilio WebSocket connections. Disable it from the service's Settings under the Edge section and the 429s will clear.
Status changed to Awaiting User Response Railway • 15 days ago
8 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 • 8 days ago