5 ms·

https://status.slack.com/2022-02/3083852db30af86f https://status.slack.com/2022-02/3083852db30af86f

by oplav 5y ago

ben174 5y ago
Their incident was reported a full 33 minutes after downdetector first started showing spikes in reports. That's pretty bad.
- ceejayoz 5y ago
  A sampling of Down Detector comments on https://downdetector.com/status/aws-amazon-web-services/ https://downdetector.com/status/aws-amazon-web-services/ (which is also showing a spike right now, with no indication of an actual AWS outage I'm aware of): > Was the internet and #AWS recently hacked? Seems like a lot of softwares are not working properly > That’s so odd. Wi-Fi is out for me too. AWS outage? > Another problem which definitely doesn’t make sense why server itself gone wild and not responsive to ssh. We will keep investigating this but it can be aws virtualization issues but interesting. Slack has to do a little more due dilligence than "wifi's down, must be AWS" for their status page.
  - corin_ 5y ago
    They need to do more due diligence on the cause before announcing the cause, but they don't need to do more than confirm users are having problems to update the status page that problems exist. Even assuming they can't instantly see the problems in a dashboard and need to take time to understand user feedback to see which aspects specifically are affected to update the page in more detail, nothing is stopping them from very quickly putting a "Connectivity issues reported by some users, investigating the extent and cause currently" banner at the top of the page which should be ready to go at a moment's notice anyway.
- brynx97 5y ago
  I started having failed messages in channels and threads around 0605 PST... so about 20 minutes. Not too terrible considering the usual due diligence to escalate, determine scope of impact, and then push the buttons to update the status page with the approved messaging.
  - ben174 5y ago
    I completely disagree. It should go yellow the second they see that there is a spike in any abnormality. This type of issue would have been obvious seconds after it occurred. They don't need to report why but they should report that something is wrong. It's not fair to say "it's not me it's you" when they definitely know it's them.

https://status.slack.com/2022-02/3083852db30af86f https://status.slack.com/2022-02/3083852db30af86f

by oplav 5y ago

https://status.slack.com/2022-02/3083852db30af86f https://status.slack.com/2022-02/3083852db30af86f

Their incident was reported a full 33 minutes after downdetector first started showing spikes in reports. That's pretty bad.

ceejayoz 5y ago
A sampling of Down Detector comments on https://downdetector.com/status/aws-amazon-web-services/ https://downdetector.com/status/aws-amazon-web-services/ (which is also showing a spike right now, with no indication of an actual AWS outage I'm aware of): > Was the internet and #AWS recently hacked? Seems like a lot of softwares are not working properly > That’s so odd. Wi-Fi is out for me too. AWS outage? > Another problem which definitely doesn’t make sense why server itself gone wild and not responsive to ssh. We will keep investigating this but it can be aws virtualization issues but interesting. Slack has to do a little more due dilligence than "wifi's down, must be AWS" for their status page.
- corin_ 5y ago
  They need to do more due diligence on the cause before announcing the cause, but they don't need to do more than confirm users are having problems to update the status page that problems exist. Even assuming they can't instantly see the problems in a dashboard and need to take time to understand user feedback to see which aspects specifically are affected to update the page in more detail, nothing is stopping them from very quickly putting a "Connectivity issues reported by some users, investigating the extent and cause currently" banner at the top of the page which should be ready to go at a moment's notice anyway.
brynx97 5y ago
I started having failed messages in channels and threads around 0605 PST... so about 20 minutes. Not too terrible considering the usual due diligence to escalate, determine scope of impact, and then push the buttons to update the status page with the approved messaging.
- ben174 5y ago
  I completely disagree. It should go yellow the second they see that there is a spike in any abnormality. This type of issue would have been obvious seconds after it occurred. They don't need to report why but they should report that something is wrong. It's not fair to say "it's not me it's you" when they definitely know it's them.