Hobby plan still hitting 25 service/day limit after midnight UTC reset — please raise limit
hulkmode85
PROOP

2 months ago

Hi Railway team,

I'm on the Hobby plan (workspace: hulkmode85's Projects) and I'm hitting the 25 service/day creation limit even after midnight UTC today (April 5, 2026).

Error message received via GraphQL API:

"You've hit the service creation limit for new accounts (25 services per day). Contact us at station.railway.com to raise this."

Situation:

  • I upgraded to Hobby plan specifically to run multiple services
  • - I have 4 projects that were created but have no services attached yet due to hitting this limit:
  • - kalshi-correlation-arb-bot (project ID: d4a1db94-b7eb-4475-a24f-582f95d85bb2)
  • - kalshi-fed-futures-bot (project ID: 63661cd9-4971-4b82-a045-c33ada3c0d0a)
  • - kalshi-volume-spike-bot (project ID: 1535cdbe-ba46-4a27-93e5-379c1d036d4e)
  • - kalshi-pnl-tracker (project ID: 00c2018f-b2bc-4463-87d8-8082cd2d4807)
  • - I currently have ~19 services running across ~23 projects (all legitimate bots)
  • - The limit appears to be a rolling 24-hour window, not a calendar-day reset — could you clarify exactly how the reset works?

Requests:

  1. Please raise the service creation limit for my account so I can deploy the 4 remaining services
  2. 2. Confirm whether the 25/day limit applies on Hobby plan or if this is a "new account" restriction that should be lifted

Thank you

Solved

3 Replies

Status changed to Awaiting Railway Response Railway about 2 months ago


2 months ago

We cannot raise or remove limits for hobby users. Your current limit will reset 24 hours from when you were limited; it does not necessarily reset at midnight.

If you aggressively retried while rate-limited, you may have extended your timeout well beyond the 24-hour period.


Status changed to Awaiting User Response Railway about 2 months ago


brody

We cannot raise or remove limits for hobby users. Your current limit will reset 24 hours from when you were limited; it does not necessarily reset at midnight. If you aggressively retried while rate-limited, you may have extended your timeout well beyond the 24-hour period.

hulkmode85
PROOP

2 months ago

how do i know if i did that? and how do i know when the 24 hr period ends? does the higher upgrade plan solve this?


Status changed to Awaiting Railway Response Railway about 2 months ago


2 months ago

Since it is a 24-hour timer, wait 24 hours after your last deployment attempt, and the time will be up.


Status changed to Awaiting User Response Railway about 2 months ago


Railway
BOT

a month 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 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...