Very high ping spikes to the second hop, 10.xxx.
Any tracert I run goes through the same ip, which as a 10.xxx so should be part of Cox's private network: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 13 ms 10 ms 60 ms 10.33.40.1 Pinging it yields alarming results: Pinging 10.33.40.1 with 32 bytes of data: Reply from 10.33.40.1: bytes=32 time=14ms TTL=254 Reply from 10.33.40.1: bytes=32 time=14ms TTL=254 Reply from 10.33.40.1: bytes=32 time=15ms TTL=254 Reply from 10.33.40.1: bytes=32 time=19ms TTL=254 Reply from 10.33.40.1: bytes=32 time=10ms TTL=254 Reply from 10.33.40.1: bytes=32 time=15ms TTL=254 Reply from 10.33.40.1: bytes=32 time=12ms TTL=254 Reply from 10.33.40.1: bytes=32 time=27ms TTL=254 Reply from 10.33.40.1: bytes=32 time=13ms TTL=254 Reply from 10.33.40.1: bytes=32 time=27ms TTL=254 Reply from 10.33.40.1: bytes=32 time=19ms TTL=254 Reply from 10.33.40.1: bytes=32 time=87ms TTL=254 Reply from 10.33.40.1: bytes=32 time=35ms TTL=254 Reply from 10.33.40.1: bytes=32 time=123ms TTL=254 Reply from 10.33.40.1: bytes=32 time=77ms TTL=254 Reply from 10.33.40.1: bytes=32 time=15ms TTL=254 Reply from 10.33.40.1: bytes=32 time=49ms TTL=254 Reply from 10.33.40.1: bytes=32 time=16ms TTL=254 Reply from 10.33.40.1: bytes=32 time=12ms TTL=254 Reply from 10.33.40.1: bytes=32 time=13ms TTL=254 Reply from 10.33.40.1: bytes=32 time=17ms TTL=254 Reply from 10.33.40.1: bytes=32 time=45ms TTL=254 Reply from 10.33.40.1: bytes=32 time=15ms TTL=254 Reply from 10.33.40.1: bytes=32 time=105ms TTL=254 Reply from 10.33.40.1: bytes=32 time=26ms TTL=254 Reply from 10.33.40.1: bytes=32 time=30ms TTL=254 Reply from 10.33.40.1: bytes=32 time=110ms TTL=254 Reply from 10.33.40.1: bytes=32 time=15ms TTL=254 Reply from 10.33.40.1: bytes=32 time=14ms TTL=254 Reply from 10.33.40.1: bytes=32 time=75ms TTL=254 Reply from 10.33.40.1: bytes=32 time=35ms TTL=254 Reply from 10.33.40.1: bytes=32 time=147ms TTL=254 Reply from 10.33.40.1: bytes=32 time=23ms TTL=254 Reply from 10.33.40.1: bytes=32 time=70ms TTL=254 Reply from 10.33.40.1: bytes=32 time=124ms TTL=254 Request timed out. Reply from 10.33.40.1: bytes=32 time=42ms TTL=254 Reply from 10.33.40.1: bytes=32 time=36ms TTL=254 Reply from 10.33.40.1: bytes=32 time=63ms TTL=254 Reply from 10.33.40.1: bytes=32 time=55ms TTL=254 Reply from 10.33.40.1: bytes=32 time=41ms TTL=254 Reply from 10.33.40.1: bytes=32 time=114ms TTL=254 Reply from 10.33.40.1: bytes=32 time=113ms TTL=254 Reply from 10.33.40.1: bytes=32 time=43ms TTL=254 Reply from 10.33.40.1: bytes=32 time=18ms TTL=254 Reply from 10.33.40.1: bytes=32 time=29ms TTL=254 Reply from 10.33.40.1: bytes=32 time=50ms TTL=254 Reply from 10.33.40.1: bytes=32 time=17ms TTL=254 Reply from 10.33.40.1: bytes=32 time=45ms TTL=254 Reply from 10.33.40.1: bytes=32 time=11ms TTL=254 Reply from 10.33.40.1: bytes=32 time=38ms TTL=254 Reply from 10.33.40.1: bytes=32 time=45ms TTL=254 Reply from 10.33.40.1: bytes=32 time=42ms TTL=254 Reply from 10.33.40.1: bytes=32 time=13ms TTL=254 Reply from 10.33.40.1: bytes=32 time=66ms TTL=254 Reply from 10.33.40.1: bytes=32 time=15ms TTL=254 Reply from 10.33.40.1: bytes=32 time=41ms TTL=254 Reply from 10.33.40.1: bytes=32 time=48ms TTL=254 Reply from 10.33.40.1: bytes=32 time=37ms TTL=254 Reply from 10.33.40.1: bytes=32 time=15ms TTL=254 Reply from 10.33.40.1: bytes=32 time=10ms TTL=254 Reply from 10.33.40.1: bytes=32 time=57ms TTL=254 Reply from 10.33.40.1: bytes=32 time=28ms TTL=254 Reply from 10.33.40.1: bytes=32 time=28ms TTL=254 Reply from 10.33.40.1: bytes=32 time=63ms TTL=254 Reply from 10.33.40.1: bytes=32 time=59ms TTL=254 Reply from 10.33.40.1: bytes=32 time=47ms TTL=254 Reply from 10.33.40.1: bytes=32 time=31ms TTL=254 Reply from 10.33.40.1: bytes=32 time=22ms TTL=254 Reply from 10.33.40.1: bytes=32 time=11ms TTL=254 Reply from 10.33.40.1: bytes=32 time=27ms TTL=254 Reply from 10.33.40.1: bytes=32 time=13ms TTL=254 Reply from 10.33.40.1: bytes=32 time=12ms TTL=254 Reply from 10.33.40.1: bytes=32 time=31ms TTL=254 Reply from 10.33.40.1: bytes=32 time=11ms TTL=254 Reply from 10.33.40.1: bytes=32 time=12ms TTL=254 Reply from 10.33.40.1: bytes=32 time=12ms TTL=254 Reply from 10.33.40.1: bytes=32 time=16ms TTL=254 Reply from 10.33.40.1: bytes=32 time=43ms TTL=254 Reply from 10.33.40.1: bytes=32 time=49ms TTL=254 Reply from 10.33.40.1: bytes=32 time=12ms TTL=254 Reply from 10.33.40.1: bytes=32 time=15ms TTL=254 Reply from 10.33.40.1: bytes=32 time=10ms TTL=254 Reply from 10.33.40.1: bytes=32 time=41ms TTL=254 Reply from 10.33.40.1: bytes=32 time=43ms TTL=254 Reply from 10.33.40.1: bytes=32 time=23ms TTL=254 Reply from 10.33.40.1: bytes=32 time=15ms TTL=254 Reply from 10.33.40.1: bytes=32 time=73ms TTL=254 Reply from 10.33.40.1: bytes=32 time=14ms TTL=254 Reply from 10.33.40.1: bytes=32 time=43ms TTL=254 Reply from 10.33.40.1: bytes=32 time=33ms TTL=254 Reply from 10.33.40.1: bytes=32 time=16ms TTL=254 Reply from 10.33.40.1: bytes=32 time=26ms TTL=254 Reply from 10.33.40.1: bytes=32 time=12ms TTL=254 Reply from 10.33.40.1: bytes=32 time=10ms TTL=254 Reply from 10.33.40.1: bytes=32 time=60ms TTL=254 Reply from 10.33.40.1: bytes=32 time=39ms TTL=254 Reply from 10.33.40.1: bytes=32 time=19ms TTL=254 Reply from 10.33.40.1: bytes=32 time=25ms TTL=254 Reply from 10.33.40.1: bytes=32 time=17ms TTL=254 Ping statistics for 10.33.40.1: Packets: Sent = 100, Received = 99, Lost = 1 (1% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 147ms, Average = 36ms I am plugged directly into the router, and there's nothing using any significant bandwidth on my local network. Any idea what this server is? Even if it's in Phoenix, and even in the best case scenario, 14 ms is a bit high, but I'm getting nasty ping spikes which show up everywhere else. What should I do? Please help.