Well, 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!
I 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.
Unfortunately 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.
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.