<story><title>Facebook-owned sites were down</title><url>https://www.facebook.com/</url></story><parent_chain><item><author>okwubodu</author><text>I don’t know how true it is but a few reports claim employees can’t get into the building with their badges.</text></item><item><author>kiernanmcgowan</author><text>My suspicion is that since a lot of internal comms runs through the FB domain and since everyone is still WFH, then its probably a massive issue just to get people talking to each other to solve the problem.</text></item><item><author>Animats</author><text>There&amp;#x27;s still no connectivity to Facebook&amp;#x27;s DNS servers:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    &amp;gt; traceroute a.ns.facebook.com
      traceroute to a.ns.facebook.com (129.134.30.12), 30 hops max, 60 byte packets
      1  dsldevice.attlocal.net (192.168.1.254)  0.484 ms  0.474 ms  0.422 ms
      2  107-131-124-1.lightspeed.sntcca.sbcglobal.net (107.131.124.1)  1.592 ms  1.657 ms  1.607 ms 
      3  71.148.149.196 (71.148.149.196)  1.676 ms  1.697 ms  1.705 ms
      4  12.242.105.110 (12.242.105.110)  11.446 ms  11.482 ms  11.328 ms
      5  12.122.163.34 (12.122.163.34)  7.641 ms  7.668 ms  11.438 ms
      6  cr83.sj2ca.ip.att.net (12.122.158.9)  4.025 ms  3.368 ms  3.394 ms
      7  * * *
      ...
&lt;/code&gt;&lt;/pre&gt;
So they&amp;#x27;re hours into this outage and still haven&amp;#x27;t re-established connectivity to their own DNS servers.</text></item></parent_chain><comment><author>cududa</author><text>I remember my first time having a meeting at Facebook and observing none of the doors had keyholes and thinking &amp;quot;hope their badge system never goes down&amp;quot;</text></comment>
<story><title>Facebook-owned sites were down</title><url>https://www.facebook.com/</url></story><parent_chain><item><author>okwubodu</author><text>I don’t know how true it is but a few reports claim employees can’t get into the building with their badges.</text></item><item><author>kiernanmcgowan</author><text>My suspicion is that since a lot of internal comms runs through the FB domain and since everyone is still WFH, then its probably a massive issue just to get people talking to each other to solve the problem.</text></item><item><author>Animats</author><text>There&amp;#x27;s still no connectivity to Facebook&amp;#x27;s DNS servers:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    &amp;gt; traceroute a.ns.facebook.com
      traceroute to a.ns.facebook.com (129.134.30.12), 30 hops max, 60 byte packets
      1  dsldevice.attlocal.net (192.168.1.254)  0.484 ms  0.474 ms  0.422 ms
      2  107-131-124-1.lightspeed.sntcca.sbcglobal.net (107.131.124.1)  1.592 ms  1.657 ms  1.607 ms 
      3  71.148.149.196 (71.148.149.196)  1.676 ms  1.697 ms  1.705 ms
      4  12.242.105.110 (12.242.105.110)  11.446 ms  11.482 ms  11.328 ms
      5  12.122.163.34 (12.122.163.34)  7.641 ms  7.668 ms  11.438 ms
      6  cr83.sj2ca.ip.att.net (12.122.158.9)  4.025 ms  3.368 ms  3.394 ms
      7  * * *
      ...
&lt;/code&gt;&lt;/pre&gt;
So they&amp;#x27;re hours into this outage and still haven&amp;#x27;t re-established connectivity to their own DNS servers.</text></item></parent_chain><comment><author>jonny_eh</author><text>&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;sheeraf&amp;#x2F;status&amp;#x2F;1445099150316503057&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;sheeraf&amp;#x2F;status&amp;#x2F;1445099150316503057&lt;/a&gt;</text></comment>