[OT from cottage renovations]
it is customary to dislike the 'phone company. Lily Tomlin's "one ringy-dingy" skit is still one of the best telco rants ever: not only is it funny, but we can all relate to it.
the cottage relies on Verizon DSL for broadband internet access which is shared by several devices and applications.
- inbound and outbound ATCS data streams are always running but need negligible bandwidth.
- streaming audio is also low impact and only runs when somebody connects to it, which isn't very often.
- the porch webcam needs the occasional burst for uploading image captures triggered by motion detection to the HSP in Toronto.
- the remaining usage is on-demand: email, web browsing and image transfer for this journal, of which the latter two can be bandwidth intensive though again only in bursts.
for the most part it just works. but now and then something happens: there's still connectivity, but the throughput drops to a trickle. of the uses above, the first two continue without interruption and the rest basically shut down. when it happens, as it did Monday, I check all the devices attached to the house network, the router and DSL modem, and reboot everything. that's just a ritual, though, and like most is completely pointless because the problem is on the Verizon end of the connection.
excruciating as it is for data to not move (even simple web pages time out), far worse is the prospect of interaction with the carrier's support staff. trouble calls generally result in 15-20 minutes of being on hold and are answered by folks who insist the problem is on this end and who absolutely cannot and will not deviate from a canned script that's completely unsuitable to the situation and configuration here. they also refuse to escalate the query to a supervisor, which would generally be the only other way to get the information to a technician who could actually do something about it. it is, in a word, hopeless.
I have come to associate these network disruption with sightings of telco repair trucks in the neighbourhood. it seems that whenever they turn up somebody's service or otherwise touch the infrastructure, circuits get switched to different wire pairs and the line ends up on a voice grade rather than a data grade pair.
I've learned -- the hard way -- that the only workable approach is to ride it out and just wait for it to go away. it did just that, about 24 hours after it started (this time I lucked out as sometimes it goes on for days at a time).
so I spent the day puttering in the yard, an activity infinitely more soothing than waiting for the web that wasn't there or trying to take on the carrier. even taking Meg to the vet for checkup and booster shots (she's fine) was better than that.