a month ago
Our account was blocked due to a payment issue. We made a payment several hours ago, and the account has been unblocked. However, we are experiencing residual access restrictions that persist after the unblock:
Current Issues:
All services are inaccessible without VPN (Railway domain and custom domain)
Railway domain kordanexus-production-bcd2.up.railway.app returns access restrictions without VPN
Custom domain syntax.su (delegated via Cloudflare) also inaccessible without VPN
All three services (Korda_syntax, Korda-ivest, etc-korda) show "Online" status and are working correctly when accessed via VPN
Current Configuration:
All services are online and operational
DNS settings for syntax.su are correctly configured in Cloudflare (CNAME record, NS delegation via nic.ru)
No service configuration issues detected
What We've Verified:
Services are running (all replicas healthy)
Billing issue is resolved (payment processed)
DNS configuration is correct
Services work fine when accessed via VPN
This appears to be a residual IP-blocking or geo-blocking restriction from the account lock that was not automatically lifted when access was restored.
Project ID: df4d164e-0162-467e-974c-a6e8eb910c90
We need your team to manually remove these residual restrictions so our services are accessible normally without VPN.
Pinned Solution
a month ago
Users in Russia (or possibly around Russia) have been known to have their traffic blocked when trying to access Railway's edge.
Unfortunartely, if that's the case, Railway isn't able to do anything about it, and your only option is to use a VPN to access these sites.
5 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
Users in Russia (or possibly around Russia) have been known to have their traffic blocked when trying to access Railway's edge.
Unfortunartely, if that's the case, Railway isn't able to do anything about it, and your only option is to use a VPN to access these sites.
0x5b62656e5d
Users in Russia (or possibly around Russia) have been known to have their traffic blocked when trying to access Railway's edge. Unfortunartely, if that's the case, Railway isn't able to do anything about it, and your only option is to use a VPN to access these sites.
a month ago
Thank you for your reply, but I don't believe this is related to a general regional block.
Here is why:
I have another active Railway account, and all the projects hosted there are fully accessible from Russia right now without any issues or need for a VPN.
The timing of the issue is directly tied to the billing lock. The services on this specific account were working perfectly fine without a VPN right up until the moment the account was suspended due to the payment issue.
The access restrictions only appeared exactly when the account was blocked. After the payment was processed and the account was unblocked, the access never returned to its original working state.
This strongly suggests that the problem is a residual restriction, a stalled state, or a routing glitch related to the account suspension/unblocking process on Railway's side, rather than a general network block in the region.
Could you please escalate this to the engineering team so they can check if there are any lingering blocks, suspended edge routes, or frozen IP states specifically tied to our recent billing suspension?
a month ago
Have you tried redeploying all your affected services?
Also, I'm able to access syntax.su, but not your kordanexus URL (404). Make sure that service is online.
0x5b62656e5d
Have you tried redeploying all your affected services? Also, I'm able to access syntax.su, but not your kordanexus URL (404). Make sure that service is online.
a month ago
Yes, I have already tried redeploying all of the existing projects. I also created entirely separate project folders and tried deploying them there, and I even changed the default root domains provided by Railway. Unfortunately, none of these steps resolved the issue.
For reference, the affected Project ID is: bc5cb896-e176-4663-ba36-c164e8c0c3ca.
Status changed to Solved 0x5b62656e5d • 7 days ago