|
I found that, via PingPlotter, there are a lot of packet loss ( the red line in the figure are packet loss).
The ping starts at Hop 1, and reaches the destination after 11 hops. Notice that the majority of the packet loss occurs between hop 5- 11, indicating that the network connection at those points are poor. The question is, can we thus conclude that this is the ISP's problem? Maybe a second screenshot will give a better overview picture on what's going on:
|
||||
|
|
|
There's a lot of packet loss on the first hop, which does suggest that you've got a problem on your own link (i.e. the one between you and the ISP). However in my experience that's normally because something else is using that link and saturating it - it's not often because of real network failures. When I was running ISP network ops we'd often get users phone up and say that their line was very slow. Almost every time it was an infected machine spewing out spam and using up all of their bandwidth. p.s. you've obscured your internal address (unnecessary, because it's a private address) but left your real public IP unobscured! |
||||
|
|
Not necessarily. There's a drop at 219.93.218.177, which I'm assuming is your router/DSL/cable modem's outside IP, but then everything's clear up to 74.125.50.229, which is the first Google IP. Google's packets being slower to return to you could be something to do with your ISP, but I wouldn't assume so; are you getting a similar problem with other sites? |
|||
|
|
