[04:20] *** ziyourenxiang has joined #arpnetworks
[04:51] <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.
[04:52] <up_the_irons> That's why it took a while to notice the problem (I didn't end up getting paged)
[05:00] *** carvite has quit IRC (Ping timeout: 240 seconds)
[05:07] *** carvite has joined #arpnetworks
[08:04] *** carvite has quit IRC (Ping timeout: 260 seconds)
[08:04] *** carvite has joined #arpnetworks
[09:09] *** tellnes has quit IRC (*.net *.split)
[09:09] *** awyeah has quit IRC (*.net *.split)
[09:09] *** pyvpx has quit IRC (*.net *.split)
[09:14] *** tellnes has joined #arpnetworks
[09:14] *** awyeah has joined #arpnetworks
[09:14] *** pyvpx has joined #arpnetworks
[09:18] *** qbit[m] has quit IRC (Ping timeout: 247 seconds)
[09:31] *** ziyourenxiang has quit IRC (Ping timeout: 264 seconds)
[10:00] *** qbit[m] has joined #arpnetworks
[11:28] <brycec> I think I'm seeing some more connectivity issues today, this time with IPv4 traffic.
[11:28] <brycec> (Gathering data still, but mentioning it for the sake of logging and such)
[11:34] <brycec> 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)
[12:07] <trobotham> comcast had some major issues earlier
[12:07] <trobotham> nationwide issues
[12:08] * brycec is happily not a Comcast users/subscriber
[16:28] *** ziyourenxiang has joined #arpnetworks
[23:23] *** qbit[m] has quit IRC (Ping timeout: 256 seconds)