Re: Downtime Announcements
We're back. I think. Whew.
So. As noted above, we'd been struggling with server load. HawaiiThreads, as well as the many other domains I manage, were starting to bog down (both for all of us, as well as hundreds of other sites hosted on the same machine). In the past week, I've upgraded twice to improve capacity and performance. First from an old machine to a newer one, and then from that newer one to a "virtual private server" (which has strictly segregated resources and fewer tenants overall).
That last move, the big move, was supposed to take an hour. And it started 30 hours ago.
Part of it, no doubt, was my fault, given that I'd configured many of my sites years and years ago, before I knew what I was doing, with bizarre dependencies and user permission quirks I'd long forgotten. Meanwhile, my webhost was -- and still is? -- having severe problems with a DNS DDoS (Distributed Denial of Service) attack that is rendering its machines unreachable. Chances are, they were more distracted by that than anything.
In any case, I sincerely apologize for this extended outage. It was supposed to be so quick, the downtime would be indistinguishable from some of the outages we've seen lately. I was finally investing the money to give HawaiiThreads.com and its siblings a better home, and in the end, it took things down longer than they'd ever been down.
Thanks for your patience. The upside of all this is, hopefully, more reliable performance overall. At the very least, I'll have finer, direct control over everything. I'll still set a load limit that will require people to log in at peak times (i.e. limiting guests and search engine robots), but that may be slowly raised as well.
We're back. I think. Whew.
So. As noted above, we'd been struggling with server load. HawaiiThreads, as well as the many other domains I manage, were starting to bog down (both for all of us, as well as hundreds of other sites hosted on the same machine). In the past week, I've upgraded twice to improve capacity and performance. First from an old machine to a newer one, and then from that newer one to a "virtual private server" (which has strictly segregated resources and fewer tenants overall).
That last move, the big move, was supposed to take an hour. And it started 30 hours ago.
Part of it, no doubt, was my fault, given that I'd configured many of my sites years and years ago, before I knew what I was doing, with bizarre dependencies and user permission quirks I'd long forgotten. Meanwhile, my webhost was -- and still is? -- having severe problems with a DNS DDoS (Distributed Denial of Service) attack that is rendering its machines unreachable. Chances are, they were more distracted by that than anything.
In any case, I sincerely apologize for this extended outage. It was supposed to be so quick, the downtime would be indistinguishable from some of the outages we've seen lately. I was finally investing the money to give HawaiiThreads.com and its siblings a better home, and in the end, it took things down longer than they'd ever been down.
Thanks for your patience. The upside of all this is, hopefully, more reliable performance overall. At the very least, I'll have finer, direct control over everything. I'll still set a load limit that will require people to log in at peak times (i.e. limiting guests and search engine robots), but that may be slowly raised as well.
Comment