5 replies to this topic

[kareneiko]

So the screenshots below explains my problem, and is anyone experiencing the same thing? I've been suffering from RO lag since summer started, and I thought at first it was the whole "everyone is home from school, let's all be online 24/7." But it's just with Ragnarok that I've experienced any sort of problem. I ping everything and it's fine, EXCEPT Ragnarok. And here's a YT link someone posted on another forums about the lag. I experienced something like this, but about 5 times worse. And it's been particularly laggier since Saturday's horrific WoE lag.



And PING TO WARPPORTAL WEBSITE below:

[espeon]

Ping statistics for 128.241.93.57:

    Packets: Sent = 65, Received = 65, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 81ms, Maximum = 100ms, Average = 89ms

[DrAzzy]

Use a tracert, so we can see where the problem is, instead of just being able to see that there is a problem.

[kareneiko]

I'm confused as what one single tracert would prove. The issue I have is random packet loss as you can see, when I ping the WarpPortal website. If I do a traceroute at a certain time, it might come out fine, and it WAS completely fine when I did a traceroute LAST NIGHT. But maybe the next second I do a traceroute, it might come off different and with * at certain spots, no? Because the packet loss is at different times, and the traceroute is only what it experiences at that given time. I'm not experiencing constant high ping which would result in an equal amount of delay between actions. I experience lag spikes, in which at one point it's completely lag free, and a few seconds later the game just lags for 1-3 seconds, but randomly. But please correct me if I'm wrong about the whole traceroute thing because to me I always just took it as something useful only if you're experiencing constant high ping.

At any case, here are a FEW traceroutes to iro.ragnarokonline.com in which the * are present at different spots. I'm doing this right after WoE. Keep in mind though that last night I was also experiencing bad lag but I did the traceroute and it LOOKED COMPLETELY FINE.

C:\Users\Owner>tracert iro.ragnarokonline.com

Tracing route to iro.ragnarokonline.com [128.241.92.210]
over a maximum of 30 hops:

1 5 ms 4 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 18 ms 13 ms 12 ms ge-9-1-ur01.plymouth.mn.minn.comcast.net [68.85.
166.177]
4 8 ms 7 ms 9 ms te-8-3-ur02.plymouth.mn.minn.comcast.net [68.87.
174.42]
5 10 ms 10 ms 9 ms te-2-1-ur01.anoka.mn.minn.comcast.net [68.87.174
.54]
6 8 ms 9 ms 9 ms te-8-3-ur02.anoka.mn.minn.comcast.net [68.87.174
.58]
7 9 ms 9 ms 9 ms s-4-1-0-ur01.roseville.mn.minn.comcast.net [68.8
7.174.241]
8 29 ms 40 ms 22 ms te-0-4-0-6-cr01.chicago.il.ibone.comcast.net [68
.86.91.5]
9 27 ms 20 ms 28 ms pos-0-2-0-0-pe01.350ecermak.il.ibone.comcast.net
[68.86.86.78]
10 21 ms 33 ms 20 ms Vlan565.icore1.CT8-Chicago.as6453.net [206.82.14
1.137]
11 20 ms 19 ms 25 ms ix-3-0.icore1.CT8-Chicago.as6453.net [206.82.141
.130]
12 25 ms 20 ms 20 ms ae-3.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.7
2]
13 51 ms 53 ms 60 ms ae-4.r21.dllstx09.us.bb.gin.ntt.net [129.250.2.2
00]
14 65 ms 49 ms 57 ms ae-0.r20.dllstx09.us.bb.gin.ntt.net [129.250.2.5
8]
15 * 97 ms 88 ms ae-5.r20.lsanca03.us.bb.gin.ntt.net [129.250.2.1
68]
16 228 ms 95 ms 96 ms po-1.r00.lsanca19.us.bb.gin.ntt.net [129.250.6.3
8]
17 89 ms * 93 ms xe-6-4.r00.lsanca19.us.ce.gin.ntt.net [204.1.253
.102]
18 92 ms 90 ms 87 ms la-annex.demarcation.gravityus.com [204.2.170.62
]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.


--

C:\Users\Owner>tracert iro.ragnarokonline.com

Tracing route to iro.ragnarokonline.com [128.241.92.210]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 10 ms 10 ms ge-9-1-ur01.plymouth.mn.minn.comcast.net [68.85.
166.177]
4 7 ms 9 ms 10 ms te-8-3-ur02.plymouth.mn.minn.comcast.net [68.87.
174.42]
5 10 ms 11 ms 11 ms te-2-1-ur01.anoka.mn.minn.comcast.net [68.87.174
.54]
6 10 ms 9 ms 8 ms te-8-3-ur02.anoka.mn.minn.comcast.net [68.87.174
.58]
7 10 ms 11 ms 11 ms s-4-1-0-ur01.roseville.mn.minn.comcast.net [68.8
7.174.241]
8 20 ms 18 ms 36 ms te-0-4-0-6-cr01.chicago.il.ibone.comcast.net [68
.86.91.5]
9 19 ms * 21 ms pos-0-2-0-0-pe01.350ecermak.il.ibone.comcast.net
[68.86.86.78]
10 29 ms 21 ms * Vlan565.icore1.CT8-Chicago.as6453.net [206.82.14
1.137]
11 21 ms 27 ms 19 ms ix-3-0.icore1.CT8-Chicago.as6453.net [206.82.141
.130]
12 20 ms 20 ms 20 ms ae-3.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.7
2]
13 57 ms 57 ms 59 ms ae-4.r21.dllstx09.us.bb.gin.ntt.net [129.250.2.2
00]
14 54 ms 56 ms 56 ms ae-0.r20.dllstx09.us.bb.gin.ntt.net [129.250.2.5
8]
15 114 ms 113 ms 92 ms ae-5.r20.lsanca03.us.bb.gin.ntt.net [129.250.2.1
68]
16 84 ms 86 ms 85 ms po-1.r00.lsanca19.us.bb.gin.ntt.net [129.250.6.3
8]
17 * * 86 ms xe-6-4.r00.lsanca19.us.ce.gin.ntt.net [204.1.253
.102]
18 94 ms * 90 ms la-annex.demarcation.gravityus.com [204.2.170.62
]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.

[Br4nd0n]

Yeah, a tracert wont normally help much with this kind of problem. Since the packet losses are random and each router needs it's own packet sent there is no concrete way to know where it's dropping.

You can do a statistical method though. If you do lot's of tracert's, and find that they sometimes drop at a certian point (not all the time), then that might indicate where the packets are being lost.

Anyways, comcast is known not to work well with Gravity. Not much you can do.

EDIT: Never mind about the statisitical method. If the packet is being sent to a later router, and it drops at an earlier router, then it will report that the problem is with the later. It wont work.

Edited by Br4nd0n, 08 September 2010 - 05:00 PM.

[DrAzzy]

Packet loss is starting at comcast, judging by the second one. Run it a few more times to confirm. If you confirm that, i think your only choice is to complain to comcast about their bad router.

That's strange though - as6453 has been TERRIBLE this summer, and frequently drops packets, but i've yet to see someone on comcast with packet loss starting before that