a month ago
Our Hobby-plan service's inbound webhooks are all rejected by the Railway edge with 429 "rate limited" (headers show x-railway-edge=jfk1, responses in ~8ms). Single POST requests, first attempt, no bursts — from Twilio's webhook fleet AND from Twilio Functions (AWS serverless IPs), on both our railway-provided domain and our verified custom domain (rhino.wilcoangels.com). Browser requests work fine. This appears to be IP-range throttling of cloud providers that is blocking legitimate low-volume webhooks (Twilio SMS, Calendly) to our production app. Project: miraculous-possibility, service: web. Please advise or exempt.
1 Replies
a month ago
Your service has Under Attack Mode enabled (set to stay on until manually disabled), which challenges every inbound request that cannot complete a browser-style verification. Programmatic callers like Twilio and Calendly webhooks fail that challenge and get rejected at the edge. Disable Under Attack Mode in your service's edge settings and the webhook POST requests will reach your app normally.
Status changed to Awaiting User Response Railway • about 2 months ago
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