Dear Heiml.
Your Question :
Hello.
I`m expirencing lag peaks while playing iRO. The packetloss only occurs between 2 Cogentco`s routers (p4-0.core01.dus01.atlas.cogentco.com -> p13-0.core01.ams03.atlas.cogentco.com). I have included traceroute report and 2 ping reports with 100 packets to mentioned hosts (if it was my ISP that was losing packets, the packets wouldn`t have 0% packetloss to the first mentioned router).
Traceroute report:
Tracing route to iro.ragnarokonline.com [38.144.194.3]
over a maximum of 30 hops:
1 6 ms 1 ms 1 ms rei.serv.home [192.168.0.1]
2 27 ms 23 ms 23 ms oulu-erx.hel.elisa-laajakaista.fi [88.113.144.1]
3 27 ms 23 ms 22 ms 172.29.249.25
4 30 ms 28 ms 29 ms 10-1-10.seisei1.fi.elisa.net [139.97.8.73]
5 29 ms 29 ms 29 ms 1-2-1.seisei1.fi.elisa.net [139.97.8.110]
6 37 ms 31 ms 31 ms 2-1-3.tamnal2.fi.elisa.net [139.97.8.106]
7 35 ms 31 ms 31 ms 1-2-1.tamnal2.fi.elisa.net [139.97.8.42]
8 * 35 ms 33 ms 2-1-2.helpa1.fi.elisa.net [139.97.8.46]
9 33 ms 38 ms 33 ms 1-3.ficix2.fi.elisa.net [139.97.8.14]
10 33 ms 33 ms 33 ms ip-rr.ficix1-tli.fi.elisa.net [139.97.2.21]
11 38 ms 33 ms * ge0-0-0-1.bbr1.hel2.fi.eunetip.net [213.192.191.
65]
12 43 ms 35 ms 36 ms ge1-1-0-1.bbr1.esp1.fi.eunetip.net [213.192.191.
45]
13 * 40 ms 39 ms so1-1-0-0.bbr1.sto1.se.eunetip.net [213.192.191.
210]
14 41 ms 41 ms 39 ms netnod-ix-ge-b-sth-1500.cogent.com [194.68.128.1
55]
15 55 ms 53 ms 53 ms p15-2.core01.ham01.atlas.cogentco.com [130.117.0
.129]
16 82 ms 75 ms 75 ms p4-0.core01.dus01.atlas.cogentco.com [130.117.1.
177]
17 76 ms 75 ms * p13-0.core01.ams03.atlas.cogentco.com [130.117.1
.125]
18 150 ms 148 ms 149 ms p9-0.core02.jfk02.atlas.cogentco.com [130.117.1.
170]
19 146 ms 147 ms 147 ms p15-0.core01.jfk02.atlas.cogentco.com [66.28.4.1
3]
20 168 ms 165 ms 163 ms p9-0.core01.atl01.atlas.cogentco.com [154.54.5.9
8]
21 196 ms * * p10-0.core01.iah01.atlas.cogentco.com [154.54.5.
89]
22 229 ms 227 ms 227 ms p14-0.core01.san01.atlas.cogentco.com [66.28.4.6
]
23 229 ms 229 ms 229 ms p4-0.core01.lax01.atlas.cogentco.com [66.28.4.77
]
24 230 ms 231 ms 229 ms p4-0.core01.lax02.atlas.cogentco.com [154.54.5.7
0]
25 230 ms 229 ms 229 ms g5-1.hc01.lax02.atlas.cogentco.com [38.112.34.19
0]
26 234 ms 229 ms 229 ms Gravity_Interactive.demarc.cogentco.com [38.112.
30.126]
27 ^C
Ping result with 100 packets to router dus01:
Ping statistics for 130.117.1.177:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 59ms, Maximum = 67ms, Average = 62ms
Ping statistics for 130.117.1.177:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 59ms, Maximum = 67ms, Average = 62ms
Ping result to router after that (ams01):
Ping statistics for 130.117.1.125:
Packets: Sent = 100, Received = 95, Lost = 5 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 98ms, Average = 72ms
Ping statistics for 130.117.1.125:
Packets: Sent = 100, Received = 90, Lost = 10 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 81ms, Average = 69ms
Answer :
We apologize for the inconvenience but please forward this tracert to your ISP. While the ping times are low on your ISP network there are significant dropped packets that will make any outside connection even worse than it would be otherwise.
Thank you,
iRO GM Team
Gravity Interactive, Inc.