I don't normally post this type of thread, but I need a sanity check on this one.

I'm currently seeing between 4 and 33 percent packet loss at my webreseller-based machines, depending on where I traceroute from. The Williams/Yipes connection is by far the worst, and has been acting up horribly for days. The Level3/Yipes connection is considerably better, but is still showing 4% loss at the moment (it was as high as 30% earlier this morning).

To other webreseller clients - If you wouldn't mind, could you please throw 100 pings at your servers and post the results here? If you could include a traceroute as well, it would be most appreciated.

Thanks,
-Bob

Ping statistics for 66.227.26.1:
Packets: Sent = 100, Received = 82, Lost = 18 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 441ms, Average = 72ms

I knew it. Thanks,

-B

Talked to the Robert a few days ago on the phone he said some changes were taking place over the next short while to add alot of new security stuff and make the network more redundant so i'm not sure if this has anything to do with that or not so hopefully thier network can only get better ;)

i've dropped my server there but I had a long talk with Robert about it and maybe in the future if im in more severs in that area then i'll probably look into them again.

I pinged my server and got 99 recieved, 1 lost. This coulda been the fact that im on a wireless connection using a laptop but who knows

From South Florida:



Ping statistics for 66.227.**.***:
Packets: Sent = 100, Received = 94, Lost = 6 (6%
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 106ms, Average = 61ms





Tracing route to *******.com [66.227.**.***]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 26 ms 11 ms 10.107.192.1
3 8 ms 20 ms 12 ms pos6-1.orldflmlbr-rtr1.cfl.rr.com [24.95.225.1]

4 12 ms 9 ms 9 ms pos1-0.orldflcoco-rtr1.cfl.rr.com [24.95.225.9]

5 9 ms 9 ms 10 ms srp2-0.orldflwrpk-rtr1.cfl.rr.com [24.95.224.65]

6 11 ms 10 ms 9 ms srp4-0.orldfldvsn-rtr3.cfl.rr.com [24.95.224.9]

7 19 ms 19 ms 20 ms pop2-tby-P0-2.atdn.net [66.185.136.189]
8 18 ms 22 ms 17 ms bb1-tby-P0-1.atdn.net [66.185.136.176]
9 43 ms 33 ms 34 ms bb2-atm-P7-0.atdn.net [66.185.152.245]
10 35 ms 34 ms 36 ms pop1-atm-P4-1.atdn.net [66.185.150.3]
11 35 ms 36 ms 52 ms WIlliamsCommunications-ATM.atdn.net [66.185.147.
198]
12 35 ms 38 ms 37 ms drvlga1wcx2-pos15-0.wcg.net [64.200.127.61]
13 59 ms 59 ms 58 ms hrndva1wcx3-pos11-0.wcg.net [64.200.232.126]
14 69 ms 60 ms 77 ms hrndva1wcx2-oc48.wcg.net [64.200.95.73]
15 56 ms 66 ms 57 ms nycmny2wcx2-oc48.wcg.net [64.200.240.45]
16 66 ms 62 ms 61 ms phlapa1wce1-atm3-0.wcg.net [64.200.240.186]
17 * 66 ms 68 ms phlapa1wce1-yipes-gige.wcg.net [65.77.115.46]
18 54 ms 55 ms 53 ms o0-4jp2.phl004bd02.yipes.com [66.54.175.202]
19 63 ms 71 ms * o1-4bd2.phl004bd01.yipes.com [66.54.175.125]
20 54 ms * * o1-4bd1.phl053s101.yipes.com [66.54.144.109]
21 * 57 ms 56 ms o1-53s11.phl054s101.yipes.com [66.54.144.190]
22 69 ms 78 ms 55 ms 66.7.139.82
23 76 ms 73 ms 58 ms 66.227.**.***

Trace complete.

Right in the nick of time - it looks as though they've begun blocking icmp packets. That's one way to fix it, I suppose...

-Bob

Yes, we have done this....