republican-creole
site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Uniqs:
268
Share Topic
Post a:
Post a:
AuthorAll Replies

jca2050
Premium
join:2002-02-04
Hacienda Heights, CA
Reviews:
·Verizon FiOS

ughhh

Pinging eof.qwca.net [64.208.50.10] with 32 bytes of data

Reply from 64.208.50.10: bytes=32 time=160ms TTL=246
Reply from 64.208.50.10: bytes=32 time=170ms TTL=246
Reply from 64.208.50.10: bytes=32 time=200ms TTL=246
Reply from 64.208.50.10: bytes=32 time=170ms TTL=246

Getting 170+ ping in-game. So much for 'priority'.
This is what happens when people start downloading, seems like its happening more often.


Count Hogula$
Notorious Dog
Premium
join:2002-06-19
Corona, CA

They should kill off P2P like Coastinet did.



Count Hogula$
Notorious Dog
Premium
join:2002-06-19
Corona, CA

reply to jca2050
My latency has improved...today at least.

Pinging redirect.gamespy.com [207.38.1.157] with 32 bytes of data:

Reply from 207.38.1.157: bytes=32 time=36ms TTL=50
Reply from 207.38.1.157: bytes=32 time=35ms TTL=50
Reply from 207.38.1.157: bytes=32 time=34ms TTL=50
Reply from 207.38.1.157: bytes=32 time=41ms TTL=50
Reply from 207.38.1.157: bytes=32 time=36ms TTL=50
Reply from 207.38.1.157: bytes=32 time=38ms TTL=50
Reply from 207.38.1.157: bytes=32 time=37ms TTL=50
Reply from 207.38.1.157: bytes=32 time=37ms TTL=50
Reply from 207.38.1.157: bytes=32 time=37ms TTL=50
Reply from 207.38.1.157: bytes=32 time=38ms TTL=50

Ping statistics for 207.38.1.157:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 41ms, Average = 36ms

Pinging lax.speakeasy.net [64.81.45.2] with 32 bytes of data:

Reply from 64.81.45.2: bytes=32 time=30ms TTL=247
Reply from 64.81.45.2: bytes=32 time=34ms TTL=247
Reply from 64.81.45.2: bytes=32 time=36ms TTL=247
Reply from 64.81.45.2: bytes=32 time=31ms TTL=247
Reply from 64.81.45.2: bytes=32 time=30ms TTL=247
Reply from 64.81.45.2: bytes=32 time=32ms TTL=247
Reply from 64.81.45.2: bytes=32 time=33ms TTL=247
Reply from 64.81.45.2: bytes=32 time=35ms TTL=247
Reply from 64.81.45.2: bytes=32 time=32ms TTL=247
Reply from 64.81.45.2: bytes=32 time=33ms TTL=247

Ping statistics for 64.81.45.2:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 36ms, Average = 32ms

Maybe it's time of day.
--
The democracy will cease to exist when you take away from those who are willing to work and give to those who would not. -Thomas Jefferson


jca2050
Premium
join:2002-02-04
Hacienda Heights, CA
Reviews:
·Verizon FiOS

Pinging lax.speakeasy.net [64.81.45.2] with 32 bytes of data:

Reply from 64.81.45.2: bytes=32 time=160ms TTL=245
Reply from 64.81.45.2: bytes=32 time=40ms TTL=245
Reply from 64.81.45.2: bytes=32 time=150ms TTL=245
Reply from 64.81.45.2: bytes=32 time=120ms TTL=245
Reply from 64.81.45.2: bytes=32 time=181ms TTL=245
Request timed out.
Reply from 64.81.45.2: bytes=32 time=160ms TTL=245
Reply from 64.81.45.2: bytes=32 time=161ms TTL=245

This is at 12:45am, hehe. I guess it was just that time of the day when no one was owning the connect via P2P.


Monday, 04-Jun 14:21:00 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics