

Those metrics aren’t any more trustworthy than their own subjective word anyway. If they wanted to say they took more time then they could delay at their whim anyway. If they said their production costs increased, then again, they could spend the money to fit the narrative. On those particular points objective evidence is so susceptible to being gamed that it isn’t really more valuable than their subjective reporting.
Numbers of subscribers/views could be a bit more informative, but then people inclined to disbelieve would claim it’s because of any number of other reasons not because of AI slop.
Problem is that as a provider, if you are sure you are confident you’ll get hit by an outage at some point anyway, it’s actually better for you if a bunch of other big names are brought down at the same time.
Instead of “that one service sucked”, the story is “aws sucked”. If it happens too much people will more widely say “ok they suck for using aws”, but for now the transparency gets them treated more like being affected by an unavoidable external condition.
I’m grateful a lot of sites I like didn’t use aws, but I’m not exactly a common demographic and even I won’t know if she is the services even move or not until another such outage.