101–110 of 840 posts
Earlier quoted context omitted.
My feeling is this is an AWS issue. Our services hosted in AWS are not working either.
Do you have more info like services, regions etc? I see all green checks on the AWS Status page.
I'm sure you know this already, but that status page isn't worth the cycles on your CPU, you would be better served asking the toaster if AWS is functioning properly than checking that status page.
These events seem to be happening almost on a monthly basis now. IRC was never this unreliable and at least with netsplits it was obvious what had happened because you'd see the clients disconnect. IME messages just fail to send with Slack, then you can retry but they're not properly idempotent and you end up sending the messages twice. It's really poor.
My feeling is this is an AWS issue. Our services hosted in AWS are not working either.
These events seem to be happening almost on a monthly basis now. IRC was never this unreliable and at least with netsplits it was obvious what had happened because you'd see the clients disconnect. IME messages just fail to send with Slack, then you can retry but they're not properly idempotent and you end up sending the messages twice. It's really poor.
My feeling is this is an AWS issue. Our services hosted in AWS are not working either.
This is definitely going to catalyze a nascent move over to Discord for my team. (~80 person consulting agency, distributed)
When I was at Uber, we noticed that most incidents are directly caused by human actions that modify the state of the system. Therefore, a large "backlog" of human actions that modify the system state have a much higher chance of causing an incident. My bet is that this incident is caused by a big release after a post-holiday "code freeze".
Doubt anyone releasing big changes Monday morning.
Earlier quoted context omitted.
Do you have more info like services, regions etc? I see all green checks on the AWS Status page.
> I see all green checks on the AWS Status page. I'm sure you know this already, but that status page isn't worth the cycles on your CPU, you would be better served asking the toaster if AWS is functioning properly than checking that status page.
These events seem to be happening almost on a monthly basis now. IRC was never this unreliable and at least with netsplits it was obvious what had happened because you'd see the clients disconnect. IME messages just fail to send with Slack, then you can retry but they're not properly idempotent and you end up sending the messages twice. It's really poor.
My feeling is this is an AWS issue. Our services hosted in AWS are not working either.