Yeah I just saw that date and that is odd, I got the link yesterday from somewhere and didn't notice the date was old.
They do mention the configuration change issue in this one though that is dated today 14th - https://www.cbsnews.com/news/facebook-instagram-down-wednesday-facebook-blames-server-configuration-for-longest-ever-outage/ >From my understanding yesterday is they invalidated their world cache and all the traffic hit their backend quickly overwhelming their servers. It was strange that they didn't really talk about the issue just some brief messages on their twitter saying it wasn't ddos. On Thu, 14 Mar 2019 at 15:08, Luke Guillory <lguill...@reservetele.com> wrote: > That’s old. > > > > By Robert Johnson on Thursday, September 23, 2010 at 7:29 PM > > > > > > Luke > > > > Ns > > > > > > > > *From:* NANOG [mailto:nanog-boun...@nanog.org] *On Behalf Of *Selphie > Keller > *Sent:* Thursday, March 14, 2019 4:06 PM > *To:* Mike Hammett > *Cc:* NANOG list > *Subject:* Re: FB? > > > > I did see this article indicating they had somehow invalidated their cache > in a botched deployment of changes - > https://www.facebook.com/notes/facebook-engineering/more-details-on-todays-outage/431441338919/ > > > > On Thu, 14 Mar 2019 at 06:18, Mike Hammett <na...@ics-il.net> wrote: > > So what happened at Facebook today? 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. Usually there are a few independent posts out > there by now. > > > > ----- > Mike Hammett > Intelligent Computing Solutions > http://www.ics-il.com > > Midwest-IX > http://www.midwest-ix.com > > > >
