This is a story about how weird the Internet can get.
Last night I finished a mix of a synthesizer piece I’ve been working on. I wanted to upload it so that the six or seven people who wander over to this blog could listen to it and be amazed, disturbed, or just plain bored.
WordPress won’t let you upload audio media. Probably some lawyer has convinced them that users would engage in wholesale copyright violation (a good guess) and that WordPress could be liable (who knows?). What I do is, I upload the mp3 files to the server of my “real” website (musicwords.net) and then link to them from this blog. I call it my “real” website because it’s even less visited and less relevant than the blog. But I’ve had it for 12 years or so. It just sits there. It’s on a server operated by a company called Lunar Pages.
So I launch FileZilla Client, the ftp client that I use for uploading music to the Lunar Pages server. And FileZilla can’t access the server. This is the first time that has ever happened.
My first thought is, I just updated to a new version of FileZilla. That could be the source of the difficulty … or the Lunar Pages server could be down. Sure enough, my web browser can’t get to musicwords.net either. So I contact Lunar Pages tech support (via email, after getting tired of listening to their on-hold music). The tech reports that, working from a remote location, he IS able to get to musicwords. So are a couple of my Facebook friends, when I ask them to try. One of them can reach musicwords from a hotel in Guatemala — and within minutes of when I ask folks to give it a try.
The rest of my Internet connectivity works perfectly, but I can’t reach my own website.
So maybe FileZilla has hosed that particular IP address on this particular computer. But no, I have the same problem on my Mac, which connects wirelessly to the same home router. So the problem would have to be in the router, right?
I phone AT&T. It’s their router. The AT&T tech is unable to come up with a theory as to what might be going on. (I cleverly don’t mention to him that I updated FileZilla Client, because if I do, he will instantly blame them. I know how this game is played.) We try unplugging the router and plugging it back in. No luck. We try turning off Windows Firewall — not that that would help with the Mac’s inability to find the site. That doesn’t work either. I quickly turn it back on.
I post a query on the FileZilla support forum. Someone there suggests that I try pinging the server. That doesn’t work from here, either on the Mac or in Windows. ping (Windows) and traceroute (Mac) can’t find the server. So I locate a web page (wormly.com) that can ping a server remotely. wormly can find the server all right — it gives me the number address of the server. But it fails to connect. Evidently this morning the Lunar Pages server is down.
Sort of. Maybe. Sometimes wormly can get a response to 4 of the 8 packets that it sends (a 50% failure rate). Sometimes it gets no response at all. This is highly suspicious.
Naturally, I’m unable to get through to phone support at Lunar Pages. Their system invites me to register my phone number so that a tech can call me back. I do so. No tech calls me back.
Toward the end of the afternoon, after exchanging a couple of emails with Lunar Pages tech support, I try phoning their support line again. This time an automated message tells me that there’s a conflict between the Lunar Pages servers and the AT&T servers, and that AT&T is working on a fix. Well, what do you know! It wasn’t just me having a screwball problem. I may not have been the first to report it, but then again, maybe I was.