Facebook and the services owned by the social media giant were hit hard by a massive outage this afternoon that resulted in all such services going down for nearly four hours at this point. However, Google’s 18.104.22.168 DNS service, which slowed down amid the Facebook crash, is caught in the mess.
DNS, or Domain Name System, basically acts as a way for browsers to translate an IP address into something that users can easily understand. A DNS resolver is the server that handles this translation, and often users will use one provided by their ISP or use a third-party option.
Google’s DNS resolver is 22.214.171.124, and there is also 126.96.36.199, although this one doesn’t seem to be affected to the same extent. The company launched the resolver in 2009 with the goal of “connecting to the Internet much faster.”
The response time and performance of Google’s DNS service were affected amid the Facebook outage due to the influx of additional traffic. As requests to Facebook from regular users as well as online services continuously fail and retry, these DNS services start to take on a higher load than usual which can adversely affect performance as various benchmarks and monitoring tools spectacle. The service still works despite the increased load.
Google’s DNS service is not alone in seeing the effects of the Facebook outage. Telegram confirmed he was facing a heavier load as WhatsApp users switch over, and CloudFlare’s DNS service is to be touched in the same way with an increase in requests by the Facebook outage, but without any problems as a result.
FTC: We use automatic affiliate links which generate income. Following.
Check out 9to5Google on YouTube for more information: