Massive Lag Issue?

[uakf.b]

Hm, seems like you're getting really bad routing at tinet-gw.customer.alter.net. Based on google search, it seems like other people are having the same problem as you.

http://forums.verizon.com/t5/FiOS-Inter ... d-p/525091
http://www.dslreports.com/forum/r279376 ... ing-issues

Edit1: Wow, according to the first link, Verizon FIOS is actually working on fixing this.
Edit2: read a bit more, maybe not. If you post your issue in the first link and also call them, then maybe if other people do it too then they'll fix it. The problem seems to be with one of their routing nodes.
Edit3: I'm going to try and get ENT Connect to support tunneling through our Boston server (eihl.clanent.net) as an option. Thanks for doing the traceroute, they are being very helpful.

[gkgough]

I really appreciate your help.. I've learned a lot about the process at least! If it doesn't fix itself, I think I will drop Fios, because i was wise enough to ask the question and found out that to get Fios without a 2 year contract all you have to do is pay an extra five dollars a month hah!

If you need anything else from me to help getting it routed through Boston, let me know and Ill do it!

[uakf.b]

I really appreciate your help.. I've learned a lot about the process at least! If it doesn't fix itself, I think I will drop Fios, because i was wise enough to ask the question and found out that to get Fios without a 2 year contract all you have to do is pay an extra five dollars a month hah!

If you need anything else from me to help getting it routed through Boston, let me know and Ill do it!

Try ENT Connect now. Go to ENT Connect tab and then click "click to enable" proxy settings button, and then join the games through LAN and see if your ping is lower.

[gkgough]

ENT Connect seems to have worked. Great job diagnosing and resolving my problems!!! Its funny, my ping is in the 90's on connect (30's in Bnet when not on ENT), but the non stop lagging seems to have gone away..I don't understand it but I don't care as long as it is fixed!

Thanks!

[uakf.b]

Ping is higher because you have to go to the eihl.clanent.net server before going to the Atlanta server. But for you it seems like that is still faster than going through Verizon's node.

[Grimlorn]

Code: Select all

Tracing route to s5.clanent.net [192.30.34.50]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  WL.domain.com [192.168.2.1]
  2     8 ms     7 ms     7 ms  10.49.240.1
  3     7 ms     7 ms     8 ms  ten0-1-0-7.orld01-ser2.bhn.net [72.31.194.62]
  4    15 ms    11 ms    12 ms  ten0-15-0-9.orld71-car2.bhn.net [71.44.60.186]
  5    15 ms    15 ms    16 ms  hun0-7-0-0.orld71-cbr3.bhn.net [72.31.193.24]
  6    63 ms    64 ms    61 ms  te9-0-0d0.cir1.miami2-fl.us.xo.net [216.156.104.
49]
  7    73 ms    62 ms    68 ms  216.156.15.5.ptr.us.xo.net [216.156.15.5]
  8    84 ms    82 ms    82 ms  206.111.1.222.ptr.us.xo.net [206.111.1.222]
  9   125 ms   140 ms   125 ms  xe-3-0-0.atl11.ip4.tinet.net [89.149.180.202]
 10    42 ms    48 ms    52 ms  ramnode-gw.ip4.tinet.net [77.67.78.254]
 11    87 ms    88 ms    91 ms  192.30.33.8
 12    90 ms    92 ms    93 ms  192.30.34.50

Code: Select all

Pinging s5.clanent.net [192.30.34.50] with 32 bytes of data:
Reply from 192.30.34.50: bytes=32 time=93ms TTL=51
Reply from 192.30.34.50: bytes=32 time=102ms TTL=51
Reply from 192.30.34.50: bytes=32 time=100ms TTL=51
Reply from 192.30.34.50: bytes=32 time=97ms TTL=51

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


Code: Select all

Tracing route to s10.clanent.net [198.23.154.229]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  WL.domain.com [192.168.2.1]
  2    12 ms     7 ms     7 ms  10.49.240.1
  3     7 ms     7 ms     8 ms  ten0-1-0-7.orld01-ser2.bhn.net [72.31.194.62]
  4     9 ms    11 ms    11 ms  ten0-15-0-9.orld71-car2.bhn.net [71.44.60.186]
  5    15 ms    14 ms    15 ms  hun0-7-0-0.orld71-cbr3.bhn.net [72.31.193.24]
  6    17 ms    17 ms    17 ms  ae-4-11.cr1.atl20.tbone.rr.com [66.109.10.14]
  7    20 ms    25 ms    22 ms  107.14.19.36
  8    46 ms    19 ms    17 ms  ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
  9    20 ms    22 ms    22 ms  66.109.10.62
 10    19 ms    18 ms    27 ms  ae0-50g.cr1.atl1.us.nlayer.net [69.31.135.129]
 11    31 ms    34 ms    34 ms  xe-0-1-0.cr2.iad1.us.nlayer.net [69.22.142.106]

 12    35 ms    35 ms    32 ms  ae1-30g.cr1.iad1.us.nlayer.net [69.31.31.153]
 13    59 ms    62 ms    60 ms  xe-2-0-1.cr2.ord1.us.nlayer.net [69.22.142.32]
 14    56 ms    56 ms    55 ms  as23352.ae6-102.cr2.ord1.us.nlayer.net [69.31.11
1.3]
 15    56 ms    55 ms    59 ms  ae12.cr2.ord6.us.scnet.net [204.93.204.83]
 16    58 ms    62 ms    61 ms  ae4.ar6.ord6.us.scnet.net [204.93.204.67]
 17    57 ms    58 ms    57 ms  as36352.xe-2-0-2.ar6.ord6.us.scnet.net [50.31.15
4.182]
 18    66 ms    58 ms    60 ms  10ge-1-3-1.fz146.cr1.chi.colocrossing.com [206.2
17.130.114]
 19  ae1015-fu174.chi.colocrossing.com [206.217.131.142]  reports: Destination h
ost unreachable.

Code: Select all

Pinging s10.clanent.net [198.23.154.229] with 32 bytes of data:
Reply from 206.217.131.142: Destination host unreachable.
Request timed out.
Reply from 206.217.131.142: Destination host unreachable.
Request timed out.

Ping statistics for 198.23.154.229:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

Code: Select all

Tracing route to eihl.clanent.net [18.181.6.185]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  WL.domain.com [192.168.2.1]
  2     8 ms     8 ms     7 ms  10.49.240.1
  3     8 ms     8 ms     9 ms  ten0-1-0-7.orld01-ser1.bhn.net [72.31.194.64]
  4    20 ms    11 ms    11 ms  ten0-1-0-5.orld71-car1.bhn.net [71.44.60.30]
  5    11 ms    17 ms    14 ms  hun0-0-0-0.orld71-cbr3.bhn.net [72.31.193.18]
  6    12 ms     9 ms     9 ms  xe-11-3-0.bar1.Orlando1.Level3.net [4.79.116.137
]
  7     *        *        *     Request timed out.
  8    40 ms    40 ms    38 ms  ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10
6]
  9    38 ms    39 ms    38 ms  ae-1-100.ebr2.Washington12.Level3.net [4.69.143.
214]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12    40 ms    43 ms    40 ms  ae-0-11.bar1.Boston1.Level3.net [4.69.140.89]
 13   228 ms   219 ms   217 ms  ae-7-7.car1.Boston1.Level3.net [4.69.132.241]
 14    41 ms    39 ms    39 ms  MASSACHUSET.car1.Boston1.Level3.net [4.53.48.98]

 15    39 ms    41 ms    40 ms  DMZ-RTR-1-EXTERNAL-RTR-1.MIT.EDU [18.192.9.1]
 16   130 ms   190 ms    43 ms  BACKBONE-RTR-1-DMZ-RTR-1.MIT.EDU [18.168.5.1]
 17    38 ms    39 ms    39 ms  W92-RTR-1-BACKBONE-2.MIT.EDU [18.168.1.25]
 18    38 ms    38 ms    39 ms  GLOBAL-DYNAMICS.MIT.EDU [18.181.0.99]
 19    39 ms    39 ms    40 ms  XVM-SIX-185.MIT.EDU [18.181.6.185]

Code: Select all

Pinging eihl.clanent.net [18.181.6.185] with 32 bytes of data:
Reply from 18.181.6.185: bytes=32 time=43ms TTL=46
Reply from 18.181.6.185: bytes=32 time=39ms TTL=46
Reply from 18.181.6.185: bytes=32 time=39ms TTL=46
Reply from 18.181.6.185: bytes=32 time=40ms TTL=46

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


So pinged and tracerted all 3 and this is what I came up with. Seems like the spikes come from Atlanta and Boston where the bots are located. Not sure if it's fixable or not.

[uakf.b]

s10.clanent.net no longer exists, it has been replaced by s12.clanent.net or s11.clanent.net (don't remember which).

You don't seem to have any problem with connecting to the Boston server, so maybe try ENT connect with the eihl.clanent.net proxy enabled.

[Grimlorn]

Wouldn't the 200ms spikes on the tracert for eihl mean there would also be lag there? There was also timeout on the hops right? That's what those stars mean right?

How do I change what servers I connect to?

[uakf.b]

You connect to whatever server the bots are hosted on (almost all in Atlanta). The proxy server for ENT Connect only supports eihl.clanent.net.

[Grimlorn]

Posted this in another thread earlier today about the lag in games.

I'll play a few games that are mostly lag free, but it seems like the longer you play the more laggy it gets. It's fine on dotacash. I'm in Florida btw. So Atlanta isn't far away. What's also funny, is when I ping, I get between 20-60 ms, but when playing it looks awful with a lot of spikes happening constantly. I'm assuming the longer the bot works without being reset (or whatever you guys do) the worse everyone's games get with lag. I've tried different game modes (bots), to see if that helped but it didn't. Lag just got worse. I have cable internet too.

Just tried a game with ENT Connect and same lag, but this time showed up in !checkme, 150-250 ms. Just did a speed test in Atlanta and connection speed looks same as always does.

Maybe it's an internet connection issue, but maybe it's near where the servers bots are located? Maybe the more games the bots host the bigger the strain on the hosts that cause lag spikes? Or maybe Internet traffic is high at certain times causing lag spikes in games? I don't know, but there are too many complaints in games, and it's noticeable when people are just autoattacking creeps while you're killing them or doing other stupid stuff, dying then complaining about lag. I've played with ENT clan members who also complained about the lag in games when I was also lagging. And like I mention in the quote, it usually gets progressively worse the longer you play.

[uakf.b]

The servers themselves don't have issues, for example I always have a good and stable connection from northeast or Texas. Something in your connection route has a problem that is unrelated to where the servers are actually hosted. 89.149.180.202... seems to be in Ireland for example o_O

[Grimlorn]

You sure it's Ireland? I assumed because atl was in the name it was Atlanta. If that's the case then what can I do? If I call up my ISP and tell them my connection is routing through Ireland to get to Atlanta, can they fix it if I tell them to? How does this explain the progressive lagging as I play more and more games though?

I just did a tracert on s11.clanent.net and it seemed to have no lag. If you guys are using that one to host games, can you tell me which games that bot/server is hosting so I can join and try them out?

If I'm lagging due to my connection can that affect others and make them spike in game because they are playing catchup with my delayed commands?

[uakf.b]

I'm not sure, but according to both geoiptool and geomaplookup, the server is located in Ireland for some reason.

GHost implements asyncronous lag so your delay shouldn't cause problems for other players (except in the form of the lag screen, when that comes up).

s11 is hosting ENT83 to ENT86, you can get the games from viewtopic.php?f=5&t=501

[Strikest]

I've had a problem with massive spiking, but it only occasionally. This is not just me, but many people have complained of spiking. This has been recent, I've never had lag issues like this before... What leads me to believe that it is fixable is that the spiking does not occur all the time, just sometimes.

[DAbot]

Yes, i also noticed lagg and delaying and spikes for like an 3,5 yard a nano-sec
Game uneven when lagging cause people to DC'D in most played games when I progress in just undefined.