Hacker News new | past | comments | ask | show | jobs | submit login

I just tested something to a similar effect. It's much more jumpy time-wise, yes.



Just pinged my isp router in Kathmandu for 30 seconds, 172-174ms return. It’s on AS4007.

From my router in Dhaka pining a router on airtel in India, 36-38ms

Routers in the real would give very stable ping responses, no matter where they are based.


There was a time latency on AT&T 3G was 9 seconds during congestion.

The last mile is usually the issue. Pretty much only Cogent and HE allow you to have packet loss


The argument was “Most routers do not put ping-processing in the "fast path". That is, instead of having the ping be processed by an ASIC, the ping gets processed by the router's CPU.”

That’s meaningless. Control planes are often policed sure, but on overload will simply drop. In my experience they drop icmp to expired before echo response but most will generate ttl expired just fine.

Any router capable of processing a full bgp table, and to be honest any router made in the last 20 years, is perfectly capable of responding to icmp echos.

There was then a second argument that “3rd world” routers aren’t as good as ones in western country. In the majority of cases they’re exactly the same. That western arrogance is somewhere between insulting and amusing.

The final argument is about path loss/jitter/etc, specially loss on the first hop (your “my crappy 3G provider” argument)

That’s exactly what this test of starlink is showing.

Starlink is a great tool in specific cases, but the fanboyish ness often drowns out the actual benefits.


It's not unusual to see occasionally missing routers in a traceroute, please.

You be capping




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: