19 days ago
Project: smartkts
Project ID: f7f8c51b-5c5a-4b45-9b9a-a2973c602025
Service: jiwon-saup
Service ID: c0e12469-e559-4668-a0ce-413bddb7ecd5
Domain: jiwon-saup-production.up.railway.app
Since approximately 2026-06-18 03:50 UTC, all public requests to this
service's domain return:
HTTP/1.1 429 Too Many Requests
server: railway-hikari
The service itself is healthy (deployment status: SUCCESS, container logs
show the app starts and serves correctly). HTTP request logs show no
entries for these requests, indicating the block is happening at the edge
layer before reaching the application.
This appears to have been triggered by a burst of test requests and
redeploys during initial setup. It has now persisted for over an hour.
Could you please check whether this service/domain has an edge-level
rate limit or block applied, and lift it if so?
1 Replies
Status changed to Awaiting Railway Response Railway • 19 days ago
19 days ago
That 429 with a "rate limited" body comes from a per-source-IP request limiter at our edge, not a block applied to your service or domain. It triggers when a single client IP exceeds roughly 10,000 requests/second sustained, and it clears on its own once that IP drops back below the threshold. There is nothing pinned to your service for us to lift, and because the rejection happens before the request reaches your container, it won't appear in your HTTP logs.
If you're still seeing 429s well after your test burst stopped, that points to continued high-rate traffic from a single source IP rather than a lingering block. Sending requests from a different IP, or spreading them across more than one source, will not hit the per-IP limit.
Status changed to Awaiting User Response Railway • 19 days ago
12 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 • 12 days ago