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