a month ago
Hi! Our service is healthy, but Railway's edge is returning HTTP 429 to legitimate,
low-volume clients, so those requests never reach our app.
-
Project: ruiz-priego-abogados · Service: portal · Region: iad
-
Domain: ruizypriego.up.railway.app
-
Latest deployment: SUCCESS. /health returns 200 in our HTTP logs when requests get through.
-
Blocked response: HTTP 429, body "rate limited",
headers "server: railway-hikari", "x-railway-edge: iah1", "x-hikari-trace: iah1.k00j"
-
Affected clients:
-
UptimeRobot monitor on /health (1 request every 5 minutes)
-
Our scheduled GitHub Actions backup job (1 request every 6 hours);
it failed on 2026-10-07 at 18:57 UTC with 429 on all 5 retries.
-
Could you check why the edge is rate-limiting these clients and lift it? Thanks!
1 Reply
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago