routing issues with gtt.net and Verizon in New York

[Aria_Stars]

So I'm on Verizon FiOS and there's a router between Verizon and gtt.net backbones that acts up EVERY day between around 7:30pm EST and 10pm EST with dropped pings, packet loss, and lag spikes. I'm getting fed up emailing both ISP's, this seems like an issue SE needs to have fixed on their end as I'm getting nowhere with them. I'm 100% positive this is not an issue on my end.

The culprit is tinet-gw.customer.alter.net (152.179.72.122) which connects alter.net (MCI/Verizon) and gtt.net which then goes to the FFXIV servers.

This has been going on for far too long and I'm getting sick of having to use proxy services like WTFast to bypass this route. Is this another one of those "Verizon wants more money for the increased traffic" situations like Netflix?

Target Name: N/A
IP: 199.91.189.30 (Balmung)
Date/Time: 9/16/2014 7:29:55 PM to 9/16/2014 10:12:01 PM

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]

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.

Edit: and here's a pretty graph showing this BS

[Squa11_Leonhart]

Verizon is fobbing you off mate, its up to them to follow up and/or correct routing issues.

[joelvelez93]

Verizon is fobbing you off mate, its up to them to follow up and/or correct routing issues.

^^^^ This.

[TeaTimeBear]

To many answers with no precise recommendation. I had this with comcast then swapped to verison.. Still had it. I finally just got purevpn and fixed everything by using. If you're fed up and on PC then this is about the only real solution I could find. If you're on ps3/4 then the same applies. Forum users will lead you in circles just as much as our ISP/SE. It's either VPN or quit or.. Wait till it finally gets mysteriously fixed.

Edit: this problem affects many ISP's it goes so deep I don't know if anyone knows WHAT exactly causes. http://forum.square-enix.com/ffxiv/t...and-catches-up is proof enough and so is that sticky topic.

[joelvelez93]

To many answers with no precise recommendation. I had this with comcast then swapped to verison.. Still had it. I finally just got purevpn and fixed everything by using. If you're fed up and on PC then this is about the only real solution I could find. If you're on ps3/4 then the same applies. Forum users will lead you in circles just as much as our ISP/SE. It's either VPN or quit or.. Wait till it finally gets mysteriously fixed.

Using a VPN is risky, all your info passing through another persons filters. I mean, if it works it works, but keep in mind that it is a security risk. You may want to add a token beforehand to be safe.

[TeaTimeBear]

Using a VPN is risky, all your info passing through another persons filters. I mean, if it works it works, but keep in mind that it is a security risk. You may want to add a token beforehand to be safe.

Tokened since day 1 ;P. But I get what you're saying.

[joelvelez93]

Good! Aha. Well, I've heard a lot of people getting around stuff like this by using a VPN, so if the shoe fits

[Sonoran]

To many answers with no precise recommendation. I had this with comcast then swapped to verison.. Still had it. I finally just got purevpn and fixed everything by using. If you're fed up and on PC then this is about the only real solution I could find. If you're on ps3/4 then the same applies. Forum users will lead you in circles just as much as our ISP/SE. It's either VPN or quit or.. Wait till it finally gets mysteriously fixed.

Edit: this problem affects many ISP's it goes so deep I don't know if anyone knows WHAT exactly causes. http://forum.square-enix.com/ffxiv/t...and-catches-up is proof enough and so is that sticky topic.

This, Ive had issues for months with 90K issues and 90002 disconnects, trust me I tried EVERYTHING to fix it and spent quite a bit of $$, it was not on my end or Comcast, it was simply the routing to the server in Montreal. Im using a VPN service now and I have not had 1 disconnect since. I know WTFast seems to have worked for a lot of people, I tried it but didnt fix the disconnect problem, just improved ping a little.

[Raist]

Verizon is fobbing you off mate, its up to them to follow up and/or correct routing issues.

This... clear and simple.

Your ISP has control of who they partner with for peering/transit to get you from their network into Ormuco (SE's ISP). They are the ones with the means to influence those third (and sometimes 4th) parties in between that are being shown more and more frequently to have a share of responsibility for our routing problems. If they can't get those outside parties to clean up their network issues, they should have at LEAST two other options available (in the US, the major ISP's are required to have a minimum of 3 providers for this task).

Last night, TATA's packet losses/delays were steadily on the rise between Virginia and Toronto (a little between Toronto and Montreal, but it was mostly getting across the border). We even saw it showing up in the forwarding tests with pathping, crossing the 12% threshold at times, resulting in regular ping spikes up over 300ms (normally under 80 even in busy times). Reported the results of my traces to TWC, and shortly after midnight they bounced my modem. I am now on Cogent again, and have <70ms response times once again.

There IS something your ISP can do for you. Do NOT take no for an answer... it may take persistence to get escalation to a higher tier of support before it happens (need to be in touch with at least Tier3), but they CAN and are SUPPOSED to do something about it. If they repeatedly refuse, report them to your local regulatory authority. Contact details are supposed to be included with your bill.

Edit:
Oh, and btw... TiNet (original owner of those lines just before Ormuco, rebranded a few times--most recently to GTT a while back-- but the networks still have issues) was often reported for having issues with their routing. The FQDN's are still used even though the company has been sold, and you can see them come up often when you google them for packet loss issues with different games. Comes up less often for the NA players of this game because they aren't that big a player for the CA/US border... but you can see it come up a lot on the international scene.

[Aria_Stars]

This... clear and simple.

Your ISP has control of who they partner with for peering/transit to get you from their network into Ormuco (SE's ISP). They are the ones with the means to influence those third (and sometimes 4th) parties in between that are being shown more and more frequently to have a share of responsibility for our routing problems. If they can't get those outside parties to clean up their network issues, they should have at LEAST two other options available (in the US, the major ISP's are required to have a minimum of 3 providers for this task).

Last night, TATA's packet losses/delays were steadily on the rise between Virginia and Toronto (a little between Toronto and Montreal, but it was mostly getting across the border). We even saw it showing up in the forwarding tests with pathping, crossing the 12% threshold at times, resulting in regular ping spikes up over 300ms (normally under 80 even in busy times). Reported the results of my traces to TWC, and shortly after midnight they bounced my modem. I am now on Cogent again, and have <70ms response times once again.

There IS something your ISP can do for you. Do NOT take no for an answer... it may take persistence to get escalation to a higher tier of support before it happens (need to be in touch with at least Tier3), but they CAN and are SUPPOSED to do something about it. If they repeatedly refuse, report them to your local regulatory authority. Contact details are supposed to be included with your bill.

Edit:
Oh, and btw... TiNet (original owner of those lines just before Ormuco, rebranded a few times--most recently to GTT a while back-- but the networks still have issues) was often reported for having issues with their routing. The FQDN's are still used even though the company has been sold, and you can see them come up often when you google them for packet loss issues with different games. Comes up less often for the NA players of this game because they aren't that big a player for the CA/US border... but you can see it come up a lot on the international scene.

Thanks, this sheds a lot of light on this issue. Verizon using cheap routing solutions... thinking of just switching ISP's cause I'm getting fed up with them. Last person I called at verizon said "we don't support games" LOL... yeah it's gonna take a long time to get through with someone knowledgeable about routing.