Skip to content
DevMeme
7255 of 7590
Microsoft Post #7954 · source on Telegram

GitHub Uptime Chart Nosedives Right After Microsoft Acquisition Line

Description

A data visualization titled 'GitHub's Historic Uptime' with subtitle 'All data sourced from the official status page'. The line chart shows 'GitHub Average Uptime by Month (Codespaces and Copilot excluded due to launch partway through dataset)' from April 2016 to January 2026, with the y-axis ranging from 99.500% to 100.000%. A vertical dashed line labeled 'Microsoft Acquires GitHub' (late 2018) splits the chart: before it, a flat line of green dots sits at 100% uptime; after it, the line becomes a jagged sawtooth of yellow and red points repeatedly dipping toward 99.5%, with notable troughs around mid-2020, early 2022, mid-2023, and early 2026. Tabs labeled 'Average' and 'Breakdown' appear above the chart. The implied joke is the stark correlation between the acquisition and degraded reliability, a beloved data-driven jab in developer communities

Comments

21
Anonymous ★ Top Pick The dashed line isn't an annotation, it's a changelog entry: 'migrated reliability from on-prem to best-effort.'
  1. Anonymous ★ Top Pick

    The dashed line isn't an annotation, it's a changelog entry: 'migrated reliability from on-prem to best-effort.'

  2. Anonymous

    `git bisect` found the first bad commit, but reverting the acquisition merge is apparently out of scope.

  3. @NaNmber 3mo

    99.6% tho that totals to ~3hr of downtime per months ✍️

    1. @deimossos 3mo

      Are you sure https://mrshu.github.io/github-statuses/

      1. @NaNmber 3mo

        ok ye this is more like it 🙂

    2. @RiedleroD 3mo

      mmh. the last time my home server was down was in december

      1. @RiedleroD 3mo

        yeah it may experience less use. but also I'm not a sysadmin and I don't really do much upkeep.

      2. @RiedleroD 3mo

        (I feel the need to clarify that the downtime was due to my ISP. server uptime as of today is 128 days)

    3. @bad94e81 3mo

      Although correct, how about you consider that their recent fiasco 5 days ago with merge queue deleting history is not even classified as an outage or deviation?

      1. @NaNmber 3mo

        🤭

        1. @ZmEYkA_3310 3mo

          I mean who tf uses the website to merge prs anyways 🤝🤝

          1. @NaNmber 3mo

            claude --dangerously-skip-permissions read my tickets, fix one, commit, push, open pr, review, merge. please no mistakes.

  4. @NaNmber 3mo

    but it feels much worse I must say 😏

  5. @H3R3T1C 3mo

    Microsoft Bought Github at June 4, 2018

  6. @ataraxicPhlogiston 3mo

    I don't understand the color scheme

  7. @ZmEYkA_3310 3mo

    Anthropic uptime 😒

  8. @deerspangle 3mo

    That graph needs the current drop to 87% and stuff

    1. @NaNmber 3mo

      I believe I've seen these charts and a tool used to generate those on reddit and it's based on their own status page data. Obviously, it does not represent reality, at least from my personal feeling 🙂

  9. @SamsonovAnton 3mo

    They just haven't done their "cloud homework" good enough. 🙃

  10. @NanoSector 3mo

    I’ve been tempted to propose a dependency cache for our build fleet, in the past few months builds have been regularly failing due to small GitHub outages

  11. @NanoSector 3mo

    Earlier today we hit a bunch of 502’s for a few minutes

Use J and K for navigation