4 ms·
At the risk of going recursive, how do you define not bad? Could be worse?
by MeetingsBrowser 7mo ago
At the risk of going recursive, how do you define not bad?
Could be worse?
- graphememes 7mo agoYes, and honestly, for it's usage, similar feelings for AWS, not bad. Although, I guess I could ask, are you looking for a rubrick that I follow? Not trying to be inflammatory, just trying to understand what exactly you're looking for. I am mostly going off of overall usage vs downtime.
- MeetingsBrowser 7mo agoHow often can a service be down and still be considered to have incredible uptime. Personally, I would define incredible uptime as roughly 5 minutes down per month, or around 99.99% uptime. GitHub is currently sitting at about 70 hours of downtime per month, on average across all services.