up_the_irons: This IPv6 circuit flapped so frequently that it would always recover before our monitoring would hit the 3 minute threshold, and as such halt the escalation of the incident. Then, it would start all over.
That's why it took a while to notice the problem (I didn't end up getting paged) ***: carvite has quit IRC (Ping timeout: 240 seconds)
carvite has joined #arpnetworks
carvite has quit IRC (Ping timeout: 260 seconds)
carvite has joined #arpnetworks
tellnes has quit IRC (*.net *.split)
awyeah has quit IRC (*.net *.split)
pyvpx has quit IRC (*.net *.split)
tellnes has joined #arpnetworks
awyeah has joined #arpnetworks
pyvpx has joined #arpnetworks
qbit[m] has quit IRC (Ping timeout: 247 seconds)
ziyourenxiang has quit IRC (Ping timeout: 264 seconds)
qbit[m] has joined #arpnetworks brycec: I think I'm seeing some more connectivity issues today, this time with IPv4 traffic.
(Gathering data still, but mentioning it for the sake of logging and such)
Update: False alarm, seems to be The Internet At Large that cut-off one DC from ARP briefly as Level3 was dropped from their routing. (Weird) trobotham: comcast had some major issues earlier
nationwide issues -: brycec is happily not a Comcast users/subscriber ***: ziyourenxiang has joined #arpnetworks
qbit[m] has quit IRC (Ping timeout: 256 seconds)