- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So I started having this problem about 2-3 weeks ago. I play on a server for a game APB Reloaded. The IP for this server is US-West 173.195.32.254. This server is obviously in the US. I never had problems before as I used to be around 40-80ms connection wise. Recently however I've been around 150-200ms. The problem is when I run a tracert I am now routed to Europe before coming back to the US which makes no sense. I would be so grateful if someone could fix this routing issue. Tracert is below.
Tracing route to 173.195.32.254 over a maximum of 30 hops
1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 4 ms 16 ms L100.DLLSTX-VFTTP-60.verizon-gni.net [96.226.238.1]
3 8 ms 7 ms 8 ms G0-9-1-0.DLLSTX-LCR-21.verizon-gni.net [130.81.183.22]
4 8 ms 6 ms 6 ms so-4-1-0-0.DFW9-BB-RTR1.verizon-gni.net [130.81.151.242]
5 8 ms 6 ms 6 ms 0.xe-4-0-0.XL4.DFW7.ALTER.NET [152.63.103.54]
6 11 ms 11 ms 8 ms TenGigE0-7-2-0.GW4.DFW13.ALTER.NET [152.63.101.29]
7 95 ms 96 ms 101 ms teliasonera-gw.customer.alter.net [63.65.123.46]
8 136 ms 144 ms 144 ms las-bb1-link.telia.net [213.155.131.77]
9 147 ms 149 ms 139 ms k2network-ic-140087-las-bb1.c.telia.net [213.248.79.246]
10 131 ms 136 ms 136 ms ten1-1-bor1-idc.gamersfirst.com [173.195.32.70]
11 * * * Request timed out.
12 190 ms 148 ms 146 ms 173.195.32.254
Trace complete.
As you can see a problem occurs at line 7 with the US IP 63.65.123.46. It appears to be a broken DNS or something. I would like it if someone could change my routing or fix that server. If you notice afterwards in line 8 I am then routed to Europe with the IP 213.155.131.77. There is no reason for me to be routed to Europe to come back to the US. This has been a very frustrating issue. Nobody on phone tech support can help me or even knows what the hell I am talking about. All they do is try and spam me with 20$ charges for their "premium computer support". No matter how many times I try and explain that it's not a problem with my computer. Someone please help so I can sleep at night!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
those servers are managed at NOC levels, and so the problem will likely fix itself.
that is a router that probably needs more capacity. or just getting a little peak time traffic. I would wait, the internet uses a shortest path, fastest path algorithm, so whatever routers are in your area or after that DFW hop, are probably having trouble, and that is why you got shot over to teliasonera.
you can try this.
The trick to this next set of instructions is to leave your router off for about 5+ minutes. anything short runs the risk of getting the same ip address, and you don't want that. you want a new ip and a new route.
- release your DHCP lease
- Quickly uplug your router after you release it.
- leave it off 5-10 minutes
- turn it back on and test.
@BrIIcE wrote:So I started having this problem about 2-3 weeks ago. I play on a server for a game APB Reloaded. The IP for this server is US-West 173.195.32.254. This server is obviously in the US. I never had problems before as I used to be around 40-80ms connection wise. Recently however I've been around 150-200ms. The problem is when I run a tracert I am now routed to Europe before coming back to the US which makes no sense. I would be so grateful if someone could fix this routing issue. Tracert is below.
Tracing route to 173.195.32.254 over a maximum of 30 hops
1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 4 ms 16 ms L100.DLLSTX-VFTTP-60.verizon-gni.net [96.226.238.1]
3 8 ms 7 ms 8 ms G0-9-1-0.DLLSTX-LCR-21.verizon-gni.net [130.81.183.22]
4 8 ms 6 ms 6 ms so-4-1-0-0.DFW9-BB-RTR1.verizon-gni.net [130.81.151.242]
5 8 ms 6 ms 6 ms 0.xe-4-0-0.XL4.DFW7.ALTER.NET [152.63.103.54]
6 11 ms 11 ms 8 ms TenGigE0-7-2-0.GW4.DFW13.ALTER.NET [152.63.101.29]
7 95 ms 96 ms 101 ms teliasonera-gw.customer.alter.net [63.65.123.46]
8 136 ms 144 ms 144 ms las-bb1-link.telia.net [213.155.131.77]
9 147 ms 149 ms 139 ms k2network-ic-140087-las-bb1.c.telia.net [213.248.79.246]
10 131 ms 136 ms 136 ms ten1-1-bor1-idc.gamersfirst.com [173.195.32.70]
11 * * * Request timed out.
12 190 ms 148 ms 146 ms 173.195.32.254
Trace complete.As you can see a problem occurs at line 7 with the US IP 63.65.123.46. It appears to be a broken DNS or something. I would like it if someone could change my routing or fix that server. If you notice afterwards in line 8 I am then routed to Europe with the IP 213.155.131.77. There is no reason for me to be routed to Europe to come back to the US. This has been a very frustrating issue. Nobody on phone tech support can help me or even knows what the hell I am talking about. All they do is try and spam me with 20$ charges for their "premium computer support". No matter how many times I try and explain that it's not a problem with my computer. Someone please help so I can sleep at night!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I still haven't received a message back from telasionera. Still can't get any help from verizon either. What's weird is it seems to fix itself at PEAK HOURS? Which is opposite of how I would think it'd work. I work nightshift so I get off work and play in the mornings. Up till around 4 in the afternoon my time the connection is broken. After that though its fixed till early morning. Then it's broken again. I've changed my ip several times with no positive affect. It was even worse one time i changed it. It takes the same route every time.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So when looking into this further with telasionera this has to be a problem with verizon. At this line 6 11 ms 11 ms 8 ms TenGigE0-7-2-0.GW4.DFW13.ALTER.NET [152.63.101.29] I get pointed to Europe. I am connecting to servers in the US. There is no reason for me to be pointed to Europe. ALTER.NET is the verizon network correct? I really need some assistance from verizon personnel. The phone support and online support just read scripts and have no idea what I'm talking about.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I can tell you that you are not getting to Europe. You're going through some problematic links as recently mentioned during non-peak hours. A back of my mind educated guess is a misconfigured router someplace at the peering between Telia and Verizon that is not load balancing circuits properly. At work, which happens to be a datacenter, our fastest route to Europe scores 70ms from me (Western NY area) to London. 8ms delay between me and New York City using the fastest fiber run. Between the Datacenter and Los Angeles, CA can be anywhere from 60ms to 90ms depending on the route and providers we must go through. Awesome for gaming, that's for sure. Going from Dallas to Europe would score at least 140ms latency with how Verizon routes. A return route going to Los Angeles would result in nearly 280ms of latency, which is what I score to Australia from my home on DSL.
Either way, you're going to need to get both companies to get a backbone network engineer to take a look at the network. Keep in mind too, alter.net is UUNET/Verizon Business, so residential support will give you some trouble with alter.net hops until you get to the right person. DNS also does not affect your route unless you're dealing with AnyCast IPs often found in CDNs. Game servers don't operate within CDNs by design.
So, I have no idea where the route to Europe is coming from here but I'm failing to see it. Your latency would be a lot worse. Upon reflection, here's a trace to that game server from my home DSL connection.
Tracing route to 173.195.32.254 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.3.1
2 7 ms 6 ms 6 ms 10.41.15.1
3 6 ms 6 ms 6 ms P1-0.BFLONY-LCR-01.verizon-gni.net [130.81.195.144]
4 17 ms 17 ms 17 ms so-6-3-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.28.138]
5 22 ms 23 ms 21 ms 0.xe-8-1-0.XL3.NYC1.ALTER.NET [152.63.5.213]
6 21 ms 22 ms 26 ms 0.xe-2-1-1.XT1.NYC4.ALTER.NET [152.63.20.237]
7 20 ms 27 ms 20 ms GigabitEthernet4-0-0.GW1.NYC4.ALTER.NET [152.63.20.97]
8 20 ms 19 ms 19 ms teliasonera-gw.customer.alter.net [157.130.60.14]
9 20 ms 20 ms 20 ms nyk-bb2-link.telia.net [213.155.131.138]
10 106 ms 107 ms 153 ms las-bb1-link.telia.net [80.91.252.165]
11 108 ms 106 ms 115 ms k2network-ic-140087-las-bb1.c.telia.net [213.248.79.246]
12 109 ms 108 ms 107 ms ten1-1-bor1-idc.gamersfirst.com [173.195.32.70]
13 * * * Request timed out.
14 109 ms 110 ms 110 ms 173.195.32.254
Trace complete.
It's more specific to your area I'm afraid. You may want to see if other connections give the same sign. That helps add weight onto Verizon and lessens it from Telia. Telia can help get Verizon to fix the problem though if their Operations Center contacts them about poor routing performance if it does not match what their peering agreements or Service Level Agreements call for.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oh, if that's the case then sorry for the Europe confusion. I was just doing an IP lookup of the hops. http://www.itistimed.com/what-is-my-ip/ip-location/MX/213.155.131.138/?m=2. Game server again and some others. There are actually 2 game servers. I play on the west coast server which is the first tracert. I'll put up a tracert of the east coast server second. Everytime I connect to teliasonera I go from 9 to 100ms. Whenever I'm not routed through teliasonera it's fine. If anyone has some ideas of what else I should tracert then throw them at me.
West Coast
Tracing route to 173.195.32.254 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms L100.DLLSTX-VFTTP-60.verizon-gni.net [96.226.238.1]
3 4 ms 4 ms 4 ms G0-9-1-1.DLLSTX-LCR-22.verizon-gni.net [130.81.183.90]
4 6 ms 7 ms 4 ms so-4-1-0-0.DFW9-BB-RTR2.verizon-gni.net [130.81.151.244]
5 8 ms 7 ms 7 ms 0.xe-4-1-0.XL4.DFW7.ALTER.NET [152.63.5.145]
6 9 ms 10 ms 9 ms TenGigE0-7-1-0.GW4.DFW13.ALTER.NET [152.63.101.25]
7 101 ms 99 ms 87 ms teliasonera-gw.customer.alter.net [63.65.123.46]
8 144 ms 139 ms 129 ms las-bb1-link.telia.net [213.155.134.124]
9 142 ms 124 ms 125 ms k2network-ic-140087-las-bb1.c.telia.net [213.248.79.246]
10 121 ms 119 ms 122 ms ten1-1-bor1-idc.gamersfirst.com [173.195.32.70]
11 * * * Request timed out.
12 134 ms 139 ms 144 ms 173.195.32.254
Trace complete
East Coast
Tracing route to 173.195.39.254 over a maximum of 30 hops
1 <1 ms <1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 22 ms L100.DLLSTX-VFTTP-60.verizon-gni.net [96.226.238.1]
3 4 ms 4 ms 4 ms G0-9-1-1.DLLSTX-LCR-22.verizon-gni.net [130.81.183.90]
4 58 ms 44 ms 4 ms so-4-1-0-0.DFW9-BB-RTR2.verizon-gni.net [130.81.151.244]
5 8 ms 7 ms 12 ms 0.xe-4-1-1.XL3.DFW7.ALTER.NET [152.63.5.173]
6 11 ms 12 ms 9 ms TenGigE0-4-0-0.GW4.DFW13.ALTER.NET [152.63.97.177]
7 108 ms 109 ms 104 ms teliasonera-gw.customer.alter.net [63.65.123.46]
8 156 ms 147 ms 144 ms ash-bb1-link.telia.net [80.91.252.121]
9 148 ms 132 ms 124 ms k2network-ic-146432-ash-bb1.c.telia.net [213.248.96.186]
10 116 ms 117 ms 124 ms ten1-1-bor1-was.gamersfirst.com [173.195.38.70]
11 131 ms 139 ms 147 ms 173.195.38.4
12 127 ms 132 ms 139 ms 173.195.39.254
Trace complete.
Tracing route to ea.com [98.129.150.221]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 4 ms 4 ms 4 ms L100.DLLSTX-VFTTP-60.verizon-gni.net [96.226.238.1]
3 3 ms 7 ms 7 ms G0-9-1-0.DLLSTX-LCR-21.verizon-gni.net [130.81.183.22]
4 6 ms 7 ms 7 ms so-4-1-0-0.DFW9-BB-RTR1.verizon-gni.net [130.81.151.242]
5 6 ms 7 ms 7 ms 0.xe-4-0-0.XL4.DFW7.ALTER.NET [152.63.103.54]
6 9 ms 9 ms 9 ms TenGigE0-5-1-0.GW4.DFW13.ALTER.NET [152.63.101.62]
7 121 ms 109 ms 109 ms teliasonera-gw.customer.alter.net [63.65.123.46]
8 109 ms 109 ms 109 ms rackspace-ic-127247-dls-bb1.c.telia.net [213.248.88.174]
9 111 ms 109 ms 112 ms corea.dfw1.rackspace.net [74.205.108.50]
10 112 ms 112 ms 109 ms core7.dfw1.rackspace.net [74.205.108.15]
11 112 ms 109 ms 109 ms aggr502a-2-core7.dfw1.rackspace.net [98.129.84.23]
12 111 ms 109 ms 109 ms 98.129.150.221
Trace complete.
Tracing route to gamefront.com [216.69.227.108]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 12 ms 7 ms L100.DLLSTX-VFTTP-60.verizon-gni.net [96.226.238.1]
3 22 ms 4 ms 4 ms G0-9-1-0.DLLSTX-LCR-22.verizon-gni.net [130.81.183.88]
4 6 ms 7 ms 7 ms so-5-0-0-0.DFW9-BB-RTR2.verizon-gni.net [130.81.199.36]
5 6 ms 7 ms 7 ms 152.63.4.17
6 7 ms 7 ms 7 ms 208.175.175.37
7 6 ms 7 ms 7 ms pr2-ge-7-0-0.daq.savvis.net [204.70.207.182]
8 20 ms 7 ms 7 ms cr1-tengig0-7-5-0.Dallas.savvis.net [204.70.200.170]
9 41 ms 42 ms 42 ms bhr1-ge-13-1.sterling2dc3.savvis.net [204.70.204.114]
10 43 ms 42 ms 43 ms hr2-te-1-0-0.elsegundola1.savvis.net [204.70.203.89]
11 42 ms 42 ms 42 ms das1-v3007.la1.savvis.net [64.70.11.58]
12 48 ms 44 ms 44 ms 216.69.227.108
13 41 ms 44 ms 42 ms 216.69.227.108
Trace complete.
Tracing route to twitter.com [199.59.150.39]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 3 ms 4 ms 4 ms L100.DLLSTX-VFTTP-60.verizon-gni.net [96.226.238.1]
3 6 ms 4 ms 7 ms G0-9-1-0.DLLSTX-LCR-21.verizon-gni.net [130.81.183.22]
4 6 ms 7 ms 7 ms so-4-1-0-0.DFW9-BB-RTR1.verizon-gni.net [130.81.151.242]
5 54 ms 7 ms 7 ms 152.63.4.21
6 7 ms 7 ms 7 ms ae7.edge2.dallas3.level3.com [4.68.62.33]
7 14 ms 7 ms 17 ms vlan90.csw4.Dallas1.Level3.net [4.69.145.254]
8 6 ms 7 ms 7 ms ae-93-93.ebr3.Dallas1.Level3.net [4.69.151.170]
9 29 ms 29 ms 29 ms ae-7-7.ebr3.Atlanta2.Level3.net [4.69.134.22]
10 31 ms 29 ms 29 ms ae-63-63.ebr1.Atlanta2.Level3.net [4.69.148.242]
11 29 ms 29 ms 29 ms ae-1-51.edge1.Atlanta4.Level3.net [4.69.150.15]
12 30 ms 29 ms 29 ms TWITTER-INC.edge1.Atlanta4.Level3.net [4.53.233.42]
13 68 ms 67 ms 67 ms ae60.sjc2-cr2.twttr.com [199.16.159.82]
14 71 ms 72 ms 77 ms xe-1-0-0.smf1-er2.twttr.com [199.16.159.41]
15 76 ms 77 ms 77 ms r-199-59-150-39.twttr.com [199.59.150.39]
Trace complete.