Hi folks, There was a problem with some prefixes New England rerouting properly during a topology change. We feel that problem has been corrected and would like to know if there were other problems seen overnight (after 0000 UTC) in that region. If you send to me, please include specific time and source/destination IP address information. Thanks, Tony On Wed, Feb 11, 2015 at 1:50 PM, Chuck Anderson <cra@wpi.edu> wrote:
I saw a problem only with my 50.176.16.0/21 subnet IP. My 24.147.20.0/21 subnet IP was working fine throughout.
On Wed, Feb 11, 2015 at 01:44:53PM -0500, Robert Webb wrote:
Looks like there were at least a couple of others that saw issues also.
http://www.dslreports.com/forum/r29852647-Connectivity-Comcast-down-Quincy-M...
Robert
On Tue, 10 Feb 2015 21:52:29 -0500 Andrey Khomyakov <khomyakov.andrey@gmail.com> wrote:
My boss has comcast at home in Milton, MA, said all was fine. Must have been prefix specific. Trace would die somewhere in level3 at the time. Was tracing to 8.8.8.8
On Tuesday, February 10, 2015, Dan Brisson <dbrisson@uvm.edu> wrote:
FWIW...no problems here in Vermont on Comcast business.
-dan
Dan Brisson Network Engineer University of Vermont
On 2/10/15 8:45 PM, Kevin Kadow wrote:
On Tue, Feb 10, 2015 at 7:27 PM, Andrey Khomyakov < khomyakov.andrey@gmail.com> wrote:
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.
You were only out for 10-15 minutes? More like an hour in New Hampshire.
traceroutes would die out in Needham, Woburn, or whatever 4.68.127.229 is.