The euro day lag

[Noah]

I know there are several euros that gets a daily unplayable lag for about 4-5 hours. This has been going on for a long time now, so I think its time that we find out what we can about this.

I want everyone who gets this lag to run a trace to see where the lags comes from, and then post a screenshot of the trace screen. Most likely there will be a router that is standing out, and with enough info someone could call/mail the owners of the router to complain about this.



PS: Free Ilyaz

[Nockm]

LOL I would be amazed if they cared.

But who knows, worth a try

[soup]

Tell me where to click on, all I do is play tw and don't care about the stuff above.

[Noah]

• There's a big button with the word "trace" on it on the login screen, click it.
  
• Let the cycle go a times while you have your lag and take a screenshot.
  
• Post said screenshot

[Turban]

There you go. Today the latency of 760ms - 790ms started 7 hours earlier than usually (11AM) and will probably last the entire day until 9PM (GMT+2).

I have had high latency the past few months for several hours a day. I know several players with similar lag issues, and they have pretty much said that if this doesn't get fixed they will just simply stop playing this game. It's about time for someone to care and get this fixed.

I would prefer Trench Wars to be moved to a different server location, such as New York (SSCE Hockey/Football Zone is located there; less latency and ploss issues, would be ideal for European).

post scriptum: Extreme Games and Chaos League have the same lag problems, but Death Star Battle is just fine. Do you want us to start playing DSB instead? :fear:

[Dutch_]

I do not have this euro lag period, but i know allot of other sage ppl that do. Its not handy during league play

[Dutch_]

What are the exact times that this happens? It sounds a bit like traffic management to me.
This is what some american internet providers do during a time of the day when there is a peek in the overall internet usage (everyone is on the internet). They slow down p2p-traffic (torrents, Limewire) so it wont slow down the rest of the internet.

[paska]

zzzz




I'm really an expert with these images
But it seems to be the same router..?

[Dutch_]

Ya its the nyc1 Hopone router from New York. I use the same hopone routers u guys are except for the nyc1. And my connection is fine.

[Noah]

What are the exact times that this happens? It sounds a bit like traffic management to me.
This is what some american internet providers do during a time of the day when there is a peek in the overall internet usage (everyone is on the internet). They slow down p2p-traffic (torrents, Limewire) so it wont slow down the rest of the internet.

This can't be right, the lag comes during the day for us euros, which means that if the problem is in USA this comes during the the night there.

It's also weird how I am the only one not being routed through hopone but I still have the same problem. Maybe my ISP somehow has renamed the routers?

[Dutch_]

This can't be right, the lag comes during the day for us euros, which means that if the problem is in USA this comes during the the night there.

It's also weird how I am the only one not being routed through hopone but I still have the same problem. Maybe my ISP somehow has renamed the routers?

Ya ure right:P
O and u prolly are getting routed trough Hopone. The screenshot u posted isnt complete, but hopone should show in hop 9 or 10.

But back to my theory. Seeing as the lag starts at the first router (nyc1) it reaches in the USA, it might be a euro peek problem. If during euro internet peek times (daytime), packets try to reach America trough the same router (nyc1), it can cause lag.

Also note that the lag turns up almost instantly, like a sudden change is being made. Could it be that during euro daytime the route changes? Can someone post a trace-route from a non-laggy period

[Turban]

Actually, the latency doesn't go up "almost instantly" as you said, Dutch. It takes approximately 3 minutes for it to go up from 120ms to 790ms, though that's irrelevant nonetheless.

Usually the lag starts at 10AM EST and at around 2PM EST making several players unable to play the game due to high latency (and at times, high ploss). Mostly this is affecting finnish players that have Elisa or Saunalahti as their ISP, although there are several players in Netherlands, Norway, Sweden and UK with similar lag issues.

I will post a new tracert when the lag goes down, which will be in around 7 hours if I'm right. :fear:

[Noah]

I wonder why my trace doesn't show the full path of my connection to the server, maybe it's the lag itself that is causing this. I'll see how it looks like when I'm not lagging, and if there's any difference I'll post a new screenshot.

[Dutch_]

Actually, the latency doesn't go up "almost instantly" as you said, Dutch. It takes approximately 3 minutes for it to go up from 120ms to 790ms, though that's irrelevant nonetheless.

Usually the lag starts at 10AM EST and at around 2PM EST making several players unable to play the game due to high latency (and at times, high ploss). Mostly this is affecting finnish players that have Elisa or Saunalahti as their ISP, although there are several players in Netherlands, Norway, Sweden and UK with similar lag issues.

I will post a new tracert when the lag goes down, which will be in around 7 hours if I'm right. :fear:

Oh ok, i just heard that from others. But still, to go from 120 to 790 in 3 mins is really fast. Normally lag doesnt behave like that.
Weird that other dutch players have this lag problem since they should use the same route I am using.

[Turban]

@ Noah: Try this.

START => RUN => CMD

Type these:

tracert 66.36.241.110 > tracert.txt
ping 66.36.241.110 > ping.txt
ping 66.36.224.209 > ping2.txt (hopone, nyc1.ge11-2.core2.dca2.hopone.net)

Those will create a .txt file in your C:\Documents and Settings\Adminstrator folder. Then you will be able to just copy paste that in here; like this..

Tracing route to sls-cb9p7.dca2.superb.net [66.36.241.110] over a maximum of 30 hops:

  1     1 ms     1 ms    <1 ms  buffalo.setup [192.168.11.1] 
  2     1 ms     1 ms     1 ms  192.168.254.254 
  3    10 ms     7 ms     6 ms  heltli1.fi.elisa.net [88.112.0.1] 
  4     6 ms     6 ms     7 ms  xe3-1-0.heltli-p2.fi.elisa.net [139.97.6.221] 
  5     6 ms     6 ms     7 ms  ae11.heltli-p1.fi.elisa.net [139.97.21.90] 
  6     6 ms     6 ms     6 ms  ae1.heltli-gw1.fi.elisa.net [139.97.6.238] 
  7     6 ms     6 ms     6 ms  ae1-10.bbr2.hel1.fi.eunetip.net [213.192.191.49] 
  8   123 ms   114 ms   114 ms  so2-3-0-0.bbr1.nyc1.us.eunetip.net [213.192.191.174] 
  9     *        *      768 ms  nyc1.ge11-2.core2.dca2.hopone.net [66.36.224.209]
 10   120 ms   120 ms   120 ms  vl2.msfc1.distb2.dca2.hopone.net [66.36.224.229] 
 11   120 ms   119 ms   120 ms  sls-cb9p7.dca2.superb.net [66.36.241.110] 

Trace complete.

PING:

Pinging 66.36.241.110 with 32 bytes of data:

Reply from 66.36.241.110: bytes=32 time=119ms TTL=120
Reply from 66.36.241.110: bytes=32 time=119ms TTL=120
Reply from 66.36.241.110: bytes=32 time=119ms TTL=120
Reply from 66.36.241.110: bytes=32 time=119ms TTL=120

Ping statistics for 66.36.241.110:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 119ms, Maximum = 119ms, Average = 119ms

Now when pinging to the NYC1 router (HopOne) you will most likely get this:

Pinging 66.36.224.209 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 66.36.224.209:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

@ Dutch_: I am pretty sure not all Dutch ISP's use the same route. Let's use Finland as an example:

Finland has two ISP's that have lag issues from 10AM to 2PM EST; Elisa and Saunalahti. However, our other ISPs (such as Welho) do not have any lag as they use a different route to the server.