Request for information: ISPs and P2P throttling

**Zoultrias** · 10-29-2013 01:17 PM

Reply from 199.91.189.74: bytes=32 time=120ms TTL=53
Reply from 199.91.189.74: bytes=32 time=111ms TTL=53
Reply from 199.91.189.74: bytes=32 time=106ms TTL=53
Reply from 199.91.189.74: bytes=32 time=109ms TTL=53
Request timed out.
Reply from 199.91.189.74: bytes=32 time=109ms TTL=53
Reply from 199.91.189.74: bytes=32 time=124ms TTL=53
Request timed out.
Reply from 199.91.189.74: bytes=32 time=109ms TTL=53
Reply from 199.91.189.74: bytes=32 time=107ms TTL=53
Reply from 199.91.189.74: bytes=32 time=159ms TTL=53
Request timed out.
Reply from 199.91.189.74: bytes=32 time=113ms TTL=53
Reply from 199.91.189.74: bytes=32 time=110ms TTL=53
Reply from 199.91.189.74: bytes=32 time=110ms TTL=53
Reply from 199.91.189.74: bytes=32 time=109ms TTL=53
Reply from 199.91.189.74: bytes=32 time=111ms TTL=53
Reply from 199.91.189.74: bytes=32 time=110ms TTL=53
Request timed out.
Reply from 199.91.189.74: bytes=32 time=151ms TTL=53
Reply from 199.91.189.74: bytes=32 time=114ms TTL=53
Reply from 199.91.189.74: bytes=32 time=111ms TTL=53
Reply from 199.91.189.74: bytes=32 time=120ms TTL=53
Request timed out.
Reply from 199.91.189.74: bytes=32 time=112ms TTL=53
Request timed out.
Reply from 199.91.189.74: bytes=32 time=112ms TTL=53
Reply from 199.91.189.74: bytes=32 time=111ms TTL=53
Reply from 199.91.189.74: bytes=32 time=111ms TTL=53
Reply from 199.91.189.74: bytes=32 time=110ms TTL=53
Request timed out.
Reply from 199.91.189.74: bytes=32 time=111ms TTL=53

Ping statistics for 199.91.189.74:
Packets: Sent = 113, Received = 99, Lost = 14 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 106ms, Maximum = 159ms, Average = 114ms
Control-C
^C
C:\WINDOWS\system32>ping 199.91.189.74

Pinging 199.91.189.74 with 32 bytes of data:
Reply from 199.91.189.74: bytes=32 time=124ms TTL=53
Reply from 199.91.189.74: bytes=32 time=109ms TTL=53
Reply from 199.91.189.74: bytes=32 time=112ms TTL=53
Request timed out.

Ping statistics for 199.91.189.74:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 124ms, Average = 115ms

C:\WINDOWS\system32>tracert 199.91.189.74

Tracing route to 199.91.189.74 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms DD-WRT-WRT320N [192.168.1.1]
2 * * * Request timed out.
3 11 ms 10 ms 9 ms ocnscmtk04-gex030000.sd.sd.cox.net [68.6.12.46]

4 * * * Request timed out.
5 12 ms 11 ms 36 ms fed1dsrj01-xe130.0.rd.sd.cox.net [68.6.8.0]
6 40 ms 34 ms 31 ms sanjbprj02-ae0.0.rd.sj.cox.net [68.1.5.186]
7 22 ms 22 ms 23 ms te0-7-0-30.ccr21.sjc03.atlas.cogentco.com [154.5
4.10.125]
8 31 ms 31 ms 33 ms be2000.ccr21.sjc01.atlas.cogentco.com [154.54.6.
105]
9 32 ms 24 ms 33 ms be2164.ccr21.sfo01.atlas.cogentco.com [154.54.28
.33]
10 62 ms 64 ms 67 ms be2135.mpd22.mci01.atlas.cogentco.com [154.54.6.
34]
11 78 ms 76 ms 74 ms be2159.mpd22.ord01.atlas.cogentco.com [154.54.24
.82]
12 95 ms 94 ms 97 ms be2082.ccr22.yyz02.atlas.cogentco.com [154.54.28
.10]
13 106 ms 102 ms 101 ms be2092.ccr21.ymq02.atlas.cogentco.com [154.54.25
.26]
14 140 ms 139 ms 140 ms 38.122.42.34
15 * * * Request timed out.
16 117 ms 125 ms 120 ms 192.34.76.2
17 122 ms 122 ms 117 ms 199.91.189.234
18 110 ms 111 ms 111 ms 199.91.189.74

Trace complete.

COX Cable
San Diego, California
Pretty unplayable, disconnects often, very laggy and skipping. Only FFXIV is affected.
All they did was reset my modem, which I had already done.

**Mikolan** · 10-30-2013 04:03 AM

I've done some further investigations.

ISP: Telia
Been getting constant lag in the evenings (~6pm+ GMT)

This is how my route looked yesterday when I experienced some serious lag:

Code:

                                              My traceroute  [v0.85]
fs (0.0.0.0)                                                                              Mon Oct 28 21:31:03 2013
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                          Packets               Pings
 Host                                                                   Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. unknown                                                              0.0%  1585    0.2   0.2   0.2  60.4   1.7
 2. gw-n1-ekg-a12.ias.bredband.telia.com                                 0.0%  1585    1.4   4.4   0.6 397.0  20.9
 3. s-b1-link.telia.net                                                  0.0%  1585    2.5   3.2   2.4  62.8   4.5
 4. s-b3-link.telia.net                                                  0.0%  1585    2.4   3.8   2.4  64.5   6.7
    s-b3-link.telia.net
    s-b3-link.telia.net
    s-b3-link.telia.net
    s-b3-link.telia.net
 5. vsnl-ic-124239-s-b1.c.telia.net                                      0.0%  1585    3.0  15.0   2.7 271.7  33.7
 6. if-2-1-0.core2.OS1-Oslo.as6453.net                                   0.1%  1585    9.3  26.7   9.3 239.4  39.4
 7. if-1-3-1-0.tcore2.AV2-Amsterdam.as6453.net                           0.0%  1585  110.3 114.1 110.2 152.5   6.9
 8. if-8-2.tcore2.L78-London.as6453.net                                  0.0%  1585  138.5 118.0 114.2 177.0   7.7
 9. if-20-2.tcore2.NYY-NewYork.as6453.net                                1.5%  1585  121.6 115.9 110.5 186.2   9.2
10. if-2-2.tcore2.MTT-Montreal.as6453.net                                0.0%  1585  112.8 116.1 112.6 208.5   7.9
11. if-0-2.tcore1.MTT-Montreal.as6453.net                                0.0%  1584  143.0 120.2 114.5 175.7  10.7
12. if-5-2.tcore1.W6C-Montreal.as6453.net                                0.0%  1584  114.5 115.8 111.6 174.9   7.5
13. 66.198.96.50                                                         5.3%  1584  178.8 184.9 158.0 250.2   4.7
14. 192.34.76.2                                                          5.4%  1584  184.8 192.1 164.0 262.8  10.1
15. 199.91.189.234                                                       5.2%  1584  183.7 188.0 167.4 258.2   6.1
16. 199.91.189.19                                                        6.4%  1584  187.3 191.1 168.2 376.6  26.0

And this is today after dropping out of a Titan HM because weight of the land was going off before i even saw the animations:

Code:

                                                 My traceroute  [v0.85]
fs (0.0.0.0)                                                                                    Tue Oct 29 20:01:51 2013
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                                Packets               Pings
 Host                                                                         Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. unknown                                                                    0.0%  3191    0.2   0.2   0.2  52.0   1.6
 2. gw-n1-ekg-a12.ias.bredband.telia.com                                       0.0%  3191    0.8   3.5   0.6 233.2  16.5
 3. s-b1-link.telia.net                                                        0.0%  3191    2.4   3.8   2.4  74.4   7.4
 4. s-b3-link.telia.net                                                        0.0%  3191    2.6   3.6   2.4  73.5   7.3
    s-b3-link.telia.net
    s-b3-link.telia.net
    s-b3-link.telia.net
    s-b3-link.telia.net
 5. vsnl-ic-124239-s-b1.c.telia.net                                            0.1%  3191    2.8  18.0   2.7 291.8  37.8
 6. if-2-1-0.core2.OS1-Oslo.as6453.net                                         0.2%  3191    9.3  31.1   9.3 1971.  60.6
 7. if-1-3-1-0.tcore2.AV2-Amsterdam.as6453.net                                 0.0%  3191  110.4 112.0 110.2 171.6   7.0
 8. if-7-2.tcore2.L78-London.as6453.net                                        0.0%  3191  117.3 116.9 114.3 189.4   6.9
 9. if-20-2.tcore2.NYY-NewYork.as6453.net                                      0.1%  3190  113.2 112.5 109.6 180.6   7.7
10. if-2-2.tcore2.MTT-Montreal.as6453.net                                      0.0%  3190  115.7 113.8 111.7 178.3   7.0
11. if-0-2.tcore1.MTT-Montreal.as6453.net                                      0.0%  3190  114.0 114.8 113.6 173.5   7.0
12. if-5-2.tcore1.W6C-Montreal.as6453.net                                      0.0%  3190  111.1 113.6 110.7 184.0   7.2
13. 66.198.96.50                                                               3.8%  3190  186.7 184.6 159.2 251.9   4.0
14. 192.34.76.2                                                                3.6%  3190  189.6 189.9 173.0 324.3   9.2
15. 199.91.189.234                                                             3.4%  3190  188.1 184.9 154.5 226.4   3.6
16. 199.91.189.26                                                              3.2%  3190  188.8 188.2 161.8 267.0   3.7

**Folsom** · 10-30-2013 04:15 AM

ISP - Charter Communications
Country - United States (Oregon)
Problem Times - Between 9am and 3pm Pacific Time
Reference Number - N/A

Note: The problem tends to slowly build up from 9am to 12pm, and then remains at its worst until about 2pm. It will generally drop off very quickly, though sometimes lasts until about 3pm. This seems to correlate with the times listed in the UK from other players.

**Eindwe** · 10-30-2013 05:26 AM

ISP: Comcast Communications
Country: United States (Michigan)
Problem Times: 2:00 PM until Midnight Eastern Time 1 to .5 second bursts every ~4-15 seconds. Rarely, it lasts for about 5 seconds before clearing which ends up in a rapid "catch-up" mode. It gets worse from 2:00 PM until 10:00 PM and then starts recover. By midnight, the problem is gone.

This trace route report was completed at 4:18 PM on 10/29/2013.

Code:

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|(initial hops removed for security)                                                       |

|he-4-5-0-0-cr01.350ecermak.il.ibone.comcast.net -    0 | 1576 | 1576 |   17 |   23 |   71 |   27 |

|ix-8-0-3-0.tcore1.CT8-Chicago.as6453.net -    0 | 1576 | 1576 |   16 |   26 |  107 |   22 |

|   if-22-2.tcore2.CT8-Chicago.as6453.net -    2 | 1510 | 1493 |   36 |   46 |  102 |   40 |

|   if-3-2.tcore1.W6C-Montreal.as6453.net -    0 | 1576 | 1576 |   35 |   46 |  112 |   46 |

|                            66.198.96.50 -    8 | 1209 | 1118 |   78 |  113 |  156 |   78 |

|                             192.34.76.2 -    8 | 1214 | 1124 |   81 |  116 |  185 |   89 |

|                          199.91.189.234 -    0 | 1576 | 1576 |   37 |   44 |  105 |   38 |

|                           199.91.189.25 -    6 | 1274 | 1198 |   78 |  114 |  149 |  101 |

|________________________________________________|______|______|______|______|______|______|

As others have already pointed out...

66.198.96.50 (Tata Communications) seems to be a root problem for people in the US and EU.
192.34.76.2 (Ormuco) is another problem that needs to uninstall. =P
199.91.189.25 (Eidos) is your own server (Gilgamesh)

I guess you could put Chicago on alert, but all these issues really start in Canada.

**Kurai_Arashi** · 10-30-2013 06:38 AM

- Name of ISP: Vodafone
- Country of Residence: Ireland
- When does the problem occur (always, only during specific times?): During peak hours (Late afternoon, evening)

Massive lagskipkes and delay. Unplayable.

**Donze** · 10-30-2013 06:49 AM

Name of ISP: TDS Telecom
Country of Residence: United States
When does the problem occur: constantly the last few days/week

**CriticalCrystal** · 10-30-2013 09:15 AM

Name of ISP: Plusnet
Country of Residence: United Kingdom
When does the problem occur: Starts around 6pm and can persist until the early hours of the morning. I get noticeable lag on everything I do making actions in dungeons unresponsive as well as massive latency delays with various dialog boxes and actions in-world.
It gets very annoying especially as my raid group plans raids for a 7pm start...

**GravenKing** · 10-30-2013 12:46 PM

Error 90000 within a minute or two of logging on. Started happening today.

Name of ISP: Teksavvy (reseller for Rogers)
Country of Residence: Canada
When does the problem occur: Since today. I noticed issues all day long.
I ran traceroute 3 times and captured the results below:

>tracert 199.91.189.74

Tracing route to 199.91.189.74 over a maximum of 30 hops

1 73 ms 1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 10.124.136.1
3 * 14 ms * 24.156.137.205
4 39 ms * 9 ms 69.63.253.118
5 * * 25 ms 2150.ae1.bdr04.tor.man.teksavvy.com.packetflow.c
a [69.196.136.164]
6 41 ms 14 ms 10 ms tge6-1.fr3.yyz.llnw.net [208.111.134.237]
7 22 ms * * ae0-351.tor10.ip4.tinet.net [77.67.78.157]
8 24 ms 23 ms * xe-4-0-0.mtl10.ip4.tinet.net [141.136.108.190]
9 * 19 ms 20 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 30 ms 19 ms 19 ms 192.34.76.2
11 20 ms 22 ms * 199.91.189.234
12 * 20 ms 31 ms 199.91.189.74

Trace complete.

>tracert 199.91.189.74

Tracing route to 199.91.189.74 over a maximum of 30 hops

1 1 ms 1 ms <1 ms 192.168.1.1
2 8 ms 10 ms * 10.124.136.1
3 13 ms 12 ms 13 ms 24.156.137.205
4 8 ms 11 ms * 69.63.253.118
5 10 ms * 8 ms 2150.ae1.bdr04.tor.man.teksavvy.com.packetflow.c
a [69.196.136.164]
6 16 ms 11 ms 19 ms tge6-1.fr3.yyz.llnw.net [208.111.134.237]
7 20 ms 31 ms 21 ms ae0-351.tor10.ip4.tinet.net [77.67.78.157]
8 25 ms 23 ms * xe-4-0-0.mtl10.ip4.tinet.net [141.136.108.190]
9 39 ms 20 ms 20 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 22 ms * 18 ms 192.34.76.2
11 66 ms 19 ms 24 ms 199.91.189.234
12 19 ms * 21 ms 199.91.189.74

Trace complete.

>tracert 199.91.189.74

Tracing route to 199.91.189.74 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.1.1
2 23 ms 7 ms 7 ms 10.124.136.1
3 13 ms 10 ms 11 ms 24.156.137.205
4 12 ms 12 ms 10 ms 69.63.253.118
5 25 ms 11 ms * 2150.ae1.bdr04.tor.man.teksavvy.com.packetflow.c
a [69.196.136.164]
6 19 ms 11 ms 20 ms tge6-1.fr3.yyz.llnw.net [208.111.134.237]
7 27 ms * 45 ms ae0-351.tor10.ip4.tinet.net [77.67.78.157]
8 26 ms 23 ms 23 ms xe-4-0-0.mtl10.ip4.tinet.net [141.136.108.190]
9 * 19 ms 20 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 20 ms 19 ms 19 ms 192.34.76.2
11 22 ms 21 ms 20 ms 199.91.189.234
12 20 ms 19 ms 19 ms 199.91.189.74

Trace complete.

**Hollitz** · 10-30-2013 07:46 PM

Originally Posted by Folsom

ISP - Charter Communications
Coutnry - United States (Oregon)
Problem Times - Between 9am and 3pm Pacific Time
Reference Number - N/A

Note: The problem tends to slowly build up from 9am to 12pm, and then remains at its worst until about 2pm. It will generally drop off very quickly, though sometimes lasts until about 3pm. This seems to correlate with the times listed in the UK from other players.

I have Charter and I'm in the Midwest. Taking time zones into account, these are very close to the times when I start getting throttled as well.

**QuiKy** · 10-30-2013 08:54 PM

Name of ISP: Charter Communications
Country of Residence: USA
When does the problem occur: Occurs throughout the day, starting from 8am - 12am.
Reference number from your ISP: None yet but plan to.

Thread: Request for information: ISPs and P2P throttling

Thread Tools

Search Thread

Display