For bonus points, folks have figured out that "read" means "load in any way, shape, or form", and includes things like replies to a post that loads. People are hitting the rate limit from nothing, sometimes on loading literally one post (due to it having a lot of replies). It's wildly broken.
It's worth noting, google was due to cancel cloud services because of non-payment, well. Yesterday/today. There's reporting some sort of deal was made to continue functionality on that front, but this whole mess looks a lot like their hosting services (quite possibly involving more companies than just google) decided they were tired of musk's shit and stopped providing, with twitter's reaction being to drastically cut traffic in a very short period to keep their in-house stuff from buckling entirely.
... though do note, the uptick in scraping is largely self-inflicted due to twitter playing fuck-fuck games with API access and such. The issue* was manageable before the management in question decided to intentionally screw the pooch.
* To the extent it actually was one, mind; it's a big claim to say one of the biggest social media websites in the world was being meaningfully impacted in regards to server capability by what scraping efforts existed, and one of the only sources making that claim is, well. Twitter. Currently lead by a prolific liar, one known for doing things like not paying their bills and firing a great deal of what staff might have been able to navigate the problem, heh. It's more likely server capability's been kneecapped by poor admin decisions than anything related to scraping.