Loss Lately? Post your pingplotter

[Fatty]

Can you guys run another pathping and post up the current results please?

[Fatty]

0/ 100 = 0% |

1 8ms 0/ 100 = 0% 0/ 100 = 0% 10.48.64.1

0/ 100 = 0% |

2 8ms 0/ 100 = 0% 0/ 100 = 0% gig2-2.akrnoh1-ybr1.neo.rr.com [24

.164.102.13]

0/ 100 = 0% |

3 9ms 0/ 100 = 0% 0/ 100 = 0% srp12-0.ncntoh1-rtr1.neo.rr.com [2

4.164.101.13]

0/ 100 = 0% |

4 10ms 0/ 100 = 0% 0/ 100 = 0% son0-0-2.ncntoh1-rtr0.neo.rr.com [

65.25.128.237]

0/ 100 = 0% |

5 20ms 0/ 100 = 0% 0/ 100 = 0% so-2-0-0-0.gar1.Chicago1.Level3.ne

t [67.72.120.5]

0/ 100 = 0% |

6 19ms 0/ 100 = 0% 0/ 100 = 0% ge-1-1.ipcolo2.Chicago1.Level3.net

[4.68.101.105]

0/ 100 = 0% |

7 21ms 0/ 100 = 0% 0/ 100 = 0% 4.79.66.18

0/ 100 = 0% |

8 20ms 0/ 100 = 0% 0/ 100 = 0% at-2-2-0-33.core2.core1.ord1.nozon

enet.com [63.208.72.109]

0/ 100 = 0% |

9 20ms 0/ 100 = 0% 0/ 100 = 0% 216-86-154-200.chi.aim2game.com [2

16.86.154.200]

 

Trace complete.

 

C:\DOCUME~1\FATTY>

 

Looking clean!

[ZesteR]

Target Name: 216-86-154-199.chi.aim2game.com

IP: 216.86.154.199

Date/Time: 12/18/2005 10:18:30 AM to 12/18/2005 10:20:09 AM

 

Hop Sent Err PL% Min Max Avg Host Name / [iP]

1 100 0 0.0 0 0 0 [192.168.254.254]

2 100 0 0.0 11 34 12 [205.238.231.97]

3 100 0 0.0 11 174 15 s4-1-0-25-0-hrbe.epix.net [199.224.90.93]

4 100 0 0.0 12 201 19 pos3-1-lkst7613.epix.net [66.33.229.146]

5 100 0 0.0 31 36 32 [12.126.174.121]

6 100 0 0.0 56 235 66 gbr5-p30.wswdc.ip.att.net [12.123.9.66]

7 100 0 0.0 58 78 60 tbr1-p013301.wswdc.ip.att.net [12.122.11.169]

8 100 0 0.0 57 72 58 tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]

9 100 0 0.0 56 276 59 [12.122.9.142]

10 100 0 0.0 58 209 62 tbr2-cl7.cgcil.ip.att.net [12.122.10.45]

11 100 0 0.0 57 75 58 gar1-p390.chail.ip.att.net [12.123.216.217]

12 100 0 0.0 57 89 58 [12.119.137.78]

13 100 0 0.0 55 76 57 at-2-2-0-33.core2.core1.ord1.nozonenet.com [63.208.72.109]

14 100 0 0.0 57 65 58 216-86-154-199.chi.aim2game.com [216.86.154.199]

 

 

I seem good to go also.

[Brillow_Head]

Scopless is pingen great too

[VooDooPC]

Target Name: 216-86-154-199.chi.aim2game.com

IP: 216.86.154.199

Date/Time: 12/18/2005 11:51:52 AM to 12/18/2005 11:53:31 AM

 

Hop Sent Err PL% Min Max Avg Host Name / [iP]

1 100 0 0.0 1 14 1 [192.168.0.1]

2 100 0 0.0 7 19 10 [10.60.32.1]

3 100 1 1.0 7 18 10 fas4-2.fmhlmi1-rtr1.twmi.rr.com [24.169.225.9]

4 100 0 0.0 8 22 11 pos0-3.lvnami1-rtr1.twmi.rr.com [24.169.225.66]

5 100 0 0.0 8 20 10 pos0-2.lvnami1-rtr2.twmi.rr.com [24.169.225.78]

6 100 1 1.0 17 28 19 son1-0-0.mtgmoh1-rtr0.columbus.rr.com [65.25.128.153]

7 100 0 0.0 27 44 30 son3-0-2.ncntoh1-rtr0.neo.rr.com [65.25.128.209]

8 100 1 1.0 38 69 40 so-2-0-0-0.gar1.Chicago1.Level3.net [67.72.120.5]

9 40 0 0.0 38 47 40 ge-1-0.ipcolo2.Chicago1.Level3.net [4.68.101.41]

10 100 0 0.0 38 79 42 [4.79.66.18]

11 100 0 0.0 38 49 40 at-2-2-0-33.core2.core1.ord1.nozonenet.com [63.208.72.109]

12 100 0 0.0 38 53 41 216-86-154-199.chi.aim2game.com [216.86.154.199]

 

No loss at all in the last three hops.

[LeftDfence]

Target Name: 216-86-154-199.chi.aim2game.com

IP: 216.86.154.199

Date/Time: 12/18/2005 12:34:54 PM to 12/18/2005 12:35:58 PM

 

Hop Sent Err PL% Min Max Avg Host Name / [iP]

1 65 0 0.0 0 0 0 [192.168.0.1]

2 65 0 0.0 6 20 9 [10.56.0.1]

3 65 0 0.0 7 16 9 er-1-fe.dlth.mn.charter.com [24.158.16.49]

4 54 54 100.0 0 0 0 [-]

5 54 54 100.0 0 0 0 [-]

6 54 54 100.0 0 0 0 [-]

7 65 0 0.0 26 41 30 [12.118.144.61]

8 65 0 0.0 34 238 56 gbr1-p20.sl9mo.ip.att.net [12.123.24.210]

9 64 0 0.0 35 58 38 tbr2-p013502.sl9mo.ip.att.net [12.122.11.113]

10 64 0 0.0 35 46 37 tbr2-cl7.cgcil.ip.att.net [12.122.10.45]

11 64 0 0.0 34 46 37 gar1-p390.chail.ip.att.net [12.123.216.217]

12 64 0 0.0 35 80 38 [12.119.137.78]

13 64 0 0.0 34 44 37 at-2-2-0-33.core2.core1.ord1.nozonenet.com [63.208.72.109]

14 64 0 0.0 35 58 38 216-86-154-199.chi.aim2game.com [216.86.154.199]

[All Kill3r]

Target Name: 216-86-154-199.chi.aim2game.com

        IP: 216.86.154.199

  Date/Time: 11/5/2005 6:19:43 AM to 11/5/2005 6:20:48 AM

 

Hop Sent Err  PL% Min Max Avg  Host Name / [iP]

1    55  55 100.0  0  0  0  [-]

2    65  0  0.0  6  20  8  [67.20.33.89]

3    65  0  0.0  13  27  16  69-161-20-217.chvlva.adelphia.net [69.161.20.217]

4    65  4  6.2  13  65  17  unk-426d0ea5.adelphiacom.net [66.109.14.165]

5    65  0  0.0  29  44  31  p3-00-01-00.c0.atl90.adelphiacom.net [66.109.0.105]

6    65  0  0.0  49  54  50  p3-00-01-00.c1.dfw91.adelphiacom.net [66.109.0.17]

7    65  0  0.0  49 144  55  g1-03-02-00.p0.dfw91.adelphiacom.net [66.109.3.78]

8    65  0  0.0  49 107  53  ge-0-3-0.cr1.dfw1.nlayer.net [206.223.118.61]

9    65  0  0.0  54  82  56  0.so-0-3-0.cr1.ord1.us.nlayer.net [69.22.142.81]

10    65  0  0.0  53  91  56  steadfast.109.ae0.cr1.ord1.us.nlayer.net [69.31.111.36]

11    65  2  3.1  53  74  56  at-2-2-0-33.core2.core1.ord1.nozonenet.com [63.208.72.109]

12    65  4  6.2  54  73  56  216-86-154-199.chi.aim2game.com [216.86.154.199]

<{POST_SNAPBACK}>

 

 

Target Name: 216-86-154-199.chi.aim2game.com

IP: 216.86.154.199

Date/Time: 11/19/2005 9:24:47 AM to 11/19/2005 9:25:19 AM

 

Hop Sent Err PL% Min Max Avg Host Name / [iP]

1 33 33 100.0 0 0 0 [-]

2 33 0 0.0 7 15 9 [67.20.33.89]

3 33 0 0.0 12 23 14 [67.20.47.185]

4 33 3 9.1 12 92 18 unk-426d0fa9.adelphiacom.net [66.109.15.169]

5 17 0 0.0 12 19 14 a1.00-00-00.c1.dca91.adelphiacom.net [66.109.1.137]

6 13 0 0.0 12 29 15 [66.109.1.134]

7 33 0 0.0 17 34 20 ge-0-3-0.cr1.iad1.nlayer.net [206.223.115.61]

8 33 0 0.0 33 40 35 0.so-0-1-0.cr1.ord1.us.nlayer.net [69.22.142.106]

9 33 0 0.0 33 79 38 steadfast.109.ae0.cr1.ord1.us.nlayer.net [69.31.111.36]

10 33 0 0.0 33 44 36 at-2-2-0-33.core2.core1.ord1.nozonenet.com [63.208.72.109]

11 33 0 0.0 33 41 35 216-86-154-199.chi.aim2game.com [216.86.154.199]

 

much better then last.

[farmerisme]

Still getting loss here. Sorry about the image, when I copy as text it seems to be in a odd format that is not anything like what people have above.

[Goofus Maximus]

Target Name: 216-86-154-199.chi.aim2game.com

IP: 216.86.154.199

Date/Time: 12/21/2005 2:22:46 PM to 12/21/2005 2:24:25 PM

 

Hop Sent Err PL% Min Max Avg Host Name / [iP]

1 100 0 0.0 6 18 8 [10.30.32.1]

2 100 0 0.0 6 28 8 24-171-15-49.dhcp.stls.mo.charter.com [24.171.15.49]

3 100 0 0.0 15 77 19 so-1-2-0.gar2.chi1.bbnplanet.net [4.79.74.1]

4 20 0 0.0 15 19 17 ge-6-0.ipcolo2.Chicago1.Level3.net [4.68.101.9]

5 100 0 0.0 15 54 19 [4.79.66.18]

6 100 0 0.0 17 49 21 at-2-2-0-33.core2.core1.ord1.nozonenet.com [63.208.72.109]

7 100 0 0.0 16 43 20 216-86-154-199.chi.aim2game.com [216.86.154.199]

 

 

Same as I got with my Hypertrace long ago. I get no packet loss at all, except ingame, though my ping sure does swing up and down, don't it?

 

I think Source is just being confused, and reporting a choke situation as a loss situation. I seem to remember the steam forums mentioning an "out of order packet problem" with Source's netcode...

Edited December 21, 2005 by Goofus Maximus

[EbilDustBunny]

Target Name: 216-86-154-199.chi.aim2game.com

        IP: 216.86.154.199

  Date/Time: 06/12/2005 11:43:34 PM to 06/12/2005 11:45:13 PM

 

Hop Sent Err PL% Min Max Avg  Host Name / [iP]

1  100  0 0.0  1  2  1  123-6.201-68.swfla.res.rr.com [68.201.6.123]

2  100  0 0.0  6  26  8  [10.112.16.1]

3  100  0 0.0  6  23  9  21-112.34-65.swfla.res.rr.com [65.34.112.21]

4  100  0 0.0  15  28  17  pos1-1.tampflerl-rtr3.tampabay.rr.com [65.32.8.61]

5  100  0 0.0  15 211  26  pos5-0-OC-192.tampflerl-rtr4.tampabay.rr.com [65.32.8.130]

6  100  0 0.0  15 113  21  so-9-1.car2.Tampa1.Level3.net [4.79.174.1]

7  100  0 0.0  15  86  21  ae-1-51.mp1.Tampa1.Level3.net [4.68.104.1]

8    51  0 0.0  51  64  53  ae-0-0.bbr1.Chicago1.Level3.net [64.159.1.33]

9    15  0 0.0  51  82  56  ge-1-1.ipcolo2.Chicago1.Level3.net [4.68.101.105]

10  100  1 1.0  52  90  54  [4.79.66.18]

11  100  3 3.0  52  69  54  at-2-2-0-33.core2.core1.ord1.nozonenet.com [63.208.72.109]

12  100  3 3.0  51  64  55  216-86-154-199.chi.aim2game.com [216.86.154.199]

 

I'm getting loss again!?! anyways here's my new plotter... maybe it's just a bad night.

 

Target Name: 216-86-154-199.chi.aim2game.com

IP: 216.86.154.199

Date/Time: 08/01/2006 10:28:41 PM to 08/01/2006 10:30:20 PM

Hop Sent Err PL% Min Max Avg Host Name / [iP]

1 100 0 0.0 0 0 0 [192.168.0.1]

2 100 0 0.0 5 114 16 [10.112.16.1]

3 100 0 0.0 5 45 16 21-112.34-65.swfla.res.rr.com [65.34.112.21]

4 100 1 1.0 14 57 25 pos1-1.tampflerl-rtr3.tampabay.rr.com [65.32.8.61]

5 100 3 3.0 14 166 30 pos5-0-OC-192.tampflerl-rtr4.tampabay.rr.com [65.32.8.130]

6 100 2 2.0 15 196 28 so-9-1.car2.Tampa1.Level3.net [4.79.174.1]

7 100 3 3.0 15 127 27 ae-1-53.mp1.Tampa1.Level3.net [4.68.104.65]

8 51 0 0.0 52 91 61 as-1-0.bbr2.Chicago1.Level3.net [64.159.3.154]

9 16 0 0.0 53 75 61 ge-6-1.ipcolo2.Chicago1.Level3.net [4.68.101.73]

10 100 5 5.0 52 112 64 [4.79.66.18]

11 100 4 4.0 51 80 62 at-2-2-0-33.core2.core1.ord1.nozonenet.com [63.208.72.109]

12 100 6 6.0 51 82 61 216-86-154-199.chi.aim2game.com [216.86.154.199]

Edited January 9, 2006 by EbilDustBunny

[Guest a2g-Sam]

ATT transported lines are having issues country wide including myself on specific routes. The known cases include california at san fran, Chicago, New York and Florida. Right now there are so many issues after Christmas time nationwide that our admins are spending 1/4 of their time helping people run traces vs working on servers.

 

In Chicago alone the problems are so far reaching it has made us start negotiations with another bandwidth provider on a nationwide commitment. While we can deal with transit issues like the att trace above since it is a bit out of our hands, we cant deal with the issues our provider made us face a few times through the course of last year. We do know there will be changes this year. Either very fast or this summer.

 

There is a very high likelihood that Chicago will be paving the way for us nationwide which is exciting in itself. There will be no details released beyond what I have said above. But information will be announced when we feel it is appropriate.

 

Sam

[stutters]

thx for the update, sam.

 

meanwhile, i'm STILL having sbc related issues between san francisco and la. while this kind of sucks for me playing on my preferred server, it's a good reason for me to play on #1 or #4, both of which could use some .gc love. even with tonights issues in chicago, i still ping better there (60-80ish) than i do to la, and i've got no loss on the route.

 

ouch

 

if your ping/loss is teh suck, try another gc server in another part of the country. it's only temporary, and there's a lot of new faces to get to know.

 

[Laz.e.rus]

[stutters]

 

ouch.

[farmerisme]

 

 

Quite a bit of loss this afternoon on 1... been great up till lately though.

[strangefamous]

Just incase you're interested, the loss seems to be coming from the hosting company..

 

loss on #2

[stutters]

it has everything in the world to do with your route. i'm not going to act like i know who goes where, but like i said before, i had (kinda continue to have) this issue via sbc to the west server.

 

only sbc dsl customers in northern california are having these issues on #3.

not everyone connecting to #3 experiences the loss/ping we do.

only sbc, only norcal. that's like 10% of the regs, at most.

 

what's this have to do with #1/#2? i have had 0 network trouble with #1/#2. in fact, when sbc really starts puking on #3, i head to the chicago servers and ping better there. last night i was averaging 50ms. it does make the hosting company look bad, but since they have multiple backbones into each data center, it only affects people on a fraction of the routes. if they only had one backbone, it would affect EVERYONE. it's cool of sam (a2g cheese) to stop by and keep us posted. i think any of us that have played in the tech/customer support arena would know that it's easier to tell people to reboot, or to uninstall something, or to try again and call back later. he's addressing the problem, and hopefully it'll get fixed soon.

 

 

anyways, this is a (short) trace to #2, but shows i have a completely different route than those

having problems.

Target Name: 216-86-154-200.chi.aim2game.com

IP: 216.86.154.200

Date/Time: 1/9/2006 7:54:13 PM

 

1 1 ms 1 ms adsl-69-109-250-144.dsl.pltn13.pacbell.net [69.109.250.144]

2 10 ms 10 ms bras10-l0.pltnca.sbcglobal.net [151.164.184.66]

3 11 ms 8 ms dist1-vlan50.pltn13.pbi.net [64.164.97.66]

4 12 ms 9 ms bb1-10g2-0.pltnca.sbcglobal.net [151.164.42.100]

5 13 ms 9 ms bb1-p4-0.crsfca.sbcglobal.net [151.164.41.5]

6 13 ms 10 ms ex1-p14-0.eqsjca.sbcglobal.net [151.164.41.10]

7 13 ms 10 ms bpr2-ge-6-0-0.SanJoseEquinix.savvis.net [151.164.89.42]

8 12 ms 12 ms dcr2-so-3-2-0.SanFranciscosfo.savvis.net [206.24.211.77]

9 13 ms 13 ms dcr1-so-5-0-0.SanFranciscosfo.savvis.net [204.70.192.149]

10 66 ms 64 ms dcr2-so-0-0-0.Denver.savvis.net [204.70.192.113]

11 66 ms 67 ms dcr1-so-7-0-0.Chicago.savvis.net [204.70.192.134]

12 69 ms 66 ms bpr2-so-0-0-0.ChicagoEquinix.savvis.net [208.175.10.98]

13 67 ms 67 ms bpr1-so-0-0-0.ChicagoEquinix.savvis.net [208.175.10.238]

14 N/A 66 ms aer1-po10.ChicagoEquinix.savvis.net [208.175.9.133]

15 67 ms 66 ms 216-86-154-200.chi.aim2game.com [216.86.154.200]

[strangefamous]

I ping great to #1 and #2 and not half bad on 3. My ping on scopeless is between 17-30 most of the time, but my loss is averaging about 15-20 with a max of 80.

[EbilDustBunny]

yeah I ran another ping plot tonight.. it's just butt ugly. But the crazy thing was that a few days ago there was no problem! not one! there was no choke no lag.... but Sunday after I reinstalled my HL2. (my pc was formatted and restored) It was rabbit season and everyone had a bazooka... and the tmp & carrot was nowhere to be found.