There was a wobble at one of the big providers this week, the sort where half your feed suddenly fills with "is it just me" before the status page has admitted anything. I watched it unfold from the cheap seats, which is to say nothing I run was downstream of it, and it was a strange relief to be a spectator for once.
You can read these things in real time if you know where to look. The status page is always last and always grudging. The signal is the chorus of unrelated services degrading at once, all leaning on the same quiet dependency nobody lists on their architecture diagram. When three things that have nothing to do with each other break together, you have found a shared single point of failure, and you are usually watching it on someone else's bill.
The part I keep relearning is how deep these dependencies run, and how invisible they are until the day they are the whole story. Someone, somewhere, was having the worst afternoon of their quarter, and the rest of us got a free reminder to go and check what we are quietly assuming will always be there. I went and checked. It mostly was. Mostly.