Verizon FiOS out for 5th time in 7 months, but …

This time it's at least possible that Verizon is not to blame; both my wife and I are leaning in the charitable direction at this moment … although the conspiracy-minded among you may think otherwise.

In either case, my family didn't get to watch the Red Sox last night, I didn't get my customary early-morning jump on blogging today, and my wife, Julie, had to do the always-annoying wait-for-the-serviceman thing (after cancelling a hair appointment).

These disruptions have happened so frequently of late -- this is at least our fifth major FiOS outage since mid-March -- the details no longer matter. All I know for certain is that our TV, telephone and Internet services went dark yesterday afternoon (is that what they mean by triple play?) and only returned about 2:30 today after visits from two different Verizon techs.

At least the first one spotted the cut cable and the second one did the necessary splicing, which I'll get to in more detail in a moment. (Although I have no idea why the first one couldn't do both jobs.)

Now, I've been accused by a Verizon exec of wanting to "take down" the company, and by a reader of harboring a vendetta -- actually, "Can you spell VANDATTA???" was the verbatim charge. Neither is true, and while I will cop to knowing a human-interest/misery story when I experience one, at this point I'd just as soon be denied any more fresh material if it means my 6-year-old son, Grant, will be able to watch Game 2 of the Red Sox/Angels series tomorrow night.

I'm also aware -- oh, am I aware -- that my family is by no means the only to experience FiOS-related distress. I've written about the fires, and the smoke, and the busted gas lines, and even the sewage so often in recent months that I can't really blame my colleagues for joshing about retribution or that reader for wondering if I might have a "vandatta."

I really don't. It's just that stuff keeps happening.

Like two days ago. Have I mentioned the smoke and flames -- maybe they were just sparks -- from the pole across the street? Definitely not Verizon that time. On Tuesday afternoon, Julie called me at the office to report that an Nstar electric company worker in a cherry picker had somehow done something or other that produced a visible plume of smoke. Our daughter, Emma, said she saw flames, too, although she's only 6 so it's possible she mistook sparks for flames … but again with the details. Anyway, Julie suspected we might be in for some electrical problems, but Tuesday passed into Wednesday morning uneventfully.

Wednesday afternoon we get the FiOS triple play. Might there be some relationship between the Nstar plume and the Verizon cable cut? New homes are being built in our neighborhood and there are enough utility and construction trucks driving about -- both Nstar and Verizon were around Wednesday -- to make any scenario you'd like to imagine possible.

What we know for certain is that someone or something cut the Verizon cable that feeds into our house -- and only our house, apparently -- at cherry-picker height between two poles, realized what had happened (we're presuming it was unintentional -- honestly), coiled the flapping ends and taped them to their respective poles.

Then Josh Beckett shut out the Angels on four hits while I heard only bits and pieces between the static on AM radio.

Julie says the Verizon guys did a good job putting things back in order today.

And we're not bitter.

Just sick of it all.

Join the Network World communities on Facebook and LinkedIn to comment on topics that are top of mind.
Related:
Now read: Getting grounded in IoT