This looks much better. You local latencies are fine. I don't know if that 10.4.32.1 is your modem, which it shouldn't be, or something out on your service provider's network. My recommendation would be to send an email to your ISP asking if 10.4.32.1 is your equipment or theirs, and pasting the output that you just posted into it, highlighting the fact that one of their routers is dropping a -lot- of packets. The people on the front line of ISP support are typically completely oblivious to the network topology, so hopefully they'll send it onto a second line supporter.aimless wrote:
This is through my router:I had to ping yahoo because google was giving me the unending list of ips.Code:
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | cpe-24-175-93-7.tx.res.rr.com - 0 | 424 | 424 | 0 | 1 | 16 | 0 | | 10.4.32.1 - 0 | 424 | 424 | 0 | 34 | 203 | 62 | | gig2-23.dllatxrch-rtr1.tx.rr.com - 1 | 423 | 419 | 0 | 37 | 234 | 31 | | gig5-0-0.dllatxchn-rtr6.tx.rr.com - 0 | 423 | 423 | 0 | 35 | 188 | 15 | | gig0-1-0.hstntxl3-rtr1.texas.rr.com - 26 | 423 | 315 | 0 | 40 | 328 | 31 | | 4.79.180.65 - 0 | 423 | 423 | 0 | 45 | 235 | 63 | | YAHOO-INC.car1.Dallas1.Level3.net - 0 | 423 | 423 | 0 | 39 | 203 | 15 | | ge-0-1-0-p120.msr1.mud.yahoo.com - 0 | 423 | 423 | 0 | 42 | 281 | 31 | | te-8-1.bas-c2.mud.yahoo.com - 0 | 423 | 423 | 0 | 46 | 469 | 31 | | f1.www.vip.mud.yahoo.com - 0 | 423 | 423 | 0 | 43 | 344 | 78 | |________________________________________________|______|______|______|______|______|______| WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com )
That hstntxl3 server is still losing packets.
If you don't get any response, I'd recommend calling them up, asking for a manager, and asking to have your case escalated since you did not get a response, and your product is bordering on the unusable. The closer you get to the people dealing with the network, the better the responses will be. Chances are that they know all about the degraded line performance.