Exp_Tristan posted:
Oh Yea i am on At&t DSL(Kansas City MO.), 768kup and 6.0mb down and Still today getting:
Pinging 206.112.64.6 with 32 bytes of data:
Reply from 206.112.64.6: bytes=32 time=67ms TTL=241
Reply from 206.112.64.6: bytes=32 time=67ms TTL=241
Reply from 206.112.64.6: bytes=32 time=66ms TTL=240
Reply from 206.112.64.6: bytes=32 time=66ms TTL=240
Ping statistics for 206.112.64.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 66ms, Maximum = 67ms, Average = 66ms
So yea NOT my end!
ping response time isnt the same as data packet response time these days..
bandwidth shaping and throttling is big in ISPs these days ever sense comcast won a case involving its limiting of torrents....
if your ISP is doing the same thing for certain types of data or ports, and say they are mistakenly picking up mythics data packets as that type of data.. your ping to mythics gateway would be fine, even though the ISP is slowing the transfer rate of the data packets..
not saying thats whats happening... but considering theres a large portion with lag problems and a large portion without lag problems... that leaves me to suspect something fishy on the route around the internet, not at mythics end, or the customers end.. but out there.. in one of the 20-30 other systems your information passes through.
-----signature-----
-=no pity for the majority=-