| [Northeast] Fios Routing issues Short Version: How do I get Verizon to adjust routing?
_
Long Version:
I've been having awful latency to my current game of choice since Tuesday the 15th. After a little discussion with the games support I was able to track down the likely cause. I'm in Pittsburgh, the server in question is in Toronto, only ~300 miles away. But apperently I have to go to Germany to get there (wtf!)
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home xxxxxxx
2 8 ms 7 ms 5 ms L100.PITBPAxxxxx
3 8 ms 9 ms 8 ms G0-1-1-6.PITBPA-LCR-22.verizon-gni.net [130.81.212.58]
4 15 ms 18 ms 43 ms xe-0-1-6-0.PHIL-BB-RTR2.verizon-gni.net [130.81.209.76]
5 19 ms 18 ms 19 ms xe-9-1-4-0.NY5030-BB-RTR2.verizon-gni.net [130.81.23.70]
6 20 ms 18 ms 20 ms 0.so-0-0-0.XT2.NYC4.ALTER.NET [152.63.17.21]
7 21 ms 22 ms 23 ms TenGigE0-5-0-0.GW8.NYC4.ALTER.NET [152.63.21.65]
8 115 ms 111 ms 136 ms tinet-gw.customer.alter.net [152.179.72.122]
100 extra MS!
9 153 ms 150 ms 150 ms xe-4-3-0.tor10.ip4.tinet.net [89.149.184.110]
Is this IP actually in Germany?!
10 141 ms 139 ms 144 ms internap-gw.ip4.tinet.net [77.67.70.94]
Is this IP actually in Germany part2?!
11 134 ms 136 ms 232 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]
12 145 ms 136 ms 130 ms 70.42.29.65
Terrible performance at tinet-gw.customer.alter.net [152.179.72.122]
seems like a common problem after doing some googling, and ironically the extra latency to get to that server seems worse than going to europe and back.
The game in question does not play well with any proxy services I've tried so far, and even if I do find one that works I really don't want to spend more money if I don't have to.
I had a very unproductive discussion with Verizon's online support; and found some individuals with similar problems on Verizon's forums. Any thoughts would be really appreciated. |
|
guppy_fishPremium
join:2003-12-09
Lakeland, FL
kudos:1 Reviews:
 ·Verizon FiOS
| That looks like the peering point for tinet, they will only get what they payfor and looks like there overloaded. Verizon can only push or pull as much data as the peering path allows by the customer
This isn't Verizon's issue, its the routing the game servers have paid for, either with the game server ISP or next level up. |
|
| same probs here in syracuse NY same time roughly.
what can we do about it?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Tracing route to 68.232.177.102.choopa.net [68.232.177.102]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 6 ms 4 ms L100.SYRCNY-VFTTP-13.verizon-gni.net [71.176.109
.1]
3 6 ms 4 ms 4 ms G9-1-213.SYRCNY-LCR-02.verizon-gni.net [130.81.9
7.252]
4 72 ms 13 ms 13 ms P15-3.CLPPVA-LCR-02.verizon-gni.net [130.81.28.1
86]
5 17 ms 38 ms 23 ms 0.so-6-1-0.XT1.NYC9.ALTER.NET [152.63.9.253]
6 * * 38 ms 0.ge-5-2-0.XL3.CHI13.ALTER.NET [152.63.64.217]
7 78 ms 78 ms 79 ms TenGigE0-4-0-2.GW5.CHI13.ALTER.NET [152.63.69.14
9]
8 81 ms 76 ms 77 ms nlayer.customer.alter.net [63.84.100.186]
9 82 ms 81 ms 78 ms ae1-50g.cr2.ord1.us.nlayer.net [69.31.111.137]
10 81 ms 80 ms 80 ms ae2-20g.ar1.ord6.us.nlayer.net [69.31.110.254]
11 41 ms 40 ms 39 ms as20473.xe-3-0-5.ar1.ord6.us.nlayer.net [69.31.1
11.54]
12 77 ms 77 ms 77 ms 68.232.177.102.choopa.net [68.232.177.102]
Trace complete. |
|
Reviews:
·Verizon FiOS
 ·CenturyLink
| reply to guppy_fish
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 |
|
