There are about fifteen points of failure between my upstairs computer and the Internet at large. So when my web access stopped working last Thursday night, I had a long way to go before I blamed my Internet Service Provider (Bresnan). Having worked at a sort of ISP for four years (the DirectConnect Office at the University of Montana), I was quite used to customers immediately blaming their provider, instead of the technology that was immediately at their control. After all, they hadn’t changed anything, right, so it must be the connection itself. Or, as they each usually liked to call it, “my Internet.” Oh, that’s nice. Got your own personal Internet, huh?
The point is, I didn’t call my ISP the second something went wrong. Because the probability that it was on my end was greater than 86.525%, I started troubleshooting my way upstream. Now, between my upstairs computer, there are a number of failure points. To wit:
- The computer itself connects to a D-Link wireless bridge (the model number escapes me now). This bridge works flawlessly until something goes wrong, at which point it acts like a brick with a five-port switch.
- Downstairs is the bridge’s counterpart, a D-Link Draft N access point. Because of the layout of my house and probably due to its age, the highest signal strength I can on the wireless bridge upstairs is about 66%. The signal has to travel through two walls and a ceiling to get upstairs, and I have the strength set lower than maximum to keep the signal within a reasonable range of my house.
- From there, the signal has to go through a switch to the actual router, which is a LinkSys model running the Tomato firmware.
- Finally, from the router, we get to the cable modem, which plugs into the ‘real’ Internet and signals the end of my responsibility.
Between each of these nodes, of course, are the usual points of failure. This includes the hodge-podge of Ethernet cables I’ve collected throughout my life, any of which might have lost the tab that’s supposed to hold it in place. I had a bit of troubleshooting to do, but was still pretty certain that the problem rested with me.
The first thing I did was connect to the router’s web configuration. This worked right away, which eliminated most of my signal chain. Unless my connection problems were the result of some bad Voodoo (which has happened before; maybe sometime I’ll tell you the horror story of my Ethernet-Over-Power attempts to link my upstairs and downstairs network legs), it was looking more and more like Bresnan’s fault. This was confirmed when I checked the lights on my cable modem. Being a rational-thinking person, I resisted the temptation to reset my router and my cable modem. I have known people who instantly do this even if their connection is a bit slow, and I assume that the one or two times this actually worked was enough to reinforce the superstition in them. The final nail in coffin for Bresnan was that I could release and renew my router’s IP address, but could not use my router to ping anything upstream, except my router’s router.
Since it was a bit late in the day, I resisted the urge to call my ISP and complain. Often people would aggravate me by calling to complain about outages at school. These outages could be beyond our control, as we were not the people in charge of the ‘pipe’ to the Internet, but were merely intermediaries between the campus’s IT department and the dorm residents. I figured that if it were a serious problem, my connection would still not be working in the morning.
As the sun was climbing in the sky I checked, and everything was working. I really didn’t give it much more thought; after all six hours of downtime in the fourteen months I’d been a customer translated to at least three nines (99.9%) of uptime, which was pretty good for a residential service.
I didn’t give it much thought, but my ISP did.
I’m used to being given a bad shake by corporations, but this time Bresnan came through. This weekend, I got a voicemail from an unknown number, which turned out to be a recording from them, apologizing for my downtime. This wasn’t a half-assed CYA thing, because it had obviously cost them some money: somebody had to write the words, and they had to call all the customers who were affected, which would have cost them a bit. I wasn’t expecting any sort of acknowledgement of the outage; after all, I hadn’t called to complain. The fact that they left me a message means that they left everyone who was affected a message, too. And that shows that they care. This is good for me, because a company that cares about its image is probably less likely to be a jerk to its customers.
Often in business, those who are loudest are the ones who receive the most attention. It’s good to see that every once in a corporations can rise about the soullessness with which we often endow them, put on a human face, and treat their customers with respect.