The TLS cert expires on December 12.
$ openssl s_client -servername twitter.com -connect twitter.com:443 2>/dev/null | openssl x509 -noout -dates
notBefore=Nov 14 00:00:00 2022 GMT
notAfter=Nov 14 23:59:59 2023 GMT
Not everything is automated. There's a finite amount of time to create new automation, and that time goes first toward the things that happen hourly or daily. The things that happen monthly still get handled by humans. Not everything is in the runbook either, and what is often ends up scattered among many wiki pages and help notes in tools, so it's not easy for a newcomer to find. So those monthly things have to be done by people who remember.
They remember how to clean stuff up when a quota/capacity limit is being approached, and who to call when they need more, and they can expect a response. They remember how to recognize when their service is approaching overload, or about to enter an oscillating state, and they know how to nudge it back toward sanity before the errors start to pile up. None of that happens when whole groups are gone.
Sooner or later, a service will start to run off the rails in one way or another, and the person who inherited that service will either not recognize it or not find the solution in time. Then it's Fail Whale time.
I’d take that bet.
Edit: downvoting doesn’t change reality
Pretty sure a number of AWS and Azure engineers believed the same thing.
Of course, even if it was automated, you still have to pay the bills, and if payroll quit as has been suggested in the thread, I'd be suprised if accounts payable is sticking around
but it looks like somebody had their eyes on that issue
Expires: Tuesday, November 14, 2023 at 3:59:59 PM Pacific Standard Time
The new one isn’t even indexed on crt.sh yet.