r/github • u/StatusGator • Mar 03 '26
News / Announcements GitHub is down
Nothing on the official status page but StatusGator shows a big spike: https://statusgator.com/services/github
139
u/saaket2201 Mar 03 '26
This has become so frequent now, it's frustrating.
21
u/naikrovek Mar 03 '26
Indeed. Just as my employer moves from GHES to an EMU enterprise on GitHub.com. We ain’t happy.
26
u/saaket2201 Mar 03 '26
I wonder if it's the 30% AI code, like windows 11.
9
2
u/Key-Direction-7842 Mar 05 '26
Or the fact that could be used by billions of agents and can't keep alup with so much "users"?
3
u/roastedfunction Mar 04 '26
Ugh, I’m a few months out from this same migration and I’m not looking forward to it.
5
u/naikrovek Mar 04 '26
It would be fine if they could keep the damn site up. My GHES instance has 100% uptime for the past 6 months. My people are very used to that.
2
u/Qs9bxNKZ Mar 04 '26
So you have never done an upgrade?
3
u/naikrovek Mar 04 '26
I’ve done many, but I don’t do it if it doesn’t bring useful advances. I’ve been upgrading this long enough to know that upgrades frequently break as much as they fix, and right now my users are happy with what they have.
2
u/True-Strike7696 Mar 04 '26
don't they force you to new versions eventually?
1
u/naikrovek Mar 04 '26
Sort of, you can only upgrade two minor revisions at a time, and they release at one minor revision every three months, so we are usually 6 months behind.
We keep up with hotfixes and don’t reboot if it can be avoided.
With the release of 3.20, we’re now three behind, but we are ok waiting a bit longer.
We are a huge GHES customer and we always ask support what problems people are having with new versions and we get vague answers about general problems. Ultimately, we get an upgrade recommendation based on what they know of our use of GHES and the problems we’ve had in the past as to whether or not we should upgrade to latest or latest-1. They rarely recommend it.
3
u/Paranemec Mar 04 '26
They were going to hire me for it, because I've done it twice before and on larger systems. 4 months of interviews just for their last reorg to cause them to lose the req. I'm 99% sure this is stuff I could have prevented. Oh well.
2
2
1
38
u/Stuffy123456 Mar 03 '26
Don’t worry, they are merging 3000 PRs a minute created from slack threads that PASS all tests (that the PR modified so it would pass).
7
1
30
9
14
u/UsualResult Mar 03 '26
Who would have thought that firing all the QA people would have side effects?
I bet Microsoft is "saving" a lot of money right now.
6
4
7
11
3
u/justaleafhere Mar 03 '26
it says i violated terms of service and that my account is suspended now? is this a mistake as a result of the outage
4
u/3spky5u-oss Mar 03 '26
I got one of those last week too. I only had like 5 repos up, literally zero comments. I have no idea what I “did”.
Of course, they don’t reply either. Because fuck you.
I just moved to Gitlab and Codeberg.
2
u/justaleafhere Mar 04 '26
actually i reported it via their mail and they said its a issue from their side and they immediately gave me access
0
3
3
u/heyitsmdr Mar 04 '26
All of their recent outages these past few months are likely coming from their on-going migration to Azure: https://news.ycombinator.com/item?id=45517173
3
2
2
u/LordRelix Mar 03 '26
My company is considering Gitlab. This is way too annoying recently.
1
u/LolComputers Mar 03 '26
We are moving off GitLab to GH, rip
2
u/LordRelix Mar 03 '26
Any reason why? Just wondering!
2
u/LolComputers Mar 04 '26
Something about the price jump for licensed users between what we're on now and what we need.
Also because we're a Microsoft/Azure shop, and it apparently integrates roles and billing into a convenient now for management.
TLDR: management
3
1
u/Confident_Essay3619 Mar 03 '26
works for me in PA. can access and modify my repos and access copilot
1
u/Efficient_Tell_449 Mar 03 '26
Faced this issue a while ago when I pushed some code and the ci was failing
1
1
0
9
Mar 03 '26
[removed] — view removed comment
3
u/dashingThroughSnow12 Mar 03 '26 edited Mar 04 '26
It depends. They seem quite delayed recognizing the issues. I’ve seen issues exist for dozens of minutes to hours and never show up in the status page.
If there are any SLA agreements with compensation, I’m sure it is dissected. If GitHub actions are down, I can’t merge any code. If Github PRs are having issues, same deal. Packages, I need them for the build for my actions. Git operations? Same. Over and over.
But if they each had a different 1% outage, they’d all pass their SLAs.
1
3
22
u/StatusGator Mar 03 '26
GitHub official status page shows the outage now:
Started out as "Incident with Copilot and Actions" though it's expanded:
"We're seeing some service degradation across GitHub services."
Now Webhooks, too.
For me it's mostly impacting access to the web interface, loading pages.