No, it was a route leak by a colo provider (Axcelx) downstream. Regards,
Tim Raphael > On 1 Jul 2015, at 11:37 am, Justin Paine via NANOG <nanog@nanog.org> wrote: > > Any confirmation if the AWS outage was leap second-related? > > ____________ > Justin Paine > Head of Trust & Safety > CloudFlare Inc. > PGP KeyID: 57B6 0114 DE0B 314D > > >> On Tue, Jun 30, 2015 at 8:32 PM, Dovid Bender <do...@telecurve.com> wrote: >> I read that and that at midnight local time since that's when you have the >> extra second. I know a large carrier in Israel is down. Waiting for conf. If >> it's leep second related. >> >> ------Original Message------ >> From: Stefan >> Sender: NANOG >> To: frnk...@iname.com >> Cc: nanog@nanog.org >> Subject: Re: leap second outage >> Sent: Jun 30, 2015 23:30 >> >> This was supposed to have happened @midnight UTC, right? Meaning that we >> are past that event. Under which scenarios should people be concerned about >> midnight local time? Lots of confusing messages flying all over... >>> On Jun 30, 2015 10:13 PM, <frnk...@iname.com> wrote: >>> >>> We experienced our first leap second outage -- our SHE (super head end) is >>> using (old) Motorola encoders and we lost those video channels. They >>> restarted all those encoders to restore service. >>> >>> Frank >> >> Regards, >> >> Dovid
