It wasn't intended to start troubleshooting end user's internet. It was more to know what is up when my customer hold queue goes up to a couple of thousand calls on hold and my monitoring system lights up like a christmas tree.
--Andrey On Wed, Feb 11, 2015 at 9:12 AM, Bob Evans <b...@fiberinternetcenter.com> wrote: > Since, we reduced ourselves to the level of troubleshooting consumer home > access on a cable network. I can let you know that this happens to me at > home, in silicon valley area of California routinely several times a week. > In fact, so much that I have ATT, Comcast and Verizon hot spot for the > rare event it happens to the first two at the same time. I simply flip > between access points. The only thing I found worth the time it to test > from home is to the destination points where our network has sessions with > ATT, Comcast, etc.. With more than one consumer provider at here at home, > it have happens often enough and it becomes clear that it's rarely worth > the effort to troubleshoot from a consumer end point, unless of course if > you work for them. > > Thank You > Bob Evans > CTO > > > > > > Hey, anyone had problems just now? My team and I at homes lost internet > > access for about 10 min. I also had many sites drop off. Still digging, > > but > > maybe trouble upstream? I'm in 50.133.128.0/17 at home. > > > > --Andrey > > > > >
