Comments on: pierce getting new hardware http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/ Information about DreamHost Services Fri, 21 Nov 2008 04:19:44 +0000 http://wordpress.org/?v=2.6.2 By: Jacques http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-72731 Jacques Fri, 26 Oct 2007 05:10:39 +0000 http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-72731 No email yet? No email yet?

]]> By: NightmareHost http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-72265 NightmareHost Wed, 24 Oct 2007 16:52:42 +0000 http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-72265 [Didn’t really notice the downtime except that the rsync for the extremely large backup of my entire movie/mp3/porn/rom collection failed. J/K] k, now, i have no problem with the usual shoddy service and downtime of NightMare host, however, messing with my porn??!! You better own a bigger weapon :p j/k [Didn’t really notice the downtime except that the rsync for the extremely large backup of my entire movie/mp3/porn/rom collection failed. J/K]

k, now, i have no problem with the usual shoddy service and downtime of NightMare host, however, messing with my porn??!! You better own a bigger weapon :p

j/k

]]> By: Jimmy http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71959 Jimmy Wed, 24 Oct 2007 04:35:52 +0000 http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71959 Didn't really notice the downtime except that the rsync for the extremely large backup of my entire movie/mp3/porn/rom collection failed. J/K Didn’t really notice the downtime except that the rsync for the extremely large backup of my entire movie/mp3/porn/rom collection failed. J/K

]]> By: Ryan http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71956 Ryan Wed, 24 Oct 2007 04:35:16 +0000 http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71956 This is seriously the last straw for me. Good thing I just picked up another client... as soon as I get his first payment, I'm packing up and moving every damn site I run and moving over to Rackspace/Mosso. This is seriously the last straw for me. Good thing I just picked up another client… as soon as I get his first payment, I’m packing up and moving every damn site I run and moving over to Rackspace/Mosso.

]]> By: microcars http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71954 microcars Wed, 24 Oct 2007 04:34:42 +0000 http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71954 FYI- it just happened in August when EVERYTHING went down, including dreamhoststatus.com: http://blog.dreamhost.com/2007/08/21/it-all-falls-down/ at least Blog.Dreamhost.com works, thank goodness. FYI- it just happened in August when EVERYTHING went down, including dreamhoststatus.com:
http://blog.dreamhost.com/2007/08/21/it-all-falls-down/

at least Blog.Dreamhost.com works, thank goodness.

]]> By: Russ D http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71953 Russ D Wed, 24 Oct 2007 04:34:38 +0000 http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71953 network outage? panel.dreamhost.com is out my web sites are out no ssh or ftp hopefully it is just for a couple hours tonight (11:30 PM CST). network outage?

panel.dreamhost.com is out
my web sites are out
no ssh or ftp

hopefully it is just for a couple hours tonight (11:30 PM CST).

]]> By: Joe http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71950 Joe Wed, 24 Oct 2007 04:34:03 +0000 http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71950 Hello DH Staff, I'd normally file a formal support ticket, but it appears the hamsters are tired, hungry and thirsty and needed a break so I am posting my concern here. I am not able to reach my sites. I tested independently with the Verizon DNS, resetting my local Winsock, Power cycling, using Open DNS, and tried the AOL software (uses ATDN-powered proxies). I've successfully narrowed my concern down to the box that hosts my site (SAKE). For reference, here is the output of my pings. As you can see, I have decent internet connectivity, except to my SAKE box. === MY SITE -- JOEMANNA.COM === C:\Documents and Settings\Joe>ping joemanna.com Pinging joemanna.com [205.196.214.48] with 32 bytes of data: Request timed out. Reply from 205.196.214.48: bytes=32 time=85ms TTL=54 Reply from 205.196.214.48: bytes=32 time=85ms TTL=54 Request timed out. Ping statistics for 205.196.214.48: Packets: Sent = 4, Received = 2, Lost = 2 (50% loss), Approximate round trip times in milli-seconds: Minimum = 85ms, Maximum = 85ms, Average = 85ms === AOL/AIM INSTANT MESSAGING: LOGIN.MESSAGING.AOL.COM === C:\Documents and Settings\Joe>ping login.messaging.aol.com Pinging login.messaging.aol.com [205.188.153.121] with 32 bytes of data: Reply from 205.188.153.121: bytes=32 time=12ms TTL=55 Reply from 205.188.153.121: bytes=32 time=16ms TTL=55 Reply from 205.188.153.121: bytes=32 time=12ms TTL=55 Reply from 205.188.153.121: bytes=32 time=12ms TTL=55 Ping statistics for 205.188.153.121: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 12ms, Maximum = 16ms, Average = 13ms === MAIN DREAMHOST WEB SERVER === C:\Documents and Settings\Joe>ping dreamhost.com Pinging dreamhost.com [66.33.201.141] with 32 bytes of data: Reply from 66.33.201.141: bytes=32 time=86ms TTL=54 Reply from 66.33.201.141: bytes=32 time=86ms TTL=54 Reply from 66.33.201.141: bytes=32 time=84ms TTL=54 Reply from 66.33.201.141: bytes=32 time=86ms TTL=54 Ping statistics for 66.33.201.141: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 84ms, Maximum = 86ms, Average = 85ms === TRACEROUTE TO JOEMANNA.COM (SAKE) === C:\Documents and Settings\Joe>tracert joemanna.com Tracing route to joemanna.com [205.196.214.48] over a maximum of 30 hops: 1 1 ms Hello DH Staff,

I’d normally file a formal support ticket, but it appears the hamsters are tired, hungry and thirsty and needed a break so I am posting my concern here.

I am not able to reach my sites. I tested independently with the Verizon DNS, resetting my local Winsock, Power cycling, using Open DNS, and tried the AOL software (uses ATDN-powered proxies). I’ve successfully narrowed my concern down to the box that hosts my site (SAKE).

For reference, here is the output of my pings. As you can see, I have decent internet connectivity, except to my SAKE box.

=== MY SITE — JOEMANNA.COM ===

C:\Documents and Settings\Joe>ping joemanna.com

Pinging joemanna.com [205.196.214.48] with 32 bytes of data:

Request timed out.
Reply from 205.196.214.48: bytes=32 time=85ms TTL=54
Reply from 205.196.214.48: bytes=32 time=85ms TTL=54
Request timed out.

Ping statistics for 205.196.214.48:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 85ms, Average = 85ms

=== AOL/AIM INSTANT MESSAGING: LOGIN.MESSAGING.AOL.COM ===
C:\Documents and Settings\Joe>ping login.messaging.aol.com

Pinging login.messaging.aol.com [205.188.153.121] with 32 bytes of data:

Reply from 205.188.153.121: bytes=32 time=12ms TTL=55
Reply from 205.188.153.121: bytes=32 time=16ms TTL=55
Reply from 205.188.153.121: bytes=32 time=12ms TTL=55
Reply from 205.188.153.121: bytes=32 time=12ms TTL=55

Ping statistics for 205.188.153.121:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 16ms, Average = 13ms

=== MAIN DREAMHOST WEB SERVER ===
C:\Documents and Settings\Joe>ping dreamhost.com

Pinging dreamhost.com [66.33.201.141] with 32 bytes of data:

Reply from 66.33.201.141: bytes=32 time=86ms TTL=54
Reply from 66.33.201.141: bytes=32 time=86ms TTL=54
Reply from 66.33.201.141: bytes=32 time=84ms TTL=54
Reply from 66.33.201.141: bytes=32 time=86ms TTL=54

Ping statistics for 66.33.201.141:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 86ms, Average = 85ms

=== TRACEROUTE TO JOEMANNA.COM (SAKE) ===
C:\Documents and Settings\Joe>tracert joemanna.com

Tracing route to joemanna.com [205.196.214.48]
over a maximum of 30 hops:

1 1 ms

]]> By: Aaron http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71946 Aaron Wed, 24 Oct 2007 04:33:18 +0000 http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71946 Got a status now... see the new announcement: http://www.dreamhoststatus.com/2007/10/23/secondary-name-server-experiencing-packet-loss/ Got a status now… see the new announcement: http://www.dreamhoststatus.com/2007/10/23/secondary-name-server-experiencing-packet-loss/

]]> By: Oh no, not again http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71945 Oh no, not again Wed, 24 Oct 2007 04:32:43 +0000 http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71945 can't ftp to titan. woah... can’t ftp to titan. woah…

]]> By: Aaron http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71944 Aaron Wed, 24 Oct 2007 04:30:05 +0000 http://www.dreamhoststatus.com/2007/10/21/pierce-getting-new-hardware/#comment-71944 Personally I manage over 25 Web sites on DH and I'll say this... *usually* when one goes down they all go... and I know these sites are on at least 2 different servers. I'll also agree with you on the "down" comment... they are not usually down, but 25% packet loss might as well be. Personally I manage over 25 Web sites on DH and I’ll say this… *usually* when one goes down they all go… and I know these sites are on at least 2 different servers. I’ll also agree with you on the “down” comment… they are not usually down, but 25% packet loss might as well be.

]]>