...that I published this morning. I think I may have been too quick to excoriate SoapBlox solely on the basis of problems we've had in the past.
UPDATE: "Think" and "maybe" nothin'.
Just received this from the SoapBlox folks:
This outage was not at all due to any fault of Soapblox. It was due to a storm that brought down our data center on the East Coast of the US (http://www.pcworld.com/...).
We learned of the outage at about midnight on Friday night and had two full-time folks working with Amazon support, virtually round the clock until early this morning to bring it back up.
In fact, it quite fortunate for our bloggers that there is an established support system to respond to hosting emergencies like this. The lack of such a system is what motivated me to first reach out to offer support services to the original owners of Soapblox three years ago to offer professional hosting and software support services, and what motivated me to direct Warecorp to purchase the network outright last year
We have recently made significant investments in bringing together this important national network of bloggers by appointing Tina Dupuy as EIC at Netroots this year. http://eon.businesswire.com/....
I assure you, we will continue to invest to create a unique, fact-centered community of observation and commentary, news, and video.
I did hear this from weatherdude:
The derecho last night knocked out tons of servers in the DC area. If their servers are down, and if the people who run it have no power, that could be why. Millions are without power.
I thought the Soapy servers were in Minneapolis, not the D.C. area.....see their main page's TOS (which is up).
Anyway, lots of stuff in the D.C. area is down.
Like, fer instance, try this website.
Cuatro cero cuatro.
(UPDATE: It took like a half hour to resolve, but WaPo's site finally came up.)
Don't really care if this gets a lot of recs or anything, I mainly want it in my history, because I was pretty rough on Soapblox and maybe I shouldn't have been.
On to the next thing.