The good folks atNC have let us know they are aware of the lag issues many players are facing, and they are working to resolve it.
What they need from us is additional data. If you are having more lag than usual, please submit a support ticket through the contact support link at www.lineage.com.
The support team needs as much data as possible from as many locations as possible to resolve this issue.
Thanks.
Mr C i gave NC a piece of my
Mr C i gave NC a piece of my mind the other nite (it wasnt much) but they did respond to me and told me what to do. they told me my video drives where out of date and to get the newest version drives,and they wanted me to change my virtual memory values. Well i did just as they instructed by the responce i got annnnnnnd (drum roll) it did absolutly NOTHING!!!! So what ever they have to say is a bunch of BS, i sent them a full copy of my system and thats what they told me to do, so i think they rreally think it is our end and not theirs. They always tell me the same thing that it its my direct 3D well i proved it to them this time it wasnt me.
That's always the case, but
That's always the case, but to get it fixed we have to get everyone to open up support tickets until they are forced to accept that is not on the user end. It's somewhere between the user and NC. If they get enough data to figure out where exactly the problem is they can assert a little force.
Until then we just have to go through the three day runaround.
well if getting to the
well if getting to the support tickets wasnt such a pain in the rump im sure more ppl would do so.. i had a SS to subitt of an incedent and i couldnt even do it because it was a do this do that do this click here check that send this in blah blah blah i said *^%*^(&)&^*(^%&^$&%(^)&*)(*_))*^%*$ and quit trying.. lol
MuddyWater
www.muddymudpuddle.blogspot.com
Submitting tickets with
Submitting tickets with tracert information helps our network nerds figure out where things are going sour. We need to find patterns but we can't do that without plenty of data. Give us data!
While at the office today I experienced nothing but the greatest connection ever. From home tonight, however, it's an entirely different story. I feel the pain and would like nothing more than to do something about it...but I can't (at least not by myself).
I compared my office tracert to my home tracert and, although I'm just down the road, they were dramatically different. For kicks I'd like to see some tracerts posted in this thread, if y'all can muster up the strength to do that much. Whether you're lagging or not, throw some data out here (along with a note saying whether or not you're experiencing lag). I'll go first.
From Home (laggy):
3 17 ms 10 ms 8 ms gig15-0-4.austtxrdcsc-rtr2.austin.rr.com [66.68.
2.186]
4 11 ms 9 ms 10 ms gig2-0-0.austtxrdcsc-rtr4.texas.rr.com [24.93.33
.150]
5 17 ms 19 ms 25 ms gig5-3-0.hstntxl3-rtr1.texas.rr.com [72.179.205.
37]
6 20 ms 20 ms 18 ms te-7-2.car1.Houston1.Level3.net [4.79.88.21]
7 30 ms 19 ms 19 ms ae-5-5.ebr1.Dallas1.Level3.net [4.69.132.230]
8 19 ms 17 ms * ae-14-55.car4.Dallas1.Level3.net [4.68.122.144]
9 18 ms 17 ms 17 ms dpr1-ge-5-0-0.DallasEquinix.savvis.net [208.173.
178.141]
10 27 ms 18 ms 20 ms dcr2-so-7-2-0.Dallas.savvis.net [204.70.193.214]
11 53 ms 52 ms 52 ms dcr2-so-2-0-0.LosAngeles.savvis.net [204.70.192.
86]
12 52 ms 51 ms 52 ms ber1-tenge-2-1.losangeles.savvis.net [204.70.193
.106]
13 60 ms * 52 ms ber1-tenge-3-1.losangeles.savvis.net [204.70.193
.50]
14 * * * Request timed out.
15 * * * Request timed out.
I want to make it clear that I'm not suggesting blog comment fields should replace support tickets now or in the future. I just want some data and I want it now! :)
Fracas thats a good idea and
Fracas thats a good idea and i would but im not sure how to go and get that info, if you can give an idea or a place to get this info. I am running windows XP and it has a pathping but it always says that there is no packet loss, even tonite with all the lag we were having,please give me a link to find these things
info would be awesome.. as
info would be awesome.. as mrhood said we are unsure where to get the info..
MuddyWater
www.muddymudpuddle.blogspot.com
You can refer to our KB
You can refer to our KB article which suggests using a program called "Ping Plotter" if you're on PC or using the traceroute command if on a Mac.
http://www.plaync.com/us/support/doc_172.html?prod=8
You can also use the command line on a PC by doing the following.
1. Start
2. Run
3. "cmd" (without the quotes) [ENTER]
This should open up a Windows command prompt window
4. Type "tracert <ip of the server you play on>" (without the quotes and using the list below for the IP)
5. Once it has finished, right click anywhere in the window and choose "Mark" from the right-click menu.
6. Highlight the nerd garbage that was spewed at you when you ran the tracert command (it should look like what I pasted above)
7. When you've highlighted all of it, press [ENTER] to copy it to your clipboard
8. Come back here and paste it into a comment box.
List of server IPs (per the KB article linked above)
216.107.243.51 for Depardieu
216.107.243.52 for Ken Rauhel
216.107.243.53 for Lands of Aden
216.107.243.50 for Test
1 * * *
1 * * * Request timed out.
2 14 ms 16 ms 29 ms 67-58-165-1.dynamic.zitomedia.net.165.58.67.in-a
dr.arpa [67.58.165.1]
3 12 ms 13 ms 11 ms 67.58.160.129
4 16 ms 15 ms 16 ms 67.58.160.181
5 31 ms 29 ms 27 ms 64.8.34.193
6 45 ms 33 ms 33 ms 24.56.106.205
7 36 ms 30 ms 33 ms p03-6-1-0.a0-phla.telcove.net [24.56.96.98]
8 40 ms 37 ms 42 ms 24.56.96.41
9 38 ms 39 ms 39 ms te-3-1-70.car1.Philadelphia1.Level3.net [4.68.63
37]
10 38 ms 43 ms 41 ms ae-11-11.car2.Philadelphia1.Level3.net [4.69.133
166]
11 41 ms 34 ms 36 ms ae-6-6.ebr1.NewYork1.Level3.net [4.69.133.170]
12 49 ms 40 ms 34 ms ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]
13 37 ms 36 ms 36 ms ae-2-79.edge5.NewYork1.Level3.net [4.68.16.73]
14 45 ms 40 ms 44 ms dcr6-so-6-1-0.NewYork.savvis.net [4.68.127.206]
15 35 ms 36 ms 33 ms bcs1-so-6-0-0.NewYork.savvis.net [204.70.192.37]
16 111 ms 107 ms 106 ms bcs1-so-6-1-0.Washington.savvis.net [204.70.192.
]
17 109 ms 104 ms 106 ms dcr1-so-3-0-0.Atlanta.savvis.net [204.70.192.53]
18 77 ms 109 ms 76 ms dcr1-so-1-2-0.dallas.savvis.net [204.70.192.74]
19 81 ms 91 ms 111 ms dcr2-so-2-0-0.LosAngeles.savvis.net [204.70.192.
6]
20 111 ms 110 ms 113 ms ber1-tenge-3-1.losangeles.savvis.net [204.70.193
50]
21 105 ms * 105 ms ber1-tenge-2-1.losangeles.savvis.net [204.70.193
106]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * *
ok i have no idea what all this junk means it really is "nerd garbage" lol
MuddyWater
www.muddymudpuddle.blogspot.com
1 * * *
1 * * * Request timed out.
2 15 ms 24 ms 12 ms 67-58-165-1.dynamic.zitomedia.net.165.58.67.in-a
ddr.arpa [67.58.165.1]
3 21 ms 23 ms 17 ms 67.58.160.129
4 21 ms 20 ms 22 ms 67.58.160.181
5 33 ms 27 ms 43 ms 64.8.34.193
6 48 ms 38 ms 39 ms 24.56.106.205
7 41 ms 38 ms 44 ms p03-6-1-0.a0-phla.telcove.net [24.56.96.98]
8 43 ms 40 ms 41 ms 24.56.96.41
9 40 ms 41 ms 42 ms te-3-1-70.car1.Philadelphia1.Level3.net [4.68.63
.37]
10 39 ms 42 ms 45 ms ae-11-11.car2.Philadelphia1.Level3.net [4.69.133
.166]
11 38 ms 37 ms 36 ms ae-6-6.ebr1.NewYork1.Level3.net [4.69.133.170]
12 41 ms 38 ms 50 ms ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]
13 37 ms 34 ms 38 ms ae-2-79.edge5.NewYork1.Level3.net [4.68.16.73]
14 44 ms 46 ms 61 ms dcr6-so-6-1-0.NewYork.savvis.net [4.68.127.206]
15 40 ms 41 ms 35 ms bcs1-so-6-0-0.NewYork.savvis.net [204.70.192.37]
16 111 ms 106 ms 115 ms bcs1-so-6-2-0.Washington.savvis.net [204.70.192.
13]
17 107 ms 116 ms 104 ms dcr1-so-3-0-0.Atlanta.savvis.net [204.70.192.53]
18 106 ms 105 ms 72 ms dcr1-so-1-2-0.dallas.savvis.net [204.70.192.74]
19 88 ms 237 ms 113 ms dcr2-so-2-0-0.LosAngeles.savvis.net [204.70.192.
86]
20 203 ms 113 ms 114 ms dcr1.lay-so-3-2-0.losangeles.savvis.net [204.70.
194.53]
21 119 ms * 102 ms ber1-tenge-2-1.losangeles.savvis.net [204.70.193
.106]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 *
Heres what i came up with Fracas ....thank you much i hope it helps!!!!
hope it helps Fracas ty for
hope it helps Fracas ty for the help
MuddyWater
www.muddymudpuddle.blogspot.com
Oh yea me and muddy are
Oh yea me and muddy are running under the same router she is just a few inches from me so we see how different they are
btw our pings were for ken
btw our pings were for ken server if u would like to see like test or loa let us know and we will run them for u on this end we are way out in Penn.. :)
MuddyWater
www.muddymudpuddle.blogspot.com
I assume you guys are
I assume you guys are experiencing lag, correct?
yes we are 5sec to a full
yes we are 5sec to a full min in spikes.. lol like i said we cant read that stuff so we are unsure what it says.. hopefully u could explaine breifly to us in a privite message or something.. i would be very interested in what it means.. thx
MuddyWater
www.muddymudpuddle.blogspot.com
I am behind a firewall here
I am behind a firewall here at work (I am the IT guy and I do not feel like modifying my Firewall settings to get a complete tracert) I tested the game instead =],I have no lag at this location. Although at home, I have dialup, and I have been experiencing the lag =(
This is actually one I sent
This is actually one I sent to support over my lunch break yesterday when it was really bad, but not as bad as it usually is at night. For what it's worth, my biggest problem is my ISP will usually reroute me; but won't this time because they say losing 2 out of 3 packets in that last hop is too likely to be the problem for them to commit resources to rerouting. But support says that is normal.
traceroute to 216.107.243.52 (216.107.243.52), 30 hops max, 40 byte packets
1 10.68.96.1 (10.68.96.1) 8.072 ms 8.98 ms 11.119 ms
2 gig2-1.kscymolibe-rtr1.kc.rr.com (24.94.161.101) 6.825 ms 7.488 ms 8.616 ms
3 srp1-1.kscymonort-rtr2.kc.rr.com (24.31.239.97) 14.411 ms 8.44 ms 7.83 ms
4 gig4-2.kscymonort-rtr1.kc.rr.com (24.94.164.141) 8.742 ms 11.632 ms 12.081 ms
5 srp14-0.kscymordc-rtr1.kc.rr.com (24.31.239.1) 9.317 ms 8.694 ms 8.161 ms
6 srp9-0.kscymordc-rtr2.kc.rr.com (24.31.239.121) 10.265 ms 8.284 ms 9.569 ms
7 so-3-1-1.kscymol3-rtr1.kc.rr.com (24.94.160.169) 8.705 ms 17.347 ms 7.925 ms
8 ge-5-1-203.hsa1.stlouis1.level3.net (4.79.132.13) 15.957 ms te-1-3.car1.stlouis1.level3.net (4.79.132.33) 14.439 ms ge-5-1-203.hsa1.stlouis1.level3.net (4.79.132.13) 34.433 ms
9 ae-11-11.car2.stlouis1.level3.net (4.69.132.186) 16.177 ms 13.257 ms 14.39 ms
10 ae-4-4.ebr2.chicago1.level3.net (4.69.132.190) 19.23 ms 18.89 ms 36.886 ms
11 ae-21-56.car1.chicago1.level3.net (4.68.101.162) 19.089 ms ae-21-52.car1.chicago1.level3.net (4.68.101.34) 19.136 ms ae-21-54.car1.chicago1.level3.net (4.68.101.98) 22.475 ms
12 dcr1-ge-2-0-0.chicago.savvis.net (208.175.10.1) 21.559 ms 29.923 ms 18.707 ms
13 dcr2-so-5-0-0.chicago.savvis.net (204.70.192.46) 23.23 ms 49.974 ms 23.702 ms
14 dcr2-so-0-0-0.dallas.savvis.net (204.70.192.98) 55.93 ms dcr1-so-4-3-0.denver.savvis.net (204.70.193.225) 45.126 ms 42.995 ms
15 dcr1-so-6-0-0.dallas.savvis.net (204.70.192.49) 54.633 ms dcr1.lay-so-6-2-0.losangeles.savvis.net (204.70.192.145) 88.526 ms dcr1-so-6-0-0.dallas.savvis.net (204.70.192.49) 78.87 ms
16 dcr2-so-2-0-0.losangeles.savvis.net (204.70.192.86) 91.935 ms ber1-tenge-2-1.losangeles.savvis.net (204.70.193.106) 80.166 ms dcr2-so-2-0-0.losangeles.savvis.net (204.70.192.86) 81.677 ms
17 ncsoft.ge5-11.br01.lax05.pccwbtn.net (63.218.73.2) 74.679 ms 76.908 ms ber1-tenge-3-1.losangeles.savvis.net (204.70.193.50) 82.942 ms
18 * ncsoft.ge5-11.br01.lax05.pccwbtn.net (63.218.73.2) 75.364 ms *
I normally never lag at all.
I normally never lag at all. so figured I post a good ping plotter for you all!
This was done with command prompt. and the "Tracert" command
C:\Documents and Settings\Anju>tracert 216.107.243.50
Tracing route to 216-107-243-50.plaync.com [216.107.243.50]
over a maximum of 30 hops:
TEST Server
1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 2 ms 2 ms launchmodem [192.168.1.254]
3 16 ms 16 ms 17 ms 68.152.183.110
4 16 ms 16 ms 16 ms 68.152.183.121
5 27 ms 25 ms 26 ms 205.152.175.50
6 32 ms 31 ms 26 ms ixc00cae-pos-7-1.bellsouth.net [65.83.239.118]
7 26 ms 25 ms 25 ms 65.83.239.115
8 27 ms 25 ms 25 ms axr00asm-so-2-3-0.bellsouth.net [65.83.239.86]
9 25 ms 25 ms 25 ms axr00msy-0-3-0.bellsouth.net [65.83.236.44]
10 44 ms 43 ms 45 ms 0.so-1-0-0.GW13.ATL5.ALTER.NET [157.130.73.109]
11 43 ms 45 ms 47 ms 0.so-1-0-3.XT2.ATL5.ALTER.NET [152.63.84.102]
12 138 ms 108 ms 108 ms 0.so-6-0-0.XL2.LAX1.ALTER.NET [152.63.57.81]
13 108 ms 107 ms 107 ms POS7-0.GW4.LAX1.ALTER.NET [152.63.53.61]
14 * * * Request timed out.
DEP
C:\Documents and Settings\Anju>tracert 216.107.243.51
Tracing route to 216-107-243-51.plaync.com [216.107.243.51]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 <1 ms 1 ms 2 ms launchmodem [192.168.1.254]
3 16 ms 16 ms 15 ms 68.152.183.110
4 16 ms 16 ms 16 ms 68.152.183.121
5 26 ms 25 ms 25 ms 205.152.175.50
6 25 ms 25 ms 25 ms ixc00cae-pos-7-1.bellsouth.net [65.83.239.118]
7 25 ms 25 ms 26 ms 65.83.239.115
8 25 ms 25ms 25 ms axr00asm-so-2-3-0.bellsouth.net [65.83.239.86]
9 25 ms 25 ms 25 ms axr00msy-0-3-1.bellsouth.net [65.83.236.46]
10 43 ms 42 ms 44 ms 0.so-0-0-0.GW13.ATL5.ALTER.NET [157.130.73.97]
11 43 ms 43 ms 44 ms 0.so-1-0-3.XT2.ATL5.ALTER.NET [152.63.84.102]
12 108 ms 160 ms 108 ms 0.so-6-0-0.XL2.LAX1.ALTER.NET [152.63.57.81]
13 107 ms 107 ms 108 ms POS7-0.GW4.LAX1.ALTER.NET [152.63.53.61]
No lag at all on the servers for me. I did have some this weekend but that was with 90% of the server hehe I lived so I was happy! and I was chao o.o talk about a scare!
To yours this way go to
Start--> Run--> Type in "CMD" Press enter
In the new window type tracert "IP adress" in this case 216.107.243.51 for DEP so it looks like
Tracert 216.107.243.51 --> Press enter
Once it start to time out on 2-3 Hopps in a row Press
Ctrl + C
This will cancel it
Now right click and hit "Mark" in the window/ Click and drag your mouse to highlight everything then press enter! (command prompt is a bit odd you have to Mark then highlight and press Enter to copy stuff)
Now come and to this and Paste it in.
Mac users! Open a terminal
Mac users!
Open a terminal and type:
traceroute
Here's roo's:
From the office:
traceroute to 216.107.243.52 (216.107.243.52), 64 hops max, 40 byte packets
1 intr2e2.ukcore.eservglobal.co.uk (192.168.24.254) 1.981 ms 1.439 ms 1.455 ms
2 192-168-16-129.intra.eservglobal.co.uk (192.168.16.129) 2.912 ms 2.188 ms 2.185 ms
3 62.253.205.254 (62.253.205.254) 3.446 ms 2.761 ms 2.810 ms
4 popl-lam-1-multilink26.inet.ntl.com (62.255.92.13) 204.504 ms 71.588 ms 333.833 ms
5 popl-t3core-1b-so-701-0.inet.ntl.com (62.255.64.201) 7.806 ms 6.666 ms 6.479 ms
6 pop-bb-b-so-020-0.inet.ntl.com (213.105.174.238) 7.216 ms 16.645 ms 7.379 ms
7 gfd-bb-a-so-010-0.inet.ntl.com (213.105.172.137) 9.833 ms 8.907 ms 11.373 ms
8 gfd-bb-b-ge-000-0.inet.ntl.com (213.105.172.6) 38.060 ms 8.861 ms 9.724 ms
9 redb-ic-1-so-700-0.inet.ntl.com (62.253.185.78) 11.153 ms 9.901 ms 9.830 ms
10 cr02.ldn01.pccwbtn.net (195.66.224.167) 22.521 ms 14.041 ms 13.617 ms
11 pos2-1.br01.lax05.pccwbtn.net (63.218.72.70) 181.091 ms * 249.392 ms
12 ncsoft.ge5-11.br01.lax05.pccwbtn.net (63.218.73.2) 178.648 ms 186.523 ms 181.057 ms
13 * * *
14 * * *
From LineageOne.com:
mheath@pulsar:~$ /usr/sbin/tracepath 216.107.243.52
1: pulsar.ukshells.co.uk (217.10.140.9) 0.330ms pmtu 1500
1: ukshells-ar3.stud1.router.uksolutions.net (217.10.140.1) 0.887ms
2: ge1-4.cr1.stud1.router.uksolutions.net (217.10.157.25) 0.870ms
3: ge1-8.cr2.stud1.router.uksolutions.net (217.10.157.66) asymm 6 10.425ms
4: ge1-7-5.cr1.rbs.router.uksolutions.net (217.10.157.86) asymm 3 9.882ms
5: ge0-1.er1.rbs.router.uksolutions.net (82.147.2.2) asymm 4 10.248ms
6: cr02.ldn01.pccwbtn.net (195.66.224.167) asymm 5 46.235ms
7: pos1-1.br01.lax05.pccwbtn.net (63.218.72.66) asymm 12 155.411ms
8: ncsoft.ge5-11.br01.lax05.pccwbtn.net (63.218.73.2) asymm 11 160.453ms
9: no reply
10: no reply
11: no reply
I didnt start lagging real
I didnt start lagging real bad till today's reset!!!
I CANT DO THE EVENT LIKE THIS =(((((
Got Blog?
From home: traceroute to
From home:
traceroute to 216.107.243.52 (216.107.243.52), 64 hops max, 40 byte packets
1 192.168.28.1 (192.168.28.1) 4.976 ms 0.654 ms 0.581 ms
2 l1.ar20.gs1.dsl.pipex.net (195.112.5.29) 12.489 ms 13.192 ms 12.249 ms
3 ge-1-0-1-0.cr02.gs1.dsl.pipex.net (84.12.224.29) 13.441 ms 11.934 ms 14.675 ms
4 pc9.cr05.tn5.bb.pipex.net (62.72.137.13) 13.762 ms 13.116 ms 12.256 ms
5 cr02.ldn01.pccwbtn.net (195.66.224.167) 13.182 ms 13.077 ms 12.613 ms
6 pos2-1.br01.lax05.pccwbtn.net (63.218.72.70) 158.670 ms 158.898 ms 157.942 ms
7 p5-15-c0-ncla-pub.plaync.net (208.251.113.186) 168.295 ms 169.782 ms 169.409 ms
8 * * *
hasnt the server had lag
hasnt the server had lag since the end of ep4 to now? does the lag have anything to do with the server changes?
I get it off and on. But
I get it off and on. But normally when I do, so do others.
I rarely lag do to my ISP.
But after this reset for event... ITS HORRIBLE
Got Blog?
its all in ur mind....FREE
its all in ur mind....FREE YOUR MIND...and itll free ur lag...
...if this doesnt work...ur not trying hard enough...
I wonder if there is any
I wonder if there is any progress being made on this front.
I think there is, and at the
I think there is, and at the same time there isnt.
I know that at least one person with real bad lag before this reset, doesnt have it anymore. But at the same time that hers went away, mine came in 10x worse than before.
Got Blog?
Last night was as bad as it
Last night was as bad as it has been for me since the lag started several days ago. The game was unplayable. I didn't even bother participating in the event because babysitting me every 15 seconds when I lagged out was holding back my pledge.
I just wish someone could give me an explanation as to why it does not matter that I'm dropping 2 out of 3 packets at NC's server. That's the reason my ISP won't reroute me is because they think that has to be a problem if 2/3 of the packets arent' making it through that hop. NC support says it's normal. If someone at NC could explain to me, preferably in English, why I should expect 2 out of 3 packets lost at ncsoft.ge5-11.br01.lax05.pccwbtn.net I could then (maybe) explain to by ISP why that is not the problem.
Right after the reset i
Right after the reset i wasnt to bad ,it was bareable, but today it has just gotten bad enough the im having 2-5 second lag spikes. Swing lag is terrible also, glad to see that NC is right on top of the problem
Microsoft Windows XP
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Obz>pathping 216.107.243.52
Tracing route to 216-107-243-52.plaync.com [216.107.243.52]
over a maximum of 30 hops:
0 lake01.hsd1.mi.comcast.net. [192.168.1.100]
1 73.47.156.1
2 VL-22-sr01.elkhart.in.sbend.comcast.net [68.87.250.97]
3 te-8-1-ur02.mishawaka.in.sbend.comcast.net [68.87.235.45]
4 te-8-4-ar02.mishawaka.in.sbend.comcast.net [68.87.235.13]
5 12.117.169.5
6 tbr2.dtrmi.ip.att.net [12.123.139.142]
7 tbr2.cgcil.ip.att.net [12.122.10.134]
8 ggr2.cgcil.ip.att.net [12.123.6.69]
9 0.so-1-1-0.BR6.CHI2.ALTER.NET [204.255.174.9]
10 0.so-0-0-0.XL1.CHI13.ALTER.NET [152.63.73.26]
11 0.so-6-0-0.XL1.LAX1.ALTER.NET [152.63.57.77]
12 POS6-0.GW4.LAX1.ALTER.NET [152.63.53.57]
13 * * *
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 lake01.hsd1.mi.comcast.net. [192.1
68.1.100]
0/ 100 = 0% |
1 6ms 0/ 100 = 0% 0/ 100 = 0% 73.47.156.1
1/ 100 = 1% |
2 23ms 1/ 100 = 1% 0/ 100 = 0% VL-22-sr01.elkhart.in.sbend.comcas
t.net [68.87.250.97]
0/ 100 = 0% |
3 23ms 1/ 100 = 1% 0/ 100 = 0% te-8-1-ur02.mishawaka.in.sbend.com
cast.net [68.87.235.45]
0/ 100 = 0% |
4 24ms 1/ 100 = 1% 0/ 100 = 0% te-8-4-ar02.mishawaka.in.sbend.com
cast.net [68.87.235.13]
0/ 100 = 0% |
5 32ms 2/ 100 = 2% 1/ 100 = 1% 12.117.169.5
0/ 100 = 0% |
6 --- 100/ 100 =100% 99/ 100 = 99% tbr2.dtrmi.ip.att.net [12.123.139.
142]
0/ 100 = 0% |
7 --- 100/ 100 =100% 99/ 100 = 99% tbr2.cgcil.ip.att.net [12.122.10.1
34]
0/ 100 = 0% |
8 --- 100/ 100 =100% 99/ 100 = 99% ggr2.cgcil.ip.att.net [12.123.6.69
]
0/ 100 = 0% |
9 34ms 2/ 100 = 2% 1/ 100 = 1% 0.so-1-1-0.BR6.CHI2.ALTER.NET [204
.255.174.9]
0/ 100 = 0% |
10 34ms 1/ 100 = 1% 0/ 100 = 0% 0.so-0-0-0.XL1.CHI13.ALTER.NET [15
2.63.73.26]
0/ 100 = 0% |
11 87ms 1/ 100 = 1% 0/ 100 = 0% 0.so-6-0-0.XL1.LAX1.ALTER.NET [152
.63.57.77]
0/ 100 = 0% |
12 86ms 1/ 100 = 1% 0/ 100 = 0% POS6-0.GW4.LAX1.ALTER.NET [152.63.
53.57]
99/ 100 = 99% |
13 --- 100/ 100 =100% 0/ 100 = 0% lake01 [0.0.0.0]
Trace complete.
C:\Documents and Settings\Obz>
Here ye Be Fracas .. Straight up outa T3C2 .. South Central Mishigan (on the Indiana Border). Not alot of lag issues here ever .. every now and again I get studder steps very few stops over a few seconds. I have been droped a hand full of times in the last 3 yrs. I've had the Cable connection here, not that I'm "lag Free" but few an far between are they bad bad. Hope that helps.
Beer Me !!
Visit Tikies Home on the Web Here!
Microsoft Windows XP
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\User>tracert 216.107.243.52
Tracing route to 216-107-243-52.plaync.com [216.107.243.52]
over a maximum of 30 hops:
1 * * * Request timed out.
2 17 ms 14 ms 14 ms 67-58-165-1.dynamic.zitomedia.net.165.58.67.in-a
ddr.arpa [67.58.165.1]
3 * 12 ms 20 ms 67.58.160.129
4 15 ms 13 ms 19 ms 67.58.160.181
5 29 ms 28 ms 29 ms 64.8.34.193
6 30 ms 31 ms 33 ms 24.56.106.153
7 * 44 ms 39 ms 24.56.96.45
8 41 ms 51 ms 46 ms te-3-1-70.car1.Philadelphia1.Level3.net [4.68.63
.37]
9 42 ms 45 ms 55 ms ae-11-11.car2.Philadelphia1.Level3.net [4.69.133
.166]
10 49 ms 51 ms 59 ms ae-6-6.ebr1.NewYork1.Level3.net [4.69.133.170]
11 54 ms 49 ms 53 ms ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]
12 52 ms 47 ms 50 ms ae-2-79.edge5.NewYork1.Level3.net [4.68.16.73]
13 51 ms 58 ms 44 ms dcr6-so-6-1-0.NewYork.savvis.net [4.68.127.206]
14 119 ms 134 ms 119 ms 204.70.196.121
15 118 ms 115 ms 116 ms 204.70.196.138
16 122 ms 120 ms 122 ms dcr1-so-3-0-0.Atlanta.savvis.net [204.70.192.53]
17 94 ms 88 ms 88 ms dcr1-so-1-2-0.dallas.savvis.net [204.70.192.74]
18 116 ms 115 ms 116 ms dcr2-so-2-0-0.LosAngeles.savvis.net [204.70.192.
86]
19 118 ms 112 ms 112 ms ber1-tenge-3-1.losangeles.savvis.net [204.70.193
.50]
20 * * * Request timed out.
21 * * * Request timed out.
22 ^C
C:\Documents and Settings\User>
First of all, how can we
First of all, how can we possibly do an accurate tracert when somewhere down the road one of the hops is blocking most udp/icmp packets... i cant even trace all the way to the server itself. Which means when the 10-15 second COMPLETE DEATH LAG will occur on the bad hop, i'll never be able to get to it. (unless its anywhere in or before the llnw.net route)
anyway heres my tracert result, but it doesnt mean a damn thing, neither does any of your tracerts.
Im willing to bet you guys didnt do the tracert DURING the small window frame when the hop is entirely dead. Anyway, I tried writing to support and now they are screwing with me instead of listening to what im telling them. "Oh, go do this and that and this" bla bla facking blah. Reinstalling my drivers wont do a frickin thing for a case of a DEAD BACKBONE RELAY ON THEIR OWN NETWORK WHICH THEY ARE TOO STUPID TO SPOT. <-- so sad, a 5$ admin could do a better job than nc u.s
P.S: I chose to hide my own first 2 hops , at least from this public viewing, for personal reasons.
tracert 216.107.243.53
Tracing route to 216-107-243-53.plaync.com [216.107.243.53]
over a maximum of 30 hops:
1 22 ms 15 ms 15 ms **** [***]
2 15 ms 15 ms 15 ms **** [***]
3 15 ms 15 ms 15 ms core1-ottawa23_GE6-1.net.bell.ca [64.230.208.249
]
4 15 ms 15 ms 15 ms core4-montreal02_POS9-0.net.bell.ca [64.230.147.
86]
5 31 ms 31 ms 31 ms core1-newyork83_pos_4_0_0.net.bell.ca [64.230.20
7.134]
6 31 ms 31 ms 31 ms bxX5-newyork83_POS9-0-0.net.bell.ca [64.230.187.
42]
7 31 ms 31 ms 31 ms tge8-2.fr3.lga.llnw.net [208.111.134.205]
8 46 ms 46 ms 46 ms tge1-2.fr4.ord.llnw.net [69.28.171.193]
9 46 ms 46 ms 45 ms ve6.fr3.ord.llnw.net [69.28.172.41]
10 62 ms 62 ms 62 ms tge2-1.fr3.dal.llnw.net [69.28.171.197]
11 93 ms 93 ms 93 ms tge1-2.fr3.phx2.llnw.net [69.28.171.129]
12 93 ms 93 ms 93 ms tge2-1.fr4.phx2.llnw.net [69.28.171.102]
13 93 ms 93 ms 93 ms tge2-1.fr3.phx1.llnw.net [69.28.171.89]
14 109 ms 109 ms 109 ms tge1-2.fr3.lax.llnw.net [69.28.171.82]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
BTW this is LOA server.
wow ok this is all greek to
wow ok this is all greek to me
"The only friends that matter are the ones you can call at 4am."
www.crystaljeanelf.blogspot.com