Lag Spikes, howto track the problem.

[Devile]

Same here. Its K2 who has to fix it, not me. I can't do anything since its a problem with their ISP.

[Goathorns]

I dont get dc, but i get 2-3 second delay on everything, did a trace and i get

6 694 ms 711 ms 723 ms 213.140.50.201
7 710 ms * 724 ms 213.140.38.166
8 * * 712 ms 213.140.36.89
9 731 ms * 748 ms 213.140.36.37

and so on, but it gets worse, some of those numbers reach 1000 ms or more, can someone explain to me why does this happen?

[justicetoall]

208.50.86.50 is problematic
and bet K2 testing something with xtrap w/o announces or else that we have no idea as if there any Gms in this game?

[hej]

This one is not nice:
ping -t 63.208.234.134

Skickar signaler till 63.208.234.134 med 32 byte data:

Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.
Begäran gjorde timeout.

Ping-statistik för 63.208.234.134:
Paket: Skickade = 17, mottagna = 0, Förlorade = 17 (100 %)

[OsirisG]

I use WinMTR to trace/ping , hope it is not a problem :

[Z3non]

Microsoft Windows XP [Versão 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

Cocuments and SettingsGerson>tracert -d 207.38.26.1

1 19 ms 8 ms 12 ms 10.27.63.254
2 9 ms 7 ms 10 ms 212.113.162.62
3 12 ms 13 ms 32 ms 212.113.160.210
4 10 ms 20 ms 8 ms 212.113.160.197
5 13 ms 10 ms 31 ms 212.113.176.65
6 9 ms 11 ms 7 ms 195.8.10.41
7 11 ms 8 ms 12 ms 195.8.0.213
8 64 ms 56 ms 67 ms 195.8.0.222
9 63 ms 67 ms 49 ms 213.206.159.169
10 44 ms * 45 ms 213.206.128.104
11 115 ms 113 ms 143 ms 144.232.9.163
12 146 ms 154 ms 113 ms 144.232.7.106
13 138 ms 141 ms 138 ms 144.232.20.102
14 149 ms 149 ms 155 ms 144.232.26.90
15 200 ms 172 ms 173 ms 144.232.20.108
16 202 ms 183 ms 180 ms 144.232.20.4
17 191 ms 186 ms 186 ms 144.232.20.64
18 187 ms 181 ms 186 ms 144.232.8.94
19 217 ms 230 ms 214 ms 144.232.154.206
20 195 ms 201 ms 209 ms 216.52.255.115
21 195 ms 207 ms 199 ms 216.52.253.234
22 217 ms 236 ms 215 ms 207.38.26.1

Numbers 1 and 7 never got any response, packets always timed out, the others just had request timed out a little few times, if they are important too ill post them.

[Mage_of_DestinY]

Since im not even able 2 login the website here's my tracing:

Bezig met het traceren van de route naar 207.38.26.1 via maximaal 30 hops

1 95 ms 99 ms 99 ms 192.168.1.254
2 12 ms 14 ms 14 ms 195.190.249.54
3 17 ms 15 ms 16 ms 213.75.1.169
4 16 ms 15 ms 15 ms 213.75.1.146
5 * * * Time-out bij opdracht.
6 28 ms 23 ms 23 ms 134.222.231.134
7 23 ms 23 ms 22 ms 134.222.231.142
8 23 ms 22 ms 22 ms 134.222.231.214
9 113 ms 113 ms 116 ms 89.167.141.65
10 183 ms 182 ms 182 ms 68.1.0.189
11 181 ms 183 ms 182 ms 68.4.14.214
12 182 ms 183 ms 183 ms 68.4.13.246
13 182 ms 182 ms 185 ms 64.58.132.102
14 185 ms 183 ms 183 ms 64.58.132.113
15 182 ms 181 ms 180 ms 64.58.132.238
16 * * * Time-out bij opdracht.
17 * * * Time-out bij opdracht.
18 * * * Time-out bij opdracht.
19

Can some1 help me 2 get back into the game/website cannot load anything........

[dark_item]

how can we tell it to k2??

i got this

second time i got this


so shen i am right the number 213.224.253.110 is the thing by me

[Silent Nemesis]

[Adi]

where im need to report my problem ?

this the ip was do me the lag spike : 64.215.28.150

[Trawma_35]

hey i need some help
the ips that got with Request timed out that:
207.38.31.234
70.42.117.90
its dont write something like that "Reply from 207.38.26.1: bytes=32 time=229ms TTL=242" just write Request timed out that ...
so what my problem someone can help me pls and tell me what to do ?

[evilstevil]

you can explain this in english too? :lol:

damnnn u computernerds :lol:

[Gollum]

Tracing route to 207.38.26.1 over a maximum of 60 hops

1 21 ms 16 ms 18 ms 189.102.160.1
2 * 21 ms 18 ms 201.6.0.4
3 * * * Request timed out.
4 219 ms 211 ms 217 ms 67.17.195.30
5 214 ms 210 ms 212 ms 68.1.2.107
6 220 ms 218 ms 219 ms 68.4.13.70
7 219 ms 209 ms 218 ms 68.4.13.190
8 204 ms 218 ms 219 ms 64.58.152.166
9 188 ms 190 ms 189 ms 216.231.24.170
10 195 ms 192 ms 187 ms 216.23.160.209
11 203 ms 217 ms 211 ms 207.38.31.234
12 188 ms 184 ms 198 ms 207.38.31.233
13 219 ms 219 ms 219 ms 207.38.31.234
14 189 ms 198 ms 199 ms 207.38.31.233
15 220 ms 210 ms 209 ms 207.38.31.234
16 186 ms 197 ms 190 ms 207.38.31.233
17 213 ms 211 ms 216 ms 207.38.31.234
18 215 ms 191 ms 199 ms 207.38.31.233
19 209 ms 217 ms 219 ms 207.38.31.234
20 182 ms 199 ms 190 ms 207.38.31.233
21 213 ms 209 ms 216 ms 207.38.31.234
22 185 ms 197 ms 190 ms 207.38.31.233
23 214 ms 217 ms 210 ms 207.38.31.234
24 186 ms 198 ms 189 ms 207.38.31.233
25 205 ms 208 ms 218 ms 207.38.31.234
26 186 ms 200 ms 185 ms 207.38.31.233
27 215 ms 211 ms 209 ms 207.38.31.234
28 185 ms 199 ms 210 ms 207.38.31.233
29 217 ms 210 ms 209 ms 207.38.31.234
30 189 ms 197 ms 190 ms 207.38.31.233
31 219 ms 209 ms 209 ms 207.38.31.234
32 195 ms 192 ms 189 ms 207.38.31.233
33 205 ms 219 ms 209 ms 207.38.31.234
34 195 ms 192 ms 197 ms 207.38.31.233
35 209 ms 217 ms 212 ms 207.38.31.234
36 353 ms 208 ms 330 ms 207.38.31.233
37 233 ms 208 ms 209 ms 207.38.31.234
38 189 ms 338 ms 228 ms 207.38.31.233
39 218 ms 219 ms 212 ms 207.38.31.234
40 183 ms 200 ms 190 ms 207.38.31.233
41 222 ms 210 ms 216 ms 207.38.31.234
42 195 ms 199 ms 190 ms 207.38.31.233
43 216 ms 219 ms 209 ms 207.38.31.234
44 192 ms 190 ms 197 ms 207.38.31.233
45 205 ms 217 ms 211 ms 207.38.31.234
46 193 ms 191 ms 199 ms 207.38.31.233
47 207 ms 217 ms 219 ms 207.38.31.234
48 192 ms 197 ms 198 ms 207.38.31.233
49 201 ms 219 ms 219 ms 207.38.31.234
50 186 ms 199 ms 189 ms 207.38.31.233
51 207 ms 216 ms 229 ms 207.38.31.234
52 190 ms 197 ms 191 ms 207.38.31.233
53 219 ms 219 ms 210 ms 207.38.31.234
54 196 ms 197 ms 199 ms 207.38.31.233
55 220 ms 219 ms 219 ms 207.38.31.234
56 190 ms 198 ms 189 ms 207.38.31.233
57 213 ms 207 ms 211 ms 207.38.31.234
58 185 ms 195 ms 199 ms 207.38.31.233
59 213 ms 220 ms 212 ms 207.38.31.234
60 198 ms 189 ms 200 ms 207.38.31.233

Trace complete.

C:\Users\Administrator>

now this is weird ............from 11 - 60th hop i get the same craps o.O

[Chuck Norris]

Tracing route to 207.38.26.1 over a maximum of 60 hops

1 21 ms 16 ms 18 ms 189.102.160.1
2 * 21 ms 18 ms 201.6.0.4
3 * * * Request timed out.
4 219 ms 211 ms 217 ms 67.17.195.30
5 214 ms 210 ms 212 ms 68.1.2.107
6 220 ms 218 ms 219 ms 68.4.13.70
7 219 ms 209 ms 218 ms 68.4.13.190
8 204 ms 218 ms 219 ms 64.58.152.166
9 188 ms 190 ms 189 ms 216.231.24.170
10 195 ms 192 ms 187 ms 216.23.160.209
11 203 ms 217 ms 211 ms 207.38.31.234
12 188 ms 184 ms 198 ms 207.38.31.233
13 219 ms 219 ms 219 ms 207.38.31.234
14 189 ms 198 ms 199 ms 207.38.31.233
15 220 ms 210 ms 209 ms 207.38.31.234
16 186 ms 197 ms 190 ms 207.38.31.233
17 213 ms 211 ms 216 ms 207.38.31.234
18 215 ms 191 ms 199 ms 207.38.31.233
19 209 ms 217 ms 219 ms 207.38.31.234

Trace complete.

C:\Users\Administrator>

now this is weird ............from 11 - 60th hop i get the same craps o.O[/b]

Well besides bumping a 2 year old topic, the reason for this is that a router somewhere has gone down and the routers on the way have not yet corrected the routing tables (or there is no alternative route).

Here's the non-code explanation...
207.38.31.234 says "I can get to the target in N hops by sending data to 207.38.31.233" so it sends it.
207.38.31.234 says "I can get to the target in (N-1) hops by sending data to xxx.xxx.xxx.xxx" (the downed router) so it tries to send and fails.
It re-checks its tables and says "I can't get to xxx.xxx.xxx.xxx in (N-1) hops, but I know that 207.38.31.234 can get there in N hops. Therefore I shall send the data to 207.38.31.234" This is the "next best route" method when one route fails.

207.38.31.234 is a bit thick, and says "I can get to the target in N hops by sending data to 207.38.31.233" so it sends it. N.B. This is the same as line 1. 207.38.31.234 needs to update it's routing table to remove the "via 207.38.31.233" route. Unfortunately these tables only get updated every however many minutes. This is to allow time for a router to be rebooted or hardware replaced.

After that routing table is updated, this "broken route" propagates backwards towards your own PC until a router somewhere offers a different path to the target IP.

For a better description of what's going on try: http://en.wikipedia.org/wiki/Routing...ation_Protocol