New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Request timed out in your route means absolutely nothing. It's just a device that doesn't respond to ICMP.
If a device doesn't respond to ICMP, then all packets will be timed out, only some would indicate some kind of problems.
you can have ICMP set to a very low priority. Some pings get through, most are dropped go make way for a final traffic.
you could try tcp traceroute / tcp ping.
some network also drop (manipulate) icmp but tcp & udp are fine.
That might be possible, but in most common scenarios , especially for someone's normal vps, timed out indeed means something wrong in the network.
the A seems to be a better choice over all.
less hops means fewer points of failure and packet loss is generally more important and noticeable than a 15ms latency difference.
Anyway depends a lot on the usage, if you need the lowest possible latency, then go for the B
Lumen is notorious for dropping ICMP traffic.
So in reality hops don't mean much in that case.
Let alone in OPs case. Only 2 more hops aint going to make a major difference and in their case was lower overall response times.
Latency is a king here. Go with lower latency. Less hops only mean easier debugging for network failures, nothing more
Thanks for all comments, in the end i refunded service in Network A and kept B.
Despite more freq packet loss (im using PingPlotter software), both control panel somehow load at same speed as in no 404 or infinite loading etc. Hence i went with latency as the final choice.