Request for information: ISPs and P2P throttling

[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