GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (58%)
• Errors (32%)
• Sign in (11%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Haarlem	Sign in	2 days ago
Villemomble	Website Down	2 days ago
Bordeaux	Website Down	6 days ago
Ingolstadt	Errors	10 days ago
Paris	Website Down	11 days ago
Berlin	Website Down	12 days ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Dan TAIKO (@realdantaik) reported 36 seconds ago

  @turingou Cannot sign in with Github, no error shown

• 
  artee (@artee_49) reported 43 seconds ago

  we are still fighting issues from github incident from last night. merged commits suddenly being deleted completely ruined my mental model on how github works and provided reliability.

• 
  Rachel Blum (@groby) reported 6 minutes ago

  "some pull requests may have been merged incorrectly between 2026-04-23 16:05-20:43 UTC." HOW? "This behavior is still present in GitHub Enterprise Cloud with Data Residency, and we are rolling out the same fix." Highest paying customers last? What's in the water over there?

• 
  Bnaf.OG | 🟧 (@bnafOg) reported 9 minutes ago

  @tokara_camara The GitHub Actions permission requirement is the real enterprise friction — most orgs run locked-down runners with no internet egress. Cloud agent is frictionless for personal repos; enterprise procurement for Actions secrets is where it stalls.

• 
  RΛZ13L 🌒 (@Xubu_Trad) reported 11 minutes ago

  Peer review of the latest gilga GitHub updates. 👇 More commits. More files changed. More technical language. But the core issue remains the same. He said the trustless fixes were “actually pretty easy” and told us to “check back tomorrow or later tonight.” It is now the third day past that promise, and the deployed testnet contracts we checked still returned LIVE_OWNER across all 12 queried addresses. In a serious engineering environment, you do not get credit for burying a missed security promise under more activity. You either prove the system is trustless on-chain, or you admit it is not there yet. Right now, the repo is moving. The proof is not. #CAW

• 
  ByteCrafter (@bytecrafter_1) reported 14 minutes ago

  @theo the fix isn't a new provider, it's merge queues that treat the post-rebase SHA as a first-class commit. github rewrote history between the queued and merged state which is why recovery is brutal. gitlab's MR pipeline has the same class of bug waiting to fire.

• 
  Tech Ironic (@techironic11) reported 16 minutes ago

  @howfxr I didn't research in detail of exact issue here. But github actions allows you to automate certain workflows such as after every comit pushed, build an apk and release it. So attackers manipulated it to make it mailicious

• 
  am.will (@LLMJunky) reported 17 minutes ago

  @elvissun @Teknium @NousResearch Is this a stability issue? Because it sure doesn't sound like one. I'm not going to lie man this feels awfully dramatic. You know what I do when I'm having an issue? I create an issue on GitHub or I just reach out to Tek lol. Doing a very public post on X is not the format for this in my opinion Especially when you are calling their trust into question is a very accusatory statement

• 
  Matt Helm (@matthelm) reported 17 minutes ago

  @noahzweben Fantastic! I tried it out with Issue opened, creating a new GitHub Issue on the repo, but it didn't trigger the routine. trig_01MNuMWeDvQLTw3arNHoSysT

• 
  oxiverse (@oxiverseinc) reported 21 minutes ago

  RAVANA v2 bug fix deployed. Dissonance dropped from 0.8 to 0.3, identity growth improved from 0.3 to 0.85. Check GitHub for details.

• 
  G/M (@gslashm) reported 24 minutes ago

  @vinccool96 @noinconsistency I'd instantly move to intelliJ if the fix the god awful github copilot plugin integration thing, or the claude code plugin. claude code at least kinda works sometimes, but gh is absolutely unusable. i have to code MANUALLY. the autocomplete in java is insane tho ngl

• 
  AGI Thrive Prep (@AGIThrive) reported 25 minutes ago

  The fix that actually worked: Delete vault → create brand new one named literally “Q” (single letter). Re-clone the same GitHub repo. Suddenly staging, committing, and pushing works perfectly. Short path = no more buffer overflow in the JS *** engine. Wild but true.

• 
  Abdulmuiz Adeyemo (@AbdMuizAdeyemo) reported 26 minutes ago

  Most people will read Satya’s post and think it is just another Microsoft product update. It is not. It is Microsoft showing us where work is going. For years, the biggest advantage at work was knowing how to use the right software. Excel. PowerPoint. GitHub. Outlook. Teams. Word. Jira. Slack. Figma. Every serious worker had to learn tools, switch tabs, remember workflows, chase updates, write docs, reply messages, attend meetings, and still find time to actually do the real work. That was the hidden tax of modern work. You could be smart and still feel slow. You could have good ideas and still get buried under process. You could know exactly what needs to be done and still lose hours moving information from one place to another. That is why GPT 5.5 rolling into Copilot, GitHub, M365, Copilot Studio, and Foundry matters. The model is no longer sitting outside work waiting for you to copy and paste things into it. It is moving into the places where the work already happens. That is the real shift. Not better chat. Better execution. Imagine a developer with a messy ticket, a half broken codebase, unclear requirements, and a PR waiting for review. Before now, he had to hold everything in his head. Read the ticket. Understand the repo. Ask questions. Write code. Test it. Push it. Review comments. Update the task. Explain what changed. Now imagine an AI that can help move through that whole chain with him. Not perfectly. Not magically. But enough to remove the heavy friction that used to slow him down. That changes the feeling of work. Now zoom out beyond developers. A manager has meeting notes, action items, emails, reports, and decisions to make. A founder has customer feedback, bugs, investor updates, product plans, and team conversations flying everywhere. A student has research, assignments, projects, and deadlines. A consultant has client calls, proposals, analysis, and follow ups. Everybody is drowning in scattered work. So when Microsoft says GPT 5.5 is coming into the tools people already use, the story is not just AI getting smarter. The story is that the gap between idea and execution is shrinking again. And that is exciting. But it is also uncomfortable. Because once some people have AI helping them plan deeper, execute faster, review better, and move across tools with less friction, the old speed of work starts looking slow. Not because people are lazy. But because the standard is changing. The person who knows how to use these tools well will not just write faster. They will think faster. Build faster. Respond faster. Document faster. Ship faster. And in a world where everyone is competing for attention, jobs, clients, customers, and opportunities, that kind of speed compounds. That is the tension. AI is no longer just something you use when you are stuck. It is becoming part of the daily workflow. The danger is waiting until it feels normal before you start learning it. By then, the people who started early will already have new habits, new systems, and new output speed. So the action is simple. Do not just watch these announcements like tech gossip. Pick one workflow in your life today and ask: Where am I wasting the most time? Writing? Coding? Research? Emails? Meetings? Reports? Planning? Then use AI there until it becomes a real advantage. Because the future of work will not belong only to people with the best tools. It will belong to people who know how to turn those tools into leverage. Satya is not just announcing a model rollout. He is telling every worker, founder, student, and builder that the tools of work are being rebuilt in real time. And the people who adapt early will feel like they are moving with a second brain. The people who ignore it will wonder why everyone else suddenly got faster.

• 
  will 🌱 (@GovAmyKlobuchar) reported 29 minutes ago

  @akshat_b This seems more like a *** issue than a GitHub issue

• 
  Gman (@gmaniac) reported 30 minutes ago

  @satyanadella maybe you can put it to work and fix deploying to @Azure from @github 🧠

• 
  Alex Yumashev (@jitbit) reported 31 minutes ago

  Microsoft just injected this ad into my commit just because I have a copilot extension installed in VSCode. There are now 4M (four million) commits like this if you search github for "Co-authored by Copilot" @timrogers tagging you since you addressed a similar issue at HN

• 
  ryan (@ryanpcrab) reported 32 minutes ago

  @github the fix is actually to just click files lol thats unintuitive though

• 
  Kyle Galbraith (@kylegalbraith) reported 34 minutes ago

  github isn't getting better. it seems to only be getting worse. ******* up with the latest outage around reverting merged commits does massive damage to production applications and wastes a massive amount of time for those that are impacted. putting out a message that minimizes this tells you everything you need to know about the internal perspective. it's time we had something better.

• 
  Tudor Golubenco (@tudor_g) reported 35 minutes ago

  New excuse landed: github silently reverted my fix.

• 
  Riyaz Saiyad (@Rj_Saiyad) reported 35 minutes ago

  @github I’ve been overcharged for Copilot Pro (Ticket #4299654). You charged me $10 instead of the promised $5.11, counting free trial requests as paid! 😡 No response for 7-10 days while my money is gone and I have no access. Fix this ASAP! #GitHub #Copilot

• 
  _its_not_real_ (@_its_not_real_) reported 36 minutes ago

  3) He has telecom people he could have told to kick it off because it has a little gui start button. He just didn't delegate even that. 4) felt weird to leave a single bullet point in the last tweet. Surprisingly, the code is in our github org. I'm pulling it down to fix it.

• 
  Simon J.K. Pedersen (@simped) reported 37 minutes ago

  @GergelyOrosz Github is on a slow decline to irrelevancy, like most of Microsofts portfolio, something must change.

• 
  🧙‍♂️Mo0nless (@LCSeekers) reported 38 minutes ago

  $340 seed. $18,700 in 31 days. One Python file. $5 server 4 open-source repos. Claude as the brain. That's the entire stack Here's what actually matters 86 million Polymarket trades. Every wallet. Every exit. Free on GitHub Claude scanned 14,000 wallets in 4 minutes Top 20 wallets made more than the bottom 13,000 combined That's not a stat. That's a target list The scanner kills 93% of markets before a dollar is touched Gap below 7%? Dead. Depth under $500? Dead. Resolution outside 4-48 hours? Dead 487 markets become 35. That's the point Then the brain runs 4 checks on every survivor Base rate — how often does this type of event actually happen? News — did anything change in the last 6 hours? Whale check — are any of the 47 top wallets already in this position? Disposition — is the crowd making a known cognitive error? 3 out of 4 agree → thesis generated. Confidence above 75% → Quarter Kelly sizing f* = (p x b - q) / b Two agents agree → full position. One agent only → half. Agents disagree → no trade That consensus filter alone killed 40% of losing trades The exit is where most bots die 91% of top wallet exits happen before resolution Three triggers. No exceptions 85% of expected move hit — take profit Volume spike 3x normal — smart money leaving 24 hours of silence — thesis dead $25/month total. One tab to check in the morning.

• 
  Gergely Orosz (@GergelyOrosz) reported 43 minutes ago

  Massive L from GitHub One of the most embarrassing outage that can happen (a data integrity issue), and the response is "well, actually, it's only 0.07% of customers...") Customers whose workflow is messed up badly are fuming reading this. No respect for the customer...

• 
  Teknium 🪽 (@Teknium) reported 45 minutes ago

  @movingux @natsume_aurlia can you be more specific? 3 days of research and no issue on the github x[[[[

• 
  Santiago (@spersico) reported 51 minutes ago

  But it's becoming a problem, already. Isn't it? This is not a single incident. This yet another issue in a constant string of issues that have been occurring in GitHub for the last... Year?

• 
  joacod (@joacodok) reported 52 minutes ago

  i experienced this at work, it was a major wtf happened, we were all under a lot of pressure because of the size of affected clients, and it was a github major issue… simply unacceptable

• 
  Francesco — oss/acc (@ceccon_me) reported 53 minutes ago

  We just released a small package to record and replay @EffectTS_ HttpClient requests to tape. Making external APIs available to tests running on GitHub actions is both dangerous and leads to long running and flaky tests. It's no wonder that most people resort to mocking the upstream API service. The issue is that you'll have to manually collect sample data and deal with drifts. This package records all HTTP interactions and stores the requests/responses on disk. All subsequent calls will read from the file, without interacting with the upstream server. Your tests are now fast, safe, and reproducible!

• 
  sushen (@sushentalwar) reported 53 minutes ago

  i have been vibe coding for the last two months, mostly random stuff or my online portfolio (resume) website. But I have come to a dead stop with @github because i am doing something wrong and i just dont know what and the support team has not resolved/responded so far. As someone who has never coded, this is a hard experience. I have an idea of why my github profile got flagged (likely because im vibe coding and pushing entire index copy-paste from claude code to my repo?) anyways hoping this can be resolved soon. Looking to learn here how to be better so any feedback would be great! To avoid in future running into the same issues in the future. @github - i cannot connect github to vercel - updated commits arent showing on vercel either. - the live website isnt being udpated either.

• 
  Manuel Schiller (@schanuelmiller) reported 55 minutes ago

  @aiiiden0 @TansTack probably a but. please create a GitHub issue