Why am I suddenly pinging terrible in Seattle servers?

supermaN · Post by **supermaN** » Mon Aug 14, 2006 9:32 pm

I wasn't sure where else to post this. Here's my story. A couple of months ago I used to play on NuclearFallout's official CS 1.6 DM server that they have so you can test it out. After a few months, my ping suddenly jumped from being in the thirties to being in the 60-80s. I'm in Edmonton, Alberta Canada by the way. Anyways, I thought it was just the server so i decided to just play on different servers. I played on numerous Seattle servers where I had a ping of 30-40 that is until today. After leaving the game for a while, I came back and saw that my ping was in the 70s =|. I wasn't surprised to find out it was provided by NF. Now I'm just wondering is this temporary or is there something wrong with my connection. My service provider is Shaw if that helps. Thanks for all the help in advance

Nick|NFo · Post by **Nick|NFo** » Mon Aug 14, 2006 9:57 pm

I'm not seeing an issue on your outbound:

Code: Select all

1   0.3 ms   0.2 ms   0.3 ms  nuclearfallout-4.sef.pnap.net [66.150.165.189]
 2   0.4 ms   0.3 ms   0.3 ms  core6.t4-2-bbnet2.sef.pnap.net [63.251.160.81]
 3   0.5 ms   0.5 ms   0.4 ms  bpr3-ge-7-0-0.SeattleSwitchDesign.savvis.net [208.173.49.89]
 4   0.5 ms   0.7 ms   1.0 ms  208.173.49.6
 5   0.6 ms   0.7 ms   0.6 ms  0.so-1-2-0.XL1.SEA1.ALTER.NET [152.63.106.2]
 6   0.5 ms   0.4 ms   0.7 ms  POS6-0.GW11.SEA1.ALTER.NET [152.63.107.17]
 7   0.6 ms   0.5 ms   0.5 ms  bigpipe92-gw.customer.alter.net [63.65.78.38]
 8   4.4 ms   4.4 ms   4.3 ms  rc1bb-pos10-0-0.vc.shawcable.net [66.163.76.141]
 9  19.2 ms  19.3 ms  19.4 ms  rc1ar-pos14-0.ed.shawcable.net [66.163.76.162]
10  20.1 ms  20.0 ms  20.0 ms  dx1cd-g1.ed.shawcable.net [64.59.189.73]
11   *        *        *       Request timed out.
12   *        *        *       Request timed out.
13   *        *        *       Request timed out.
14   *        *        *       Request timed out.
15   *        *        *       Request timed out.

Has your problem passed already? If so, next time just run a tracert and you can see where the problem lies. If not, still run a tracert to the server by running tracert serverip in the command prompt. That does a traceroute from you to the server in question, mapping out the route you go over the internet.

supermaN · Post by **supermaN** » Mon Aug 14, 2006 10:06 pm

thanks for the fast response. Yea, it seems the server I usually play on has resolved it's issues but I still can't get a normal ping on your CSDM that you guys provide as a test server.

Nick|NFo · Post by **Nick|NFo** » Mon Aug 14, 2006 10:13 pm

supermaN wrote:thanks for the fast response. Yea, it seems the server I usually play on has resolved it's issues but I still can't get a normal ping on your CSDM that you guys provide as a test server.

That is hosted at another colocation. Can you send us a tracert to rentals @ nuclearfallout.net along with your home ip and an explanation of the issue? We'll take a look into it. Shaw sometimes has weird routing or a backbone issue to some places.

supermaN · Post by **supermaN** » Mon Aug 14, 2006 10:16 pm

Nick|NFo wrote:
supermaN wrote:thanks for the fast response. Yea, it seems the server I usually play on has resolved it's issues but I still can't get a normal ping on your CSDM that you guys provide as a test server.
That is hosted at another colocation. Can you send us a tracert to rentals @ nuclearfallout.net along with your home ip and an explanation of the issue? We'll take a look into it. Shaw sometimes has weird routing or a backbone issue to some places.

a tracert using the CSDM underground ip?

Nick|NFo · Post by **Nick|NFo** » Mon Aug 14, 2006 10:18 pm

Yes, to the server in question.

supermaN · Post by **supermaN** » Mon Aug 14, 2006 10:23 pm

e-mail sent

Post by **Edge100x** » Tue Aug 15, 2006 7:04 am

I've responded to your trace and unfortunately it's not with good news. Shaw is misrouting you through Chicago on the way to us, which adds significant latency. InterNAP's outbound path already goes directly onto Shaw, so there's nothing we can do about it from our end; you'd need to talk to your ISP about the problem to the CSDM server.

The good news is that the CSDM server is on a discontinued location and no new servers are being created there (starting a couple of years ago).

supermaN · Post by **supermaN** » Tue Aug 15, 2006 10:39 am

Edge100x wrote:I've responded to your trace and unfortunately it's not with good news. Shaw is misrouting you through Chicago on the way to us, which adds significant latency. InterNAP's outbound path already goes directly onto Shaw, so there's nothing we can do about it from our end; you'd need to talk to your ISP about the problem to the CSDM server.

The good news is that the CSDM server is on a discontinued location and no new servers are being created there (starting a couple of years ago).

I guess that's semi good news

. Would they be able to fix the routing problem if I ask them or is it not possible?

Post by **Edge100x** » Tue Aug 15, 2006 11:42 am

They could. They probably won't, basedo n what we've seen before. But it's worth a shot