Target Name: argon.gamerslobby.net
IP: 206.123.111.42
Date/Time: 3/2/2006 4:26:43 AM
1 6 ms 5 ms 5 ms 5 ms avradionet.com [67.99.246.1]
2 12 ms 12 ms 13 ms 12 ms [67.98.227.145]
3 11 ms 12 ms 12 ms 12 ms P3-3.a0.lsan.broadwing.net [216.140.3.45]
4 13 ms 12 ms 12 ms 12 ms so-3-1-2.gar2.LosAngeles1.Level3.net [4.68.127.173]
5 13 ms N/A N/A 12 ms ae-1-55.bbr1.LosAngeles1.Level3.net [4.68.102.129]
6 73 ms N/A 74 ms 74 ms as-3-0.bbr1.Dallas1.Level3.net [64.159.3.214]
7 N/A N/A N/A 74 ms ae-22-52.car2.Dallas1.Level3.net [4.68.122.46]
8 75 ms 77 ms 78 ms 75 ms [4.78.224.74]
9 45 ms 77 ms 49 ms 45 ms [206.123.64.30]
10 47 ms 46 ms 45 ms 46 ms [206.123.64.98]
11 76 ms 76 ms 75 ms 75 ms argon.gamerslobby.net [206.123.111.42]
Ping statistics for argon.gamerslobby.net
Packets: Sent = 4, Received = 4, Lost = 0 (0.0%)
Round Trip Times: Minimum = 75ms, Maximum = 76ms, Average = 75ms
Yesterday ping was at 45 , but this morning is in 70's ,
so it is worse....
Every ping check this morning shows problem at same hop, ,:mad:
That being @ Dallas Level 3.net 64.159.3.214