Request for information: ISPs and P2P throttling

[Ervin]

Still having issues.

Location: Sweden
ISP: Bredbandsbolaget
Time: 18.00-21.00CET or 19.00-22.00CET, it's a bit random. Was kinda decent for a few weeks until the last patch hit.

This is far from acceptable since it's a sub-to play game. I'ts the first game since I started MMO gaming where I've had this issue and I started back in DaoC years and years ago when you would expect issues since MMOs was kinda new. They really need to fix this, either by changing something within their servers/the game or contacting and straightening it out with all effected ISPs. Otherwise they wont have my money for long.

[Klingsan]

Problems here too.

Location: Sweden
ISP: Telia
Time: from around 6-7PM till midnight

[Rohirrim]

-Otenet Hellas
-Greece
-Always

tracert


ping

[Golom]

i have the same problems, rubberbanding to 3-7sec lag

Location: Sweden
ISP: bahnhof (i know they allow p2p)
Time: from around 6-7PM till midnight (GMT +1

[Mikolan]

- Telia
- Sweden
- I've experienced severe lagspikes (10+ seconds) twice before, tonight marked the third time. Started around 21:00CET when I was in Coil.

I've identified the problem node in my route and it's 66.198.96.50, apparently owned by Tata Communications. Up until this node I have a consistent ~120ms connection, but when I hit that node I'm getting upwards of 30% packet loss at times.

Traceroute:

Tracing route to 199.91.189.19 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  unknown [192.168.1.1]
  2    13 ms    <1 ms    <1 ms  gw-n1-ekg-a12.ias.bredband.telia.com [90.225.79.193]
  3    15 ms     2 ms     2 ms  s-b1-link.telia.net [213.155.136.7]
  4    15 ms     2 ms     2 ms  s-b3-link.telia.net [80.91.249.250]
  5    57 ms     4 ms   199 ms  vsnl-ic-124239-s-b1.c.telia.net [213.248.104.162]
  6    21 ms     9 ms     9 ms  if-2-1-0.core2.OS1-Oslo.as6453.net [80.231.89.1]
  7   108 ms   108 ms   108 ms  if-1-3-1-0.tcore2.AV2-Amsterdam.as6453.net [80.231.152.41]
  8   142 ms   136 ms   145 ms  if-8-2.tcore2.L78-London.as6453.net [80.231.131.5]
  9   122 ms   111 ms   109 ms  if-20-2.tcore2.NYY-NewYork.as6453.net [216.6.99.13]
 10   124 ms   116 ms   111 ms  if-2-2.tcore2.MTT-Montreal.as6453.net [64.86.226.13]
 11   124 ms   127 ms   130 ms  if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115.89]
 12   111 ms   135 ms   111 ms  if-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.6]
 13   169 ms   169 ms   169 ms  66.198.96.50
 14   237 ms   175 ms   181 ms  192.34.76.2
 15   172 ms   172 ms   167 ms  199.91.189.234
 16   177 ms   159 ms   171 ms  199.91.189.19

Trace complete.

Up to here it's fine:

Ping statistics for 64.86.31.6:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 113ms, Maximum = 156ms, Average = 126ms

Problem node:

Ping statistics for 66.198.96.50:
    Packets: Sent = 100, Received = 92, Lost = 8 (8% loss),
Approximate round trip times in milli-seconds:
    Minimum = 110ms, Maximum = 193ms, Average = 149ms

[Alixandir]

I just wanted to say my problem is still ongoing now for several weeks.

Location: Sweden
ISP: Telia
Time: Rubberbanding all the time. Lag in instances progressively getting worse from 4:00 PM GMT up until midnight.

I have talked to myu ISP that assure me no throttling is being done on their part.

[Bokuhn]

Same problem as the rest. . Horrible lag, rubberband effect, 5-15sec lag spikes

Location: United States, Florida
ISP: Comcast Xfinity
When does problem occur: Started on most recent patch, been having lag ever since. The game is unplayable.

Fix it.
Please.

[Kaori_Nisharu]

Same problem.

Location: California, USA
ISP: Time Warner Cable
When does problem occur: All day long since last patch

Confirmed with TWC there is 5% intermittent packet loss to 184.107.107.176

[Cadger]

As stated by a few other's PlusNET in the UK is definitely having issues. They do also have a thread open on their own forum, that is publicly accessible, and are looking into it. If a dev or rep could get involved with it, maybe it could speed things along. Link: http://community.plus.net/forum/inde...,118895.0.html

Although according to the thread it seems to be more a problem with their uplink suppliers than the routing within PlusNET themselves. There are a LOT of traceroutes within that thread that may help.

[Hannia]

Experanceing huge spikes on Cactuar today
Location: VA
ISP: Comcast

heres the traceroute

Tracing route to 199.91.189.48 over a maximum of 30 hops

  1     9 ms    <1 ms    <1 ms  192.168.1.1
  2     7 ms     7 ms     7 ms  96.120.80.69
  3     7 ms     7 ms     7 ms  te-9-3-ur01.danville.va.richmond.comcast.net [68
.86.200.33]
  4    15 ms    13 ms    12 ms  xe-5-1-0-0-ar02.staplesmllrd.va.richmond.comcast
.net [68.86.172.161]
  5    24 ms    24 ms    22 ms  pos-0-7-0-0-cr01.charlotte.nc.ibone.comcast.net
[68.86.91.153]
  6    30 ms    28 ms    27 ms  pos-3-11-0-0-cr01.56marietta.ga.ibone.comcast.ne
t [68.86.85.225]
  7     *       36 ms     *     pos-0-3-0-0-pe01.56marietta.ga.ibone.comcast.net
 [68.86.87.134]
  8    44 ms    44 ms    40 ms  ix-0-2-0-0.tcore1.A56-Atlanta.as6453.net [209.58
.44.1]
  9    68 ms    75 ms    74 ms  if-25-2.tcore1.AEQ-Ashburn.as6453.net [64.86.113
.2]
 10    70 ms    73 ms    63 ms  64.86.85.1
 11    70 ms    73 ms    78 ms  if-10-2.tcore1.TTT-Scarborough.as6453.net [64.86
.32.33]
 12    64 ms    66 ms    77 ms  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.2
5]
 13    68 ms    64 ms    64 ms  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.61]
 14    67 ms    55 ms    53 ms  66.198.96.50
 15    49 ms    49 ms    53 ms  192.34.76.2
 16    56 ms    56 ms    51 ms  199.91.189.234
 17    66 ms    61 ms    60 ms  199.91.189.48

Trace complete.

And here is another

Tracing route to 199.91.189.48 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     8 ms     7 ms     7 ms  96.120.80.69
  3     7 ms     7 ms    15 ms  te-9-3-ur01.danville.va.richmond.comcast.net [68
.86.200.33]
  4    14 ms    15 ms    12 ms  xe-5-1-0-0-ar02.staplesmllrd.va.richmond.comcast
.net [68.86.172.161]
  5    21 ms    24 ms    22 ms  pos-0-9-0-0-cr01.charlotte.nc.ibone.comcast.net
[68.86.95.65]
  6    28 ms    29 ms    29 ms  pos-3-11-0-0-cr01.56marietta.ga.ibone.comcast.ne
t [68.86.85.225]
  7    35 ms    30 ms    30 ms  pos-0-3-0-0-pe01.56marietta.ga.ibone.comcast.net
 [68.86.87.134]
  8    43 ms    43 ms    43 ms  ix-0-2-0-0.tcore1.A56-Atlanta.as6453.net [209.58
.44.1]
  9    69 ms    70 ms    66 ms  if-25-2.tcore1.AEQ-Ashburn.as6453.net [64.86.113
.2]
 10    82 ms    74 ms    64 ms  64.86.85.1
 11    72 ms    79 ms    68 ms  if-10-2.tcore1.TTT-Scarborough.as6453.net [64.86
.32.33]
 12    68 ms    77 ms    71 ms  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.2
5]
 13    70 ms    65 ms    67 ms  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.61]
 14    55 ms    57 ms    69 ms  66.198.96.50
 15    53 ms    49 ms    51 ms  192.34.76.2
 16    50 ms    56 ms    54 ms  199.91.189.234
 17    77 ms    62 ms    59 ms  199.91.189.48

Trace complete.

It seems that this one is my problem i need to know if i need to call my isp up and chew them out or what?

7     *       36 ms     *     pos-0-3-0-0-pe01.56marietta.ga.ibone.comcast.net
 [68.86.87.134]