15 days ago
Subject: Production service unreachable from Hostinger (India) - 15s timeouts / 502s
Hi Railway team,
Our production service is intermittently unreachable, which looks related to the ongoing incident where some network providers are blocking Railway IPs.
Project: cozy-determination
Service: kirixa-saas (production environment)
Public URL: kirixa-saas-production.up.railway.app
What we see:
- Our web host (Hostinger, shared hosting in India) proxies API requests to the Railway URL above. Requests time out after 15 seconds and our users get 502 errors.
- Our service itself is running; deploys are fine and logs show no crash.
- This started on 4 Nov 2026 and is still happening on 5 Nov 2026.
What we need:
- Can you confirm whether our service's IP range is affected by the blocking?
- Is there an ETA for the fix?
- Is there any option to move our service to a different IP range/region, or a recommended workaround (e.g. a custom domain behind Cloudflare) while this is ongoing?
This is a paying customer-facing SaaS (billing, WhatsApp, mobile app), so the impact is significant. Thank you.
Kirixa
1 Reply
15 days ago
We're sorry for the trouble. Your kirixa-saas production deployment is running normally, and the timeouts from your Hostinger proxy match the ongoing incident, External network blocks affecting access to Railway, which affects public networking in all regions and is currently in the Identified stage while we keep monitoring it.
Some network providers and security services are blocking Railway IP addresses because a third party is sending scanning traffic with forged Railway source IPs. That traffic does not come from our network. We've asked security vendors to review the blocks and are working with network operators, but we don't have an ETA yet for every affected network to remove them.
The most direct fix is to ask Hostinger to review any rules blocking Railway IP addresses and share the incident notice with them. Legitimate traffic can be allowed while protection against the scanning stays in place. Until then, sending requests through a different network may work as a temporary path.
Status changed to Awaiting User Response Railway • 15 days ago
8 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 • 8 days ago
