AWS as a whole has never been down.
It's Cloud 101 to architect your platform to operate across multiple availability zones (data centres). Not only to insulate against data centre specific issues e.g. fire, power. But also AWS backplane software update issues or cascading faults.
If you read what they did it's actually worse than AWS because their Kubernetes control plane isn't highly-available.
Sounds like they already have their bases covered.
HA architectures exist for a reason because that last step is a massive headache.
Not all DNS servers properly observe caching timeouts, so some customers may experience longer delays before they see it working again.
Because TTLs are a guide not mandatory. And many companies/ISPs ignore it for cost reasons.
A huge multi billion dollar company with "cloud" in its name recently had a big downtime because they did not follow "cloud 101".