Facebook, WhatsApp and Instagram have all gone down in a major outage.
Such problems – especially after they have been ongoing for hours – likely indicates there is a major problem with the technology underpinning Facebook’s services.
And it could last for hours. In 2019, when it suffered from its biggest ever outage, it was more than 24 hours from the beginnings of the problem until Facebook said it was resolved.
:: Follow our live coverage of the outage here ::
What’s more, Facebook might never truly reveal what caused the problems. After that record outage in 2019, it said only that the problems were “a result of a server configuration change”.
This time around, at least some of the problems are related to the domain name system, or DNS, which works something like a phone book for the internet. When a user types in a web address – such as facebook.com – then the computer needs to turn that into a an IP address, which is a series of numbers, so that it can access the data that makes up the page you want to see.
With Facebook down, however, that system is not working: the computer searches for the numbers it wants to see, but the numbers aren’t there. Facebook’s servers should provide them, but the phone book is in effect blank.
To sign up to our breaking email alerts click here
That means that anyone attempting to access the site will see an error code, depending on what browser they use. Apps might work a little differently – they will still show existing content, such as WhatsApp messages or Instagram posts – that have already been downloaded, but they will not be able to ask Facebook’s servers for new ones.
It is far from the only company to suffer such issues. In July, many major websites – including those of seemingly unconnected companies such as Home Depot and Delta Airlines – went down because of problems at Akamai, which offers DNS to its customers.
But Facebook’s DNS problems are only a symptom, even if they are the one that means many people are unable to access those sites. The system would not break spontaneously, and so it is likely that something has happened to the underlying infrastructure – a stray settings change, a physical outage at a server, or something else entirely – that has stopped it from working.
