Request for information: ISPs and P2P throttling

[Chaddo19]

- Name of ISP : Telstra BigPond
- Country of Residence : Australia, New South Wales
- When does the problem occur : 9pm - 11:30pm GMT+10 every night since recently
- Reference number from your ISP, if you raised this matter with them : http://crowdsupport.telstra.com.au/t...t/false#M22145

[XenonZer0]

- Name of ISP: Comcast Cable
- Country of Residence: United States (Connecticut)
- When does the problem occur: All times of the day at 1-hour intervals

Unsure if this is actually the issue, but a consistent influx of 90k errors over the last three weeks has me curious.

[plasmacutter]

ISP: Comcast
Location: US - Bay area California
Occurs pretty much any time I log in these days (evenings and weekends pacific).

As you can see.. comcast treats it fairly decently at only 1ms per hop.. It reaches L3 which decides to play "cranky customs agent" and suddenly the packet drops occur.

Traceroute:

$ traceroute 199.91.189.46
traceroute to 199.91.189.46 (199.91.189.46), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  3.844 ms  0.837 ms  0.765 ms
 2  50.131.12.1 (50.131.12.1)  19.579 ms  8.915 ms  9.444 ms
 3  68.86.249.29 (68.86.249.29)  9.797 ms  9.367 ms  9.296 ms
 4  68.87.194.94 (68.87.194.94)  13.880 ms
    68.87.194.98 (68.87.194.98)  14.886 ms
    te-1-15-0-13-ar01.sfsutro.ca.sfba.comcast.net (68.86.143.42)  14.266 ms
 5  he-1-6-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.90.157)  16.106 ms  17.901 ms  16.754 ms
 6  50.242.148.34 (50.242.148.34)  13.910 ms  17.215 ms  13.068 ms
 7  vlan90.csw4.sanjose1.level3.net (4.69.152.254)  87.008 ms * *
 8  * * *
 9  * * *
10  * * *
11  ae-3-3.ebr1.chicago2.level3.net (4.69.132.62)  92.767 ms  85.903 ms  86.031 ms
12  * * *
13  ae-10-10.car2.montreal2.level3.net (4.69.153.86)  343.514 ms  125.283 ms  126.450 ms
14  ormuco-comm.car2.montreal2.level3.net (4.59.178.74)  86.381 ms  88.004 ms  87.446 ms
15  * * *
16  192.34.76.2 (192.34.76.2)  87.496 ms  91.199 ms  87.770 ms
17  * * *
18  * * *

[Akaris]

- Name of ISP : Verizon FIOS
- Country of Residence : United States of America
- When does the problem occur : Every night for the last few weeks. Mostly in instances but occasionally out in the world.

[BloodVixen]

ISP: AT&T High speed DSL

Residence: USA

Prognosis: Quite possibly a P2P throttling issue, since it only occurs playing FFXIV.

Symptoms: Random 90k messages during world exploration, or at a set 30 minute or 1 hour interval. Modem will disconnect from broadband service, and reconnect promptly. (Went through 4 different modems with my ISP, and 4 different technician visits over this problem. The likelihood of this being hardware/network defect would be beyond ridiculous.)

[champlaine]

- Verizon FIOS
- USA
- It started to happen once I switched from cable to FiOS.
- Reference # Chat ID 09111432490


Is this issue being taken care of lately? I called and we did a traceroute and found out that on line #5 there is a time out from your end.

[Saix_Serge]

ISP: At&t
Country: United States
I'll get random 2-3 second lag spikes ever so often in instances.
Has been happening the past few weeks, didn't ever happen any time before then.
It happens like clock work at 8:30 pm Central every night, and lasts till around 10 or 11 central every night, then is completely fine.

[RitzNBitz]

Hi! Can I ask what separate service is that?

Battleping

[kram]

Battleping

hmm ok, ill try. But I already tried wtfast and still the same. Is battleping different from wtfast?

[Aria_Stars]

I posted a separate thread but here's my info anyways:
ISP: Verizon FIOS
Location: New York, USA
Server: Balmung
Times: 7:30pm-10pm usually every day.

Culprit is tinet-gw.customer.alter.net (152.179.72.122) which connects MCI/Verizon's backbone and gtt.net

My thread is here: http://forum.square-enix.com/ffxiv/t...York?p=2445064

Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 5000 0 0.0 0 6 0 [172.30.42.1]
2 5000 0 0.0 1 373 9 L100.NYCMNY-VFTTP-82.verizon-gni.net [96.232.200.1]
3 5000 4 0.1 2 24 7 G0-12-4-4.NYCMNY-LCR-22.verizon-gni.net [100.41.200.240]
4 5000 1 0.0 3 145 17 ae2-0.NY5030-BB-RTR2.verizon-gni.net [130.81.199.170]
5 5000 5 0.1 2 192 15 0.so-0-0-0.XT2.NYC4.ALTER.NET [152.63.17.21]
6 506 0 0.0 3 21 11 TenGigE0-7-0-5.GW8.NYC4.ALTER.NET [152.63.25.230]
7 5000 247 4.9 3 91 20 tinet-gw.customer.alter.net [152.179.72.122]
8 2286 144 6.3 11 169 35 xe-4-2-0.mtl10.ip4.gtt.net [141.136.107.125]
9 5000 252 5.0 12 75 30 ormuco-gw.ip4.gtt.net [216.221.156.110]
10 5000 256 5.1 12 134 32 [192.34.76.2]
11 5000 247 4.9 12 528 31 [199.91.189.234]
12 4999 224 4.5 12 74 29 [199.91.189.30]

Getting sick of having to pay for services like WTFast to bypass this gtt.net bull$!@#. Verizon says tinet-gw.customer.alter.net is customer equipment that they cannot troubleshoot, and that the customer would have to call in a support request. gtt.net won't troubleshoot since i'm not the customer. SE? Are you the customer? Call it in.

Unfortunately that IP/device is customer equipment, it is their side
of their connection to our backbone. the GW hop prior to that device
is the last device on our network that we can troubleshoot.

The customer would need to call into 1-888-444-1111 to report a
repair/outage issue as we do not handle them at this address, only
change management.