Out of curiosity, I tried it from my location (Clearwater, FL):
traceroute to 70.42.29.65 (70.42.29.65), 15 hops max, 40 byte packets
1 L100.TAMPFL-VFTTP-141.verizon-gni.net (96.254.154.1) 1.167 ms 0.842 ms 0.711 ms
2 G0-9-3-0.TAMPFL-LCR-22.verizon-gni.net (130.81.140.74) 1.244 ms 1.148 ms 1.154 ms
3 * * *
4 so-4-1-0-0.ATL01-BB-RTR2.verizon-gni.net (130.81.19.60) 17.899 ms 94.251 ms 59.924 ms
5 0.ge-7-1-0.XT2.ATL4.ALTER.NET (152.63.81.1) 18.205 ms 18.111 ms 18.101 ms
6 0.so-6-0-1.XL4.IAD8.ALTER.NET (152.63.36.209) 34.947 ms 33.366 ms 34.675 ms
7 GigabitEthernet7-0-0.GW8.IAD8.ALTER.NET (152.63.33.17) 36.455 ms 36.480 ms 35.486 ms
8 tinet-gw.customer.alter.net (152.179.50.30) 34.230 ms 35.677 ms 34.226 ms
9 xe-3-3-0.tor10.ip4.tinet.net (141.136.110.9) 61.557 ms 68.727 ms 61.522 ms
10 internap-gw.ip4.tinet.net (77.67.70.94) 55.093 ms 54.909 ms 59.469 ms
11 border1.te7-1-bbnet1.tor001.pnap.net (70.42.24.132) 53.845 ms 53.923 ms 53.845 ms
12 70.42.29.65 (70.42.29.65) 56.013 ms 56.310 ms 56.335 ms
I don't think you will have any success with Verizon support since it seems the problem is more on your particular tinet point - on tinets side