DA laggy?

[MickDono]

Sorry to keep bumping this, but its incredibly annoying!

One weird thing that i have noticed is that late at night, my time, the lag seems non existent, but every other time, it's unbearable! 
I'm at a loss with what to do about it.

[The Fugitive]

Wait until the wedding is over then it will most likely settle back down.

[MickDono]

I thought you were joking lol

[The Fugitive]

Are you kidding, it's THE biggest thing going on in the world right now and every woman in the world needs instant updates !! I'm willing to bet it settles down after it's over.

[Noir]

BUMP, would using the secondary route help things? Is it possible to force it?

Yesterday we were doing 5V5's in the DA and 3 of us were laggy/discoing/having delayed hit registers...

[MickDono]

This is gibberish to me, but someone might be able to tell me what's going on?

[Skuzzy]

Looks like the gateway between tinet and AT&T is taking a beating.  1/4 to 1/3 second latencies is pretty high.  Normally, when a gateway gets that crowded, packet loss is also a problem.

[MickDono]

hmmm thanks skuzzy,

i guess there's nothing i can do about it?

[Skuzzy]

I am curious.  Has it always been that bad, or is this the first time you have started looking at it?

I know the wedding, you folks recently had, spiked Internet traffic by about 1000% for a long time before the wedding.  It still may not have dropped back to what it was.

[MickDono]

Well ~2 months ago it was perfect, then all of a sudden, the lag started happening for me and a couple of other players aswell.
It is only since then that i have tried pingplot etc, so i cant compare these results to anything else.

What is also interesting is that the MA is fine, along with the other arenas.

[Skuzzy]

The traces to any other arena is going to be the same as the servers do not impact the route the data takes, unless there is some type of bad route injection happening somewhere on the Internet.

[MickDono]

I emailed a technician at tinet and here are his replies:

From looking at your traceroutes and our own traceroutes the issue seems to be towards the destination and not on the 2 hops that you are passing over in Tinet. I just doublechecked and am not really seeing any issues reaching the 206.16.60.39. Keep in mind that you are going from England(Manchester?) all the way to Texas, so an rtt of about 200-220ms is going to be normal. I believe that our peer might be having some internal issues on their own network(possibly a maintenance on their equipment etc). Please monitor this and let me know the time-frames that you are seeing the issue. Again I just checked our graphs and peer facing interface at nyc20 and I am not seeing any congestion/packetloss outgoing from Tinet to our peer, nor
incoming.

Yes I agree, both traces are identical. I assume then that the issue is on the destination. Judging by the difference in the destination IP addresses(206.16.60.39 and 206.16.60.41) it would seem that the 2 servers are likely virtually hosted on the same server blade or in the same physical location. You should write to the webmaster/host of the servers and request them to investigate.

[Skuzzy]

I would think a TTL over 200ms is a bit high coming from England to New York.  I'll have to run some calculations to see what speed that equates to.

With the routes being through the Southern part of the U.S., where over 300 tornadoes have recently devastated that are of the country, the tele comms are probably not at their best, at the moment.

[Bruv119]

192.205.37.37

this IP address appears to be the cause of today's issues.  

after some more comparisons with nuke's French route to HTC that has no lag at all right now :

Tracing route to 206.16.60.39 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  192.168.0.254
2   deleted  
  3    20 ms    20 ms    34 ms  78.254.2.254
  4    25 ms    27 ms    21 ms  fla93-1-v902.intf.nra.proxad.net [78.254.255.106]
  5    20 ms    21 ms    26 ms  p19-6k-2-po10.intf.nra.proxad.net [78.254.255.110]
6     *       24 ms    21 ms  th2-crs16-1-be1010.intf.routers.proxad.net [212.27.50.13]
  7    22 ms    28 ms    27 ms  te1-2.332.ccr01.par04.atlas.cogentco.com [149.6.164.217]
  8    30 ms    21 ms    27 ms  te0-1-0-4.ccr21.par01.atlas.cogentco.com [130.117.2.21]
  9    35 ms    40 ms    31 ms  te3-7.ccr01.lon01.atlas.cogentco.com [130.117.2.162]
 10   130 ms   128 ms   123 ms  te0-3-0-4.ccr22.bos01.atlas.cogentco.com [154.54.5.122]
 11   129 ms   128 ms   130 ms  te0-0-0-2.ccr22.ord01.atlas.cogentco.com [154.54.45.241]
 12   137 ms   142 ms   140 ms  te0-4-0-5.ccr22.mci01.atlas.cogentco.com [154.54.45.149]
 13   151 ms   146 ms   157 ms  te4-7.ccr02.dfw01.atlas.cogentco.com [154.54.25.209]
 14   150 ms   148 ms   150 ms  te3-3.ccr02.dfw03.atlas.cogentco.com [154.54.6.98]
 15   149 ms   147 ms   151 ms  192.205.36.181
 16   153 ms   151 ms   165 ms  cr1.dlstx.ip.att.net [12.122.139.110]
 17   153 ms   149 ms   151 ms  gar23.dlstx.ip.att.net [12.122.139.153]
 18   158 ms   159 ms   159 ms  12-122-254-154.attens.net [12.122.254.154]
 19   151 ms   147 ms   151 ms  63.241.193.18
 20   149 ms   148 ms   150 ms  206.16.60.39


Mine:
  2    36 ms    13 ms    56 ms  cosh-core-1a-ae1-997.network.virginmedia.net [80.3.161.69]
  3    42 ms    57 ms    68 ms  winn-bb-1a-ae2-0.network.virginmedia.net [212.43.163.209]
  4    45 ms    30 ms    30 ms  glfd-bb-1b-so-100-0.network.virginmedia.net [213.105.172.130]
  5    14 ms    15 ms    17 ms  ae1.lon25.ip4.tinet.net [77.67.65.161]
  6   112 ms   131 ms   112 ms  xe-2-3-0.nyc20.ip4.tinet.net [89.149.187.109]
  7   375 ms   640 ms   313 ms  192.205.37.37
  8   360 ms   349 ms   374 ms  cr2.n54ny.ip.att.net [12.122.86.10]
  9   360 ms   378 ms   392 ms  cr2.wswdc.ip.att.net [12.122.3.38]
 10   362 ms   349 ms   347 ms  cr1.attga.ip.att.net [12.122.1.173]
 11   379 ms   344 ms   371 ms  cr2.dlstx.ip.att.net [12.122.28.174]
 12   346 ms   379 ms   384 ms  gar23.dlstx.ip.att.net [12.122.138.161]
 13   465 ms   356 ms   354 ms  12-122-254-154.attens.net [12.122.254.154]
 14   350 ms   343 ms   331 ms  mdf001c7613r0003-gig-12-1.dal1.attens.net [63.241.193.22]
 15   330 ms   338 ms   337 ms  206.16.60.39


Amsoil's from the UK but with BT a different ISP.


1    39 ms    99 ms    99 ms  BThomehub.home [192.168.1.254]
  2    24 ms    25 ms    23 ms  217.32.140.64
  3    24 ms    27 ms    27 ms  217.32.140.30
  4    24 ms    25 ms    25 ms  213.120.161.10
  5    24 ms    25 ms    27 ms  217.32.26.18
  6    24 ms    25 ms    25 ms  217.32.26.178
  7    24 ms    25 ms    25 ms  acc1-10GigE-0-7-0-4.bm.21cn-ipp.bt.net [109.159.248.70]
  8    38 ms    32 ms    31 ms  core2-te-0-4-0-4.ilford.ukcore.bt.net [109.159.248.6]
  9    29 ms    53 ms    33 ms  transit1-xe-11-1-0.ilford.ukcore.bt.net [194.72.20.146]
 10   208 ms   321 ms   139 ms  t2c1-ge13-0-0.uk-ilf.eu.bt.net [166.49.168.85]
 11   107 ms    62 ms    30 ms  POS4-0-2.ar6.LON3.gblx.net [64.212.225.13]
 12     *      270 ms   142 ms  192.205.34.141
 13   145 ms   148 ms   147 ms  cr2.dlstx.ip.att.net [12.122.80.102]
 14   141 ms   141 ms   141 ms  gar23.dlstx.ip.att.net [12.122.138.161]
 15   780 ms   485 ms   201 ms  12-122-254-154.attens.net [12.122.254.154]   <-----  eek
 16   145 ms   145 ms   147 ms  mdf001c7613r0004-gig-10-1.dal1.attens.net [63.241.193.18]
 17   144 ms   145 ms   143 ms  206.16.60.39

[Skuzzy]

Bruv, you had some packet loss at hop #6, in that first trace.