There was a wobble at one of the big cloud providers in the back half of May, the sort of thing that shows up first as a flurry of "is it just us?" messages before any official word. I will not pin it to a specific service or a specific minute, because the honest answer is that the early picture was a fog and the status page was the last thing to admit anything was wrong. But the shape of it was familiar enough to write about.
What I find interesting is never the root cause, which usually turns out to be mundane: a config push, a certificate, a control plane that fell behind. What grips me is the gap between when the system knows and when the status page says so. For a good twenty minutes the only reliable signal was other engineers shouting on the internet, while the dashboard sat reassuringly green.
I have been on the other side of that green dashboard, and it is not malice, it is process. Someone has to confirm, someone has to be sure it is not a fluke, someone has to write words that will be screenshotted for years. By the time all that happens, your customers have already known for a quarter of an hour.
The lesson I keep relearning: your own monitoring beats anyone's status page, every time. If you are waiting for a vendor to confirm an outage you are already behind. Watch your own error rates, trust them, and treat the official acknowledgement as a footnote that arrives later.