Problem solved. Dustbowl NY1 & NY2 Bad Lag and Horrible Ping

Xtreme2damax

Xtreme2damax

Gore-Spattered Heavy
I am pinging over 100ms to the Dustbowl NY servers today. Normally I ping around 20ms - 25ms, my ping should actually be 15ms but goes up by 10ms - 15ms once more players are on. I've been experiencing lag on these servers but today is by far the worst. My ping to other servers is normal, with this ping I might as well play on the LA servers.

Proof:

21f0f9u.jpg
 
Xtreme2damax

Xtreme2damax

Gore-Spattered Heavy
I wish I knew what the problem was and I am not certain if it's my isp or something else. I have Verizon Fios so I shouldn't be experiencing such high ping. Not much I can do other than try rebooting my router and ont but I have a feeling that won't work.
 
Xtreme2damax

Xtreme2damax

Gore-Spattered Heavy
If I was seeding anything. No active downloads or uploads going, pc is completely clean, fiber optic internet. I am puzzled as to what the problem could be.
 
Xtreme2damax

Xtreme2damax

Gore-Spattered Heavy
So it does seem to be bad routing. For some reason the route is going all the way near Texas and back to NY. At least that is what Pingtest is showing when it selects the best server for me. :confused:

It's showing my location being in the midwest when I am actually in Central New York. Not sure how that works but it looks like I will be contacting my isp. Anyways sorry once again for a bogus report. Seems I just can't escape my bad luck with any isp.

My traceroute:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\<redacted>>tracert 108.61.46.50

Tracing route to 108.61.46.50.choopa.net [108.61.46.50]
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.SYRCNY-VFTTP-06.verizon-gni.net [72.90.76.1
]
3 6 ms 4 ms 4 ms G5-0-2-116.SYRCNY-LCR-01.verizon-gni.net [130.81
.177.122]
4 45 ms 45 ms 44 ms P11-0-0.SYRCNY-LCR-02.verizon-gni.net [130.81.27
.109]
5 38 ms * * P15-3.CLPPVA-LCR-02.verizon-gni.net [130.81.28.1
86]
6 51 ms * 50 ms xe-8-0-4-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
23.103]
7 * * * Request timed out.
8 50 ms 49 ms 49 ms GigabitEthernet7-0-0.GW8.IAD8.ALTER.NET [152.63.
33.17]
9 118 ms 122 ms 119 ms 63.88.105.94
10 138 ms 130 ms 132 ms tengige0-14-0-3.nyktr1.NewYork.opentransit.net [
193.251.241.213]
11 127 ms 125 ms 126 ms choopa.GW.opentransit.net [193.251.251.102]
12 144 ms 145 ms 136 ms ve67-br1.pnj1.choopa.net [108.61.93.109]
13 120 ms 118 ms 127 ms 108.61.92.162.choopa.net [108.61.92.162]
14 122 ms 121 ms 124 ms 108.61.46.50.choopa.net [108.61.46.50]

Trace complete.
Click to expand...
 
Xtreme2damax

Xtreme2damax

Gore-Spattered Heavy
Yeah, I've been having isp problems..sigh. However this morning my latency to other NY non-skial servers is back to normal but I am still pinging between 80ms - 100ms+ to the Dustbowl NY servers.

2j1jvow.jpg
 
Xtreme2damax

Xtreme2damax

Gore-Spattered Heavy
Well I thought I would reply back about this issue. The reason my ping is as high as it is, is because I am being routed through Culpeper, VA and back up to NY. I think something changed in regards to routing on the end of the host because my ping to other NY and NJ servers is fine, nowhere near as high as it is to the Skial Dustbowl NY servers.

So it is a server/host issue, not invalid it seems.
 
KillerZebra

KillerZebra

Forum Admin
Contributor
i am going to move this to technology. since this report isn't valid and its just your connection there is no reason for it to be here.
 
Xtreme2damax

Xtreme2damax

Gore-Spattered Heavy
It is valid, this appears to be related to routing on the hosts end. My ping is fine to other NY and NJ servers as I said, but there is some routing issue with the host's isp that is causing me to take a longer route to the server. It's just the Skial Dustbowl NY servers, pretty sure now that my connection isn't the culprit especially since it's been more than a week this has been ongoing. I've ran multiple speed tests, ping tests and traceroutes and all check out fine, just that my ping to only the NY Dustbowl servers has went to crap.

2ik4oqq.png


Outlined in white is the other NY/NJ servers. Outlined in red is the Dustbowl NY1 and NY2 servers. I ping normally to all other servers not outlined. This does not seem to be an issue with my isp.
 
takethepants

takethepants

Australian Skial God
Contributor
AFAIK that drunkenbombers server is on California. Also, I've run a few tests, and I don't see that we can do anything on our end. Maybe Bot can bring it up to the provider and then they would have to talk to verizon. Your last traceroute shows it going from 6 to 45ms within Verizon's network. So they have a bottleneck there. That's 45ms of ping that we can't do anything about. That number should be in the single digits. Just for kicks, have you tried changing your router's DNS to Google's or OpenDNS? Because it looks like it's hitting a Verizon DNS server and that's what's taking a while for some reason.
 
Xtreme2damax

Xtreme2damax

Gore-Spattered Heavy
takethepants said:
AFAIK that drunkenbombers server is on California.
Click to expand...

Are you sure? I think they have several servers, that one is on the east coast and is listed in the server browser as an east coast server. I don't think my ping would be 13ms to a server in CA when I am located in Central New York.

takethepants said:
Just for kicks, have you tried changing your router's DNS to Google's or OpenDNS?
Click to expand...

Yes I've tried everything including OpenDNS, Google Public DNS, shutting down my router to obtain a new ip/route, reboot my ont etc.. Verizon was having some issues on the east coast but those issues have been addressed.

This is my speed test:

2479090954.png


This is my ping test:

 
PsychoRealm

PsychoRealm

Australian Skial God
Contributor
takethepants said:
Your last traceroute shows it going from 6 to 45ms within Verizon's network. So they have a bottleneck there. That's 45ms of ping that we can't do anything about.
Click to expand...
I have perfect response from all Skial servers. Here is my result of tracert command against the same IP address. Pay attention to response time from the third hop:
Code: 
C:\Users\Inferno>tracert 108.61.46.50
 
Tracing route to 108.61.46.50.choopa.net [108.61.46.50]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  SMCWBR14S-N4.ralinktech.com [192.168.2.1]
  2    33 ms    58 ms    39 ms  76.112.224.1
  3    107 ms    9 ms    10 ms  xe-8-2-0-32767-sur01.royaloak.mi.michigan.comcast.net [68.85.49.241]
  4    12 ms    9 ms    11 ms  xe-11-3-0-0-sur02.royaloak.mi.michigan.comcast.net [68.87.189.166]
  5    10 ms    19 ms    11 ms  te-0-3-0-1-ar01.pontiac.mi.michigan.comcast.net [68.85.222.206]
  6    26 ms    47 ms    23 ms  he-4-5-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.221]
  7    35 ms    35 ms    35 ms  he-4-3-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.88.141]
  8    38 ms    49 ms    36 ms  be-14-pe02.111eighthave.ny.ibone.comcast.net [68.86.82.242]
  9    37 ms    36 ms    38 ms  173.167.57.162
10    44 ms    35 ms    38 ms  as20473.ae7.ar1.nyc3.us.nlayer.net [69.31.34.62]
11    34 ms    42 ms    33 ms  ve20-br1.pnj1.choopa.net [108.61.65.41]
12    34 ms    49 ms    37 ms  108.61.92.162.choopa.net [108.61.92.162]
13    33 ms    35 ms    33 ms  108.61.46.50.choopa.net [108.61.46.50]
 
Trace complete.

Five minutes later....

Code: 
C:\Users\Inferno>tracert 108.61.46.50
 
Tracing route to 108.61.46.50.choopa.net [108.61.46.50]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  SMCWBR14S-N4.ralinktech.com [192.168.2.1]
  2    38 ms    20 ms    28 ms  76.112.224.1
  3    9 ms    25 ms    9 ms  xe-8-2-0-32767-sur01.royaloak.mi.michigan.comcast.net [68.85.49.241]
  4    26 ms    9 ms    9 ms  xe-11-3-0-0-sur02.royaloak.mi.michigan.comcast.net [68.87.189.166]
  5    10 ms    12 ms    11 ms  te-0-3-0-1-ar01.pontiac.mi.michigan.comcast.net [68.85.222.206]
  6    17 ms    23 ms    23 ms  he-4-5-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.221]
  7    42 ms    35 ms    35 ms  he-4-3-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.88.141]
  8    33 ms    34 ms    33 ms  be-14-pe02.111eighthave.ny.ibone.comcast.net [68.86.82.242]
  9    35 ms    35 ms    35 ms  173.167.57.162
10    42 ms    34 ms    40 ms  as20473.ae7.ar1.nyc3.us.nlayer.net [69.31.34.62]
11    33 ms    41 ms    44 ms  ve20-br1.pnj1.choopa.net [108.61.65.41]
12    37 ms    34 ms    35 ms  108.61.92.162.choopa.net [108.61.92.162]
13    33 ms    35 ms    36 ms  108.61.46.50.choopa.net [108.61.46.50]
 
Trace complete.

Well, that explains spikes I have sporadically.
 
takethepants

takethepants

Australian Skial God
Contributor
Yeah, so it looks like it's spiking on the handoff from Verizon to another peer. Not sure if we can do anything about that.
 
Xtreme2damax

Xtreme2damax

Gore-Spattered Heavy
My ping isn't spiking, ping is consistent to the server. The issue is that I am being routed through VA and back up to NY thus inflating my ping. Whois information for the ip on hop 8 lists it's geolocation as being in Ashburn, VA. So I am going from NY to VA and back up to NY by the looks of everything.
 
PsychoRealm

PsychoRealm

Australian Skial God
Contributor
By the way, have you tried "route /f" command? If not - try and and then reboot your PC. See if it helps. But before you do that do "route print" and post an output here.
 
You must log in or register to reply here.
Top Bottom