dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
676
share rss forum feed


xalox

@verizon.net

Poor FIOS routing to Dallas/Texas area game servers

I have Verizon FIOS 50/25 in New York and Im getting horendous preformance to Dallas game servers. (Pinging better to West Coast/Eurpoe)

Typical trace

Tracing route to server2.smtpcentral.com.br [216.144.255.107]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 6 ms 6 ms L100.NYCMNY-VFTTP-165.verizon-gni.net [96.239.54
.1]
3 10 ms 11 ms 12 ms G0-11-3-7.NYCMNY-LCR-22.verizon-gni.net [130.81.
139.60]
4 6 ms 6 ms 6 ms so-5-0-0-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.22.18]
5 50 ms 11 ms 12 ms 0.xe-4-0-4.XT1.NYC4.ALTER.NET [152.63.10.61]
6 8 ms 9 ms 9 ms GigabitEthernet6-0-0.GW1.NYC4.ALTER.NET [152.63.
20.49]
7 60 ms 59 ms 59 ms teliasonera-gw.customer.alter.net [157.130.60.14
]
8 62 ms 86 ms 57 ms nyk-bb1-link.telia.net [213.155.131.136]
9 92 ms 139 ms 89 ms dls-bb1-link.telia.net [213.155.130.65]
10 133 ms 137 ms 131 ms limestone-ic-135964-dls-bb1.c.telia.net [213.248
.74.222]
11 134 ms 139 ms 136 ms te5-1.bdr1.core2.dllstx3.dallas-idc.com [208.115
.192.54]
12 132 ms 139 ms 136 ms ge0-2.vl89.cr01-68.dllstx3.dallas-idc.com [208.1
15.255.206]
13 125 ms 126 ms * server3.salvadormailling.com.br [216.144.255.98]
14 90 ms 94 ms 94 ms server2.smtpcentral.com.br [216.144.255.107]
Trace complete.

McBane

join:2008-08-22
Plano, TX

3 edits
Good thing I'm on fios in Dallas, but the server itself looks like it's getting high load or something:

mcbane@deimos ~ $ traceroute 216.144.255.107
traceroute to 216.144.255.107 (216.144.255.107), 30 hops max, 60 byte packets
1 L100.DLLSTX-VFTTP-26.verizon-gni.net (71.170.175.1) 2.463 ms 2.460 ms 2.447 ms
2 G0-3-2-3.DLLSTX-LCR-22.verizon-gni.net (130.81.138.180) 6.415 ms 6.420 ms 6.417 ms
3 so-5-0-0-0.DFW9-BB-RTR2.verizon-gni.net (130.81.199.36) 4.381 ms 4.397 ms ae4-0.DFW9-BB-RTR2.verizon-gni.net (130.81.199.66) 5.359 ms
4 0.ae3.XL4.DFW7.ALTER.NET (152.63.3.233) 5.378 ms 5.364 ms 5.357 ms
5 TenGigE0-7-4-0.GW4.DFW13.ALTER.NET (152.63.101.49) 7.331 ms TenGigE0-5-1-0.GW4.DFW13.ALTER.NET (152.63.101.62) 10.107 ms TenGigE0-7-0-0.GW4.DFW13.ALTER.NET (152.63.101.9) 10.311 ms
6 teliasonera-gw.customer.alter.net (63.65.123.46) 6.330 ms 4.331 ms 4.312 ms
7 limestone-ic-135964-dls-bb1.c.telia.net (213.248.74.222) 45.466 ms 44.697 ms 44.947 ms
8 te5-1.bdr1.core1.dllstx3.dallas-idc.com (208.115.192.50) 5.935 ms 5.902 ms 5.654 ms
9 ge0-1.vl88.cr01-68.dllstx3.dallas-idc.com (208.115.255.202) 5.897 ms ge0-2.vl89.cr01-68.dllstx3.dallas-idc.com (208.115.255.206) 8.523 ms 8.712 ms
10 server3.salvadormailling.com.br (216.144.255.98) 5.034 ms 5.063 ms 5.023 ms
11 server2.smtpcentral.com.br (216.144.255.107) 46.157 ms 45.396 ms 46.187 ms

5ms to 45ms on the server itself. That's a good indication of server load.

Have to admit though that is some pretty crappy routing dumping it on teliasonera for the NY to Dallas transit. I wonder if this is indication that Verizon is becoming the new Cogent with their routes.


birdfeedr
Premium,MVM
join:2001-08-11
Warwick, RI
kudos:9

1 edit
said by McBane:

10 server3.salvadormailling.com.br (216.144.255.98) 5.034 ms 5.063 ms 5.023 ms
11 server2.smtpcentral.com.br (216.144.255.107) 46.157 ms 45.396 ms 46.187 ms

5ms to 45ms on the server itself. That's a good indication of server load.

Whois says that block is owned by Limestone Networks with a Dallas admin address, however I think hop 10 is Limestone's gateway router in Dallas. Hop 11 is in Brazil. 40ms from Dallas to Brazil is probably right.

%rwhois V-1.5:003fff:00 rwhois.limestonenetworks.com (by Network Solutions, Inc. V-1.5.9.5)
network:Class-Name:network
network:ID:LSN-BLK-216.144.240.0/20
network:Auth-Area:216.144.240.0/20
network:Network-Name:LSN-216.144.240.0/20
network:IP-Network:216.144.255.96/27
network:IP-Network-Block:216.144.255.96 - 216.144.255.127
network:Organization-Name:Revenda Brasil
network:Organization-City:Contagem
network:Organization-State:OT
network:Organization-Zip:32315090
network:Organization-Country:BR
network:Tech-Contact;I:abuse@limestonenetworks.com
network:Admin-Contact;I:abuse@limestonenetworks.com
network:Updated-By:admin@limestonenetworks.com


xalox

@verizon.net
Is this a problem with my internet or a host side issue? I've talked to Verizon and they claim no responsibility


birdfeedr
Premium,MVM
join:2001-08-11
Warwick, RI
kudos:9
I think it's a transport issue. Except for the 50ms hiccup at your hop 5 (and I think you can ignore that one), the verizon transport is good until it hits teliasonera gateway at hop 7. I don't have the time to lookup geolocation on each hop, but one explanation may be the gateway is saturated. Another explanation is your traffic is going to europe before it comes back to dallas.

Research the geolocation. That may be the clue.

McBane

join:2008-08-22
Plano, TX
reply to xalox
You *MIGHT* have more luck if you post this in the VZ Direct forum. Those guys may be able to forward it over to the VZ Neteng team to tune the routes. Otherwise your best bet is to complain to the server admins to see if Limestone can tune their routes.

Also just because those hostnames have a .br on them doesn't necessarily mean they are in Brazil. In fact with those response times I'm pretty sure they're US based.

propcgamer

join:2001-10-10
011010101
reply to xalox
Contact the game server host.

Considering the latency jumps at the last hop tells me its either their server, or the return route to you.