429 errors
trustworthyact-tech
HOBBYOP

20 days ago

Project ID: c38df80a-5ede-4e96-883c-5f961bd71f02

Service: know-your-builder-server

Problem: Edge returning 429 on all requests (edge: railway-hikari, region: hkg1) for 6+ days

Evidence:

Current deployment is healthy (running since 2026-08-01T11:10:33Z)

HTTP logs show zero traffic reaching the service

Issue persists after restart and plan upgrade

No maintenance notices correlate

$0 usage suggests edge is blocking before traffic is metered

Solved

2 Replies

Railway
BOT

20 days ago

Your service has Under Attack Mode enabled (set to stay on until manually disabled), which shows every new visitor a browser check before any request reaches your app. Since this service appears to serve an API rather than a website, all its traffic is non-browser and gets turned away at the edge, which is why zero requests are reaching the container. You can disable it from the service's Settings under the Edge section, or via the CLI with railway waf under-attack disable.


Status changed to Awaiting User Response Railway 20 days ago


Status changed to Solved trustworthyact-tech 20 days ago


trustworthyact-tech
HOBBYOP

20 days ago

thnks. you da best!


Status changed to Awaiting Railway Response Railway 20 days ago


Status changed to Solved Railway 20 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...