 papillon
join:2002-03-10 Minnetonka, MN
1 edit | reply to papillon Re: Houston Road Runner... High Pings Again##&&@
Who can f((k explain this &Hit? huh? anyone out there? Guess not. RR techs are dimwits... blah!!!!!!!!!!!!! |
|
 papillon
join:2002-03-10 Minnetonka, MN
| reply to papillon Well... at least the FU is consistant... blah.... |
|
 papillon
join:2002-03-10 Minnetonka, MN
| reply to papillon I suppose it could be worse... However, I'm not sure how... RR/ATDN PLEASE FIX ThIS!!!!!!!!!!!!!!!!!!!!!! |
|
 papillon
join:2002-03-10 Minnetonka, MN
| reply to papillon Every dam night!!!!!!!!!!!!!!!!!!!!! |
|
 papillon
join:2002-03-10 Minnetonka, MN
| reply to kstark Really bad on 12_09_03. Check out the plot. |
|
 kstark
join:2002-01-30 germany
·T-Com
| reply to jgs This is day 2 of some nasty packet loss. Called RR last night and it only took me about an hour to convince the rep that there was actually packet loss. She was accusing me of starting my firewall and turning it off while she was trying to ping me. So it was escalated, but didn't get fixed today. Hopefully tomorrow, as this is screwing with my VOIP too. |
|
 papillon
join:2002-03-10 Minnetonka, MN
1 edit | reply to jgs Re: Houston Road Runner... High Pings Again##&&@@
If it happens tonight, I'll be on the phone to RR tier three. They typically try to debug the client end (you and me) before going upstream to look for a fubared router. As I see here, I'm not the only one in the Sugar Land area with this issue. My bet... fubared router upstream. And I can even give them the hop and ip address. |
|
 jgs
join:2003-12-08 Houston, TX
| reply to jgs Tracing route to 209.120.238.13 over a maximum of 30 hops
1 15 ms 16 ms 10 ms 10.48.64.1 2 10 ms 16 ms 10 ms pos5-1.hstntxtid-rtr1.houston.rr.com [24.28.97.6 5] 3 10 ms 15 ms 10 ms srp8-0.hstntxtid-rtr3.texas.rr.com [24.93.33.147 ] 4 10 ms 16 ms 10 ms son0-0-3.hstqtxl3-rtr1.texas.rr.com [24.93.33.16 1] 5 10 ms 16 ms 10 ms pop1-hou-P0-1.atdn.net [66.185.133.145] 6 16 ms 10 ms 16 ms bb1-hou-P0-0.atdn.net [66.185.146.96] 7 16 ms 15 ms 16 ms bb1-dls-P6-0.atdn.net [66.185.152.132] 8 16 ms 15 ms 16 ms bb2-dls-P2-0.atdn.net [66.185.153.29] 9 31 ms 16 ms 31 ms bb2-kcy-P6-0.atdn.net [66.185.152.129] 10 15 ms 31 ms 32 ms bb1-kcy-P1-0.atdn.net [66.185.152.126] 11 47 ms 32 ms 46 ms bb1-chi-P6-0.atdn.net [66.185.152.124] 12 31 ms 32 ms 47 ms pop1-chi-P0-0.atdn.net [66.185.141.85] 13 32 ms 31 ms 47 ms bpr2-so-3-0-0.ChicagoEquinix.cw.net [208.174.224 .29] 14 79 ms 78 ms 78 ms 208.174.224.26 15 47 ms 47 ms 47 ms chcgil1wcx2-oc48.wcg.net [64.200.103.117] 16 47 ms 62 ms 47 ms dnvrco1wcx2-pos10-0.wcg.net [64.200.210.66] 17 63 ms 47 ms 47 ms 64.200.108.5 18 63 ms 47 ms 47 ms dllstx1wcx3-pos1-0.wcg.net [64.200.240.213] 19 47 ms 47 ms 47 ms dllstx9lcx1-pos9-0.wcg.net [64.200.232.210] 20 47 ms 46 ms 63 ms dllstx9lcx1-pos6-0.wcg.net [64.200.232.14] 21 47 ms 47 ms 62 ms dllstx9lce1-yipes.wcg.net [64.200.226.118] 22 62 ms 47 ms 47 ms 66.7.164.66 23 47 ms 62 ms 47 ms 209.120.238.13
Trace complete. jgs |
|