Downtime this weekend

[Skywing]

Well, here's what I am seeing right now (problem seems to have recurred):

skywing@valera:~$ time wget http://www.x86labs.org/forum
--14:51:52--  http://www.x86labs.org/forum
           => `forum'
Resolving www.x86labs.org... 24.76.160.70
Connecting to www.x86labs.org|24.76.160.70|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.x86labs.org/forum/ [following]
--14:51:53--  http://www.x86labs.org/forum/
           => `index.html'
Reusing existing connection to www.x86labs.org:80.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]

    [           <=>                                                                                                                                                         ] 60,910         8.93K/s

14:52:05 (8.93 KB/s) - `index.html' saved [60910]


real    0m13.222s
user    0m0.004s
sys     0m0.048s
skywing@valera:~$ traceroute www.x86labs.org
traceroute to iago.dnsalias.com (24.76.160.70), 30 hops max, 52 byte packets
 1  208.110.73.177 (208.110.73.177)  0.649 ms  0.504 ms  0.526 ms
 2  69.30.235.93 (69.30.235.93)  0.993 ms  1.298 ms  1.290 ms
 3  69.30.235.1 (69.30.235.1)  17.081 ms  1.292 ms  1.156 ms
 4  69.30.235.210 (69.30.235.210)  1.565 ms  1.506 ms  1.683 ms
 5  rrcs-67-53-162-197.west.biz.rr.com (67.53.162.197)  11.963 ms  11.797 ms  12.196 ms
 6  gig1-0-6.kscymordc-rtr1.rdc-kc.rr.com (24.94.160.41)  11.822 ms  12.124 ms  13.264 ms
 7  so5-1-1-chcgill3-rtr1.kc.rr.com (24.94.160.81)  13.306 ms  12.767 ms  11.672 ms
 8  xe-11-2-0.edge1.chicago2.level3.net (4.71.248.13)  11.528 ms xe-11-1-0.edge1.chicago2.level3.net (4.71.248.1)  16.266 ms xe-11-2-0.edge1.chicago2.level3.net (4.71.248.13)  21.313 ms
 9  ae-32-54.ebr2.chicago1.level3.net (4.68.101.126)  35.172 ms ae-31-53.ebr1.chicago1.level3.net (4.68.101.94)  38.764 ms ae-31-51.ebr1.chicago1.level3.net (4.68.101.30)  22.004 ms
10  ae-68.ebr3.chicago1.level3.net (4.69.134.58)  18.006 ms ae-78.ebr3.chicago1.level3.net (4.69.134.62)  12.848 ms ae-68.ebr3.chicago1.level3.net (4.69.134.58)  15.717 ms
11  ae-3.ebr2.denver1.level3.net (4.69.132.61)  36.438 ms  27.791 ms  33.263 ms
12  ae-2.ebr2.seattle1.level3.net (4.69.132.53)  50.575 ms  301.273 ms  92.785 ms
13  ae-23-52.car3.seattle1.level3.net (4.68.105.36)  62.623 ms ae-23-54.car3.seattle1.level3.net (4.68.105.100)  59.977 ms ae-23-56.car3.seattle1.level3.net (4.68.105.164)  63.472 ms
14  big-pipe-in.car3.seattle1.level3.net (4.71.152.26)  60.835 ms  59.252 ms  56.127 ms
15  rc1wh-pos14-0-0.vc.shawcable.net (66.163.76.1)  84.739 ms  97.882 ms  50.559 ms
16  rc1so-pos1-0-0.cg.shawcable.net (66.163.77.198)  72.259 ms  72.993 ms  71.823 ms
17  rc2nr-pos11-0-0.wp.shawcable.net (66.163.77.158)  113.353 ms  121.147 ms  97.157 ms
18  dx1sj-g15.wp.shawcable.net (64.59.181.137)  89.205 ms  88.579 ms  88.646 ms
19  * * *
20  * *
skywing@valera:~$


13-15 seconds to serve up pages definitely is not good.  However, not showing much in the way of latency spikes.

[Killer360]

Well, here's what I am seeing right now (problem seems to have recurred):

skywing@valera:~$ time wget http://www.x86labs.org/forum
--14:51:52--  http://www.x86labs.org/forum
           => `forum'
Resolving www.x86labs.org... 24.76.160.70
Connecting to www.x86labs.org|24.76.160.70|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.x86labs.org/forum/ [following]
--14:51:53--  http://www.x86labs.org/forum/
           => `index.html'
Reusing existing connection to www.x86labs.org:80.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]

    [           <=>                                                                                                                                                         ] 60,910         8.93K/s

14:52:05 (8.93 KB/s) - `index.html' saved [60910]


real    0m13.222s
user    0m0.004s
sys     0m0.048s
skywing@valera:~$ traceroute www.x86labs.org
traceroute to iago.dnsalias.com (24.76.160.70), 30 hops max, 52 byte packets
 1  208.110.73.177 (208.110.73.177)  0.649 ms  0.504 ms  0.526 ms
 2  69.30.235.93 (69.30.235.93)  0.993 ms  1.298 ms  1.290 ms
 3  69.30.235.1 (69.30.235.1)  17.081 ms  1.292 ms  1.156 ms
 4  69.30.235.210 (69.30.235.210)  1.565 ms  1.506 ms  1.683 ms
 5  rrcs-67-53-162-197.west.biz.rr.com (67.53.162.197)  11.963 ms  11.797 ms  12.196 ms
 6  gig1-0-6.kscymordc-rtr1.rdc-kc.rr.com (24.94.160.41)  11.822 ms  12.124 ms  13.264 ms
 7  so5-1-1-chcgill3-rtr1.kc.rr.com (24.94.160.81)  13.306 ms  12.767 ms  11.672 ms
 8  xe-11-2-0.edge1.chicago2.level3.net (4.71.248.13)  11.528 ms xe-11-1-0.edge1.chicago2.level3.net (4.71.248.1)  16.266 ms xe-11-2-0.edge1.chicago2.level3.net (4.71.248.13)  21.313 ms
 9  ae-32-54.ebr2.chicago1.level3.net (4.68.101.126)  35.172 ms ae-31-53.ebr1.chicago1.level3.net (4.68.101.94)  38.764 ms ae-31-51.ebr1.chicago1.level3.net (4.68.101.30)  22.004 ms
10  ae-68.ebr3.chicago1.level3.net (4.69.134.58)  18.006 ms ae-78.ebr3.chicago1.level3.net (4.69.134.62)  12.848 ms ae-68.ebr3.chicago1.level3.net (4.69.134.58)  15.717 ms
11  ae-3.ebr2.denver1.level3.net (4.69.132.61)  36.438 ms  27.791 ms  33.263 ms
12  ae-2.ebr2.seattle1.level3.net (4.69.132.53)  50.575 ms  301.273 ms  92.785 ms
13  ae-23-52.car3.seattle1.level3.net (4.68.105.36)  62.623 ms ae-23-54.car3.seattle1.level3.net (4.68.105.100)  59.977 ms ae-23-56.car3.seattle1.level3.net (4.68.105.164)  63.472 ms
14  big-pipe-in.car3.seattle1.level3.net (4.71.152.26)  60.835 ms  59.252 ms  56.127 ms
15  rc1wh-pos14-0-0.vc.shawcable.net (66.163.76.1)  84.739 ms  97.882 ms  50.559 ms
16  rc1so-pos1-0-0.cg.shawcable.net (66.163.77.198)  72.259 ms  72.993 ms  71.823 ms
17  rc2nr-pos11-0-0.wp.shawcable.net (66.163.77.158)  113.353 ms  121.147 ms  97.157 ms
18  dx1sj-g15.wp.shawcable.net (64.59.181.137)  89.205 ms  88.579 ms  88.646 ms
19  * * *
20  * *
skywing@valera:~$


13-15 seconds to serve up pages definitely is not good.  However, not showing much in the way of latency spikes.

Like iago said, there are really nasty conditions out right now. That might be affecting it.

[Camel]

The internet is pass/fail; weather may cause more people to use the internet, but that would reflect in the ping times. The problem Skywing is seeing most likely has nothing to do with iago's internet connection.

[Killer360]

The internet is pass/fail; weather may cause more people to use the internet, but that would reflect in the ping times. The problem Skywing is seeing most likely has nothing to do with iago's internet connection.

Well then it's skywing's problem... almost everyone in western Canada uses Shaw as their ISP. 

[Quik]

The internet is pass/fail; weather may cause more people to use the internet, but that would reflect in the ping times. The problem Skywing is seeing most likely has nothing to do with iago's internet connection.

Well then it's skywing's problem... almost everyone in western Canada uses Shaw as their ISP. 

You completely didn't understand what he's saying. And I think if it was you're problem, you'd want something fixed too. I can honestly say that in my opinion, Skywing has contributed MUCH more to these forums then you have, with a fraction of your posts. I think it's only reasonable to try to solve issues with the forums so that valuable users can access at ease.

Also, I have noticed a bit of a slowdown when loading pages.

[iago]

Hmm, I might consider moving back to MTS, in this case. MTS is DSL, which is affected by neighbours a lot better. I'll give it a couple weeks to see if it improves, then look into switching.

[Killer360]

- I don't think he's having too much trouble if he's accessing the forums just fine.

But yeah, missing hops suck.

[Ergot]

Wow, so... according to his traceroute... it goes half way across the US then back half way across Canada. o_O

[Blaze]

It's good over here in Eastern Canada...

  1    18 ms    35 ms    16 ms  10.230.32.1
  2    16 ms    20 ms    24 ms  vl-201.gw03.wlfdle.phub.net.cable.rogers.com [66.185.90.161]
  3    <1 ms    31 ms    10 ms  te-6-1-0.gw01.wlfdle.phub.net.cable.rogers.com [24.153.5.41]
  4    26 ms     9 ms     9 ms  so-3-0-0.gw02.wlfdle.phub.net.cable.rogers.com [66.185.80.130]
  5     8 ms    45 ms    35 ms  pos-4-0.igw01.front.phub.net.cable.rogers.com [64.71.240.53]
  6    20 ms    26 ms    27 ms  rc1sh-ge9-0-2.mt.shawcable.net [66.163.66.25]
  7    30 ms    31 ms    46 ms  rc1sc-pos13-0.wp.shawcable.net [66.163.76.74]
  8    55 ms    39 ms    40 ms  dx1sj-g15.wp.shawcable.net [64.59.181.137]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.

[iago]

There's definitely a problem at the server level, but I haven't tracked it down. :/

[rabbit]

It's fine for me, except that it's taking a stupidly long time to load stuff from a certain signature from sidoh.dark-wire.net....*cough*

[Sidoh]

It's fine for me, except that it's taking a stupidly long time to load stuff from a certain signature from sidoh.dark-wire.net....*cough*

ad block it.

[Newby]

I seem to have no issues.

[Blaze]

I seem to have no issues.

Same here.

[Sidoh]

I have intermittent latency sometimes, but it's not enough to bother me.