I wish cloud providers would just communicate outages to services I use like this to me!
In general, they seem bad at communicating relevant information. Just looking over at emails from Google, every single one of the last 10 emails they sent me was not relevant to me specifically.
> "[Important notice] Tax changes in Nepal" (yet I have never made a sale in Nepal)
> "Secure your Google Admin account with these best practices" (yet I already do all those things)
> "Preparing for the upcoming Google Ads change on October 31, 2023" (it's all about mediation waterfalls, and I'm 90% sure I don't use them, and 100% sure I don't know what they are)
Slack let’s you subscribe directly to an RSS feed using /feed.
Sounds like a good approach nonetheless
https://cloud.google.com/service-health/docs/overview#how-pe...
8:18 PM
APP UPDATE: Global: Google Kubernetes Engine Nodepool Upgrade Failures
Incident began at 2023-10-02 11:29 (all times are US/Pacific).Summary: Global: Google Kubernetes Engine Nodepool Upgrade Failures
Description: A mitigation has been rolling out and we are assessing its effectiveness. We will provide an update byTuesday 2023-10-10 12:00 US/Pacific with current details.
Diagnosis: A small number of customers are experiencing failed nodepool upgrades. Customers experiencing this, may see "Internal error" in Google Cloud Console. Retrying is suggested but may...
When you suspect things are broken, check X (FKA Twitter).
Other devs will be talking about it before there's an official status page.
If we as an industry can't think of something better (cough honest status pages cough) … can we at least transition these tweets to Mastodon.
If your connector between your status monitor and the service breaks you'll have some subset of users panicking and causing problems (or asking for refunds for outages) when the service was up the entire time.
3rd party services are the only ones that you'll get a "more honest" but not always correct view of what the actual status is.
Where I work, just about any non-false-alarm incident ends up on the status page in a timely manner. There's nothing stopping the likes of AWS from doing the same except for culture.
Well, maybe not at AWS scales though, if they have thousands of everything =/
You can easily check it manually. Search for "EBS" and see a bunch of people talking about EBS timeouts or whatever. That was what I was getting at.
But yeah scraping is harder now.
> You can easily check it manually.
You cannot. Twitter's site is plagued by redirect loops. If you work around those, these days /search just redirs to the login page. You can view single tweets, but there won't be any replies. (I have no idea if the site formerly known as Twitter is still rate-limiting views, or if they canned that.)
It is unusable if you're not actively logged in, and some of us have no desire to give away a phone number just to see AWS's true status.
See all those green there? Once it started becoming "monitored" by VPs instead of the software engineers on call, they started to become political. I bet there are several sev2s happening for several of those services even as we speak but it still shows green to the outside observer. If one has access to the actual metrics for those services, i bet we would see a different story than what is shown on the "status" page.
Not once has a status page that's devoid of information or slow to update ever saved face. I am far more annoyed to have to continue to verify "no, it is indeed that your service is down, not mine" and then file a support ticket. I am triply annoyed if the response from support is "ah yes that's a known problem and we're working on it" — known, and you just didn't bother to communicate.
I miss the days when Github had graphs. Even if they simply hadn't had the time to put a message on the page, you could tell from the graphs that it was Github. But even with "more information" that some PM might not like being put out publicly, Github felt more reliable & stable in those days.
At the end of the day, no amount of political gamesmanship will save you from having to actually run a reliable service, and gamesmanship just makes it more likely I'll ascribe false positives to your service, further lowering my perception of its reliability.
It's so watered down that the "AWS" emoji in our Slack instance is literally a meme of the status page.
I am sure that counts. Probably tied into someone's bonus as well.
very likely not just one.
not sure how this could work, as some qa/sre would have to be paid even more in order to effectively work against this type of falsification. there would have to be a very strong incentive for the company to do that.