Experiencing Higher Pings than Normal at Tastyspleen Quake 2 Servers

[[FP]Careless]

Dear Quadz,

Could you please also check the below trace?
This is from someone in Edmonton not in Vancouver but he is telling me that all of BC and AB connections routed through Vancouver so this should give some idea how good is it when we compare it to TELUS trace. If I can find someone from Vancouver, I will also post it but until then, could you please comment on below? Appreciate your all help!



"Anyways, since all of Teksavvy's BC and AB customers are thrown on the same Vancouver router, a trace from Edmonton won't differ much from a trace from Vancouver, other than the pings being about 10-15ms lower across the board.

So here it is (from Edmonton, second hop is located in Vancouver and is common to all BC and AB Teksavvy subscribers): "

Tracing route to tastyspleen.net [74.54.186.226]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 27 ms 28 ms 27 ms 76-10-191-1.dsl.teksavvy.com [76.10.191.1]
3 29 ms 27 ms 27 ms 69.90.31.241
4 27 ms 28 ms 28 ms oc48.so-2-1-0.van-spenc-cor-1.peer1.net [216.187.89.249]
5 31 ms 30 ms 31 ms oc48.so-2-0-0.sea-wes7-dis-1.peer1.net [216.187.88.226]
6 30 ms 31 ms 31 ms six.above.net [198.32.180.19]
7 50 ms 49 ms 50 ms ge-4-1-0.mpr1.sjc2.us.above.net [64.125.31.18]
8 57 ms 59 ms 59 ms so-1-0-0.mpr3.lax9.us.above.net [64.125.26.25]
9 111 ms 111 ms 133 ms so-0-1-0.mpr3.iah1.us.above.net [64.125.25.46]
10 * * 110 ms xe-1-1-0.er1.iah1.above.net [64.125.26.222]
11 111 ms 111 ms 110 ms 209.66.99.94.available.above.net [209.66.99.94]
12 110 ms 111 ms 111 ms et5-4.ibr04.dllstx3.theplanet.com [70.87.253.53]
13 110 ms 111 ms 112 ms te7-2.dsr02.dllstx3.theplanet.com [70.87.253.26]
14 110 ms 112 ms 111 ms te1-3.dsr02.dllstx2.theplanet.com [70.87.253.122]
15 127 ms 110 ms 111 ms po2.car06.dllstx6.theplanet.com [12.96.160.40]
16 110 ms 109 ms 110 ms tastyspleen.net [74.54.186.226]

Trace complete.

[console]

Could you please also check the below trace?
This is from someone in Edmonton not in Vancouver but he is telling me that all of BC and AB connections routed through Vancouver so this should give some idea how good is it when we compare it to TELUS trace. If I can find someone from Vancouver, I will also post it but until then, could you please comment on below? Appreciate your all help!

Hmmm... not sure why the pings are so much higher than the TELUS route.

TELUS went through Illinois, the route above apparently goes through Los Angeles...

Fiddling with Google maps, it seems the distance should likely be greater for the Illinois route.  And yet the ping was lower...

Dunno.

From what we've seen so far, TELUS looks like it has the best route to our Dallas servers.  (But we haven't seen a trace from Vancouver to tastyspleen via TELUS yet, just the reverse.  Maybe we can get travolta to do a trace from his end. )


Regards,

[[FP]Careless]

I do not think he would commute to that
Anyway, thank you for your all help
I will change my ISP to Telus. At least, I will try for a month without cancelling my current ISP so that I can what the difference is.
Cross your fingers for me
Appreciate your all help Quadz
Really, thanks a million

[UUD-40]

Its worth waiting. Last weekend my ping was a steady 105ms (normal for me is 37ms) It's back to normal now. 

[[FP]Careless]

Thanks for your suggestion but it has been weeks that my ping is higher.
When I checked with my ISP they keep telling me that nothing is wrong with my line, routing, hops etc.
Obviously, they changed their agreement with a third or second party ISP for the routings of some locations in North America. It is a local company here not a huge company like some of the American companies so I do not think that my ping will be like it used to be.
I wont sign a contract but I will try their service for a month to see what is it like.
Appreciate everybody's patient and help
Regards

[[BTF]Sigma]

Just an updated traceroute later on in the day:

Tracing route to tastyspleen.net [74.54.186.226]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    10 ms     9 ms     7 ms  64.59.150.162
  4     8 ms     7 ms     8 ms  rc2bb-tge0-9-2-0.vc.shawcable.net [66.163.69.41]
  5    40 ms    39 ms    40 ms  rc1sj-pos0-0.cl.shawcable.net [66.163.77.70]
  6    31 ms    29 ms    30 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  7    80 ms    90 ms    90 ms  c2.fd.5746.static.theplanet.com [70.87.253.194]
  8    81 ms    79 ms    89 ms  te9-2.dsr01.dllstx3.theplanet.com [70.87.253.14]
  9    71 ms    81 ms    71 ms  te1-4.dsr01.dllstx2.theplanet.com [70.87.253.114]
 10   107 ms    82 ms    83 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]
 11    79 ms    80 ms    80 ms  tastyspleen.net [74.54.186.226]

Trace complete.

Running better now. I don't have to remind you, Careless, about TELUS's track record with customer service. Sure they may treat you great in the honeymoon but expect no reasons for blackouts, throttling, and billing issues if you live in the city. I live within throwing distance of the TELUS boot and our company is managed with funds from their pension group. I have to let in their techs and the contract techs (Ledcor Telecom) and these guys don't know what to do in comm rooms that aren't built after 2005.

Try it out for the month but once the honeymoon is over, trust me, these guys will gyp you for the smallest request (yes they charge to send over a tech to fix their service) and the techs will be pretty rude (especially the contracted techs who don't care about TELUS's rep).

[travolta]

My lousy tracert:

Tracing route to tastyspleen.net [74.54.186.226]
over a maximum of 30 hops:

  1    13 ms    12 ms    12 ms  d154-20-128-254.bchsia.telus.net [154.20.128.254]
  2    12 ms    13 ms    12 ms  154.11.88.194
  3    16 ms    16 ms    16 ms  204.225.243.22
  4    16 ms    16 ms    16 ms  ge-11-3-5.mpr1.sea1.us.above.net [208.185.175.69]
  5    36 ms    36 ms    35 ms  ge-4-1-0.mpr1.sjc2.us.above.net [64.125.31.18]
  6    44 ms    43 ms    44 ms  so-1-0-0.mpr3.lax9.us.above.net [64.125.26.25]
  7    84 ms    83 ms    83 ms  so-0-1-0.mpr3.iah1.us.above.net [64.125.25.46]
  8     *        *        *     Request timed out.
  9    84 ms    85 ms    85 ms  209.66.99.94.available.above.net [209.66.99.94]
 10    83 ms    84 ms    84 ms  et5-4.ibr04.dllstx3.theplanet.com [70.87.253.53]
 11    84 ms    84 ms    84 ms  te9-2.dsr02.dllstx3.theplanet.com [70.87.253.30]
 12    84 ms    84 ms    84 ms  te3-3.dsr02.dllstx2.theplanet.com [70.87.253.126]
 13    84 ms    85 ms    85 ms  po2.car06.dllstx6.theplanet.com [12.96.160.40]
 14    84 ms    84 ms    84 ms  tastyspleen.net [74.54.186.226]

Trace complete.

Telus dsl is mostly ok. No down times.

I moved 3 miles and doubled my ping to the old Redmond WA ffa server.

[reaper]

You could see the routes that the planet receives for the network you get assigned on Savvis, and see if a different route is better for you.

For instance, the planet could receive your route (24.80.0.0/13) from Qwest from Level3, and from Savvis themselves.  Each of these systems is one AS, and the route is usually picked by how many AS's you go through to reach the destination.  But for whatever reasons the other route could have less latency to that location, even though it hops through less autonomous systems.  Same situation applies on the route from you.

However when you look at the BGP looking glasses online, they show an actual routing table, so they show the "best" route from that location to your network (one route to 24,80.0.0/13), because only the best route gets installed in the routing table.  But in reality there may be many routes,which you can see if you dig a little deeper, and look at the routes that are not installed in the routing table.  If they wanted they could choose any route there.

This is policy determinted by your providers, and they may not care what you have to say, or maybe they can help you. Although i wouldn't be suprised if they said that's the way it is, because it would increase their transit traffic, or require some type of policy change.  And I have no idea what's going on, that may even be your best route from Savvis.

You would have to have some type of looking glass type feature to issue something like "show ip bgp" at the planet and savvis, or somewhere along the path and see what routes are available, and look into the AS_PATH of the route,etc.

You could run pathping and see if maybe there is some congestion and point it out, but it looks like console already figured out it was simply the path that is taken, and the other providers route is better to that paticular server.

[[FP]Careless]

[BTF]Sigma,

What are you pinging at DM and Mutant servers these days?

My ping is even worse nowadays. It is around 140ms!. I really start to hate Shaw.... Ordered Telus and waiting for it to be available...
I am just curios, what you are pinging nowadays so please let me know

Thanks

[[BTF]Sigma]

MUTANT 80 steady
Tourney 1-3 @ 80-85
Tourney4 120

[Knnn]

Hi,

I met Travolta on the WEST (?) server where I had an insane ping (12-14).  He mentioned that some Vancouver Shaw users were having trouble so I thought I would throw up some tracert's to see if i can help.

I'm on Shaw, regular 5MB service, located in North Vancouver.

Tracing route to wtfever.net [67.223.224.36]

  1     3 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     8 ms     7 ms     7 ms  rd1wh-ge3-0-0-7.vc.shawcable.net [64.59.159.35]
  4    12 ms    25 ms    17 ms  rc2wh-tge0-8-0-0.vc.shawcable.net [66.163.69.169]
  5     9 ms    12 ms     8 ms  rc2bb-tge0-15-1-0.vc.shawcable.net [66.163.69.122]
  6    13 ms    12 ms    11 ms  66.163.77.138
  7    13 ms    12 ms    15 ms  six.spry.com [198.32.180.51]
  8    11 ms    12 ms    77 ms  po1-core0-tuk.wa.spry.com [64.79.223.2]
  9    13 ms    11 ms    12 ms  ovz64-009.spry.com [209.59.204.91]
 10    12 ms    12 ms    11 ms  wtfever.net [67.223.224.36]


Tracing route to tastyspleen.net [74.54.186.226]

  1    <1 ms    <1 ms     1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     7 ms    11 ms     7 ms  rd1wh-ge3-0-0-7.vc.shawcable.net [64.59.159.35]
  4     8 ms     7 ms     7 ms  rc2wh-tge0-7-0-0.vc.shawcable.net [66.163.69.165]
  5     8 ms     8 ms    11 ms  rc2bb-tge0-8-1-0.vc.shawcable.net [66.163.69.118]
  6    38 ms    39 ms    39 ms  rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  7    49 ms    50 ms    49 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  8    80 ms    80 ms    80 ms  c2.fd.5746.static.theplanet.com [70.87.253.194]
  9    79 ms    80 ms    79 ms  te7-2.dsr02.dllstx3.theplanet.com [70.87.253.26]
 10    91 ms    90 ms    91 ms  te3-3.dsr02.dllstx2.theplanet.com [70.87.253.126]
 11    84 ms    81 ms    81 ms  po2.car06.dllstx6.theplanet.com [12.96.160.40]
 12    89 ms    89 ms    90 ms  tastyspleen.net [74.54.186.226]


Not sure if that will help any, but GL.

[[FP]Careless]

Thanks for posting your tracert Knnn.
I appreciate your help. Your pings look very good especially for that West Coast US Server! I just tried it and I am pinging around 53ms. How come you are pinging like 13ms? lol. I wonder where the server is located? L.A maybe? but you ping awesome really. I am happy for you

Today is the first day with Telus and here is my new tracert below. I still have Shaw though, I have not close my account yet but I will. Meanwhile, why I am having those request time outs?

Tracing route to tastyspleen.net [74.54.186.226]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15    82 ms    82 ms    81 ms  tastyspleen.net [74.54.186.226]

Trace complete.

Jag Insane is also having some ping problems with Shaw. I just told him to take a look at this topic to see if any info can help him. He is North Van as well just like you

Anyway, thanks for your help again!

[travolta]

my telus tracert from today:

 Tracing route to tastyspleen.net [74.54.186.226]
over a maximum of 30 hops:

  1    13 ms    13 ms    13 ms  d154-20-128-254.bchsia.telus.net [154.20.128.254]
  2    12 ms    12 ms    12 ms  154.11.88.194
  3    16 ms    16 ms    16 ms  204.225.243.22
  4    16 ms    16 ms    16 ms  ge-11-3-5.mpr1.sea1.us.above.net [208.185.175.69]
  5    36 ms    35 ms    35 ms  ge-4-1-0.mpr1.sjc2.us.above.net [64.125.31.18]
  6    43 ms    43 ms    65 ms  so-1-0-0.mpr3.lax9.us.above.net [64.125.26.25]
  7    84 ms    84 ms    84 ms  so-0-1-0.mpr3.iah1.us.above.net [64.125.25.46]
  8    83 ms    83 ms    83 ms  xe-1-1-0.er1.iah1.above.net [64.125.26.222]
  9    85 ms    84 ms    85 ms  209.66.99.94.available.above.net [209.66.99.94]
10    84 ms    84 ms    84 ms  et5-4.ibr04.dllstx3.theplanet.com [70.87.253.53]
11    84 ms    84 ms    84 ms  te9-2.dsr02.dllstx3.theplanet.com [70.87.253.30]
12    84 ms    84 ms    84 ms  te3-3.dsr02.dllstx2.theplanet.com [70.87.253.126]
13   113 ms    84 ms    84 ms  po2.car06.dllstx6.theplanet.com [12.96.160.40]
14    84 ms    84 ms    84 ms  tastyspleen.net [74.54.186.226]

Trace complete.

and
Tracing route to wtfever.net [67.223.224.36]
over a maximum of 30 hops:

  1    51 ms    12 ms    12 ms  d154-20-128-254.bchsia.telus.net [154.20.128.254]
  2    12 ms    12 ms    12 ms  c2-0.kntaonacdr01.bb.telus.com [154.11.88.193]
  3    34 ms    34 ms    34 ms  204.225.244.101
  4    35 ms    35 ms    35 ms  TimeWarner.plalca01gr00.bb.telus.com [154.11.3.98]
  5    55 ms    54 ms    54 ms  66.162.128.22
  6    54 ms    54 ms    55 ms  66.162.128.22
  7    55 ms    56 ms    55 ms  g2.8-br0-tuk.wa.spry.com [64.79.223.25]
  8    54 ms    55 ms    55 ms  po1-core0-tuk.wa.spry.com [64.79.223.2]
  9    55 ms    55 ms    55 ms  ovz64-009.spry.com [209.59.204.91]
 10    55 ms    55 ms    55 ms  wtfever.net [67.223.224.36]

Trace complete.

 

[ijag]

Here is a trace I just did, still spikes at the same place...San Jose!!!   lol....why are we going to San Jose?
North Vancouver here btw.
I just checked the West Coast US Server, I ping 14 there...lol


Tracing route to tastyspleen.net [74.54.186.226]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    17 ms     8 ms    11 ms  rd1wh-ge3-0-0-7.vc.shawcable.net [64.59.159.35]
  4     9 ms     9 ms     9 ms  rc2wh-tge0-8-0-0.vc.shawcable.net [66.163.69.169]
  5    10 ms     8 ms     9 ms  rc2bb-tge0-15-1-0.vc.shawcable.net [66.163.69.122]
  6    40 ms    41 ms    39 ms  rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  7   101 ms   103 ms   101 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  8   142 ms   142 ms   141 ms  c2.fd.5746.static.theplanet.com [70.87.253.194]
  9   141 ms   141 ms   143 ms  te7-2.dsr02.dllstx3.theplanet.com [70.87.253.26]
 10   140 ms   137 ms   137 ms  te1-3.dsr02.dllstx2.theplanet.com [70.87.253.122]
 11   172 ms   151 ms   143 ms  po2.car06.dllstx6.theplanet.com [12.96.160.40]
 12   138 ms   137 ms   137 ms  tastyspleen.net [74.54.186.226]

Trace complete.

[console]

  6    40 ms    41 ms    39 ms  rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  7   101 ms   103 ms   101 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]

My understanding is it's hard to tell which of these routers is responsible for the delay...

For example, the packet could be delayed because the link from 6 -> 7 is saturated, so the delay is incurred while the packet sits in a queue at 6 waiting to be transmitted to 7.

But, the reverse could also be true... It could be sitting in a queue on 7, waiting to be transmitted back to 6.


Regards,