3 ms·
Yes, before the drop out my traffic was coming from a downlink station in Bulgaria, on an IP on AS14593 Traceroute from "the internet" back to that IP reaches
by ta1243 1y ago
Yes, before the drop out my traffic was coming from a downlink station in Bulgaria, on an IP on AS14593
Traceroute from "the internet" back to that IP reaches AS14593 just fine, and my endpoint doesn't get beyond the first hop of the local starlink router.
Whatever it is, it doesn't look like a peering problem
- indigodaddy 1y agohttps://mtr.ping.pe https://mtr.ping.pe ftw for MTR from "the internet" ? :)
- ta1243 1y agoFrom various monitoring points I have on multiple internet connections. One of the promises of starlink was it would stay in space as long as possible before being downlinked, giving far lower latency, alas that hasn't happened yet, and traffic will run thousands of miles in the wrong direction before being downlinked. For example from one location to another I have 360ms via Starlink but just 200ms rtt via local provision (5g p2p wireless then optical). On another it used to downlink in Lagos, but now it downlinks in Nairobi, meaning traffic to Lagos routes Nairobi -> Marseille -> Lagos, taking far longer than it used to. A shame really.