Post
Highlighted: the lines this signal was extracted from
I was on a United flight yesterday with the new Starlink-backed WiFi and noticed that IPv4 ping to my server was around 300-400ms while IPv6 ping to the same destination ran 120-140ms. Is the CGNAT hit on Starlink that significant? Any Starlink customers that can confirm? UPDATE: Here are the traceroutes from the server (HE FMT2) to the Starlink addresses that were used. Next flight with Starlink I'll trace from the other direction. Does look like the IPv4 routing is substantially different. First hop removed for privacy. 1 * * * 2 be7.core2.fmt2.he.net (184.104.188.173) 3.098 ms 3.405 ms 2.103 ms 3 be10.core1.sjc2.he.net (72.52.92.137) 134.932 ms 136.218 ms 163.183 ms 4 be2.core1.nyc4.he.net (184.104.189.61) 139.041 ms 140.540 ms 139.116 ms 5 be10.core4.lon2.he.net (184.104.196.70) 138.587 ms 139.809 ms 137.414 ms 6 be3.core3.ams1.he.net (184.104.188.218) 139.462 ms 138.477 ms 139.042 ms 7 port-channel28.core2.ams1.he.net (184.105.213.230) 136.168 ms 135.890 ms 138.136 ms 8 mtn-globalconnect-solutions-ltd.e0-30.switch1.ams6.he.net (216.66.83.127) 137.624 ms 137.990 ms 137.557 ms 9 41.181.244.240 (41.181.244.240) 278.220 ms 277.950 ms 277.955 ms 10 41.181.190.185 (41.181.190.185) 154.044 ms 153.978 ms 153.987 ms 11 41.181.105.114 (41.181.105.114) 263.414 ms 263.968 ms 263.547 ms 12 41.181.190.128 (41.181.190.128) 272.004 ms 272.026 ms 272.089 ms 13 41.181.244.5...
Keep reading with a free account
The rest of this post, and every signal for United Airlines, is in your free account.