Skip to content
Edge IP range 69.46.46.0/24 is "Uncategorized" in Forcepoint: corporate web filters block Railway-hosted apps
arnoldhueteg
OP

21 days ago

Our production app (chat.laboraley.aritek.pe, a custom domain on a Railway service) is blocked inside a Peruvian public-sector network that runs Forcepoint Web Security with "block Uncategorized" enabled. After three days of isolated tests we traced it to the inbound edge IP, not to our app.

  1. Forcepoint's Site Lookup (support.forcepoint.com/s/site-lookup) returns "Uncategorized" for 69.46.46.81, which ARIN lists as RLWY-HIKARI-01 (Railway, registered 2026-01-22, AS400940).

  2. The exact same static test page (HTML + one JS module + one JSON + one woff2 font + a web manifest) loads fine from that network when served from Vercel's 76.76.21.21 ("Information Technology" in Forcepoint's database) and is blocked when served from Railway. Cloudflare's shared IPs are categorized too ("Content Delivery Networks").

  3. With an uncategorized IP, Forcepoint classifies every response by its text content, so an HTML page with real text passes but every JS bundle, font and manifest is replaced by the block page (the browser console shows each asset redirected to the appliance's blockpage.cgi). Any single-page app on Railway is affected: we reproduced it with both LibreChat and Open WebUI on fresh services.

Since Railway owns the range, could Railway request categorization of 69.46.46.0/24 (and the other Hikari Edge ranges) with Forcepoint, and ideally with the other major URL-filter vendors (Zscaler, Palo Alto, Cisco Umbrella, Symantec/Broadcom)? Forcepoint's form is the Site Lookup tool linked above ("Recategorization" next to the result). We submitted a guest request today for the IP and for our own hostname, but a request from the range owner carries more weight, and the range fix covers every Railway customer behind a corporate filter.

Happy to share the full write-up and test logs.

Solved

3 Replies

Railway
BOT

21 days ago

That's correct, 69.46.46.0/24 is our edge range. It's a shared anycast pool used for many customers' public domains, so we can't give one service a different edge IP. Redeploying or changing regions also won't move a domain off it.

We can't commit to a timeline for getting the range itself recategorized with Forcepoint or the other filtering vendors. The hostname-level request you already sent to Forcepoint covers your own domain separately. For a lasting fix on networks that block uncategorized IPs, put a proxy or CDN in front of the custom domain whose IPs those filters already categorize, so visitors connect to those IPs instead of our edge range.


Status changed to Awaiting User Response Railway • 21 days ago


Railway

That's correct, 69.46.46.0/24 is our edge range. It's a shared anycast pool used for many customers' public domains, so we can't give one service a different edge IP. Redeploying or changing regions also won't move a domain off it. We can't commit to a timeline for getting the range itself recategorized with Forcepoint or the other filtering vendors. The hostname-level request you already sent to Forcepoint covers your own domain separately. For a lasting fix on networks that block uncategorized IPs, put a proxy or CDN in front of the custom domain whose IPs those filters already categorize, so visitors connect to those IPs instead of our edge range.

arnoldhueteg
OP

21 days ago

Thanks. Could someone from the Railway team confirm whether Railway itself will submit the Hikari Edge ranges (69.46.46.0/24 and siblings) to Forcepoint and the other URL-filter vendors? A one-time request from the range owner is cheap and fixes this for every customer behind a corporate filter; a per-customer proxy or CDN only moves the problem. If there is an existing internal ticket for this, a pointer to it would be enough.


Status changed to Awaiting Railway Response Railway • 21 days ago


Railway
BOT

21 days ago

We can't confirm that we'll submit 69.46.46.0/24 or our other edge ranges to Forcepoint or the other URL-filter vendors, and we don't have an internal ticket we can share for it.

What we can confirm: that range is our shared anycast edge pool, so we can't assign your service a different edge IP, and redeploying or changing regions won't move your domain off it. The hostname-level recategorization request you already sent to Forcepoint applies to your own domain on its own, separate from the IP range.


Status changed to Awaiting User Response Railway • 21 days ago


Railway
BOT

14 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 • 14 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...