🔧GitHub's 98.31% Uptime Highlights Reliability Challenges
GitHub Actions' 12-hour downtime in 30 days
TL;DR
GitHub's 98.31% uptime reveals the complexity of reaching higher reliability tiers. GitHub Actions faced 12 hours of downtime in the last month, highlighting the challenges of achieving 'three nines' reliability.
GitHub's 98.31% uptime shows the challenges of reaching higher reliability tiers. GitHub Actions faced 12 hours of downtime in the last month, illustrating the difficulty of moving from 'two nines' to 'three nines'. The journey from 90% to 99% reliability is as hard as getting to 90%, and the jump from 99% to 99.9% is equally challenging. This affects everyone, not just infrastructure teams, as status pages are now the public interface for understanding service reliability. Developers and businesses need to understand these nuances to make informed decisions about their tools and services.
Key Points
GitHub's uptime is 98.31%, reflecting 'two nines' reliability.
GitHub Actions faced 12 hours of downtime in the last 30 days.
The journey from 90% to 99% reliability is as hard as getting to 90%.
The jump from 99% to 99.9% reliability is equally challenging.
Status pages are the public interface for understanding service reliability.
Why It Matters
GitHub's 98.31% uptime and recent downtime for GitHub Actions highlight the challenges of achieving higher reliability tiers. For developers relying on GitHub Actions for CI/CD, understanding these nuances is crucial. The difference between 'two nines' and 'three nines' is significant, impacting workflows and decision-making. Infrastructure teams need to be aware of these reliability tiers to ensure service stability.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 3,482 builders reading daily.