We're sorry for the trouble. Some network providers and security services have been blocking Railway IP addresses after a third party sent scanning traffic with forged Railway source addresses, so access to Railway-hosted apps is cut off from those networks. Access has come back for some users, but it is still affected from some networks and the issue has not been fully resolved.

Your services show successful, running deployments, so what you're seeing fits this incident. Switching to another network may give you access for now, and if your users are on an affected network, their network administrator can use the incident notice to allow legitimate access. You can follow progress on the incident page.

All the networks in my region seem affected, no one has been able to use the app. Please how soon to fix it, because the last update was at November 5th, this is now almost 4 days and no fix or update

We're sorry this has gone on so long, and we know your users being cut off for days is serious. The incident is still open: some users have access back, but access is still blocked from some networks.

We've contacted network operators, security vendors and abuse database providers, and we're still working to get the remaining blocks removed. The blocks are set by those networks and providers, so we can't give you a specific ETA for when every affected network will lift them.

In the meantime, if your users' networks are run by a provider or company IT team, those administrators can review their blocks on Railway IP addresses and allow legitimate access to your app. Using another network may also give temporary access.

You said this issue has been fixed yet none of the users can still access the app, did you fix for some regions and leave mine or what? I dont understand this situation, every time one issue or another

Sorry for the confusion. This incident has not been fixed yet, and it was not fixed for some regions while yours was left out. Some users have their access back because their particular network or security provider has already removed its block on Railway IP addresses. Networks that still have the block in place, including the ones your users are on, stay cut off until that provider lifts it.

We're still working with network operators, security vendors and abuse database providers to get the remaining blocks removed, and we can't give a specific ETA. If your users' internet providers or company IT teams can review their blocks on Railway IP addresses, they can allow access to your app sooner. Using a network that isn't affected may also give temporary access.

So users should go to another country before they can access and use the app? Or what are u saying you dont have any definitive timeframe as to when it will be fixed, for a new app I just launched you are driving away all my users and telling me you dont have any ETA as to the fix. This is very unprofessional, you fixed and left the other regions like that, so what should I do now?

We understand how damaging this is for a launch you just made, and we're sorry. Your users don't need to be in another country. The blocks are set by individual internet providers and security services, not by region, so a user on a different network (another provider) may get through even from the same location. We did not fix some regions and leave yours out.

The incident is still open. We've contacted network operators, security vendors and abuse database providers, and we're working to get the remaining blocks lifted. Each provider removes its own block, so we can't give a firm ETA.

The most direct thing you can do now is ask the internet providers your users are on to review their blocks on Railway IP addresses and allow legitimate access, sharing the incident notice we linked earlier. The scanning traffic behind these blocks uses forged Railway addresses and does not come from our network, which is what providers need to know to lift them.

This is becoming very annoying, so I am the one to reach out to internet providers when my own users are seriously complaining and am loosing most of them. You dont know how damaging it is, hence you are using a BOT to reply me, probably until you are sued

Your app itself is running normally on our side. Your users are being stopped before their requests reach us, by blocks their networks put on our addresses after a third party sent scanning traffic using forged Railway addresses. Some networks have already lifted their blocks, but others haven't yet, and we can't give a firm date for the rest because each provider removes its own block.