5 ms·

No, their health page is the worst place to look for honest information. They don't want to lose another decimal on their uptime percentage. Try down detector.

by ben174 5y ago

No, their health page is the worst place to look for honest information. They don't want to lose another decimal on their uptime percentage. Try down detector. https://downdetector.com/status/slack/ https://downdetector.com/status/slack/

totaldude87 5y ago
downdetector is my go to status page
oplav 5y ago
https://status.slack.com/2022-02/3083852db30af86f https://status.slack.com/2022-02/3083852db30af86f
- 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.
martin_a 5y ago
> They don't want to lose another decimal on their uptime percentage. I was curious and found it: > September 2021 99.999% uptime Loonies.
yxwvut 5y ago
Entertaining to see them simultaneously claim 100% uptime in February and list outages both yesterday and today. If 'users can't send or receive messages' on a messaging platform, your service is down.
- sumo89 5y ago
  Can't fail those SLAs if you make up the numbers
  - srveale 5y ago
    "When a measure becomes a target, it ceases to be a good measure"
    - maxbond 5y ago
      I think in this case it's more, you can't be held accountable without oversight. You can't be held accountable to measures you define, measure, and report yourself without any oversight from anyone else.
- psanford 5y ago
  If you look today (one day after the incident) you'll see that the status page now shows only 3 9s of uptime for the quarter.
- bmitc 5y ago
  What's also interesting is their carefully crafted language. They have "Slack is not loading for some users" listed everywhere instead of "most users" or "all users" and also "Something's not quite right" instead of "Something's not working" or "Something's wrong".
sillyquiet 5y ago
time to start up a SaaS service status SaaS to serve SaaS status
- dijit 5y ago
  doesn't atlassian do that? and Pingdom? https://documentation.solarwinds.com/en/success_center/pingdom/content/topics/public-status-page.htm https://documentation.solarwinds.com/en/success_center/pingd... https://www.atlassian.com/software/statuspage https://www.atlassian.com/software/statuspage
  - sillyquiet 5y ago
    oh true! I guess there really is nothing new under the sun anymore.
  - guiriduro 5y ago
    Atlassian charge insanely much for hosting ... a web page.
    - dijit 5y ago
      Well, apparently it's hard. Even Amazon can't do it properly.
- weird-eye-issue 5y ago
  I've definitely already seen that before edit: Yeah it was Atlassian's Statuspage. I am pretty sure I saw them before they were acquired though and never realized
falcolas 5y ago
For most large companies, their health page is updated manually by project managers or directors. The reason is simple: accurate reports make them look bad. And make them liable for refunds due to broken SLAs. Amazon's famous for this; it's no surprise that Slack does it too.

by ben174 5y ago

totaldude87 5y ago

downdetector is my go to status page

oplav 5y ago

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

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.

martin_a 5y ago

> They don't want to lose another decimal on their uptime percentage. I was curious and found it: > September 2021 99.999% uptime Loonies.

yxwvut 5y ago

Entertaining to see them simultaneously claim 100% uptime in February and list outages both yesterday and today. If 'users can't send or receive messages' on a messaging platform, your service is down.

sumo89 5y ago
Can't fail those SLAs if you make up the numbers
- srveale 5y ago
  "When a measure becomes a target, it ceases to be a good measure"
  - maxbond 5y ago
    I think in this case it's more, you can't be held accountable without oversight. You can't be held accountable to measures you define, measure, and report yourself without any oversight from anyone else.
psanford 5y ago
If you look today (one day after the incident) you'll see that the status page now shows only 3 9s of uptime for the quarter.
bmitc 5y ago
What's also interesting is their carefully crafted language. They have "Slack is not loading for some users" listed everywhere instead of "most users" or "all users" and also "Something's not quite right" instead of "Something's not working" or "Something's wrong".

sillyquiet 5y ago

time to start up a SaaS service status SaaS to serve SaaS status

dijit 5y ago
doesn't atlassian do that? and Pingdom? https://documentation.solarwinds.com/en/success_center/pingdom/content/topics/public-status-page.htm https://documentation.solarwinds.com/en/success_center/pingd... https://www.atlassian.com/software/statuspage https://www.atlassian.com/software/statuspage
- sillyquiet 5y ago
  oh true! I guess there really is nothing new under the sun anymore.
- guiriduro 5y ago
  Atlassian charge insanely much for hosting ... a web page.
  - dijit 5y ago
    Well, apparently it's hard. Even Amazon can't do it properly.
weird-eye-issue 5y ago
I've definitely already seen that before edit: Yeah it was Atlassian's Statuspage. I am pretty sure I saw them before they were acquired though and never realized

falcolas 5y ago

For most large companies, their health page is updated manually by project managers or directors. The reason is simple: accurate reports make them look bad. And make them liable for refunds due to broken SLAs. Amazon's famous for this; it's no surprise that Slack does it too.