- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The WinMTR link is http://winmtr.net/ rather than .com.
Other than that, I agree with what you've said Hubrisnxs.
It occurs to me that if there's low packet loss to Israel and it's slightly higher to a U.S. destination, Verizon is doing it's job. The slightly higher loss domestically is likely just one of the vargaries of the Internet.
A WinMTR test might indeed clarily what's happening.
BTW, here's what I get from Long Island:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Everyone , take a look on the following:
From NJ , USA through Verizon FIOS To google DNS:
From NJ , USA through Verizon Fios To Israel (A DataCenter located Physically at Israel):
From Israel (A DataCenter located Physically at Israel) To Google DNS:
From Israel (A DataCenter located Physically at Israel) To Verizon FioS NJ , USA :
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks pretty good to me.
You are seeing false packet loss and false latency. General rule of thumb is that if it's real then it will sustain or grow with each subsequent hop.
Latency spikes and packet loss in the middle of a traceroute mean
absolutely nothing if they do not continue forward.
• At worst it could be the result of an asymmetric path.
• But it is probably an artificial rate-limit or prioritization issue.(likely)
• By definition, if regularly forwarded packets are being affected
you should see the issue persist on all future hops.
Also just for some perspective, A round-trip around the world at the equator, via a perfectly straight fiber route, would take ~400ms due solely to speed-of-light propagation delays
Here is some good source material so you can kinda see what I mean
- « Previous
-
- 1
- 2
- Next »