I cannot reach Railway's infrastructure IP 69.46.46.46:443 from Starlink Kenya, but the same device reaches it immediately via Liquid Telecom mobile ISP. DNS resolution is correct and other HTTPS destinations work normally.

Diagnostic findings:

• Device: Same hardware, same location
• Starlink Kenya: 69.46.46.46:443 completely unreachable
• Liquid Telecom mobile: 69.46.46.46:443 immediately reachable
• DNS: Verified correct
• Other HTTPS: Works normally from Starlink
• Service: MZURI production (mzuri-production.up.railway.app, ID 40e4f1b0-ce9c-4ea9-9421-080ff1b927f4)

Requested Railway diagnostics:

1. Is 69.46.46.0/24 being advertised normally to relevant upstreams/peers?
2. Is Railway's upstream provider receiving traffic from the Starlink/Liquid Telecom path?
3. Are source-prefix filtering, DDoS mitigation, ACLs, or edge policies dropping traffic from this route?
4. Are there other recent reachability reports to 69.46.46.0/24, particularly from Africa or Starlink users?

I have standard and TCP/443 traceroutes available. Please advise what additional diagnostics would be useful.