Unfortunately, we're unable to share the specifics of why the workspace was restricted, and for paid-plan workspaces this restriction cannot be reversed. Upgrading does not lift it once applied. You can cancel your subscription and offboard from the workspace at your billing settings.

Hi Railway team — I’m requesting a human review of this workspace restriction.

This workspace is running a legitimate Bitcoin network statistics project called Bitcoin Node Atlas. It consists of:

• a FastAPI public API
• a PostgreSQL database
• a scheduled crawler that checks public Bitcoin node reachability on port 8333
• GeoIP enrichment using MaxMind GeoLite2 databases
• a Vercel frontend

The crawler is conservative and rate-limited. It is not mining, not abusing resources, not scanning arbitrary services, not storing private user data, and not attempting to access internal/private networks. It only observes public Bitcoin node addresses and checks Bitcoin P2P reachability.

I upgraded from the free trial to Pro, but the workspace remains restricted. Could a human please review whether this restriction was triggered by the Bitcoin crawler/network-checking behavior, billing/trial status, or something else?

If the restriction cannot be reversed, please confirm whether I’m allowed to export my data and migrate away, and whether creating a new workspace for the same legitimate project would be permitted or would also be restricted.

We're not able to share the specifics of why this workspace was restricted, and for paid-plan workspaces this type of restriction is final and can't be reversed, including by upgrading to Pro. We're also unable to provide data access or exports on a restricted workspace. The same activity on a new workspace would be subject to the same enforcement.

I would like my money back, just wasted hours of time setting that up with you guys

My recommendation is that anyone thinking about using railway consider other options because they can put your project back days without any notice at all