Facebook made BGP withdrawals near the time of the incident, however, 2 prefixes covering two of their 4 DNS nameservers (a and b) are still being advertised across the Internet. They are reachable on the Internet but traffic is dropping at Facebook’s network edge.
ThousandEyes tests can confirm that at 15:40 UTC on October 4, the Facebook application became unreachable due to DNS failure. Facebook’s authoritative DNS nameservers became unreachable at that time. The issue is still ongoing as of 17:02 UTC.
"Simplified Monitoring of Patients in Situations of Mass Hospitalization (MoSimPa) - Fighting COVID-19" by Lisandro Damián Nicanor Pérez Meyer https://t.co/DKsYhfpaiK
The authoritative and real-time state of internet outages powered by ThousandEyes.
Our time to give back clarity on the internet during uncertain times when a majority of the workforce is remotely contributing.
Super proud of the…https://t.co/EMTHka3hg6 https://t.co/R6UuRJdxHI
ICYMI - [video] @rbenencia at #debconf19 presenting Shoelaces an open source tool to automate the bootstrapping of servers https://t.co/dUHoTZOITm #opensource
Humbled to be presenting Shoelaces, developed at @thousandeyes, at @debian#debconf19 in ~ 20 minutes. Especially on #SysAdminDay. Follow the stream! https://t.co/9JWueXO2bz
[update] ThousandEyes looks at issues from the user’s vantage point. When investigating Facebook’s issues today, we’re not seeing any BGP changes that are affecting connectivity, packet loss or latency.