Request for information: ISPs and P2P throttling

**Chryzo** · 10-23-2013 09:15 PM

- Country: France
- ISP: FREE
- Only lag in the evening

In the evening, when I lag:

Code:

C:\Users\Chryzo>tracert 199.91.189.48

Tracing route to 199.91.189.48 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  192.168.0.254
  2    21 ms    20 ms    21 ms  82.228.161.254
  3    21 ms    21 ms     *     tours-6k-1.routers.proxad.net [213.228.19.62]
  4    23 ms    21 ms    21 ms  orleans-6k-1-po2.intf.routers.proxad.net [212.27.50.73]
  5    24 ms     *       23 ms  bourges-6k-1-po1.intf.routers.proxad.net [212.27.57.66]
  6     *       25 ms     *     clermont-6k-1-po100.intf.routers.proxad.net [212.27.56.126]
  7     *        *        *     Request timed out.
  8    30 ms    30 ms    31 ms  lyon-crs16-1-be1005.intf.routers.proxad.net [212.27.50.181]
  9    37 ms    34 ms    34 ms  marseille-6k-1-po50.intf.routers.proxad.net [212.27.50.101]
 10    35 ms    35 ms    34 ms  p11-crs16-1-be1102.intf.routers.proxad.net [78.254.249.89]
 11    38 ms    34 ms    35 ms  bzn-crs16-2-be2000.intf.routers.proxad.net [78.254.250.125]
 12    34 ms    34 ms    33 ms  te0-1-0-5.365.mag21.par01.atlas.cogentco.com [149.6.160.101]
 13    34 ms    33 ms    33 ms  be2038.ccr21.par01.atlas.cogentco.com [154.54.74.253]
 14    42 ms    41 ms    42 ms  te0-1-0-3.ccr21.lon13.atlas.cogentco.com [154.54.59.17]
 15    48 ms    47 ms    48 ms  te0-3-0-3.ccr21.lpl01.atlas.cogentco.com [154.54.58.90]
 16   120 ms   118 ms   119 ms  te0-1-0-4.ccr21.ymq02.atlas.cogentco.com [154.54.26.141]
 17   119 ms   119 ms   119 ms  38.122.42.34
 18   119 ms   118 ms   119 ms  10.2.2.1
 19   119 ms   118 ms   119 ms  192.34.76.2
 20   118 ms   119 ms   119 ms  199.91.189.234
 21     *      119 ms   125 ms  199.91.189.48

Trace complete.

In the day when I don't lag:

Code:

C:\Users\Chryzo>tracert 199.91.189.48

Tracing route to 199.91.189.48 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  192.168.0.254
  2    21 ms    20 ms    20 ms  82.228.161.254
  3    21 ms    20 ms    20 ms  tours-6k-1.routers.proxad.net [213.228.19.62]
  4     *       23 ms    21 ms  orleans-6k-1-po2.intf.routers.proxad.net [212.27.50.73]
  5    24 ms    23 ms    24 ms  bourges-6k-1-po1.intf.routers.proxad.net [212.27.57.66]
  6    25 ms    25 ms    25 ms  clermont-6k-1-po100.intf.routers.proxad.net [212.27.56.126]
  7     *        *       28 ms  stetienne-6k-1-po1.intf.routers.proxad.net [212.27.58.62]
  8    29 ms    31 ms    31 ms  lyon-crs16-1-be1005.intf.routers.proxad.net [212.27.50.181]
  9    33 ms    34 ms    35 ms  marseille-6k-1-po50.intf.routers.proxad.net [212.27.50.101]
 10    37 ms    35 ms    35 ms  p11-crs16-1-be1102.intf.routers.proxad.net [78.254.249.89]
 11    36 ms    34 ms    35 ms  bzn-crs16-2-be2000.intf.routers.proxad.net [78.254.250.125]
 12    34 ms    33 ms    33 ms  te0-1-0-5.365.mag21.par01.atlas.cogentco.com [149.6.160.101]
 13    34 ms    34 ms    33 ms  be2038.ccr21.par01.atlas.cogentco.com [154.54.74.253]
 14    41 ms    41 ms    42 ms  te0-2-0-1.ccr21.lon13.atlas.cogentco.com [130.117.51.29]
 15    48 ms    49 ms    47 ms  te0-3-0-3.ccr21.lpl01.atlas.cogentco.com [154.54.58.90]
 16   119 ms   119 ms   119 ms  te0-1-0-4.ccr21.ymq02.atlas.cogentco.com [154.54.26.141]
 17   119 ms   119 ms   119 ms  38.122.42.34
 18   120 ms   119 ms   119 ms  10.2.2.1
 19   118 ms   119 ms   119 ms  192.34.76.2
 20   120 ms   119 ms   119 ms  199.91.189.234
 21   120 ms   120 ms   120 ms  199.91.189.48

Trace complete.

So... No difference... so... FIX YOUR SERVERS. And by the way WTF IS THAT 10.2.2.1 doing there ? What is that internal bridge you doing over there ? That IP is private guys.

Regards,

**Guapa** · 10-24-2013 12:14 AM

Name of ISP : Fastweb
Country of Residence : Italy
When does the problem occur : Always

**DiamondTheDe1** · 10-24-2013 12:22 AM

Name of ISP : NGI
Country of Residence : Italy
When does the problem occur : Always

**Maza** · 10-24-2013 01:03 AM

Name of ISP: Cox - I have talked and talked and had service come out, went through all thier tiers of support. I've done everything except put a gun to Coxs head. I give up.
Country: US
When: random, lags in high pop areas seomtimes and sometimes not.

I dred going into duty finder to complete my storyline quests because it's just not fun anymore. I can't play my best and people get mad and it's the complete opposite of my definition of what a GAME should be like. If it wasn't for this frigging lag I would be enjoying this great game greatly!

**Barthezz** · 10-24-2013 03:11 AM

- Name of ISP: Etisalat
- Country of Residence: United Arab Emirates
- When does the problem occur (always, only during specific times?): Always
- Reference number from your ISP, if you raised this matter with them: Etisalat people are absolutely useless, sent them an email with the traceroute to Sargatanas @199.91.189.33, their help email is care@etisalat.ae (which is absolutely useless).

Here is the trace route, IP is dynamic from the ISP, please help... its making almost impossible to play the game as intended due to the inability to get out of AoE at bosses, especially Titan hard mode...
I'm not the only person with this problem, there are many people who play in the UAE, not many of them are aware of this thread, and dont have the technical knowledge to figure out the problem, i really hope this get sorted out sooner rather than later...

Code:

Tracing route to 199.91.189.33 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.1.1]
  2     3 ms     3 ms     3 ms  213.42.8.34
  3     3 ms     3 ms     3 ms  213.42.8.30
  4     5 ms     4 ms     4 ms  213.42.9.98
  5     *        *        *     Request timed out.
  6     6 ms     4 ms     5 ms  194.170.0.138
  7    18 ms    11 ms    12 ms  195.229.0.237
  8    15 ms   258 ms   256 ms  pos2-0.palermo7.pal.seabone.net [195.22.197.134]

  9   259 ms   244 ms   254 ms  pos0-1-0.catania3.cat.seabone.net [93.186.129.2]

 10   335 ms   231 ms   337 ms  ge-0-0-0.mil19.ip4.tinet.net [213.200.68.145]
 11   355 ms   339 ms   353 ms  xe-1-3-0.mtl10.ip4.tinet.net [89.149.184.74]
 12   337 ms   337 ms   354 ms  xe-1-3-0.mtl10.ip4.tinet.net [89.149.184.74]
 13   339 ms   338 ms   339 ms  ormuco-gw.ip4.tinet.net [216.221.156.110]
 14   399 ms   407 ms   418 ms  192.34.76.2
 15   345 ms   339 ms   344 ms  199.91.189.234
 16   339 ms   337 ms   337 ms  199.91.189.33

Trace complete.

**Lithal** · 10-24-2013 03:32 AM

Game close to unplayable during prime hours. Sending drops down to 0

Name of ISP: Telenor
Country: Norway
Occurance: every day except saturday it seems. during prime time. (19:00 GMT +1)

**Startech** · 10-24-2013 04:51 AM

- Name of ISP: Comhem
- Country of Residence Sweden
- When does the problem occur: Mostly during prime time (uk time) but get 9000 errors from time to time always

ive had no problem during beta/early access, i even manage to survive most of the launch without much issues and now since like a week ago its been unplayble, 2 sec play 15sec lag.. sup?

Tracing route to 199.91.189.33 over a maximum of 30 hops

1 4 ms 3 ms 3 ms TO-DOC-3-Cable4-0.comhem.se [80.217.48.1]
2 9 ms 12 ms 11 ms 213.200.189.136
3 9 ms 12 ms 12 ms 83.255.253.204
4 38 ms 7 ms 9 ms s-b3-link.telia.net [213.248.99.85]
5 51 ms 78 ms 147 ms vsnl-ic-124239-s-b1.c.telia.net [213.248.104.162
]
6 16 ms 40 ms 15 ms if-2-1-0.core2.OS1-Oslo.as6453.net [80.231.89.1]

7 118 ms 114 ms 116 ms if-1-3-1-0.tcore2.AV2-Amsterdam.as6453.net [80.2
31.152.41]
8 129 ms 116 ms 118 ms if-8-2.tcore2.L78-London.as6453.net [80.231.131.
5]
9 156 ms * 158 ms if-20-2.tcore2.NYY-NewYork.as6453.net [216.6.99.
13]
10 117 ms 118 ms 117 ms if-5-2.tcore2.MTT-Montreal.as6453.net [216.6.99.
30]
11 155 ms 152 ms 152 ms if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115
.89]
12 129 ms 118 ms 131 ms if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.
6]
13 185 ms 202 ms 188 ms 66.198.96.50
14 * 191 ms 201 ms 192.34.76.2
15 195 ms 193 ms 218 ms 199.91.189.234
16 193 ms 198 ms 198 ms 199.91.189.33

Trace complete.

**Valkyrion85** · 10-24-2013 05:12 AM

Name of isp: eidsiva
Country: Norway
Occur: minor lag in evening, after 6:30-7 pm gmt+2 it's unplayable.

pinging 199.91.189.43 with 32 byte data:
Reply from 199.91.189.43: bytes=32 time=202ms TTL=235
Forespørsel avbrutt.
Reply from 199.91.189.43: bytes=32 time=202ms TTL=235
Reply from 199.91.189.43: bytes=32 time=198ms TTL=235

Ping statistics for 199.91.189.43:
Pakker: sent = 4, received = 3, lost = 1 (25% tap),
Gjennomsnittlig tid for tur-retur i millisekunder:
minimum = 198ms, maximum = 202ms, average = 200ms

Tracing route til 199.91.189.43 over a maximum of 30 hops

1 2 ms 1 ms 1 ms 192.168.1.1
2 * * * Forespørsel avbrutt.
3 6 ms 7 ms 6 ms eb-u-gw.bkkb.no [193.28.236.250]
4 6 ms 6 ms 9 ms ba-u-gw2.bkkb.no [193.28.236.249]
5 7 ms 7 ms 6 ms oso-b1-link.telia.net [213.248.87.69]
6 16 ms 15 ms 13 ms s-bb3-link.telia.net [213.155.137.80]
7 16 ms 16 ms 18 ms s-b3-link.telia.net [80.91.248.207]
8 127 ms 115 ms 116 ms vsnl-ic-124239-s-b1.c.telia.net [213.248.104.162
]
9 36 ms 37 ms 46 ms if-2-1-0.core2.OS1-Oslo.as6453.net [80.231.89.1]

10 145 ms 122 ms 120 ms if-1-3-1-0.tcore2.AV2-Amsterdam.as6453.net [80.2
31.152.41]
11 127 ms 124 ms 121 ms if-7-2.tcore2.L78-London.as6453.net [80.231.152.
14]
12 123 ms 123 ms 124 ms if-20-2.tcore2.NYY-NewYork.as6453.net [216.6.99.
13]
13 123 ms 125 ms 123 ms if-5-2.tcore2.MTT-Montreal.as6453.net [216.6.99.
30]
14 142 ms 124 ms 123 ms if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115
.89]
15 171 ms 131 ms 123 ms if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.
6]
16 197 ms 198 ms 198 ms 66.198.96.50
17 201 ms 196 ms * 192.34.76.2
18 208 ms 204 ms * 199.91.189.234
19 203 ms 203 ms 204 ms 199.91.189.43

Trace complete.

**Hectic** · 10-24-2013 05:40 AM

Name of ISP: MWeb
Country: South Africa
Occurs: Shaping picks up around 15:00 GMT and by 18:00 GMT, it becomes unplayable.

Pinging 199.91.189.43 with 32 bytes of data:
Reply from 199.91.189.43: bytes=32 time=296ms TTL=235
Request timed out.
Reply from 199.91.189.43: bytes=32 time=296ms TTL=235
Reply from 199.91.189.43: bytes=32 time=315ms TTL=235

Ping statistics for 199.91.189.43:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 296ms, Maximum = 315ms, Average = 302ms

Tracing route to 199.91.189.43 over a maximum of 30 hops

1 4 ms 3 ms 4 ms 192.168.1.1
2 * 18 ms 19 ms 41-133-132-1.dsl.mweb.co.za [41.133.132.1]
3 31 ms 34 ms 35 ms 197-84-96-138.cpt.mweb.co.za [197.84.96.138]
4 24 ms 28 ms 27 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 182 ms 183 ms 178 ms 197-84-5-226.cpt.mweb.co.za [197.84.5.226]
6 * 182 ms 178 ms 197-84-4-33.cpt.mweb.co.za [197.84.4.33]
7 170 ms 174 ms 176 ms 197-84-4-201.cpt.mweb.co.za [197.84.4.201]
8 182 ms 180 ms 188 ms 176.67.177.161
9 176 ms 180 ms 182 ms 176.67.177.131
10 178 ms 188 ms 175 ms xe-8-1-0.edge3.London1.Level3.net [195.50.124.13
3]
11 177 ms 180 ms 177 ms ix-20-0.tcore1.LDN-London.as6453.net [195.219.83
.101]
12 264 ms 255 ms 256 ms if-17-2.tcore1.L78-London.as6453.net [80.231.130
.129]
13 254 ms 255 ms 254 ms if-1-2.tcore2.L78-London.as6453.net [80.231.130.
122]
14 265 ms 253 ms 256 ms if-20-2.tcore2.NYY-NewYork.as6453.net [216.6.99.
13]
15 256 ms 257 ms 254 ms if-5-2.tcore2.MTT-Montreal.as6453.net [216.6.99.
30]
16 245 ms 246 ms 255 ms if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115
.89]
17 246 ms 246 ms 247 ms if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.
6]
18 313 ms 305 ms 268 ms 66.198.96.50
19 296 ms 322 ms 327 ms 192.34.76.2
20 295 ms 258 ms 263 ms 199.91.189.234
21 282 ms 329 ms 335 ms 199.91.189.43

**Nalazar** · 10-24-2013 09:34 AM

- Brighthouse
- USA
- Mainly in Duty Finder

Thread: Request for information: ISPs and P2P throttling

Thread Tools

Search Thread

Display

Duty lag