Hi, since ~Nov 3 22:00 – Nov 4 06:08 UTC, my VPS can't reach my Railway service at all. Continuous, 100% of attempts.

• Source: Hostinger VPS, Campinas BR, AS47583 (happy to share the source IP privately)
• Destination: my-service.up.railway.app → 69.46.46.27:443 (also .43 .46 .50 .73 .102 .103, all fail the same way)
• TCP connect times out; the same service answers instantly from other networks.
• No egress rules on the VPS; Hostinger confirmed no DDoS/null route.
• Hostinger reproduced it from a second, unrelated VPS via a different transit (EdgeUno): same stop at 79.127.195.139/140. Looks like it affects Hostinger BR traffic in general.

Could you check for any block/filter on your edge for AS47583, or a routing issue between CDN77 São Paulo and your edge? Hostinger ticket: #26245053.

mtr -T -P 443 -r -c 100 -n 69.46.46.73 (2026-11-04 12:46 UTC), hops 1–8 clean (Hostinger → Ascenty → Cirion/TIM):

9.|-- 179.54.24.45 0.0% 100 3.8 4.4

10.|-- 79.127.195.140 0.0% 100 5.5 5.5

11.|-- 10.213.247.78 45.0% 100 5.1 4.6

12.|-- 84.17.32.214 56.0% 100 3.0 3.8 (tim-sao.cdn77.com)

13.|-- 79.127.195.139 40.0% 100 2.9 3.4

14.|-- ??? 100.0 100 0.0 0.0

Same path and stop for 69.46.46.46.

nc -vz -w 5 69.46.46.{27,43,50} 443 → all "timed out" (12:49 UTC)

curl https://my-service.up.railway.app → Connection timed out after 15s

Full mtr available on request.