We managed to centralize everything, email, git, even the web. I understand 99.99 looks fine, but is somewhat sad to see half the world without email.
"Service Credit" means: (a) 10% of the total invoice charges for the affected month if the Monthly Uptime Percentage for any calendar month is between 99.0% and 99.9%; or (b) 25% of the total invoice charges for the affected month if the Monthly Uptime Percentage for any calendar month is between 99.0% and 95.0 %; or (c) 50% of the total invoice charges for the affected month if the Monthly Uptime Percentage for any calendar month is less than 95.0%.
Source: https://gsuite.google.com/terms/partner_sla.html
Edit: It appears Microsoft/Office 365 offers the same SLA / 99.9%
One thing to keep in mind is that for each 9 of uptime you have, add about two Zeros to the budget and increase the timeline by one time units up and then double it. So if 99% costs you $100 and a day of timeline on the project, then 99.9% will cost you $10,000 and two weeks of timeline, and 99.99% will cost you $1,000,000 and 4 months of timeline, and 99.999% will cost you $100,000,000 and 8 years of timeline, etc.
It's more like going from the stone age to the bronze age. You need expertise and architecture suitable for achieving high availability, these are your budget increases, they are not linear at all. But the infrastructure itself doesn't necessarily get more expensive, on the contrary, new architecture could allow you to use the cheapest stuff available on the market.
At that point we only lose our issues list, etc.
just use git remotes
Which is to say that if I can get 75% of my work done without one of my tools then the impact to the business of an hours long outage is relatively small. Even if the outages are frequent, we can learn to adapt (real example: oversubscribed Atlassian products crashing on Friday afternoon due to resource exhaustion - move work to Thursdays or Mondays).
But if the entire system goes down due to shared hardware or simultaneous software upgrades, then you can end up with an office full of people who can't get a lick of work done. Heterogeneity wins out in this case, and 9's can be measured in a way that doesn't reflect the actual business impacts accurately.
Just asking.
Other than that, thirty minutes downtime 14 months ago when the public-facing redundant routers mis-detected a failover, failed STONITH and entered split-brain status.
I wouldn't commit to better than 99.9% with our infrastructure (single datacenter with remote data backups) but we exceed the metric most years (99.99% in all but one of the last ten years).
I can't recall the last unplanned outage since the 2008 one.
That was what kept me on GMail for so long. But about a month ago I moved several accounts to FastMail (at the urging of others on HN), and have been pleasantly surprised by the results.
FM seems to have a lot fewer false positives, and the amount of spam that gets through seems only marginally more than with GMail.
FM offers a 30-day free trial, which even includes using your own domain. That I found surprising. Usually trials so restricted you can't really get a sense of what you're getting into.
It doesn’t look like they’re doing much beyond what I did 10+ years ago when I was running high volume mail servers and it was never enough: https://www.fastmail.com/help/technical/spamchecks.html
Make the move away from Google, don’t be scared and don’t be guided by false excuses.
That's $500-$1000 a year on Fastmail's Standard plan, the lowest tier plan that allows you to use your own domain.
Im not really interested in managing everything that I perceive goes into managing my own email server (ip reputation management and having to keep a box online 24/7)
This myth that nobody but Gmail can handle spam needs to die. It was true in 2006, but it is not true in 2019.