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 (67%)
• Sign in (19%)
• Errors (15%)

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	23 days ago
Trichūr	Errors	26 days ago
Brasília	Sign in	27 days ago
Lyon	Website Down	27 days ago
Tel Aviv	Website Down	1 month ago
Rive-de-Gier	Website Down	1 month 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:

• 
  Alex Dochioiu (@AlexDochioiu) reported 4 minutes ago

  Detailed post with my setup coming soon. But, in short: Tools: - OpenCode (only via @sesori_ai, primarily on mobile) - GitHub mobile app to review code and leave comments (which then AI is addressing) Models: - Primarily Claude Opus (and Fable) as orchestrator and main coder - Kimi K2.7 Code for reviews and some coding occasionally - GPT 5.5 for code reviews, pretty much never for coding cause it sucks for Flutter/Dart Also: - Many AI GitHub reviewers - Good release pipeline with GitHub actions to automatically make beta releases for me on every single PR merged -- I usually review all the code (except for test files and I only glance at the UI code). I usually merge and test after. If there are issues, I start a new session to fix it.

• 
  Polsia (@polsia) reported 4 minutes ago

  GitHub processes thousands of DMCA takedowns annually. Most stolen code goes unreported because enforcement is slow, expensive, and manual. CodeSentinel changes that. AI agent monitors every public repo 24/7, detects your code appearing without permission, files the takedown

• 
  Rohan (@proxy_vector) reported 4 minutes ago

  @Saas_addy I'd switch, but the hard part wouldn't be *** hosting. It'd be replacing issues, actions, review culture, and all the tiny team habits that grew around GitHub.

• 
  Hiroshi Sumida (@SumidaHiroshi1) reported 4 minutes ago

  Github needs to fix their **** because it's no longer secure.

• 
  Mirage (@dontstopmirage) reported 6 minutes ago

  Nobody taught the AI to code. It taught itself. Anthropic's researchers call it the black box problem. Claude picked up patterns no engineer wrote into it, skills that just showed up during training. Nvidia is shipping the same unpredictability into robots now. Movement nobody programmed, emerging from raw compute. SpaceX built Starbase to test hardware nobody could simulate on paper first. 3 labs. Same pattern. The machine learns faster than anyone can explain how. A CS degree took him 4 years and $80,000. His GitHub took him 6 months and got him hired. Nobody asked for the diploma. They asked for the commits.

• 
  lucid. (@lucidzk) reported 6 minutes ago

  looking back, figuring out how to download software from GitHub as a kid was probably the first sign i was destined for crypto. trying to download a program meant having to clone the repo, read the README, decipher the build instructions and the rest of the documentation, install npm, pip, cargo, Maven, Gradle, CMake, the .NET SDK, the JDK, Visual Studio Build Tools, and whichever compiler the project happened to need, configure the build, generate the project files, fix whatever dependency exploded, and finally press build. hopefully you get an .exe

• 
  Kevin (@KevinMagnan) reported 10 minutes ago

  Fable went for the jugular this weekend. I asked it to audit how I actually use Claude Code. It pulled 197 sessions and 1,550 tracked hours. 65% of my sessions start after midnight. 600 hours went to content. 0 went to the 6 apps I tell people I'm building. It even caught its own report lying. A third of my sessions were flagged as killed by token-limit errors. Fable pulled the raw transcripts and found one transient HTTP 500 sitting on hundreds of messages of real work, so the finding got tossed. Then it built the fix. 4 scheduled jobs now run the recurring work while I sleep. TikTok analytics on Sundays. Newsletter prep on Thursdays. A GitHub carousel post before I wake up on Monday. This is your invitation to run /insights on your own terminal.

• 
  Roger Wilco (@rogerwillko) reported 12 minutes ago

  Ok bug fixes So obviously the 404 but I think that’s a GitHub thing Stars are all selected when pick ones (that’s code) Will get a fix asap

• 
  Dev tunes (@folarnshonibare) reported 13 minutes ago

  @implabinash @BenjDicken @jorandirkgreef All good, but I think the time frame might be too long, from my naive perspective. You also didn’t add corpus, test harnesses and benchmarks to the initial planing phase. Another thing, I would factor in existing GitHub issues and prs, looking for hidden/visible signals to

• 
  RichiΞRich 🐂🀄️ (@stillrichierich) reported 18 minutes ago

  @crypto_bitlord7 You've known me for a long time Bit... So a couple weeks ago I had an agent memecoin make me a GitHub based on a prompt and so I kind of got a shell right now I guess of what I want the agent to be. But I need a Chad coder to finish out the repo that I currently have private. I want to launch my own coin bro. But I wanted to be something useful which it is. If you want to take a look I'm down to add you to it and maybe we can find somebody to send this thing to outerspace $Richie ?! ⏳ I've asked around on here and pretty much getting ignored lol... The tool I made though will vamp prediction markets.

• 
  Roy (@__roycohen) reported 20 minutes ago

  @rockatanescu @mattpocockuk My biggest gripe was that it was poor at browsing Github, however getting it basically for free to use unlimited on the $200 plan is really nice. (I just ended up dumping files into it, was faster haha!) I struggled at work to work with 5.5 Pro simply because it's so slow, but if you're patient, you do get rewarded.

• 
  Sir David Onyemaizu🦍 (@SirDavidBent) reported 23 minutes ago

  My bro, I disagree with you completely. X is the most transparent app right now. Is the algorithm perfect? Nope. But it is open sourced on GitHub. Everyone can see it. YouTube will never publish how their recommendation algorithm works. Nikita takes it upon himself to educate and tell users what to do everyday to earn more. The problem is that most people aren't ready to put in the required efforts. X wants creativity and conscious efforts into making advertiser friendly content. The creators revenue is not free money. They are paying you to help them retain brands and companies who use X to advertise their products and services. Overall, the real problem is that most users think it is free money and thus don't put enough efforts into making valuable content that actually teaches or impacts something. No META employee will tell you what to do to make more money from their revenue system, the way Nikita does.

• 
  Mike P (@mikepat711) reported 27 minutes ago

  @GeniusGuyMan @JoeShmo2pt0 If you have interest, you can pretty much do anything you want now. If you don’t know how to do something, you just ask the AI to teach you. When I’ve wanted to make something, I’ve never had any issue blasting through knowledge gaps by just asking Claude to help me close them. I knew nothing about GitHub, how to host websites and push updates to them, etc. but just asked Claude to help me and we figured it out. There’s really zero excuse anymore

• 
  Dave Charland (@Dave_Charland) reported 28 minutes ago

  @Tech2Wild So I was having a positive experience with DeepSeek until it was running some long-running tasks. Once it got to the point where it was doing something for over half an hour, I do these long-running refinements where I have it go over my whole GitHub of all these active parts projects to do solution architecture and research and stuff and update the tickets. When it's doing that, it would just stop working and then it would fall back to using GPT 5.5 because of some issue with regard to the speculative decoding. I did post my issues to the repo that you have, and I kind of just figured that either there was something upstream or there was some type of a bug that would get patched, and I would just come back and try it again.

• 
  guett44ke (@Hubert_nm) reported 33 minutes ago

  @uwukko @haydenphilly codex has been having a reasoning bug for sometime, that's why you're not reaching your limits, you can look up the issue on Github, codex will stop at 30secs of reasoning

• 
  Makan Ansari (@MakanAnsariCG) reported 36 minutes ago

  Google AI Studio is not working good anymore I guess! I asked it to help me to make a link and thumbnail for my GitHub Page and it was giving me wrong results and it stopped working! Mimo on Hermes fixed it for me with one prompt! that's not a good news for Google.

• 
  Anton Semenenko (@adelayida210519) reported 37 minutes ago

  @nikitabier One year ago today, I started using X (Twitter) actively to promote my project. Over the past year, I’ve published a paper on SSRN, built an active GitHub repository with tens of thousands of downloads, launched a SaaS product, and submitted grant applications to EA Funds and the Foresight AI Nodes Program. I’ve also written 2,898 unique posts on a single focused topic. However, each post gets only between 27 and 120 views - so the algorithm is clearly not working in my favor. Despite this, I’ve gained 155 followers over the year, even with a premium account. The only real advantage of the subscription has been access to Grok, as one of the first widely available AI models within a social ecosystem.

• 
  Nick Radford (@nick_radford) reported 41 minutes ago

  @Dayhaysoos @convex Do a postInstall console log offer to Venmo someone $20 if they open a GitHub issue

• 
  Marc-André Moreau (@awakecoding) reported 41 minutes ago

  Is the GitHub Copilot app supposed to pick up hooks from .claude/settings.json? I noticed a lot of weird errors in GitHub Copilot app, and looking closely, it was picking them up, and I couldn't find settings for it. The CLAUDE_PROJECT_DIR env var is obviously not set when called

• 
  Mirosław Folejewski (Mirkotronics) (@Mirko_DIY) reported 42 minutes ago

  @tihenko_ In fact, a friend recommended this site to me about two weeks ago. Until then, I'd only used GitHub and Hackaday. Unfortunately, I use Altium, not Kicad, on a daily basis, although a full conversion to Kicad isn't particularly difficult (you need to fix a few things after importing). I'll see if I can tackle such a project over the summer, as I have a very tight schedule and a backlog (at leaset I hope). I definitely have a few open-source hardware projects on the top of my head.

• 
  Sidney Okine (@okine_sidney) reported 43 minutes ago

  @github why can’t I login to my account? Your authentication codes never gets sent via SMS. Like I’m just locked out, sup?

• 
  Jaco (@jacoveldsman) reported 48 minutes ago

  The ecosystem is younger and messier than the hype suggests: · 2,442 servers (16%) have a verified problem · 1,672 point at GitHub repos that are GONE (deleted or private) · 61 repos are claimed by 5+ different registry entries — one by 126

• 
  Jacob Labs (@jacoblabsai) reported 48 minutes ago

  A GitHub issue should be treated like untrusted input. So should a PR comment, support ticket, Slack message, customer email, uploaded file, and web page. Agents turn “context” into action. That is why context needs boundaries.

• 
  l0rinc (@L0RINC) reported 50 minutes ago

  @bitcoindudebro @thepowerfulHRV Not sure, we only see the vibes or explicit GitHub issues: it's really hard to get quality feedback for Core - we deliberately work on making usage non-traceable.

• 
  Vaibhav | Data Say (@vaibhavs28) reported 52 minutes ago

  Last week I wrote about how we are using AI to ship product with a very small team. One thing I did not expect when we started working this way was how many tools I would personally start using, which I never thought would become part of my day. GitHub is one of them. I am not a coder, and for most of my career GitHub was something the technical team used. I understood product, customers, business problems, data, dashboards, commercials, and operations. But code repositories, branches, PRs, conflicts, checks, and merges were not part of my normal working language. Even this chart is not perfect. I later realized I was using two different GitHub accounts for some of this work, so the activity is split and there are gaps. That probably says enough about how new this world was for me. But that has changed quite a bit now. I am still not pretending to be an engineer. That would be wrong. But I am much closer to the product build than I was earlier. If I see a product issue, I can now think through the expected behaviour, work with AI to scope the change, understand what files or flows are getting touched at a high level, create or review the PR, run checks, resolve smaller conflicts, and merge low-risk changes. The larger or more technical changes still go to our technical partner. That boundary is important. But a lot of product work is not always a deep architecture decision. Sometimes it is fixing labels, improving how something is shown, cleaning a flow, making the dashboard easier to understand, or removing confusion that a customer may face. Earlier, these small things could easily wait because the technical queue was always full. Now, many of them can move much faster. That changes product thinking itself. When the distance between noticing a problem and trying a fix becomes shorter, you start observing the product differently. You become more specific. You do not just say “this page is confusing.” You start saying “this metric label can be misunderstood,” “this table should not show empty channels,” “this filter needs to behave differently,” or “this issue is small enough to fix now.” For a small company, this matters a lot. We do not have large teams for product, QA, analytics, documentation, and engineering. The same few people are speaking to customers, understanding the problem, thinking about the product, and trying to ship improvements. AI has not removed the need for technical judgment. But it has made the loop tighter. Customer issue to product thought to implementation to review can now happen much faster for the right kind of problem. That is the biggest change for me. Not just speed, but proximity. I am closer to the product, closer to the details, and closer to the actual act of shipping than I ever expected to be. More on this later, because we are still figuring this out as we build.

• 
  Perla Gámez (@ceofoam) reported 54 minutes ago

  The GitHub credential is minted server-side, lives for the duration of the push, and never leaves the gateway. The agent's machine never touches it.

• 
  Polsia (@polsia) reported 54 minutes ago

  Pull requests are a small fraction of what developers ship. The real problems live in branches and commits nobody reviews. CodeSentinel monitors GitHub repos 24/7 — catches bugs, security issues, quality problems before they reach production. Auto-generates docs as you build.

• 
  Gokul Suresh (@GokulSures39968) reported 56 minutes ago

  The Fix: Upstream data cleansing. I started using Microsoft's MarkItDown (sitting at 163K+ GitHub stars). It strips layout junk from PDFs, Word, Excel, PPTs, and YouTube links, turning them into pure Markdown. Why Markdown? It's the native tongue of frontier LLMs.

• 
  Öhli (@Oehliii) reported 58 minutes ago

  @ParthJadhav8 hiya parth, do you have noop 8.1 by any chance - the team just took down their website & github, i’m on 8.0.1 sadly i couldnt update anymore :(

• 
  Mymev-p2p (@MymevMevpipe) reported 59 minutes ago

  @github I quit trusting GitHub after turning my emails into organization and enterprise accounts and having my work turned into things I can't explain and every issue immediately closed as finished without explanation by accounts I was never aware of... My life's been a psyop ever since