Problem with spiking ping

[VaeVictis]

I dont think its an issue with my own isp because dead-beat and squarehimself had the same problem earlier in the day

C:\Documents and Settings\Entropy>ping tastyspleen.net

Pinging tastyspleen.net [74.54.186.226] with 32 bytes of data:

Reply from 74.54.186.226: bytes=32 time=93ms TTL=50
Reply from 74.54.186.226: bytes=32 time=90ms TTL=50
Reply from 74.54.186.226: bytes=32 time=89ms TTL=50
Reply from 74.54.186.226: bytes=32 time=89ms TTL=50

Ping statistics for 74.54.186.226:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 89ms, Maximum = 93ms, Average = 90ms

C:\Documents and Settings\Entropy>ping tastyspleen.net

Pinging tastyspleen.net [74.54.186.226] with 32 bytes of data:

Reply from 74.54.186.226: bytes=32 time=122ms TTL=50
Reply from 74.54.186.226: bytes=32 time=157ms TTL=50
Reply from 74.54.186.226: bytes=32 time=177ms TTL=50
Reply from 74.54.186.226: bytes=32 time=182ms TTL=50

Ping statistics for 74.54.186.226:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 122ms, Maximum = 182ms, Average = 159ms

C:\Documents and Settings\Entropy>ping tastyspleen.net

Pinging tastyspleen.net [74.54.186.226] with 32 bytes of data:

Reply from 74.54.186.226: bytes=32 time=210ms TTL=50
Reply from 74.54.186.226: bytes=32 time=222ms TTL=50
Reply from 74.54.186.226: bytes=32 time=214ms TTL=50
Reply from 74.54.186.226: bytes=32 time=246ms TTL=50

Ping statistics for 74.54.186.226:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 210ms, Maximum = 246ms, Average = 223ms

C:\Documents and Settings\Entropy>ping tastyspleen.net

Pinging tastyspleen.net [74.54.186.226] with 32 bytes of data:

Reply from 74.54.186.226: bytes=32 time=139ms TTL=50
Reply from 74.54.186.226: bytes=32 time=138ms TTL=50
Reply from 74.54.186.226: bytes=32 time=128ms TTL=50
Reply from 74.54.186.226: bytes=32 time=132ms TTL=50

Ping statistics for 74.54.186.226:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 128ms, Maximum = 139ms, Average = 134ms

C:\Documents and Settings\Entropy>ping tastyspleen.net

Pinging tastyspleen.net [74.54.186.226] with 32 bytes of data:

Reply from 74.54.186.226: bytes=32 time=130ms TTL=50
Reply from 74.54.186.226: bytes=32 time=134ms TTL=50
Reply from 74.54.186.226: bytes=32 time=131ms TTL=50
Reply from 74.54.186.226: bytes=32 time=123ms TTL=50

Ping statistics for 74.54.186.226:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 123ms, Maximum = 134ms, Average = 129ms

C:\Documents and Settings\Entropy>ping tastyspleen.net

Pinging tastyspleen.net [74.54.186.226] with 32 bytes of data:

Reply from 74.54.186.226: bytes=32 time=118ms TTL=50
Reply from 74.54.186.226: bytes=32 time=89ms TTL=50
Reply from 74.54.186.226: bytes=32 time=90ms TTL=50
Reply from 74.54.186.226: bytes=32 time=90ms TTL=50

Ping statistics for 74.54.186.226:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 89ms, Maximum = 118ms, Average = 96ms

C:\Documents and Settings\Entropy>ping tastyspleen.net

Pinging tastyspleen.net [74.54.186.226] with 32 bytes of data:

Reply from 74.54.186.226: bytes=32 time=90ms TTL=50
Reply from 74.54.186.226: bytes=32 time=89ms TTL=50
Reply from 74.54.186.226: bytes=32 time=90ms TTL=50
Reply from 74.54.186.226: bytes=32 time=89ms TTL=50

Ping statistics for 74.54.186.226:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 89ms, Maximum = 90ms, Average = 89ms

[console]

Reply from 74.54.186.226: bytes=32 time=210ms TTL=50
Reply from 74.54.186.226: bytes=32 time=222ms TTL=50
Reply from 74.54.186.226: bytes=32 time=214ms TTL=50
Reply from 74.54.186.226: bytes=32 time=246ms TTL=50

When that happens, try running a traceroute.

(tracert tastyspleen.net  ... and/or  pathping tastyspleen.net)


Regards,

[VaeVictis]

Reply from 74.54.186.226: bytes=32 time=210ms TTL=50
Reply from 74.54.186.226: bytes=32 time=222ms TTL=50
Reply from 74.54.186.226: bytes=32 time=214ms TTL=50
Reply from 74.54.186.226: bytes=32 time=246ms TTL=50

When that happens, try running a traceroute.

(tracert tastyspleen.net  ... and/or  pathping tastyspleen.net)


Regards,

considered it... but kinda a bitch when it only spikes when it wants to :/ id get normal trace routes over and over before it finally spiked at the right time... and pinging until it spikes THEN running the tracert wont work due to my router timing out whenever i run tracert's, it ends up taking a bit doing that... its very noticable in game though because im constantly effected by the ping

though square did say it was his isp because he was pinging bad elsewhere too... could just be a heavy traffic server having problems... or a mass isp epic fail -.-

[console]

When that happens, try running a traceroute.

pathping will gather statistics along the whole route for 300 seconds

For some people it doesn't always return useful results (100% packetloss on various hops) ... but when it works it can be usefull.

[VaeVictis]

When that happens, try running a traceroute.

pathping will gather statistics along the whole route for 300 seconds

For some people it doesn't always return useful results (100% packetloss on various hops) ... but when it works it can be usefull.

lol yup 100% packet loss doin that, oh well guess ill just wait and see if its still spiking tomorrow