Higher Than Usual Ping

[Whirlingdervish]

welcome WHO?!

 

[console]

  4    13 ms     9 ms     9 ms  rc2wh-tge0-8-0-0.vc.shawcable.net [66.163.69.169]
  5   208 ms   210 ms   209 ms  rc2bb-tge0-15-1-0.vc.shawcable.net [66.163.69.122]

This issue appears to be within shawcable's network...

[console]

I see im not the only one having the problem, are these all EX-low-pingers that experience this??? when was this changed?

It's not clear to me there was any "this" that was changed. 

In ijag's case, the problem looks to be in shawcable's network.

In your case, it looks like the issue is in theplanet's network.

In Krazy's case, he's apparently connecting from Belgium.  In his case, the route to and from the server is asymmetrical, and yet we see pretty similar ping times in either direction:

traceroute to 78.23.xxx.xxx (78.23.xxx.xxx), 30 hops max, 52 byte packets
 1  e1.ba.364a.static.theplanet.com (74.54.186.225)  0.715 ms  1.279 ms  0.574 ms
 2  vl2.dsr02.dllstx2.theplanet.com (12.96.160.42)  0.278 ms  0.454 ms  0.242 ms
 3  te7-4.dsr02.dllstx3.theplanet.com (70.87.253.121)  98.306 ms  1.074 ms  2.072 ms
 4  et5-2.ibr04.dllstx3.theplanet.com (70.87.253.29)  0.402 ms  0.418 ms  0.363 ms
 5  te-3-4.car4.Dallas1.Level3.net (4.71.122.1)  0.518 ms  0.608 ms  0.484 ms
 6  vlan89.csw3.Dallas1.Level3.net (4.68.19.190)  0.910 ms  11.154 ms  0.830 ms
 7  ae-83-83.ebr3.Dallas1.Level3.net (4.69.136.161)  1.469 ms  10.774 ms  1.768 ms
 8  ae-7.ebr3.Atlanta2.Level3.net (4.69.134.22)  33.545 ms  20.831 ms  32.279 ms
 9  ae-2.ebr1.Washington1.Level3.net (4.69.132.86)  34.487 ms  35.141 ms  36.486 ms
10  ae-81-81.csw3.Washington1.Level3.net (4.69.134.138)  38.852 ms  34.858 ms  35.027 ms
11  ae-82-82.ebr2.Washington1.Level3.net (4.69.134.153)  34.936 ms  35.267 ms  35.329 ms
12  ae-10-10.ebr2.Frankfurt1.Level3.net (4.69.141.109)  125.288 ms  124.920 ms  126.011 ms
13  ae-2-2.ebr1.Dusseldorf1.Level3.net (4.69.132.137)  137.444 ms  141.529 ms  128.058 ms
14  ae-45-105.ebr2.Dusseldorf1.Level3.net (4.69.141.78)  140.734 ms  141.490 ms  129.653 ms
15  ae-42.ebr1.Amsterdam1.Level3.net (4.69.141.66)  138.359 ms  140.682 ms  144.357 ms
16  ae-4-4.car2.Brussels1.Level3.net (4.69.136.253)  133.327 ms  134.538 ms  133.998 ms
17  212.3.237.38 (212.3.237.38)  138.418 ms  136.921 ms  136.440 ms
18  dD5E0FD91.access.telenet.be (213.224.253.145)  130.147 ms  127.340 ms  129.421 ms
19  * dD5E0FD5E.access.telenet.be (213.224.253.94)  130.444 ms  131.487 ms
20  * * *

So, I'm not sure any of the issues between the three of you are actually related.


Regards,

[Krazy]

I'm not sure about it but will the use of R1Q2 affect my gameplay in any positive way I don't have it installed right now.

About my ping: It has always been on around 125. Now since the last 2 weeks it suddenly rose to 140. I wonder where those 15 ms came from. There are more people out there who have notice a ping rise in the last weeks that I have spoken to on the servers. So something has changed.

Again 15 ms doesn't seem much but I notice it in my gameplay. 

Greetz,

Krazy

[ijag]

Here is a different trace, My problem is not inside shaw, yes I know that it was on that trace and I should have seen that before I pasted it in here. My problem is the planet as well. I think they need to upgrade something.
I do have an issue with having to travel over to Calgary before I leave shaw, I see no sense in this.
From 5 to 6 it jumps up 30ms, this is the move to calgary from Vancouver. Then from there to the planet where it just gets worse.
I am not sure why that last trace I posted was like that....spike in users at that time perhaps.

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    12 ms     8 ms     7 ms  rd1wh-ge3-0-0-7.vc.shawcable.net [64.59.159.35]
  4    11 ms     9 ms     7 ms  rc2wh-tge0-8-0-0.vc.shawcable.net [66.163.69.169]
  5    10 ms     9 ms    11 ms  rc2bb-tge0-15-1-0.vc.shawcable.net [66.163.69.122]
  6    41 ms    40 ms    43 ms  rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  7    98 ms    97 ms    97 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  8   139 ms   135 ms   135 ms  c2.fd.5746.static.theplanet.com [70.87.253.194]
  9   135 ms   135 ms   135 ms  te7-2.dsr02.dllstx3.theplanet.com [70.87.253.26]
 10   137 ms   136 ms   137 ms  te1-3.dsr02.dllstx2.theplanet.com [70.87.253.122]
 11   143 ms   160 ms   141 ms  po2.car06.dllstx6.theplanet.com [12.96.160.40]
 12   139 ms   137 ms   147 ms  tastyspleen.net [74.54.186.226]

Trace complete.


Reply to Krazy about R1q2. In my opinion it is very good. I have been using it for about a yr I guess, faster dloads for maps n such I believe.

Reply to Sinner about EX-low-pingers.  I have never had a super low ping but I used to hover in the high 70's to high 80's. Now over the last month I am hangin out at 140ish.

Also, it was just brought to my attention about timing on all this. It appears that this all started when all the snow started dumping here over a month ago. Begining of January.

[Pr0c3550r]

Same ping issue here too.

[|iR|Focalor]

Same ping issue here too.

I think I remember seeing something about "shawcable" in your ID on mirc. Might be helpful if you posted your traceroute here too.

  4    13 ms     9 ms     9 ms  rc2wh-tge0-8-0-0.vc.shawcable.net [66.163.69.169]
  5   208 ms   210 ms   209 ms  rc2bb-tge0-15-1-0.vc.shawcable.net [66.163.69.122]

This issue appears to be within shawcable's network...

[console]

Here is a different trace, My problem is not inside shaw, yes I know that it was on that trace and I should have seen that before I pasted it in here. My problem is the planet as well.

Ah... ok.  Hmm.  Here's the reverse trace:

traceroute to 24.80.xxx.xxx (24.80.xxx.xxx), 30 hops max, 52 byte packets
 1  e1.ba.364a.static.theplanet.com (74.54.186.225)  6.267 ms  0.447 ms  0.474 ms
 2  vl1.dsr01.dllstx2.theplanet.com (12.96.160.9)  5.562 ms  0.348 ms  0.251 ms
 3  te9-4.dsr01.dllstx3.theplanet.com (70.87.253.117)  0.429 ms  0.441 ms  0.423 ms
 4  et3-1.ibr04.dllstx3.theplanet.com (70.87.253.9)  0.494 ms  0.358 ms  0.372 ms
 5  c1.fd.5746.static.theplanet.com (70.87.253.193)  40.196 ms  40.457 ms  40.401 ms
 6  c6.fd.5746.static.theplanet.com (70.87.253.198)  69.330 ms  69.438 ms  69.484 ms
 7  rt0as-equinix.vx.shawcable.net (206.223.115.20)  70.112 ms  69.716 ms  69.802 ms
 8  rc2as-ge3-0-0.vx.shawcable.net (66.163.64.10)  70.031 ms  69.664 ms  69.805 ms
 9  rc2ch-pos3-0.il.shawcable.net (66.163.77.145)  87.782 ms  87.886 ms  88.141 ms
10  rc2nr-pos10-0-0.wp.shawcable.net (66.163.77.93)  106.003 ms  105.951 ms  106.181 ms
11  rc1sc-ge12-0-0.wp.shawcable.net (66.163.73.170)  106.625 ms  106.688 ms  106.603 ms
12  rc1ar-pos3-0.ed.shawcable.net (66.163.76.121)  118.609 ms  120.183 ms  118.836 ms
13  rc2bb-pos0-8-2-0.vc.shawcable.net (66.163.76.161)  118.997 ms  118.730 ms  118.711 ms
14  rd1bb-ge0-0-0.vc.shawcable.net (66.163.69.142)  118.471 ms  118.534 ms  118.601 ms
15  dx4nv-g1.vn.shawcable.net (64.59.159.44)  119.651 ms  119.845 ms  119.545 ms
16  * * *


Hmm.. The more traces we can get from different shawcable players the better.  It does look like Processor is on shawcable.  So yes Pro - trace from you would help too.


Regards,

[Pr0c3550r]

Yes, I am connected with Shaw cable.
Along with the intermittent drop out ( older issue ), It's getting very difficult.
I am hoping that time will eventually resolve this.

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Peter >tracert tastyspleen.net

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

  1   494 ms    <1 ms    <1 ms  192.168.0.1
  2    63 ms    29 ms    34 ms  24.69.140.1
  3    38 ms    33 ms    43 ms  rd1cv-ge3-1-2.gv.shawcable.net [64.59.166.98]
  4    61 ms    46 ms    76 ms  rc1bb-pos4-0-0.vc.shawcable.net [66.163.77.185]

  5   172 ms   218 ms   167 ms  rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  6   169 ms   147 ms   136 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  7   202 ms   223 ms   253 ms  c2.fd.5746.static.theplanet.com [70.87.253.194]

  8   184 ms   166 ms   172 ms  te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]

  9   213 ms   197 ms   205 ms  76.fd.5746.static.theplanet.com [70.87.253.118]

 10   127 ms   111 ms   102 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]
 11   103 ms    91 ms   104 ms  tastyspleen.net [74.54.186.226]

Trace complete.

C:\Users\Peter tracert tastyspleen.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    13 ms    47 ms    52 ms  24.69.140.1
  3   209 ms   238 ms   321 ms  rd1cv-ge3-1-2.gv.shawcable.net [64.59.166.98]
  4   232 ms   225 ms   167 ms  rc1bb-pos4-0-0.vc.shawcable.net [66.163.77.185]

  5   155 ms   118 ms    57 ms  rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  6    93 ms     *       68 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  7   100 ms   140 ms   117 ms  c2.fd.5746.static.theplanet.com [70.87.253.194]

  8   111 ms   102 ms   117 ms  te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]

  9   110 ms   123 ms   138 ms  76.fd.5746.static.theplanet.com [70.87.253.118]

 10   127 ms   121 ms    96 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]
 11   218 ms   189 ms   135 ms  tastyspleen.net [74.54.186.226]

Trace complete.

C:\Users\Peter>


These 2 Trace routes were done one after the other.

Miss the days of a SOLID no lag connect, with a decent ping.
Oh well.



Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Peter> tracert tastyspleen.net

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

  1    <1 ms     2 ms    <1 ms  192.168.0.1
  2   156 ms   143 ms    85 ms  24.69.140.1
  3   170 ms   191 ms   125 ms  rd1cv-ge3-1-2.gv.shawcable.net [64.59.166.98]
  4    93 ms    86 ms    39 ms  rc1bb-pos4-0-0.vc.shawcable.net [66.163.77.185]

  5   122 ms   119 ms    58 ms  rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  6   143 ms   198 ms   185 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  7   174 ms   203 ms   177 ms  c2.fd.5746.static.theplanet.com [70.87.253.194]

  8   261 ms   243 ms   296 ms  te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]

  9    98 ms    98 ms   112 ms  76.fd.5746.static.theplanet.com [70.87.253.118]

 10  1324 ms   228 ms   213 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]
 11   189 ms   304 ms   312 ms  tastyspleen.net [74.54.186.226]

Trace complete.

C:\Users\Peter >


This last one about 5 mins after.
Very inconsistent, the wireless may have something to do with that.

[console]

Yes, I am connected with Shaw cable, however it is not only Shaw clients that have this issue.

Thanks for the traces.  We will have to get some traceroutes from non-Shaw players.  They may not all be the 'same' issue.


One thing...

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    13 ms    47 ms    52 ms  24.69.140.1
  3   209 ms   238 ms   321 ms  rd1cv-ge3-1-2.gv.shawcable.net [64.59.166.98]
  4   232 ms   225 ms   167 ms  rc1bb-pos4-0-0.vc.shawcable.net [66.163.77.185]

That sure looks like a problem within the shawcable network.

So far, ijag has one trace that looks like the problem is in shawcable, and one trace that looks like the problem is in theplanet.

But when we consider ijag's two traces and your two traces, it looks more and more like a shawcable problem.





Edit: The reverse trace for Pro looks like:

traceroute to 24.69.xxx.xxx (24.69.xxx.xxx), 30 hops max, 52 byte packets
 1  e1.ba.364a.static.theplanet.com (74.54.186.225)  18.894 ms  11.111 ms  27.844 ms
 2  vl2.dsr02.dllstx2.theplanet.com (12.96.160.42)  0.324 ms  0.258 ms  0.246 ms
 3  te9-4.dsr02.dllstx3.theplanet.com (70.87.253.125)  0.435 ms  0.421 ms  0.416 ms
 4  et5-2.ibr04.dllstx3.theplanet.com (70.87.253.29)  0.412 ms  0.370 ms  0.346 ms
 5  c1.fd.5746.static.theplanet.com (70.87.253.193)  40.204 ms  40.222 ms  40.271 ms
 6  rt0sj-equinix.cl.shawcable.net (206.223.116.20)  40.897 ms  40.718 ms  40.655 ms
 7  rc2bb-pos0-15-2-0.vc.shawcable.net (66.163.77.85)  83.085 ms  82.798 ms  82.633 ms
 8  rd1cv-pos2-0-0.gv.shawcable.net (66.163.77.186)  74.788 ms  74.326 ms  74.665 ms
 9  * * *

[Pr0c3550r]

HAPPY NEW YEAR SHAW CABLE from [EoM] Pr0c3550r and on behalf of some others

[Pr0c3550r]

Thanks for the help and checking it out.

 

[ijag]

Heres a couple more...lol

Think I will call Shaw tonight and hassle...er...um...I mean "Talk" to them a little more about this issue.


8:28 PM Wednesday, February 04, 2009

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     9 ms     8 ms     7 ms  rd1wh-ge3-0-0-7.vc.shawcable.net [64.59.159.35]
  4     9 ms    11 ms    12 ms  rc2wh-tge0-8-0-0.vc.shawcable.net [66.163.69.169]
  5    13 ms     9 ms    16 ms  rc2bb-tge0-15-1-0.vc.shawcable.net [66.163.69.122]
  6    39 ms    41 ms    39 ms  rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  7   102 ms    98 ms    98 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  8   135 ms   149 ms   136 ms  c2.fd.5746.static.theplanet.com [70.87.253.194]
  9   146 ms   135 ms   137 ms  te7-2.dsr02.dllstx3.theplanet.com [70.87.253.26]
 10   139 ms   142 ms   140 ms  te1-3.dsr02.dllstx2.theplanet.com [70.87.253.122]
 11   164 ms   148 ms   144 ms  po2.car06.dllstx6.theplanet.com [12.96.160.40]
 12   137 ms   138 ms   139 ms  tastyspleen.net [74.54.186.226]

Trace complete.

--------------------------------------------------------------------------------
8:35 PM Wednesday, February 04, 2009

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    14 ms     8 ms     7 ms  rd1wh-ge3-0-0-7.vc.shawcable.net [64.59.159.35]
  4     9 ms    13 ms    12 ms  rc2wh-tge0-8-0-0.vc.shawcable.net [66.163.69.169]
  5     9 ms     8 ms     8 ms  rc2bb-tge0-15-1-0.vc.shawcable.net [66.163.69.122]
  6    41 ms    40 ms    42 ms  rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  7    99 ms    97 ms    98 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  8   137 ms   137 ms   137 ms  c2.fd.5746.static.theplanet.com [70.87.253.194]
  9   135 ms   136 ms   135 ms  te7-2.dsr02.dllstx3.theplanet.com [70.87.253.26]
 10   137 ms   139 ms   140 ms  te1-3.dsr02.dllstx2.theplanet.com [70.87.253.122]
 11   141 ms   160 ms   145 ms  po2.car06.dllstx6.theplanet.com [12.96.160.40]
 12   137 ms   137 ms   137 ms  tastyspleen.net [74.54.186.226]

Trace complete.

[Pr0c3550r]

Heres a couple more...lol

Think I will call Shaw tonight and hassle...er...um...I mean "Talk" to them a little more about this issue.


8:28 PM Wednesday, February 04, 2009

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     9 ms     8 ms     7 ms  rd1wh-ge3-0-0-7.vc.shawcable.net [64.59.159.35]
  4     9 ms    11 ms    12 ms  rc2wh-tge0-8-0-0.vc.shawcable.net [66.163.69.169]
  5    13 ms     9 ms    16 ms  rc2bb-tge0-15-1-0.vc.shawcable.net [66.163.69.122]
  6    39 ms    41 ms    39 ms  rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  7   102 ms    98 ms    98 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  8   135 ms   149 ms   136 ms  c2.fd.5746.static.theplanet.com [70.87.253.194]
  9   146 ms   135 ms   137 ms  te7-2.dsr02.dllstx3.theplanet.com [70.87.253.26]
 10   139 ms   142 ms   140 ms  te1-3.dsr02.dllstx2.theplanet.com [70.87.253.122]
 11   164 ms   148 ms   144 ms  po2.car06.dllstx6.theplanet.com [12.96.160.40]
 12   137 ms   138 ms   139 ms  tastyspleen.net [74.54.186.226]

Trace complete.

--------------------------------------------------------------------------------
8:35 PM Wednesday, February 04, 2009

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    14 ms     8 ms     7 ms  rd1wh-ge3-0-0-7.vc.shawcable.net [64.59.159.35]
  4     9 ms    13 ms    12 ms  rc2wh-tge0-8-0-0.vc.shawcable.net [66.163.69.169]
  5     9 ms     8 ms     8 ms  rc2bb-tge0-15-1-0.vc.shawcable.net [66.163.69.122]
  6    41 ms    40 ms    42 ms  rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  7    99 ms    97 ms    98 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  8   137 ms   137 ms   137 ms  c2.fd.5746.static.theplanet.com [70.87.253.194]
  9   135 ms   136 ms   135 ms  te7-2.dsr02.dllstx3.theplanet.com [70.87.253.26]
 10   137 ms   139 ms   140 ms  te1-3.dsr02.dllstx2.theplanet.com [70.87.253.122]
 11   141 ms   160 ms   145 ms  po2.car06.dllstx6.theplanet.com [12.96.160.40]
 12   137 ms   137 ms   137 ms  tastyspleen.net [74.54.186.226]

Trace complete.

In this case ( point in time ) theplanet.com is the issue.

------------------------------------------------------------------


Here too.

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    24 ms    18 ms     8 ms  24.69.140.1
  3    15 ms    15 ms    20 ms  rd1cv-ge3-1-2.gv.shawcable.net [64.59.166.98]
  4    46 ms    76 ms    65 ms  rc2bb-pos0-1-5-0.vc.shawcable.net [66.163.77.185
]
  5    96 ms    89 ms    72 ms  rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  6    91 ms    68 ms    79 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  7   291 ms   301 ms   326 ms  c2.fd.5746.static.theplanet.com [70.87.253.194]

  8   170 ms   147 ms   103 ms  te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]

  9   194 ms   193 ms   107 ms  76.fd.5746.static.theplanet.com [70.87.253.118]

 10   141 ms    94 ms   106 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]
 11   143 ms    91 ms    96 ms  tastyspleen.net [74.54.186.226]

Trace complete.

C:\Users\Peter>

[Pr0c3550r]

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

>tracert tastyspleen.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     9 ms    11 ms    11 ms  24.69.140.1
  3    10 ms     9 ms    10 ms  rd1cv-ge3-1-2.gv.shawcable.net [64.59.166.98]
  4    13 ms    11 ms    23 ms  rc2bb-pos0-1-5-0.vc.shawcable.net [66.163.77.185

  5    53 ms    55 ms    56 ms  rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  6    43 ms    43 ms    42 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  7   102 ms   107 ms    95 ms  c2.fd.5746.static.theplanet.com [70.87.253.194]

  8    94 ms    95 ms    96 ms  te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]

  9   116 ms    94 ms     *     76.fd.5746.static.theplanet.com [70.87.253.118]

 10   114 ms    96 ms    98 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]
 11    93 ms    95 ms    95 ms  tastyspleen.net [74.54.186.226]

Trace complete.

tracert tastyspleen.net

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    11 ms    11 ms     7 ms  24.69.140.1
  3    10 ms    11 ms    11 ms  rd1cv-ge3-1-2.gv.shawcable.net [64.59.166.98]
  4    12 ms    11 ms    11 ms  rc2bb-pos0-1-5-0.vc.shawcable.net [66.163.77.185
]
  5    52 ms    55 ms     *     rc1sj-pos1-0-0.cl.shawcable.net [66.163.77.86]
  6    46 ms    43 ms    43 ms  eq-sanjose-10G.theplanet.com [206.223.116.148]
  7    94 ms    96 ms    94 ms  c2.fd.5746.static.theplanet.com [70.87.253.194]

  8   107 ms    96 ms   108 ms  te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]

  9    96 ms    96 ms   107 ms  76.fd.5746.static.theplanet.com [70.87.253.118]

 10    96 ms    95 ms   118 ms  po1.car06.dllstx6.theplanet.com [12.96.160.8]
 11    95 ms    94 ms   107 ms  tastyspleen.net [74.54.186.226]

Trace complete.

I am online 24/7 (most of the time) connected to ICQ, MSN Yahoo and several channels in mIRC. ( and a couple other bells and whistles )
This trace route was done with all the IMs OFF and did a netgraph at the [EoM] server.

The ping spikes stopped and ping remained fairly consistent.

Still dealing with the 60 second RED spikes, but that's a wireless issue.