I don’t know how I should describe the nonsense I pay Virgin (“Liberty Global”) good money for. It’s supposed to be an Internet Service Provider, but it falls well short of that far too often, and sometimes for extended periods. Back in the summer I was stranded without service for several weeks.
This morning (or, more precisely, yesterday morning) I found myself unable to read my mail. I also couldn’t ssh to the server. Lynx could get the front page, but only after a long delay. This looked exactly like something that happened last week, when only after rebooting (from the rackspace console) and calling rackspace support did I realise the problem was with Virgin, and traceroute was hanging on a Virgin machine after just a few hops from here. Using my EE 4G connection, all was well.
Today as last week I could see the server was fine, as I could access it from an apache.org machine, but anything from home just timed out. I let that pass, and again used the EE connection to read mail. But after a full day of downtime I thought I’d check a little more. This time traceroute gives me an entirely different destination: 126.96.36.199, which is a machine owned by Virgin! A simple DNS lookup tells me the same. So this time it’s a DNS cockup.
If it’s a DNS cockup, how come I can still browse my website (at least using Lynx, which doesn’t time out first)? There must be a HTTP proxy – with valid DNS – on 188.8.131.52. Smells like deliberate sabotage! And how come this didn’t appear to affect other sites I’ve been to today? For example, $work email (c/o gmail), or this blog @wordpress?
Probing further, this time (unlike last week) I can route to the server by IP address. So it’s definitely just DNS.
WTF is going on? I think it’s time to drop this sick joke of a non-ISP. Maybe get a second 4G connection from another provider for a bit of redundancy: that connection seems good most of the time, but wifi to the 4G modem is totally flakey so I have to use it via USB, which is a poor second-best.
 Yeah, of course any geek should have tested that before going to rackspace. In my defence, I was flat out in bed with a nasty lurgy and in no fit state to browse the web, let alone fix a problem on it.