This post is inspired by this comment on Reddit,
thanking us for improving the stability of GitLab.com. Thanks, hardwaresofton! Making GitLab.com
ready for your mission-critical workloads has been top of mind for us for some time, and it's
great to hear that users are noticing a difference.
Please note that the numbers in this post differ slightly from the Reddit post as the data has changed since that post.
We will continue to work hard on improving the availability and stability of the platform. Our
current goal is to achieve 99.95 percent availability on GitLab.com – look out for an upcoming
post about how we're planning to get there.
GitLab.com stability before and after the migration
According to Pingdom, GitLab.com's availability for the year to date, up until the migration was 99.68 percent, which equates to about 32 minutes of downtime per week on average.
Since the migration, our availability has improved greatly, although we have much less data to compare with than in Azure.
Using data publicly available from Pingdom, here are some stats about our availability for the year to date:
| Period | Mean-time between outage events |
|---|
