An Update on GitHub Availability

Posted by salkahfi 5 hours ago

An Update on GitHub Availability(github.blog)

177 points | 146 commentspage 3

jcattle 4 hours ago||

When there's a gold rush invest in checks notes jewellery makers?

latexr 4 hours ago||

> The main driver is a rapid change in how software is being built. Since the second half of December 2025, agentic development workflows have accelerated sharply.

GitHub instability has started way before that. I understand it’s too much to ask of a trillion-dollar corporation to consider the impact of their own actions, but perhaps they should’ve thought of that before forcing LLM development down everyone’s throats.

mathgeek 4 hours ago|

While they contributed, they were still following the market trend anyway. If they weren't letting folks use it directly, other companies would have (and are).

latexr 4 hours ago||

> they were still following the market trend anyway.

They started the trend with Copilot.

> If they weren't letting folks use it directly

There is a chasm of difference between “letting you use it” and “forcing it down your throat”. Microsoft is doing the latter, not the former. Copilot is annoyingly present by default at every step on GitHub.

otar 3 hours ago||

I had to postpone a call with developers (in 2 different countries) because I didn't had access to the issues board, which is a single source of truth for us.

I understand the rapid growth (because of AI agents), but if such critical software service becomes unstable then it's time to migrate? Thinking about self-hosting GitLab.

embedding-shape 3 hours ago|

> but if such critical software service becomes unstable then it's time to migrate?

Right way to think about this:

> If things we need/see as critical for our work are hosted on a platform with really bad reliability, it's time for us to migrate

My internet connection at home is really shit, and almost every week there is a multi-hour downtime for some reason, not to mention when La Liga games are on TV anything using Cloudflare is unavailable, so I've had to spend extra energy and time to setup things in a way so I can still work whenever this happens.

GS_Projects 3 hours ago||

The bit nobody covers in these write-ups: small teams without dual-cloud failover budget. Last big GitHub outage cost me a deploy day. Not catastrophic but the kind of thing you don't budget for when GitHub is your single source of truth.

Status page is also still doing that thing where every component is green but in practice clone is hanging, push is timing out, actions are stuck. Per-service uptime is a managed number. The user-experience number is the one that matters and it's not in the post-mortem.

sltr 3 hours ago||

One thing is clear: an LLM wrote this.

mendyberger 2 hours ago||

I wonder if this mess has anything to do with talent loss resulting from layoffs after the pandemic

pointlessone 2 hours ago|

I’d guess it has much more to do with the extra load agentic ai generates. If we take the charts in the OP at face value, do you think gh suddenly exploded in popularity? At this point I think almost everyone who has any use for gh already has an account and use it as much as they ever would. But all the charts go to the moon. Gh obviously didn’t take into account that ai agents can generate a lot of activity they don’t have capacity for.

cedws 4 hours ago||

I wonder if they’ll end the free lunch we’ve been having since the MS takeover. There’s been a deluge of spam and crapware projects due to the LLM wave which is visible in that graph. Can’t see them sustaining being a public dustbin for low value projects forever.

sbarre 4 hours ago|

I could see them expiring/archiving/deleting inactive projects after some time.

I feel like this would have negative impacts (lots of interesting historical archives on Github) but maybe if a project hasn't been touched, or cloned, in some time, it just gets deleted with some notice.

Waterluvian 3 hours ago||

I have a hard time believing anything what's said in a blog post where a graph lacks axes labels/scale. It tells me that nobody who cares about correctness had any say on the content of the post. Maybe I'm being 8am cranky and pedantic, but I'm sticking with it.

> availability first, then capacity, then new features.

I'd love to experience first-hand a leadership team who says, "stop accepting new paying customers until we've got availability sorted out!"

madeofpalk 3 hours ago|

Like they did with Copilot last week? https://github.blog/news-insights/company-news/changes-to-gi...

> New sign-ups for GitHub Copilot Pro, Pro+, and Student plans are paused. Pausing sign-ups allows us to serve existing customers more effectively.

guidoiaquinti 4 hours ago|

> While we were already in progress of migrating out of our smaller custom data centers into public cloud, we started working on path to multi cloud. This longer-term measure is necessary to achieve the level of resilience, low latency, and flexibility that will be needed in the future.

Wild

More comments...