The server that 6000.co.za lives in fell over today, and I had to write a blog post on Facebook, just in case I couldn’t write a blog post on here.
Fortunately, Germaine H came to the rescue and propped the server up with a makeshift scaffold fashioned from kebab sticks, dental floss and some clay.
I’ll probably delete the Facebook post now, but let’s preserve it here first, just because:
There is clearly some issue at my hosting company and I’ve been on hold on three different platforms for over an hour now with no response. So – for the moment, at least – today’s 6000dotcodotza blog post will be posted on Facebook.
It’s a blog post about not being able to post a blog post.
You’re reading it right now.
So very meta. I hope your minds can cope.
I’m optimistic that the engineers at Afrihost will get their act together in the very near future and put the server plug back into the wall after the cleaning lady socially distanced it from its socket, although the fact that they haven’t responded to anything in a long, long time doesn’t fill me with hope. They don’t even seem to know that anything is wrong: head to their network status page and ‘hosting’ has got a big green light and the legend:
Everything is looking good!
There are no problems to report at this moment
But there clearly are problems, one of them being that there’s no-one there to report them to.
Please watch out for updates on here, and – if I get lucky (careful now) – on 6000.co.za as well.
Thanks for reading!
So now you’ve read a blog post about a blog post about not being able to post a blog post on the blog I wasn’t able to post on.
And with that, I think it’s high time for a drink.
Oh, and a gentle reminder to follow 6000.co.za on Facebook – just in case this sort of thing happens again.