2 ms·

> On the 4th of October 2021, Meta (former Facebook) and all of its organizations (e.g. Instagram, WhatsApp, Facebook Messenger) were unavailable for up to seve

> On the 4th of October 2021, Meta (former Facebook) and all of its organizations (e.g. Instagram, WhatsApp, Facebook Messenger) were unavailable for up to seven hours. ... This outrage shows that modern solutions must be designed resiliently to enable service provisioning during incidents.... The functional programming language Erlang provides inherent functionality to develop these resilient services. Ironically, What's App is written in Erlang :) That being said, it's cool project! I'm not a concurrency expert so people may disagree, but of all the paradigms I've tried, I feel the actor model has the less mental overhead.

crenwick 5y ago
IIRC that was a DNS issue, which is why it took down all the Meta services. In other words, the WhatApps Erlang servers were probably happily humming away.
- toast0 5y ago
  As a famous haiku once said: It's not DNS There's no way it's DNS It was DNS Although, actually, in this case, it was BGP. The haiku works for both. Now, because (Facebook's) BGP was broken, the DNS servers were unavailable, but WhatsApp will work without DNS (I used to work there, and helped make sure this feature continued during the move to Facebook's infrastructure). Usually, it's your network's DNS that's failing, but sometimes it's WhatsApp's DNS that's failing; either way, having IPs to connect to is sure handy.