GitHub's Historic Uptime (damrnelson.github.io)

Article summary

The article discusses GitHub's uptime, but the content is not available. However, the discussion reveals concerns about GitHub's downtime record, with some users comparing it unfavorably to their own self-hosted services. The conversation also touches on the challenges of measuring uptime and the impact of Microsoft's acquisition on GitHub's performance. GitHub's status page and metrics are scrutinized, with some arguing that the presented data does not accurately reflect the platform's overall availability.

Main themes

• GitHub uptime and downtime
• Measuring and calculating uptime
• Microsoft acquisition and its impact
• User expectations and experiences
• Transparency in reporting outages

What commenters say

• GitHub's downtime record is worse than some users' self-hosted services, suggesting a potential issue with the platform's reliability.
• The way uptime is calculated and presented can be misleading, with different methods yielding varying results.
• The acquisition by Microsoft may be contributing to GitHub's current performance issues, including downtime and outages.
• Measuring uptime is complex, and different users have different expectations and definitions of what constitutes downtime.
• Some users argue that GitHub's aggregate uptime metric is not a reasonable measure of the platform's overall availability.
• The impact of downtime on users varies, with some experiencing significant disruptions and others being less affected.
• There is a need for more transparency and honesty in reporting uptime and outages, with some suggesting that Azure's downtime may be underreported.
• The calculation of uptime should take into account the specific services and features that are affected, rather than treating the entire platform as a single entity.