Massive Lag Issue?

[TaNgAnDtOnIc]

I seem to be the only one experiencing this, but every Dota game hosted by your Bots I experience a tremendous amount of lag to the point that it's unplayable.

Cash and BGN games work fine so I'm not quite sure whats wrong. When I !checkme it's always well over 200ms

[Nz.Death]

I was in that game with you, After you were afk for the first 3 minutes of the game.
Then you feed , wasnt intentional but you were that under leveled because of been afk, The tryed to votekick yourself.

But after you died again you rage quit, Ruined our game. Thanks

[TaNgAnDtOnIc]

I do apologize for being AFK for the first 2:30 minutes, I was on the phone with my father because he'd just gotten into a car accident.

I'm not worried about my ban because I deserve it, but every ENT game I play still has a crazy amount of lag, even previous to that one. It's probably been like that for at least 2 weeks now, but that game was exceptional bad. I was just wondering if there was a way to resolve it.

[Nz.Death]

viewtopic.php?f=10&t=4156

Have a read over this, The servers have moved to atlanta. But i see your in the states anyway's.
Im playing from New Zealand and i dont have any lag issue's. I have a high ping and delay but no lag

[gkgough]

Nz.Death. Why are you accusing this person of lying, when you have been documented as responding to multiple posts referencing the same issue. I started one, and there is another one with a reference to ENT connect in the name. I think it is highly unprofessional of you to accuse him of lying especially when he is referencing the exact same problem as myself and several others.

Is there any sort of staff or administration at ENT who can give any insight to the progress of this problem? I actively donate to things I enjoy, and frankly this issue is going to keep me from ever donating to ENT. The lag ruins games, and if it wasn't for the game stacking frustration experienced on DC, I would literally never try to play ENT again.

Please provide any resolution or steps taken to identify the cause of the problem.

Thank you,

[uakf.b]

We already answered this many times. There's no "problem" that can be solved. Our servers are located in Atlanta. If you have a bad connection to that location, then you'll have higher ping and lag/delay during games.

One possibility is having two servers, one for people closer to Atlanta and one for people closer to some other location, but that's not something we're planning at the moment.

Moving servers to New York or Chicago would mean higher pings for our European and South American players.

[gkgough]

Well, thank you for the answer, I have been trying to get an answer for some time now. I guess ENT is just not in the cards for me anymore. Did you guys move the servers sometime near the end of December 2012?

[uakf.b]

Some of the bots were still in Dallas, Texas before December. But the service there was deteriorating.

[gkgough]

Well, that doesn't make any sense.. I am located in upstate NY, so moving a server from Dallas to ATL would be closer to me, not further away. I'm by no means a internet/networking expert but it seems like the physical location is a strange explanation based on this. The problem never occurred in several years of playing Dota on ENT until 12/26/2012..and has persisted ever since then.
Thank you for the responses.

[gkgough]

One more question. Since it is just some strange combination of my location and your servers moving, what can I do to fix that problem. Be creative...and remember there was never a problem before Christmas 2012. I have lots of resources I can put to work, just don't know what is worth it and what's not. That auto balance thing is really hard to resist, but i just get owned over and over because of the massive lagging problems

[uakf.b]

You can try these in Command Prompt and post output here or PM me:

ping s5.clanent.net
tracert s5.clanent.net

ping s10.clanent.net
tracert s10.clanent.net

ping eihl.clanent.net
tracert eihl.clanent.net

[gkgough]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\G>ping s5.clanent.net

Pinging s5.clanent.net [192.30.34.50] with 32 bytes of data:
Reply from 192.30.34.50: bytes=32 time=263ms TTL=55
Reply from 192.30.34.50: bytes=32 time=152ms TTL=55
Reply from 192.30.34.50: bytes=32 time=152ms TTL=55
Reply from 192.30.34.50: bytes=32 time=157ms TTL=55

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

C:\Users\G>tracert s5.clanent.net

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

1 1 ms 2 ms 2 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 5 ms 6 ms L100.BFLONY-VFTTP-10.verizon-gni.net [72.88.91.1
]
3 10 ms 5 ms 5 ms G0-0-4-7.BFLONY-LCR-22.verizon-gni.net [130.81.2
16.86]
4 39 ms 18 ms 18 ms xe-2-1-3-0.NY325-BB-RTR2.verizon-gni.net [130.81
.209.10]
5 * 51 ms 49 ms 0.so-4-0-1.XT2.NYC4.ALTER.NET [152.63.10.29]
6 21 ms 67 ms 74 ms TenGigE0-5-0-0.GW8.NYC4.ALTER.NET [152.63.21.65]

7 123 ms 127 ms 121 ms tinet-gw.customer.alter.net [152.179.72.122]
8 147 ms 148 ms 146 ms xe-7-0-0.atl11.ip4.tinet.net [141.136.108.138]
9 150 ms 161 ms 163 ms ramnode-gw.ip4.tinet.net [77.67.78.254]
10 159 ms 156 ms 161 ms 192.30.33.8
11 157 ms 152 ms 147 ms 192.30.34.50

Trace complete.

[gkgough]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\G>ping s10.clanent.net

Pinging s10.clanent.net [198.23.154.229] with 32 bytes of data:
Reply from 198.23.154.229: bytes=32 time=45ms TTL=50
Reply from 198.23.154.229: bytes=32 time=49ms TTL=50
Reply from 198.23.154.229: bytes=32 time=51ms TTL=50
Reply from 198.23.154.229: bytes=32 time=60ms TTL=50

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

C:\Users\G>tracert s10.clanent.net

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

1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 32 ms 5 ms L100.BFLONY-VFTTP-10.verizon-gni.net [72.88.91.1
]
3 5 ms 6 ms 6 ms G0-0-4-7.BFLONY-LCR-21.verizon-gni.net [130.81.2
16.84]
4 77 ms 16 ms 53 ms xe-4-1-6-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
209.8]
5 21 ms 19 ms 17 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.8
1.17.6]
6 19 ms 19 ms 36 ms xe-4-1-3-0.NY325-BB-RTR2.verizon-gni.net [130.81
.17.83]
7 18 ms 19 ms 18 ms 0.ae2.BR2.NYC4.ALTER.NET [152.63.1.205]
8 19 ms 18 ms 18 ms 204.255.168.190
9 62 ms 48 ms 69 ms xe-1-2-0.cr1.ord6.us.scnet.net [204.93.144.25]
10 58 ms 45 ms 53 ms ae3.ar5.ord6.us.scnet.net [204.93.204.47]
11 44 ms 46 ms 47 ms as36352.xe-2-0-2.ar5.ord6.us.scnet.net [50.31.15
1.170]
12 49 ms 50 ms 48 ms 10ge-1-3-2.fz146.cr2.chi.colocrossing.com [206.2
17.137.254]
13 53 ms 53 ms 57 ms ae1015-fu174.chi.colocrossing.com [206.217.131.1
42]
14 51 ms 51 ms 54 ms chinode1.ugvps.com [198.144.186.66]
15 47 ms 47 ms 46 ms host.colocrossing.com [198.23.154.229]

Trace complete.

C:\Users\G>

[gkgough]

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\G>ping eihl.clanent.net

Pinging eihl.clanent.net [18.181.6.185] with 32 bytes of data:
Reply from 18.181.6.185: bytes=32 time=40ms TTL=49
Reply from 18.181.6.185: bytes=32 time=38ms TTL=49
Reply from 18.181.6.185: bytes=32 time=42ms TTL=49
Reply from 18.181.6.185: bytes=32 time=38ms TTL=49

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

C:\Users\G>tracert eihl.clanent.net

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

1 <1 ms 2 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 15 ms 7 ms 5 ms L100.BFLONY-VFTTP-10.verizon-gni.net [72.88.91.1
]
3 5 ms 5 ms 5 ms G0-0-4-7.BFLONY-LCR-21.verizon-gni.net [130.81.2
16.84]
4 20 ms 18 ms 19 ms xe-1-1-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
209.34]
5 35 ms 34 ms 49 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.8
1.17.6]
6 22 ms 24 ms 38 ms xe-4-1-3-0.NY325-BB-RTR2.verizon-gni.net [130.81
.17.83]
7 33 ms 21 ms 47 ms 0.xe-9-1-0.BR1.NYC1.ALTER.NET [152.63.4.241]
8 * * * Request timed out.
9 38 ms 38 ms 36 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
10 34 ms 36 ms 36 ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
11 * * * Request timed out.
12 35 ms 40 ms 38 ms ae-0-11.bar1.Boston1.Level3.net [4.69.140.89]
13 165 ms 137 ms 223 ms ae-7-7.car1.Boston1.Level3.net [4.69.132.241]
14 27 ms 27 ms 47 ms MASSACHUSET.car1.Boston1.Level3.net [4.53.48.98]

15 39 ms 38 ms 50 ms DMZ-RTR-1-EXTERNAL-RTR-1.MIT.EDU [18.192.9.1]
16 45 ms 39 ms 40 ms BACKBONE-RTR-1-DMZ-RTR-1.MIT.EDU [18.168.5.1]
17 39 ms 39 ms 40 ms W92-RTR-1-BACKBONE-2.MIT.EDU [18.168.1.25]
18 40 ms 39 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]

Trace complete.

C:\Users\G>

[gkgough]

There are the outputs, it looks like the s5 is the problem, based on the 3x - 4x ms pings. On dotacash my ping is usually 30-40 ms.

Thanks let me know if you need anything else!