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 (50%)
• Errors (39%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Nové Strašecí	Website Down	4 days ago
Perpignan	Website Down	9 days ago
Piura	Website Down	9 days ago
Tokyo	Website Down	10 days ago
New Delhi	Sign in	16 days ago
Kannur	Website Down	20 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:

• 
  Juan C. Andreu 🦇🔊 (@andreujuanc) reported 20 seconds ago

  Hey @github fix the actions FFS

• 
  Mr.Pando (@jfreddy82g) reported 1 minute ago

  As of April 9, 2026, GitHub is experiencing service disruptions, particularly impacting Copilot Cloud Agent jobs and causing performance issues for some services. Users have reported delays Microslop has done again

• 
  Ed Hansberry (@ehansalytics) reported 3 minutes ago

  @WindowsLatest Everyone is burnt out on that Copilot icon and the brand. They need to start over. Bring it back as Cortana or something new. Leave Github Copilot alone - it works quite well. Burn the rest down.

• 
  louis030195 (@louis030195) reported 6 minutes ago

  @corybytheway @RewindAI Sorry to hear about the iMac Pro issues! Intel Macs can be tricky. We've made big improvements in recent versions - v22 has better Intel support. Would love to debug this with you. Can you share what error you're seeing? Join our Discord or open a GitHub issue!

• 
  Darra XRP Lord🇮🇪 (@DarraFitz) reported 7 minutes ago

  Anyone else’s GitHub having a mental breakdown, getting a random pop up to login

• 
  S. Cabana (@SimCabana) reported 7 minutes ago

  Asking claude to try to reproduce the issue with a minimal setup, we'll see. If I can get a sample that does the same, I'll push it to my github. If not, I'd be more than willing to connect and show our setup.

• 
  Patrick (@cyph9z) reported 9 minutes ago

  @francoisfleuret Github automatically scanning all repos for security vulnerabilities before commits can be publicly published would be a good start. That's half of the problem, and it'd catch supply chain attacks too.

• 
  EWomer (@e_womer) reported 20 minutes ago

  @github How long before you get shut down because of Micro$lops AI powered enshitification of Github?

• 
  Terafab (@lmqlai) reported 22 minutes ago

  @Copilot Copilot is acting weird. I created a PR in GitHub, and GitHub Copilot left comments. Then I asked Copilot in Microsoft Edge for suggestions on those same comments. It suggested some fixes, I applied them, pushed the changes, and ran Copilot review again—now it’s asking for additional changes that conflict with what Edge Copilot suggested. Has anyone else noticed differences or even conflicting suggestions between GitHub Copilot reviews and Microsoft Edge Copilot for the same issue?

• 
  Pankaj Kumar (@pankajkumar_dev) reported 26 minutes ago

  Claude Opus 4.6: 67% Drop in Thinking Depth - GitHub issue #42796 highlights a 67% drop in thinking depth since late February. - Developers report shallower reasoning and mistakes like editing code without fully reading files. - Anthropic links this to the redact thinking 2026-02-12 header, which hides reasoning from logs. - There is speculation that compute is being throttled, possibly ahead of a new Mythos-tier release. - Workarounds: use /effort high, disable adaptive thinking, and prioritize correctness in configs.

• 
  ♡ excess ✨ (@excesstigress) reported 29 minutes ago

  @CsAbyssalLight @_potatobag yeah, it was under a force loaded chunk so in theory it shouldn't have happened, but it did i also read a few reports on github about windmills etc going over chunk borders just despawning lol. seems to be an entity issue in general

• 
  Jeff Mitchell (@jeffmacguy) reported 29 minutes ago

  @ForeverPlatypus @TommyWhitehill @Math_files If the problem is so small and easy, providing an exact answer is easier than providing an estimate. If you want to teach the concept of estimates, use an example that is worthy of an estimate, for instance: Carol added 23702 lines of code to her teams GitHub codebase. Testing indicated there were 8439 errors. Is it reasonable that Carol will be fired from her job the next day? Explain your answer.

• 
  Feral Sapien Erectus (@feral_erectus) reported 31 minutes ago

  @steipete I have 0 github issues. You need to make commit hooks and a security bot that checks the work before being committed.

• 
  Mayukha Vadari (@msvadari) reported 31 minutes ago

  @Lou_Matalonga If there are gaps in the documentation, please open issues in Github so that they are addressed. Feel free to ask questions in Discord if you end up in one of those gaps, the community tends to be pretty responsive there.

• 
  Daniel Bulhosa Solórzano (@bulhosa) reported 33 minutes ago

  For this generation of models, Github seems like a great source of training data. Nowadays I just have models write full PRs, I review them on GH, then have the model pull down the comments to discuss a plan to fix. I'd rather do that than a multi-page feedback prompt.

• 
  Gustavo Alessandri (@webgus) reported 34 minutes ago

  If you find an error, have an idea, or want to propose an improvement, just open an issue or fork the project on Codeberg or GitHub. Contributions are welcome. That's exactly the point.

• 
  Nishan (@nishancodes) reported 35 minutes ago

  @NoahEpstein_ I called this out a week ago. There's an active GitHub issue exposing this. They are at a serious compute crunch and is throttling inference for current models.

• 
  Bakhtier Gaibulloev (@slashmsu) reported 37 minutes ago

  @github Auto-opening GitHub Issues for security findings is not fixing the debt - it's just making the pile more organized. Until Copilot can auto-prioritize, auto-assign, and auto-PR the fix, you've moved the problem from 'unknown' to 'acknowledged and ignored'.

• 
  Ａｘｅｌ (@_axelhere) reported 37 minutes ago

  Now compare this with Web2. When devs build apps, they use: - Google login - GitHub login This works using OAuth2. No wallet. No key. Just simple auth.

• 
  Jonathan Riche (@RicheTechGuy) reported 38 minutes ago

  @appfactory @RedwoodJS Minutes... Bcuz builds normally are that fast on the multiple machines I tried l GitHub is just slow AF

• 
  James Duke (@dukebiz) reported 39 minutes ago

  Not the biggest team. The clearest system. OpenClaw went from 9,000 GitHub stars to over 210,000 in a few months. One developer. Peter Steinberger. Built it from his flat in Austria. A personal AI assistant that runs on your own machine. Connects to WhatsApp, Telegram, Slack, Discord, Signal, iMessage. Over 50 integrations. Browses the web, reads files, runs shell commands. All local. All open-source. Started as "Clawdbot" in November 2025. Renamed twice in three days because the name didn't feel right. Then it went viral. By February 2026, OpenAI offered him a job. He took it. Handed the project to a non-profit foundation. Here's what I take from this. He didn't wait for a team. Didn't wait for funding. Didn't wait for the name to be perfect. He shipped, iterated, and let the product do the talking. That's the pattern I see in every builder who breaks through. Not perfection. Momentum. You don't need a 50-person team. You need a clear problem, a public repo, and the nerve to ship before you're ready. Momentum is the only unfair advantage that compounds.

• 
  codaks (@Codaksmade) reported 41 minutes ago

  This issue of pushing large files directly to github is <<<< " I don spend almost a day on this, and I never find way out

• 
  Dollar (@Dollar_Alpha69) reported 42 minutes ago

  ARbvFZqhtbSnHhq7c7fva8bU67GnUr14RdxpDkWUpump Now people are finally starting to hold $STREAMER. I told you… @xyz_fnzero this dev is crazyyyyy. Transparent, active GitHub, building every single day. Nothing hidden, just pure work behind the scenes. Buy early or cry later. This slow cook is going to millions lmaoooo

• 
  Jason Haugh (@jason_haugh) reported 44 minutes ago

  @EricRichards22 It caught on for the people actually building with it daily. The problem is discovery. 90% of MCP servers on GitHub are weekend projects with no error handling and zero docs. The good ones just don't get found.

• 
  Abin (@designedbyabin) reported 47 minutes ago

  @matvelloso How do they keep repeating this? Teams Consumer vs Skype vs GroupMe vs Kaziala vs Teams Business vs Yammer Copilot Consumer vs M365 Copilot vs Mico vs GitHub Copilot You would think they have learned something about building products that creates value to the user after so many mistakes. Yet, they keep repeating the same mistakes. In other companies there are seperate roles for UX Designer, Intercation Designer, UI Designer, Visual Designer. Microsoft is the only company where all of these are combined into a single role called Product Designer. Does PM do UX Research at Microsoft instead of UX Researchers? Is it a company wide problem? What’s the core reason why Microsoft can’t seem to build a great Consumer Product?

• 
  AIcceleration Holdings (@hamsarris6) reported 47 minutes ago

  A CPU shortage has emerged. Agents are getting better smarter and putting those cpu's on FIRE as mentioned by @dylan522p. @SemiAnalysis_ apparently they track github issues and noticed an increase in failed commits and other cpu based capacity issues. So $MSFT is a sure buyer. $META. Just joined the ranks with a brand new SOTA model...they are deeply entrenched with amd. $INTC vs $AMD Personally ive added reinitiated my $AMD position. Less legacy drag, DC revenue flying. Killing Intel in Client segment aswell.

• 
  AI Revolution (@TheOSSObserver) reported 49 minutes ago

  GitHub Copilot CLI automates security triage from the terminal. What's the actual security impact of hiding vulnerabilities? How many projects are affected by these issues?

• 
  Umair Ali (@buildwithumair) reported 54 minutes ago

  @steipete Why you not solved GitHub issues using open claw???

• 
  thxy (@thanksy_) reported 55 minutes ago

  Here's what Claude said about this article about Claude wasted tokens. Summary Here's what I found: The Claims You Posted Are Partially True, But Likely Conflated ✅ Real: ✅Token auditing tools exist for Claude Code (there's a GitHub token analysis script) GitHub ✅Tool schema definitions DO cause significant token waste — one internal Anthropic example showed 134K tokens from MCP tool definitions before optimization, with a typical 5-server setup consuming ~55K tokens Anthropic MCP tool definitions are deferred by default — only tool names enter context until Claude uses a specific tool Claude, which is a real solution ✅Token waste in automated tasks is real — one developer found 11,800 tokens of waste in a single recurring task Substack ✅✅Redundant file re-reads are a major waste (40-60% of read tokens), idle cache expiry is real, and these are documented problems DEV Community ❌ Unverified: I could not find the specific audit report with: 858 (or 926) sessions 18,903 turns 264 million tokens wasted The exact "ENABLE_TOOL_SEARCH": "true" config setting (this isn't a standard Claude Code setting I can document) A dashboard with "19 charts"

• 
  andrewthecoder (@_andrewthecoder) reported 58 minutes ago

  THIS WAS PLANNED. Remember when you got that message in GitHub saying you need to opt out if you don't want your code to be training data? Well, the CEO of GitHub stepped down, and Microsoft absorbed it and made it part of their AI division.