Highlighted

Re: Bad Pings to East Coast

Grasshopper

Yeah you have some pretty terrible ping spikes in there. You'll want to determine how local they are. Try doing a continuous ping to your router (ping -t 192.168.50.1) and see if the spikes show up there. If they do they are quite local (inside your local network) caused by wireless interference most likely, if you are connected via wireless.

If the latency spikes do not show up in a continuous ping of your local router, try doing a continuous ping to Shaw's Winnipeg router (ping -t 64.59.180.109) and see if the latency spikes show up there. If they do, then the latency spikes are likely being introduced on your local connection to Shaw rather than a global problem to the east coast.

You might also want to install WinMTR which does both a traceroute and a continuous ping to each step of the traceroute in one step.

0 Kudos
Reply
Loading...
Highlighted

Re: Bad Pings to East Coast

Not applicable

At first look, this appears to be the Puma issue...

Otherwise while repeated pings can be useful, it really doesn't give enough information to tell where the problem is or might be.

Need MTR data (it pings every router along the way and makes a shows results at each hop)

0 Kudos
Reply
Loading...
TALK TO US
Need more help?