4 ms·
Doesn’t work for me either. Of course, the calendar says “100% uptime” even as there’s an outage right below it: https://status.slack.com/calendar https://statu
by saagarjha 6y ago
Doesn’t work for me either. Of course, the calendar says “100% uptime” even as there’s an outage right below it: https://status.slack.com/calendar https://status.slack.com/calendar
- fgkramer 6y agoWell, in their defence, you can't really know how much the uptime is going to be affected by until the incident is resolved. If it was a live counter then you'd see the uptime go up as the month progresses!
- deathanatos 6y agoJust compute live uptime for the portion of the month that has elapsed thus far…
- filleokus 6y agoI don't have a problem with it if they update the uptime stats afterwards, but why couldn't it be implemented "live"? Basically time "down" / total time elapsed during $period. At the beginning of the month/quarter/period you'd be at 100% (if they are up at that moment). Or even simpler, just have it be a measurement of a rolling window X days in the past.
- tspike 6y agoBecause then the metrics can't be reviewed/vetoed by executives before being published. Optics > accuracy for most organizations, sadly.
- boston_clone 6y agoUnfortunately true. About a year ago, I had reported a pod-specific issue to Zendesk (I'm fuzzy on the details). They confirmed the issue but also acknowledged that it would not reflect on status.zendesk.com. I've questioned status pages since.