Request for information: ISPs and P2P throttling

[Stilp]

ISP : WiFi Spark (via BT lines)
UK
1630 to 2130 weekday evenings

[Undrentide]

Well the lag is back its been back despite using wtfast to try and smooth out the lag. As a matter of interest this is what wtfast reported back on its last session
ping average 96ms - internet 127ms
ping spikes 69 (the number of times your game traffic sees a large latency spike
ping flux average 210ms
10 sec ping - 93 ms.

Now to me 69 ping spikes doesnt sound good in a 5 hour play session.

For the record im with Orange/EE and have posted multiple times.

[Misaky]

ISP: MEO / PT comunicações
Country: Portugal
Time: Always
ping to Portugal: 17ms
ping to SE server(Canada): 120ms

[Vandeyn]

- Streamyx
- Malaysia
- Almost 24/7

[Aleich]

- Name of ISP
Cox Communications

- Country of Residence
USA(Arizona)

- When does the problem occur (always, only during specific times?)
~4PM MST daily is when I noticed it to start

- Reference number from your ISP, if you raised this matter with them
None

[Aexrael]

- Name of ISP: http://fiberby.dk/
- Country of Residence: Denmark
- When does the problem occur (always, only during specific times?): Massive unplayable lag, constant rubber banding/packet loss, consistently after 20:00 CET, have happened in the past, but started again today.

C:\>tracert 199.91.189.30

Tracing route to 199.91.189.30 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 6165001-cl69.boa.fiberby.dk [193.106.165.1]
2 <1 ms <1 ms <1 ms 4135089-cl69.boa.fiberby.dk [193.104.135.89]
3 <1 ms <1 ms <1 ms ge3-15.metro-1.fb.jay.net [86.58.194.125]
4 1 ms <1 ms <1 ms ge3-12-2913.metro-1.gl.jay.net [86.58.227.53]
5 88 ms 4 ms 6 ms ge4-1-2900.core-3.glo.jay.net [86.58.227.1]
6 1 ms 1 ms 1 ms te1-3-2910.core-1.alb.jay.net [86.58.227.42]
7 <1 ms 3 ms <1 ms xe-3-0-0-594.alb2nqe10.dk.ip.tdc.net [195.215.10
9.157]
8 1 ms 1 ms 1 ms ae1-0.alb2nqp7.dk.ip.tdc.net [83.88.21.83]
9 2 ms 1 ms 1 ms tinet.xe-3-3-0-0.alb2nqp7.dk.ip.tdc.net [195.215
.109.102]
10 127 ms 127 ms 151 ms xe-1-3-0.mtl10.ip4.tinet.net [89.149.184.74]
11 127 ms 124 ms 125 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
12 127 ms 128 ms * 192.34.76.2
13 * 125 ms 122 ms 199.91.189.234
14 * 126 ms 128 ms 199.91.189.30

Trace complete.

C:\>tracert 199.91.189.30

Tracing route to 199.91.189.30 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 6165001-cl69.boa.fiberby.dk [193.106.165.1]
2 <1 ms 1 ms 1 ms 4135089-cl69.boa.fiberby.dk [193.104.135.89]
3 <1 ms <1 ms <1 ms ge3-15.metro-1.fb.jay.net [86.58.194.125]
4 <1 ms <1 ms 1 ms ge3-12-2913.metro-1.gl.jay.net [86.58.227.53]
5 <1 ms <1 ms <1 ms ge4-1-2900.core-3.glo.jay.net [86.58.227.1]
6 1 ms 1 ms 1 ms te1-3-2910.core-1.alb.jay.net [86.58.227.42]
7 1 ms <1 ms <1 ms xe-3-0-0-594.alb2nqe10.dk.ip.tdc.net [195.215.10
9.157]
8 1 ms <1 ms <1 ms ae1-0.alb2nqp7.dk.ip.tdc.net [83.88.21.83]
9 1 ms 1 ms 1 ms tinet.xe-3-3-0-0.alb2nqp7.dk.ip.tdc.net [195.215
.109.102]
10 127 ms 128 ms 128 ms xe-1-3-0.mtl10.ip4.tinet.net [89.149.184.74]
11 128 ms * 129 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
12 * 131 ms 130 ms 192.34.76.2
13 128 ms * 140 ms 199.91.189.234
14 130 ms 129 ms 126 ms 199.91.189.30

Trace complete.

C:\>

C:\>tracert 199.91.189.30

Tracing route to 199.91.189.30 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 6165001-cl69.boa.fiberby.dk [193.106.165.1]
2 <1 ms <1 ms <1 ms 4135089-cl69.boa.fiberby.dk [193.104.135.89]
3 <1 ms <1 ms <1 ms ge3-15.metro-1.fb.jay.net [86.58.194.125]
4 1 ms <1 ms <1 ms ge3-12-2913.metro-1.gl.jay.net [86.58.227.53]
5 89 ms 1 ms 126 ms ge4-1-2900.core-3.glo.jay.net [86.58.227.1]
6 1 ms 1 ms 1 ms te1-3-2910.core-1.alb.jay.net [86.58.227.42]
7 1 ms 3 ms <1 ms xe-3-0-0-594.alb2nqe10.dk.ip.tdc.net [195.215.10
9.157]
8 * 1 ms <1 ms ae1-0.alb2nqp7.dk.ip.tdc.net [83.88.21.83]
9 1 ms 1 ms 1 ms tinet.xe-3-3-0-0.alb2nqp7.dk.ip.tdc.net [195.215
.109.102]
10 119 ms 120 ms 122 ms xe-1-3-0.mtl10.ip4.tinet.net [89.149.184.74]
11 120 ms 119 ms 117 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
12 118 ms 124 ms 122 ms 192.34.76.2
13 120 ms 121 ms 122 ms 199.91.189.234
14 * 129 ms 128 ms 199.91.189.30

Trace complete.

C:\>

[RevMether]

ISP - habonet
Country - sweden
Time - always (but more serious at 6pm-midnight gmt +1)

[Stilnight]

Free
France
Always

[Celandri]

ISP : Lyse.net
Norway
1700 to 2130 weekday evenings i get lags, before the rush of people logging in its not to bad.

[Akurudo]

ISP: TKChopin.pl
Poland
allday

traceroute to 199.91.189.60 (199.91.189.60), 30 hops max, 60 byte packets
1 * * *
2 85.237.161.125 69.017 ms 69.026 ms 69.007 ms
3 * * *
4 178.23.105.190 97.710 ms 97.735 ms 97.719 ms
5 77.67.74.85 92.384 ms 92.605 ms 92.594 ms
6 89.149.184.74 198.241 ms 141.136.107.125 212.574 ms 89.149.184.74 207.300 ms
7 216.221.156.110 197.992 ms 215.942 ms 210.391 ms
8 192.34.76.2 218.681 ms 215.050 ms 217.764 ms
9 199.91.189.234 208.813 ms 212.675 ms 191.143 ms
10 199.91.189.60 200.447 ms 200.738 ms 196.923 ms

Just want to add that packets send through edge Nexus of Telia Sonera in GB have like 70-100 ms ping :
my Server to Telia Edge Nexus:
traceroute to 213.248.91.58 (213.248.91.58), 30 hops max, 60 byte packets
1 * * *
2 85.237.161.125 87.044 ms 87.043 ms 87.023 ms
3 88.199.10.33 89.101 ms 89.108 ms 89.146 ms
4 88.199.219.58 100.760 ms 100.769 ms 100.764 ms
5 213.248.97.117 98.283 ms 99.272 ms 105.185 ms
6 213.155.130.104 117.412 ms 69.802 ms 69.779 ms
7 80.91.254.5 85.820 ms 80.239.147.181 83.744 ms 213.155.137.105 83.644 ms
8 80.91.247.90 90.764 ms 81.483 ms 80.406 ms
9 213.248.91.58 80.757 ms 80.726 ms 80.681 ms

Telia Sonera Edge Nexus to Ragnarok Server:
traceroute to 199.91.189.60 (199.91.189.60), 30 hops max, 40 byte packets
1 level3-ic-153380-ldn-b5.c.telia.net (213.248.91.58) 0.555 ms 0.503 ms level3-ic-153380-ldn-b5.c.telia.net (213.248.92.82) 0.477 ms
2 ae-52-52.csw2.London1.Level3.net (4.69.139.120) [AS 3356] 77.191 ms 77.271 ms 78.789 ms
MPLS Label=1174 CoS=0 TTL=1 S=1
3 ae-57-222.ebr2.London1.Level3.net (4.69.153.133) [AS 3356] 79.327 ms ae-59-224.ebr2.London1.Level3.net (4.69.153.141) [AS 3356] 77.267 ms 77.241 ms
MPLS Label=1147 CoS=0 TTL=1 S=1
4 ae-42-42.ebr1.NewYork1.Level3.net (4.69.137.70) [AS 3356] 77.356 ms ae-44-44.ebr1.NewYork1.Level3.net (4.69.137.78) [AS 3356] 77.204 ms ae-41-41.ebr1.NewYork1.Level3.net (4.69.137.66) [AS 3356] 79.334 ms
MPLS Label=1172 CoS=0 TTL=1 S=1
5 ae-91-91.csw4.NewYork1.Level3.net (4.69.134.78) [AS 3356] 81.639 ms ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74) [AS 3356] 77.256 ms 83.459 ms
MPLS Label=1340 CoS=0 TTL=1 S=1
6 ae-82-82.ebr2.NewYork1.Level3.net (4.69.148.41) [AS 3356] 77.447 ms ae-72-72.ebr2.NewYork1.Level3.net (4.69.148.37) [AS 3356] 78.682 ms 79.008 ms
MPLS Label=1197 CoS=0 TTL=1 S=1
7 ae-5-5.car1.Montreal2.Level3.net (4.69.141.5) [AS 3356] 92.321 ms 77.240 ms 77.312 ms
MPLS Label=713 CoS=0 TTL=1 S=1
8 ae-11-11.car2.Montreal2.Level3.net (4.69.141.1) [AS 3356] 80.006 ms 77.451 ms 77.444 ms
9 ORMUCO-COMM.car2.Montreal2.Level3.net (4.59.178.74) [AS 3356] 76.994 ms 76.831 ms 76.912 ms
10 * * *
11 192.34.76.2 (192.34.76.2) [AS 20324] 83.765 ms 87.816 ms 90.043 ms
12 199.91.189.234 (199.91.189.234) [AS 20324] 89.783 ms 85.935 ms 85.948 ms
13 199.91.189.60 (199.91.189.60) [AS 20324] 95.605 ms 89.324 ms 89.743 ms

Twice the improvement