If shadowcat's public facing website is down for a day, a few people can't read blog posts and maybe we'll miss out on a potential customer - but our existing customers will be entirely unaffected.
If our ticket tracking system is down for a day, it'll annoy the hell out of the existing customers but we can still get the work done since they all have direct email and IM contact info for people.
On the other hand if our ircd is down for an hour, it's time to panic, because that massively interrupts our ability to co-ordinate our work.
External examples:
If linked in is down for a day, I don't care - anything I do on that can wait until tomorrow.
If duckduckgo is down for a day, I am going to burst into tears because I use it all the time for information I want -now- and going via google is substantially more annoying.
So "anything that matters" is really quite relative.
I just did the calculation. That's about a day of downtime. I'd say it's bad if:
- The downtime is scattered all over the year. 1 hour downtime here, 30 min downtime there.
But not if:
- This 1 day of downtime is scheduled, e.g. during the holidays. Scheduled and planned is the keyword. If the client is informed and aware of it, the client will also remain happy.
You'd be surprised how much downtime clients are willing to put up with, as long as they are informed well ahead of time.
Of course nothing will have 100.0 (repeating)% uptime. But 99.7% uptime means it can be down for over 2 hours every month. Anything less than 99.9% uptime (which means 3x less allowed downtime--a big difference) is probably unacceptable, and if downtime costs you serious money, you're going to want more decimal places.
Part of my job is network administration of a small (~50 server) colo/hosting service. It's unacceptable for us to be down for even 30 minutes (from our perspective and our clients). We maybe top out at 5 hours of downtime a year (during a bad year) and most of that (unfortunately) is upstream from us.
Internal examples:
If shadowcat's public facing website is down for a day, a few people can't read blog posts and maybe we'll miss out on a potential customer - but our existing customers will be entirely unaffected.
If our ticket tracking system is down for a day, it'll annoy the hell out of the existing customers but we can still get the work done since they all have direct email and IM contact info for people.
On the other hand if our ircd is down for an hour, it's time to panic, because that massively interrupts our ability to co-ordinate our work.
External examples:
If linked in is down for a day, I don't care - anything I do on that can wait until tomorrow.
If duckduckgo is down for a day, I am going to burst into tears because I use it all the time for information I want -now- and going via google is substantially more annoying.
So "anything that matters" is really quite relative.