2 months ago
We are on a Pro plan (10000 RPH / 50 RPS) and have a script that reads logs from the Railway API.
Yesterday, we hit a rate limit error with a Retry-After of ~86399 seconds. However, based on our logs:
- There are ~5-10 requests per second (not exceeding RPS)
- Last count before the error was 7591 / 10000 (below RPH)
It seems we were rate-limited despite staying within limits. I have attached logs for reference.
Could this be due to Cloudflare or IP-based throttling? Any guidance would be appreciated.
Thanks
Attachments
3 Replies
2 months ago
Your account on our end shows a Hobby plan workspace (currently in trial), not Pro. Hobby plan API limits are 1,000 RPH and 10 RPS, per our API rate limits documentation. If you are accessing the API via a token tied to a different (Pro) workspace or account, the rate limit headers would reflect that workspace's limits instead. The 86,399-second Retry-After value (24 hours) can occur when additional protections beyond the standard RPH/RPS limits are triggered. Could you confirm which workspace and token type you're using to make these API calls?
Status changed to Awaiting User Response Railway • 2 months ago
Railway
Your account on our end shows a Hobby plan workspace (currently in trial), not Pro. Hobby plan API limits are 1,000 RPH and 10 RPS, per our [API rate limits documentation](https://docs.railway.com/integrations/api#rate-limits). If you are accessing the API via a token tied to a different (Pro) workspace or account, the rate limit headers would reflect that workspace's limits instead. The 86,399-second Retry-After value (24 hours) can occur when additional protections beyond the standard RPH/RPS limits are triggered. Could you confirm which workspace and token type you're using to make these API calls?
2 months ago
My account should be connected to 2 Workspaces, one of which is my individual (hobby plan) and another one is Enterprise plan (the one I am seeing the problem in)
Also requests done with this API token work when I run script locally for production environment or in other Railway environments. It fails only after deployment in production environment
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
The address you are signed in with - s.****an@ge****ee.com - only shows as being part of a trial plan for the workspace: Sofiia Chaban Geniusee's Projects. Do you have another sign-in you use that we can investigate further?
Status changed to Awaiting User Response Railway • 2 months ago
2 months 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 • about 2 months ago