dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
8

guppy_fish
Premium Member
join:2003-12-09
Palm Harbor, FL

guppy_fish to Photon1701

Premium Member

to Photon1701

Re: [Northeast] Fios Routing issues

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.

The Engine
@verizon.net

The Engine

Anon

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.
chomper87
join:2012-02-22
Clearwater, FL

chomper87 to guppy_fish

Member

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