Doing a regular ping test isn't normally enough data. Try this command in windows:
ping -n 200 12.129.222.10
(12.129.222.10 is the diablo 3 server for north america)
More pings means it will give a bigger time frame where you will get a better idea of any packet loss and latency spikes. Packet loss and latency spikes tend to be the cause of a lot of the rubber banding. A tracer route can show you what hops are causing the problem but if it's intermittent and you don't catch it during the specific trace you are doing it won't be much good to you. You're best bet is to run them manually in windows or mac and to run the trace right when you see the packet loss/latency spike during the ping test. With that you can at least get some sort of idea where to go from there and you should have enough info to narrow down the interval and send it to your ISP. Hope this helps.
Doing a regular ping test isn't normally enough data. Try this command in windows:
ping -n 200 12.129.222.10
(12.129.222.10 is the diablo 3 server for north america)
More pings means it will give a bigger time frame where you will get a better idea of any packet loss and latency spikes. Packet loss and latency spikes tend to be the cause of a lot of the rubber banding. A tracer route can show you what hops are causing the problem but if it's intermittent and you don't catch it during the specific trace you are doing it won't be much good to you. You're best bet is to run them manually in windows or mac and to run the trace right when you see the packet loss/latency spike during the ping test. With that you can at least get some sort of idea where to go from there and you should have enough info to narrow down the interval and send it to your ISP. Hope this helps.
My Twitch Channel
Do a ping and a tracert. Use at least 50 echoes for a good sample.
My Twitch Channel