The route-leak was something different that seems to have mainly hit west-Europe between 16:52 UTC to 17:08 UTC. There’s a few people in the *NOG communities still digging at the complete details of that right now, but it currently points to have originated from AS200020, impacting a few large upstreams for a short period of time.
So unless this leak caused a catastrophic cascade in FB’s network somehow, it seems to be unrelated. It looked like a valid suspect because timing was very similar between the start of the FB outage and the leak. Jeroen Wunnink Sr. Manager - Integration Engineering www.gtt.net<http://www.gtt.net/> [id:image001.png@01D37331.D1301F60] From: NANOG <nanog-boun...@nanog.org> on behalf of "Kain, Rebecca (.)" <bka...@ford.com> Date: Thursday, 14 March 2019 at 14:36 To: Mike Hammett <na...@ics-il.net>, Roland Dobbins <roland.dobb...@netscout.com> Cc: "nanog@nanog.org" <nanog@nanog.org> Subject: RE: FB? So what happened yesterday? From: NANOG <nanog-boun...@nanog.org> On Behalf Of Mike Hammett Sent: Thursday, March 14, 2019 8:29 AM To: Roland Dobbins <roland.dobb...@netscout.com> Cc: nanog@nanog.org Subject: Re: FB? Do you have a link to the clarification? With the high jitter of news, all I'm finding is people parroting the original statement. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com<https://url.emailprotection.link/?b6x9-Fnx1LAfWyqRtESstZgT_vbCd3MONOqCVFZ0R_BHO80Ox-i-8zIm9qQ1soVeoZrxi8iA3iwJ_b5GpLUD9bw~~> Midwest-IX http://www.midwest-ix.com<https://url.emailprotection.link/?bTe_C0izNVY8kqDiMqBi3hZOjTZ-zNYEmkKhYlGBamvFdtMk4Ad_MAPQonzhIUmKh8G8FAwXEtjMYejM3PlLz6A~~> ________________________________ From: "Roland Dobbins" <roland.dobb...@netscout.com<mailto:roland.dobb...@netscout.com>> To: nanog@nanog.org<mailto:nanog@nanog.org> Sent: Thursday, March 14, 2019 7:23:00 AM Subject: Re: FB? On 14 Mar 2019, at 19:17, Mike Hammett wrote: > I saw one article quoting Roland saying it was a route leak, but I > haven't seen any other sources that aren't just quoting Roland. That was the result of a miscommunication; a clarification has been issued, FYI. -------------------------------------------- Roland Dobbins <roland.dobb...@netscout.com<mailto:roland.dobb...@netscout.com>>
