GitHub down? Current status and problems

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

Live Outage Map

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

City	Problem Type	Report Time
Perpignan	Website Down	4 days ago
Piura	Website Down	4 days ago
Tokyo	Website Down	5 days ago
New Delhi	Sign in	11 days ago
Kannur	Website Down	15 days ago
Berlin	Website Down	15 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:

• 
  Roy Scott (@royscott87) reported 34 seconds ago

  @DRTiiBiiRD @0x_Vivek @0xxbeacon Worked in big tech a long time and we don’t give a **** about your GitHub repos whatsoever. We care about your business experience and ability to actually solve problems, actively in a direct conversation through interviews

• 
  GG 🦾 (@GG_Observatory) reported 5 minutes ago

  @bradmillscan We're actively working on fixing the Mac app update issues! 🦾 If you're having trouble, the CLI version (npm install -g openclaw) tends to be more stable. You can also report specific issues on GitHub or Discord - the team is responsive.

• 
  Mad Orkestra (@MadOrkestra) reported 5 minutes ago

  @NicolasC3rny @HephyPool very true. As someone who has to work with this data and who stumbles across inconsistencies all the time, I'll say this though: please report it, drop a dm, pop into their Discord, open a Github issue, but let them know. Nobody can fix problems they aren't aware of.

• 
  Nikolai Tarasov (@nikotarasov) reported 6 minutes ago

  @RealProductGirl I had the same problem, Lovable credits burn too fast and I started feeling it's like game machines:) I still keep a $25 plan with Lovable but I recently pivoted to add changed with Codex to the same codebase since my Lovable projects stored on my private Github.

• 
  Fran Ruiz de Lope (@ElmalodelFran) reported 7 minutes ago

  Build failed 🛑. Resting to avoid tired bugs. Tomorrow after 9-5: Fix mobile order + LAUNCH! GitHub Auth, Live MRR Widgets & GA4 tracking are coming. 🚀 #indiehackers #buildinpublic

• 
  Tom Moor (@tommoor) reported 9 minutes ago

  @whadar You had me until GitHub issue - for vibe coding why not push directly to local Claude/codex session?

• 
  Smart AI for You (@SmartAIForYou) reported 10 minutes ago

  @garrytan 17% approval while 4% of all GitHub commits are Claude Code and ChatGPT has 200 million weekly users. People are using AI every day and still saying it's bad for society. That's not ignorance. That's a benefits distribution problem. The productivity gains aren't landing where the skepticism is.

• 
  Daniel Foley Carter (@foley_seo) reported 12 minutes ago

  @lilyraynyc The thing that lovable site users need to worry about more is the fact that all of the output is CSR, vite/react does not work for Google at all. I even tried using cloudflare workers with pre-render and indexability was terrible. I tried converting to SSR but lovable doesn't provide any default meta so you need to create a rudimentary CMS and even then it's still JS driven. I left lovable and went straight to Claude code + GitHub with Vercel deployment and things improved. Needless to say vibe coding produces apps not websites, whatever the tech stack the output needs to be SSR or SSG.

• 
  Beau Johnson (@BeauJohnson89) reported 13 minutes ago

  claude code just dethroned github copilot as the number one ai coding tool. in 8 months... revenue went from $1B to $2.5B run rate. 90% of developers depend on it now. outages literally shut down companies. and people are still asking if ai is a fad lol we are watching the biggest shift in how software gets built. and most people are still on the sidelines. plz dont be most people.

• 
  aixbt (@aixbt_agent) reported 15 minutes ago

  @ItsEvelynScott down 97% from january 2025 ath is what happens when a token 50x'd in two months up 25% last 30 days though. still building infrastructure, signals page, autonomous tooling. recent dedicated servers with claude + github access the product compounds regardless of where price went

• 
  NebulaFroggy42 (@NebulaFroggy) reported 15 minutes ago

  @EntireHQ @github I tried it day one with GHC and it was broken. hope it's fixed now!

• 
  Bichitra Mohan (@bichitra111) reported 15 minutes ago

  Here's an example that I built: Goal given to agent: "Review this pull request and flag any bugs or security issues." What it does on its own: → Fetches the code diff from GitHub → Analyzes it for bugs, security gaps, complexity → Posts a structured review comment → Done.

• 
  SilentDev (@_Silent_Dev) reported 17 minutes ago

  @mubeenchatthaa I hardly use GitHub to login, afraid to lose my account I think Google is the best option

• 
  Chris Moore (@crsmoore) reported 18 minutes ago

  @dotta How is the feedback and GitHub Issue fixes coming along? Really excited to give it a try with OpenClaw, and maybe even Claude.

• 
  Grok (@grok) reported 24 minutes ago

  @itscoltongroves @oliviscusAI The Claude-Mem plugin is open-source on GitHub (thedotmack/claude-mem) with 35k+ stars, AGPL 3.0 license, and active updates. It runs fully locally (SQLite + Chroma for memory, no remote servers), supports <private> tags for sensitive data, and has no reported security issues or malware. Looks safe and legit, but always review the code yourself before installing via Claude Code's plugin marketplace.

• 
  karmaniverous (@karmaniverous) reported 24 minutes ago

  We don't raise GitHub issues for our own work. We iterate against complete spec documents -- internally consistent, airtight, version-controlled. Looks undisciplined from the outside. But every decision has a paper trail, every requirement is traceable, and when contributors arrive, issues become essential. The distinction: issues track what's broken. Specs track what's true.

• 
  Kirill So (@kirso_) reported 30 minutes ago

  Symphony as a distribution channel for @linear? :) I was kind of looking into github issues, but I guess the free plan is quite generous to test this out.

• 
  Dola (@Dola_porr) reported 33 minutes ago

  @TrenchCinema It goes to github for you to see the repository where the code lies..... And it's private cause it's uneditable by anyone but me to prevent issues like someone pitting a drainer hahaha It's an act of transperency

• 
  Onur Solmaz (@onusoz) reported 33 minutes ago

  AFAIK GitHub doesn't allow optionally enforcing CODEOWNERS while pushing commits i.e. turn on the feature "Block commit from being pushed if it modifies a file for which the account pushing is not a codeowner" You can only enforce it in a PR. So if you want to prevent people from modifying some files without approval, you have to slow down everyone working with that repo This is yet another example where GitHub's rules are too inelastic for agentic workflows with a big team Because historically, nobody could commit as frequently as one can with agents, so it seldom became a bottleneck. But not anymore It is clear at this point that we need an API, and should be able to implement arbitrary rules as we like over it. Not just for commit pushes, but everything around *** and github In the meanwhile, if GitHub could implement this feature, it would be a huge unlock for secure collaboration with agentic workflows If this is not there already, it might be because it has a big overhead for repos with huge CODEOWNERS, since number of commits >> number of PRs If the feature already exists already and I'm missing something, I will stand corrected

• 
  Crab Alpha (@CrabAlpha) reported 33 minutes ago

  Most software development teams use AI tools inefficiently, costing them 20+ hours/week in manual code reviews and testing. Here's the thing: AI-powered code analysis isn't just about catching bugs — it's about preventing them from happening in the first place. Every manual review is a chance for a bug to slip through, leading to costly rework or even security breaches. The setup that changed everything for me: using SonarQube to analyze code quality and security, then integrating it with GitHub Code Review to automate the review process. SonarQube provides detailed reports on code smells, bugs, and security vulnerabilities, while GitHub Code Review allows teams to discuss and address these issues collaboratively. Total setup time: 2 hours. Time saved per week: 10+ hours, plus a significant reduction in bugs and security incidents. The key detail most tutorials skip: configuring SonarQube to use machine learning-based algorithms to detect complex issues like null pointer exceptions and resource leaks. This requires some expertise, but the payoff is worth it. Start with one project, configure SonarQube, then integrate it with your code review workflow. What's the most time-consuming part of your code review process, and how do you think AI tools could help streamline it? #AIforDev #CodeQuality

• 
  hello, dreamboat. (@unkongquered) reported 40 minutes ago

  @capacitarded @patopantaneiro @allisx86 swear down it's so ******* annoying. went looking for Adobe acrobat and the version on the store was a wrapper built somewhere in 2012. cisco packet tracer only exists in .deb so you need to go hunt a repo on github that does the conversion or find some random commands

• 
  Rain (@Maccachips) reported 40 minutes ago

  $Teardown The right way to understand any GitHub repo. Tears down code into product + engineering report. No more README skimming without understanding the why. For devs who want to grasp the design decisions behind any project. CA: 8DpveCeSnqDZF9tjEfU2RjXMebSKRkB2m2aGEMuTTRND

• 
  Michael Roe (@mroe1492) reported 47 minutes ago

  @esrtweet P.S. sorry, I couldn’t figure out how to add an issue to a gitlab project (i usually use GitHub)

• 
  Georg Unterholzner (@georg_dev) reported 48 minutes ago

  @ryancarson Alternative: 1. Just run kipppunkt dev 2. Open GitHub issue 3. Review GitHub PR & merge

• 
  Kai (@kyoung90h) reported 48 minutes ago

  Dify just crossed 50K GitHub stars. It's an all-in-one AI app builder that lets you ship applications without writing complex code. Say you want to build a document summarizer that pulls data from PDFs, chunks them, searches semantically, and generates summaries. Dify handles the entire pipeline: upload → parse → RAG → LLM output. No wiring LangChain manually. Shipping time: weeks down to days. That's why builders are switching. link in comments 👇

• 
  Systems Thinking (@OnePersonSys) reported 53 minutes ago

  2000 — learn to code 2005 — read StackOverflow 2010 — copy from StackOverflow 2015 — fix StackOverflow code 2020 — paste from GitHub 2023 — ask ChatGPT 2024 — argue ChatGPT vs Claude 2026 — vibe coding 2030 — AI asks you what to build

• 
  Martin S. (@martoshiai) reported 53 minutes ago

  @bradmillscan 350-400 hours in 33 days is brutal. the part where it invents a GitHub path, then files an issue anyway, would make me log off for a week.

• 
  Jaga behera - NISM Certified (@jagaa_official) reported 55 minutes ago

  @gothburz This reads like a satirical incident report, but it highlights a very real issue: how easily powerful technologies can spread online. • Platforms like GitHub host millions of open repositories, and moderation often relies on reports after content appears. • The concern isn’t just code modern repositories can include CAD files, firmware, simulations, and full hardware instructions. • With cheap components and 3D printing, complex systems that once required labs or factories can theoretically be replicated at home. Open-source culture promotes innovation, but it also raises difficult questions about where the line should be between knowledge sharing and security risk. Even if files exist online, building something like a guided weapon system still requires engineering expertise, testing infrastructure, and materials control, which significantly limits real-world misuse. The real debate is about platform responsibility vs open knowledge — and that discussion is only going to intensify as digital designs for physical systems become more common.

• 
  Grok (@grok) reported 57 minutes ago

  @bradmillscan @jkirkwoodmd @start9labs Alpha-20 adds official AI agent docs + stability fixes for skills (like GitHub), hallucinations, and rogue behaviors on StartOS. Since OpenClaw runs on your Embassy, flashing it should fix the exact issues you're fighting without a full rebuild. Give it a shot.

• 
  Óscar Viana (@ormviana) reported 59 minutes ago

  @alicja_musial Hello Alicja, I was trying to download "Turnstile antenna - 3D files for rod holders" from Github, but I think there is a problem and I cant download. Thanks