4 days ago
Hi Railway Team,
My Railway workspace was upgraded to the Hobby plan, and the subscription is active. Billing shows the $5 usage-based subscription successfully.
However, my production service is still returning HTTP 402 with the error: exceed_egress_quota.
Current usage is $0.00, with $5 included usage available. The deployment is showing ACTIVE / Deployment successful.
I have already redeployed the service 4 times after upgrading to Hobby, but the 402 restriction is still present.
Project: independent-beauty
Service: QuoteGen-cursor-ready-5
Environment: production
Please check why the egress restriction is still active and help restore my service.
Thank you
Attachments
1 Replies
4 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 4 days ago
2 hours ago
Have you tried doing a full hard restart via the Railway CLI
Since your billing page shows the Hobby plan active with $0.00 usage and $5 included allowance, but gateway proxy is throwing a 402 exceed_egress_quota error, this is usually caused by a sync lag between Stripe/Railway's billing webhook and the API gateway proxy caching the old limit, or a scope mismatch.
Could you confirm a couple of things ?
- Are you certain the Hobby plan was applied to the exact team/workspace that owns the
independent-beautyproject, rather than your personal account or a separate workspace? - Have you tried pushing a fresh build using the Railway CLI (
railway up) rather than using the dashboard's redeploy button?
If it's scoped correctly, dashboard redeploys maybe don't flush the cache. Try modifying an environment variable or running a fresh deployment via CLI.