Request for information: ISPs and P2P throttling

[Lollerblades]

ISP : BT
County : UK
Problem Occurs most : Started getting terrible lag again after the recent NA/EU server maintenance.

Makes it unplayable again during peak times :/

[Aeliott]

Update:

Name of ISP: BT
Country of Residence: England
When does the problem occur: Constant. Whenever I appear in the game I get 90k'd after a few seconds. Or if I'm extremely lucky I can play for 5 minutes with crippling lag. Was fine before

[ReuelLeonhart]

- NetSite Netsuper
- Brazil (Minas Gerais)
- Randomly, but its been happening all the time since this morning. In Dungeon Instances, it happens all the time too. It just made Titan HM impossible for me.
- ISP have not give me a feedback yet.

[bonniebru5]

Telenor
- Norway, Oslo
- 6pm-3am


the lag spikes up which renders the game more or less unable to play. now i've noticed that not all players are occuring it but theres alot. so it would be interesting to see a location chart of where the people who lag reside

[Layzer]

- Canal Digital
- Norway, Oslo
- Spikes up to nearly unplayable conditions during weekend peak times. Otherwise it seems random.

[Srider1024]

Country : - Neo Caledonia (French Island near Australia - New Zeland)
Provider : M.L.S

When we are connected with my Wife (2 accounts - same Internet connexion), we randomly (one or the other) experienced great lags.

We both had the problem on Japonese servers, and same thing with NA servers.
Until this week end only one of us had the problem at the same time, but this week end we both experienced LAG (with less intensity) for 1 or 2 Hours, then i got disconnected (error 9000) and when i came back, i was unable to play as the lag was so heavy than when i pressed on key, there was a 30sec - 1 min latency.

Upset, i disconnected and logged my char on TITAN (Jap server), no lag, and when i disconnected after 1 or 2 min and came back to NA server, no lag anymore....

We had no current downloadings when we experienced those massive lag spikes, no Internet security soft, or active soft firewall.

So now i activated all security soft, as it seems not to have any incidences on the lag (not much or less when all security soft diseabled for 24 hours mini).

[Cadaver]

ISP: Time Warner Cable
Region/country: Texas, U.S.A.
2:00 p.m. Mountain Time (U.S. and Canada), up until about 11:00 p.m.

This is unacceptable.

[kale1112]

University of Surrey, Resnet
- UK
- Always, login then booted out from game with 90000 error

[EternityFate]

-Viacabo
-Brazil
-Aways with error 90000(impossible to play)

[Noah_]

ok did some tracert to the IP I get connected to when playing ARR :199.91.189.58
I am in TX, USA
this one is straight up from my ISP

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

C:\Users\tracert 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  10.10.10.1
  2     *        3 ms     1 ms  ben2gw1.texascellnet.com [63.246.232.254]
  3     *        5 ms     2 ms  ben2bh.texascellnet.com [63.246.224.105]
  4     8 ms     3 ms     9 ms  corban1bh.texascellnet.com [63.246.224.33]
  5     6 ms     9 ms     *     corbanrtr.texascellnet.com [63.246.224.1]
  6     6 ms     6 ms     3 ms  216.171.64.1
  7     8 ms     5 ms     6 ms  xc_45-90-171.216.xcnetworks.com [216.171.90.45]

  8     5 ms     5 ms     *     ge-8-29.car2.Dallas1.Level3.net [4.71.171.121]
  9     *        *        *     Request timed out.
 10    45 ms    41 ms    44 ms  4.68.111.102
 11    43 ms    50 ms    43 ms  be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.
45]
 12    63 ms    76 ms    67 ms  be2064.mpd21.mci01.atlas.cogentco.com [154.54.5.
217]
 13     *        *        *     Request timed out.
 14    46 ms    40 ms    49 ms  be2081.ccr21.yyz02.atlas.cogentco.com [154.54.42
.10]
 15    53 ms    48 ms     *     be2092.ccr21.ymq02.atlas.cogentco.com [154.54.25
.26]
 16    49 ms    51 ms    51 ms  38.122.42.34
 17     *        *        *     Request timed out.
 18    55 ms    96 ms     *     192.34.76.2
 19    51 ms    51 ms    52 ms  199.91.189.234
 20    55 ms    52 ms    57 ms  199.91.189.58

Trace complete.

now I switch to VPN which allows me to connect to the Montreal data center for ARR from different locations
first I tried was TX

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

C:\Users\tracert 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops

  1     8 ms     6 ms     7 ms  10.156.1.1
  2     8 ms    13 ms     7 ms  23.29.126.101
  3     6 ms     9 ms     6 ms  r1-side-from-bc1.inceronetwork.com [192.211.63.5
]
  4     7 ms     7 ms     6 ms  te4-3.ccr01.dfw10.atlas.cogentco.com [38.88.50.1
]
  5     7 ms     7 ms     6 ms  te0-2-0-7.ccr21.dfw01.atlas.cogentco.com [154.54
.86.205]
  6    20 ms    19 ms    19 ms  be2064.mpd21.mci01.atlas.cogentco.com [154.54.5.
217]
  7    28 ms    38 ms    31 ms  te0-7-0-4.mpd21.ord01.atlas.cogentco.com [154.54
.2.234]
  8    44 ms    44 ms    50 ms  be2081.ccr21.yyz02.atlas.cogentco.com [154.54.42
.10]
  9    51 ms    51 ms    55 ms  be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30
.206]
 10    52 ms    70 ms    54 ms  38.122.42.34
 11     *        *        *     Request timed out.
 12    52 ms    55 ms    53 ms  192.34.76.2
 13    52 ms    65 ms    57 ms  199.91.189.234
 14    69 ms    63 ms    50 ms  199.91.189.58

Trace complete.

next one I tried was from Seattle since it's close to canada

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

C:\Users\tracert 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops

  1    47 ms    82 ms   103 ms  10.123.1.1
  2    68 ms    48 ms    51 ms  mpdedicated.com [173.192.170.65]
  3    53 ms    52 ms    54 ms  ae12.dar01.sr01.sea01.networklayer.com [67.228.1
18.224]
  4    51 ms    51 ms    55 ms  ae8.bbr02.wb01.sea02.networklayer.com [173.192.1
8.142]
  5    47 ms    49 ms    49 ms  te-3-2.car4.Seattle1.Level3.net [4.71.152.137]
  6    54 ms    48 ms    50 ms  ae-2-52.edge1.Seattle3.Level3.net [4.69.147.170]

  7   123 ms   120 ms   114 ms  te0-3-0-16.ccr21.sea02.atlas.cogentco.com [154.5
4.12.25]
  8   130 ms   127 ms   129 ms  be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.
198]
  9   144 ms   140 ms   159 ms  be2126.ccr21.den01.atlas.cogentco.com [154.54.25
.65]
 10   167 ms     *      283 ms  be2128.ccr21.mci01.atlas.cogentco.com [154.54.25
.174]
 11   206 ms   162 ms   162 ms  te0-2-0-5.ccr21.ord01.atlas.cogentco.com [154.54
.82.142]
 12   178 ms   173 ms   178 ms  be2082.ccr22.yyz02.atlas.cogentco.com [154.54.28
.10]
 13   184 ms   197 ms   207 ms  be2092.ccr21.ymq02.atlas.cogentco.com [154.54.25
.26]
 14   127 ms   130 ms   129 ms  38.122.42.34
 15     *        *        *     Request timed out.
 16   138 ms   226 ms   149 ms  192.34.76.2
 17   174 ms   135 ms   243 ms  199.91.189.234
 18   130 ms   128 ms   132 ms  199.91.189.58

Trace complete.

next up is NY

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

C:\Users\tracert 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops

  1    43 ms    47 ms    42 ms  10.102.1.1
  2    48 ms    43 ms    40 ms  vl906-c10-8-b2-1.pnj1.choopa.net [209.222.7.233]

  3    45 ms    49 ms    47 ms  ethernet20-1-br1.pnj1.choopa.net [108.61.2.197]

  4    54 ms    48 ms    48 ms  ae7.ar2.nyc3.us.nlayer.net [69.31.34.77]
  5    42 ms    41 ms    40 ms  ae0-315.nyc41.ip4.tinet.net [199.229.230.93]
  6    49 ms    49 ms    53 ms  xe-4-2-0.mtl10.ip4.tinet.net [141.136.107.125]
  7    55 ms    52 ms    55 ms  xe-4-0-0.mtl10.ip4.tinet.net [141.136.108.190]
  8    50 ms    55 ms     *     ormuco-gw.ip4.tinet.net [216.221.156.110]
  9    56 ms    53 ms    60 ms  192.34.76.2
 10    50 ms    60 ms    49 ms  199.91.189.58

Trace complete.

now lets try from California

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

C:\Users\tracert 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops

  1    48 ms    49 ms    46 ms  10.180.200.1
  2    47 ms    48 ms    48 ms  50.23.65.1-static.reverse.uk2group.com [50.23.65
.1]
  3    75 ms    48 ms     *     ae0.dar01.sr01.sjc01.networklayer.com [50.23.118
.130]
  4    46 ms    91 ms    46 ms  ae8.bbr01.eq01.sjc02.networklayer.com [173.192.1
8.248]
  5    46 ms    54 ms    46 ms  xe-7-1-0.edge2.SanJose3.Level3.net [4.53.210.9]

  6    50 ms    56 ms    50 ms  ix-11-0.tcore2.SQN-SanJose.as6453.net [209.58.11
6.109]
  7   139 ms   135 ms   142 ms  if-5-2.tcore2.PDI-PaloAlto.as6453.net [64.86.21.
2]
  8   147 ms     *      139 ms  if-2-2.tcore1.PDI-PaloAlto.as6453.net [66.198.12
7.1]
  9   186 ms   206 ms   322 ms  if-1-2.tcore1.NYY-NewYork.as6453.net [66.198.127
.6]
 10   193 ms   137 ms   160 ms  if-11-2.tcore2.NYY-NewYork.as6453.net [216.6.99.
1]
 11   141 ms   210 ms     *     if-5-2.tcore2.MTT-Montreal.as6453.net [216.6.99.
30]
 12   138 ms   145 ms   166 ms  if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115
.89]
 13   141 ms   137 ms   141 ms  if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.
6]
 14     *        *      185 ms  66.198.96.50
 15   130 ms   136 ms   133 ms  192.34.76.2
 16     *      134 ms     *     199.91.189.234
 17   135 ms   131 ms   132 ms  199.91.189.58

Trace complete.

now lets try London

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

C:\Users\tracert 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops

  1   108 ms   112 ms   113 ms  10.124.22.1
  2     *      131 ms   114 ms  2582e38a.rdns.100tb.com [37.130.227.138]
  3   114 ms   112 ms   175 ms  83.170.70.229
  4     *      178 ms   189 ms  te4-5.ccr01.lon18.atlas.cogentco.com [149.14.8.4
1]
  5   112 ms   113 ms   109 ms  te0-0-0-23.ccr21.lon01.atlas.cogentco.com [154.5
4.62.41]
  6   110 ms     *        *     te0-1-0-4.ccr21.lon13.atlas.cogentco.com [154.54
.57.106]
  7   121 ms   117 ms   123 ms  te0-2-0-5.ccr21.lpl01.atlas.cogentco.com [154.54
.37.173]
  8   193 ms   190 ms   188 ms  te0-2-0-4.ccr21.ymq02.atlas.cogentco.com [154.54
.0.70]
  9   189 ms   185 ms   186 ms  38.122.42.34
 10     *        *        *     Request timed out.
 11   185 ms   188 ms   187 ms  192.34.76.2
 12   189 ms   195 ms   190 ms  199.91.189.234
 13   190 ms   191 ms   187 ms  199.91.189.58

Trace complete.

last one I tried to go with Toronto, CA

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

C:\Users\tracert 199.91.189.58

Tracing route to 199.91.189.58 over a maximum of 30 hops

  1     *       46 ms    42 ms  10.120.1.1
  2    41 ms    42 ms    45 ms  184-75-223-65.amanah.com [184.75.223.65]
  3    41 ms    45 ms    41 ms  xe-0-0-1-3602.cr1.tor2.ca.nlayer.net [69.31.143.
109]
  4    47 ms    42 ms    47 ms  ae0-30g.cr1.tor1.ca.nlayer.net [69.31.143.24]
  5    45 ms    42 ms    45 ms  ae2-50.tor10.ip4.tinet.net [199.229.230.89]
  6    49 ms    49 ms    48 ms  xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
  7    49 ms    48 ms     *     ormuco-gw.ip4.tinet.net [216.221.156.110]
  8    50 ms    50 ms    67 ms  192.34.76.2
  9    54 ms    49 ms    50 ms  199.91.189.234
 10    54 ms    50 ms    62 ms  199.91.189.58

Trace complete.

very interesting results, noticed the ones that does NOT route through cogentco.com has no time outs, what does this mean? I don't know....maybe some IT guru can tell more on this or maybe even SE network staff....