81–90 of 107 posts
https://health.aws.amazon.com/health/status is now showing the issue. Our first canaries fired for this at 9:43 PDT local time. The status page updated at 10:13.
Our first canaries at 9:21 PDT
It's crazy to me how long it takes Amazon to notify users that there is even an issue. I think it took 15 minutes for them to acknowledge an issue, thats a lot of time for our services.
I continue to be irritated that services that consistently return errors are characterized as "increased error rates" or "increased latency". They seem to use those phrases for any kind of outage.
Earlier quoted context omitted.
I continue to be irritated that services that consistently return errors are characterized as "increased error rates" or "increased latency". They seem to use those phrases for any kind of outage.
It's all networking issues as you're remotely access them remotely, so of course it's increased error rates or increased latency. When a piece of gear stops responding the network tries to self-heal as designed which causes those issues.
I'm reasonably sure they know when a service isn't functional at all.
Cloud9 is also down. Joy. Edit to add: I can't seem to access my NHL Season Tickets via Ticketmaster either...
Earlier quoted context omitted.
of all things to connect to a smart home, the locks to my house would be the absolute bottom of the list. i hate coming home when the power is out and cannot open the garage door. i couldn't imagine not being able to get in at all. as far as not getting out, any lock unable to be unlocked from inside seems like something should not be allowed to be made. ever.
> as far as not getting out, any lock unable to be unlocked from inside seems like something should not be allowed to be made. ever. This would vary by jurisdiction, but locks without an unlock lever are usually prohibited by the fire code.
Earlier quoted context omitted.
That's because it's a political issue inside AWS. They have the technology to report it automatically, but there's a strong pressure not to post "green-i" or yellow or red, because those things impact SLA payments. So if there's any way they can spin it as not an outage they will try not to post it.
Can confirm this, it's political. It's always great seeing the "rationality" for not doing the right thing. After the 3 outages last December, I can remember a certain person in a certain global outage slack channel laughing at customers who weren't "resilient" enough to withstand the outage. Then AWS focused a resiliency campaign to document all those customers risks, as if AWS's own poorly designed system wasn't th…
It's crazy to me how long it takes Amazon to notify users that there is even an issue. I think it took 15 minutes for them to acknowledge an issue, thats a lot of time for our services.
https://downdetector.com/status/aws-amazon-web-services/ My Roomba isn't working!!! hahahaha!
A few minutes after I hear the fans on my pc start ramping up. Sure enough, I open the system monitor and see chrome going crazy on my CPU. In chrome, I open the task manager, then click sort by CPU. The entry at the top of the list reads:
> subframe: facebook[dot]com
I get taken to the open downdetector.com tab after double clicking the entry. After closing the tab everything goes back to normal.
Does anyone know why or what downdetector/facebook would do that requires 100% of my CPU's resources?
PS. I have ublock origin installed. My cpu is an i9-12900K.