Chris Betcher

Just to finish the story I started in the last post, here's what transpired (just in case you're interested). The good news is that Optus finally found the reason for this blog being blocked on their network and have restored things to normal. You should now be able to access this site, even on the Optus network, but the nonsense I had to wade through to get things resolved was quite ridiculous. After that last blog post describing the problem with my site being blocked by Optus for reasons unexplained, I posted it out on Twitter and Facebook. It's amazing how quickly that gets a response. To their credit, I heard back from Optus's Social Media Team very quickly offering to help resolve the issue. I'm not sure why tech support problems can't just be resolved by calling Tech Support, and why it takes a very public skewering on social media to get any action these days, but apparently that the way it works now. After a series of very promising back and forth tweet...

If you've tried to access this blog lately from the Optus network, I'm going to make an educated guess and say that you haven't been able to. I have an Optus Cable Internet service at home and about two weeks ago I started to be unable to access my blog. At first I put it down to a temporary network glitch and didn't worry about it. But the problem presisted and I started be become a bit stumped as to what was happening. Every other website on the Net loaded ok, but my own blog was inaccessible. I could get to it from work, and from my phone over Telstra 4G and pretty much anywhere except from home on my Optus service. Then last week I got an email from a reader who said that she also couldn't access the blog and, surprise surprise, she is also on the Optus network. Nor could a friend of hers, who is, you guessed it, also on the Optus network. So I put a note out on Twitter to ask who could access the blog and which ISP they were using. 100% of Optus users could not...