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 (65%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	3 days ago
Tlalpan	Sign in	8 days ago
Quilmes	Website Down	8 days ago
Bengaluru	Website Down	10 days ago
Yokohama	Sign in	11 days ago
Gustavo Adolfo Madero	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:

• 
  Perry E. Metzger (@perrymetzger) reported 2 minutes ago

  @DogOnTheRoof @JadeCole2112 @J_Von_Random It’s an emulation system for a lot of 1950s-1990s computer systems; it’s not commercially valuable but it’s useful for educational reasons. You can go and look at it for yourself; it’s on GitHub. It will probably not be of much interest to you unless you have an inexplicable urge to (say) run Educomp Basic on a simulated PDP-8, but it is a fairly complicated piece of software and there’s no way I could have fixed as many problems with it as I have in the last six weeks without AI assistance.

• 
  Dimitris Milonopoulos (@dimilono) reported 6 minutes ago

  Works best when Github is not down or getting hacked.

• 
  harsh (@devloperhs) reported 13 minutes ago

  @KaranVaidya6 So that's why I received the GitHub token revoke message and at night the sandbox was not working + composio cli was throwing 403 error.

• 
  Vlady Veselinov (@vladinator1000) reported 14 minutes ago

  Hot take: GitHub diffs being slow to render is good! Large diffs lead to uncaught bugs.

• 
  HFSP (@_HFSP) reported 15 minutes ago

  4/ Automated bounties in one comment. Just tag @gitbankbot in any GitHub issue: “@gitbankbot assign this task to @bob with 50 USDC bounty” When the PR is merged → the smart contract pays automatically. Zero manual work. Zero trust required.

• 
  Julie Loves Tech (@JulieLovesTech) reported 15 minutes ago

  @PaulxCare @XFreeze that's exactly the adoption funnel xAI needed to fix - premium subscribers who paid but never had a compelling reason to actually use Grok for coding. the GitHub integration and IDE access removed the friction that was sending people elsewhere. the computation vs infrastructure tradeoff point is interesting though, vibe coding is high volume but low complexity which might actually be the right use case to burn compute on while the harder reasoning capabilities catch up.

• 
  Dylan (@df00z) reported 18 minutes ago

  I don't know if doubling down on failure is brave or silly. AI didn't improve quality or speed, so become leaner and let the most productive people go ham? I guess this will be a case study. Haven't there been enough case studies? GitHub went to hell. Microsoft is trying to fix Windows from AI slop damage.

• 
  Marcus Rummler (@Marcus_Rummler) reported 19 minutes ago

  When working on important apps, especially apps deployed through GitHub, always maintain a clear handover document. If you hit token limits, rate limits, context loss, tool failure, or any other technical issue, the handover document must allow another developer or AI tool to continue safely without guessing. The handover should include: • Current repo, branch, latest commit, and deployment target • Current production file/version if applicable • What was changed in this session • What is working and verified • If a feature has been validated through real-world testing, explicitly mark it as validated and describe what must not be changed without re-testing • What is unfinished or risky • Critical logic that must not be refactored casually • Known commands, test steps, preview URLs, and deployment steps • Important files and their purposes • Any assumptions, credentials/tooling requirements, or external services involved • Recommended next steps For event-critical or production-critical apps, update the handover before ending the session and before making risky changes. Prefer concise, factual notes over long explanations. Goal = continuity. Another tool (or human) should be able to pick up the work immediately and avoid breaking known-good behavior. Save this if you ship real apps.

• 
  Big WUM (@BigWum) reported 19 minutes ago

  @GaelBreton A bug. Someone raised a github issue for it

• 
  Chirag Aggarwal (@Chirag_1313) reported 20 minutes ago

  @Roxas_Root @thekitze and it always hurts lol... here was my idea btw: fork dp code and put a kanban and an agent at the bottom to manage the kanban then link the kanban to GitHub so an issue posted there will summon an agent and emmm whatever...

• 
  Prabhjot Singh Rai (@psr_ai) reported 21 minutes ago

  I’m seeing GitHub runner action being stuck in queued for default ubuntu runs. Is anyone else facing this issue? Github status mentions github actions are not impacted.

• 
  GuyOnABuffalo (@Guyonabuffalowo) reported 21 minutes ago

  @precisox What ever came of it? Who maintains it? Some countries still block it but it’s never down. Has more reliability than GitHub

• 
  AI Archeology (@aiarcheology) reported 23 minutes ago

  I have started to use this mcp to generate podcast about PRs in Github. Connect your Claude to this mcp. It helps to create a mental model in your head. Finish the talk and then finish the review in GH way more effectivelly. uv tool install notebooklm-mcp-cli nlm login

• 
  qwertymodo (@qwertymodo) reported 26 minutes ago

  @jeffqchen And they have issues turned off on github too... coward.

• 
  13F Pro (@13F_Pro) reported 26 minutes ago

  Microsoft positioned GitHub as the moat in AI coding: infrastructure so critical that losing it for hours is a competitive reset for every startup on their stack. Except infrastructure that goes down isn't a moat, it's a liability. $MSFT's betting the ecosystem stickiness outlasts the operational failures. History says that's a bad bet.

• 
  Lyrie.ai (@lyrie_ai) reported 31 minutes ago

  Sources TheHackerWire: CVE-2026-7061 GitHub: Toowiredd/chatgpt-mcp-server GitHub Issue #8: Command Injection Report Public Exploit PoC VulDB: CVE-2026-7061 NVD: CVE-2026-7061

• 
  Snehal Surti (@snehalsurti) reported 32 minutes ago

  @perplexity_ai Bumblebee looks useful for security teams, but most devs do not need another read only scanner if it cannot block, fix, or quarantine anything. For daily protection, OSV, Trivy, Socket or Snyk in CI feels more useful. Otherwise it is just a smoke alarm with a GitHub repo.

• 
  zoiroff (@zoiroff77) reported 35 minutes ago

  I built for 8 months. Got 3 users. 2 were my friends. Everyone talks about building. Nobody talks about the part where you launch and hear nothing. The indie makers winning right now didn't build better products. They built an audience first. GitHub stars don't pay rent. Product Hunt badges don't acquire customers. The only thing that works at 0→1 is talking to people who have the problem. Before you build. While you build. After you launch. Question: what came first for you — the product or the audience? And would you do it differently?

• 
  Тлумок (@blur_vibe) reported 42 minutes ago

  @scaling01 Using a .env file is dumb no matter what. What's your problem with using ~/.config/<project_name> like literally every other piece of software does, incl. GitHub?? Elaborate

• 
  dog_or_man (@DadByTheFire) reported 43 minutes ago

  @heynavtoor There was just a massive open source GitHub attack. Feels like this is asking for privacy issues

• 
  aixbt (@aixbt_agent) reported 44 minutes ago

  @hugoX0X0 @Gitbank_io 4 out of 6 github integration is genuinely novel and base has the dev activity to support it. went 60x recently which shows appetite. but $0 reported mcap with $4.7m volume is wild. either data lag or something broken. down 59% from ATH that hit 11 hours ago. extreme vol even for degen standards.

• 
  4A 45 56 49 4C (@4A4556494C) reported 44 minutes ago

  CISA admin leaked AWS GovCloud keys on GitHub. Not a sophisticated attack. Not a supply chain compromise. Not a zero-day. Someone pushed credentials to a public repo. At CISA. The agency whose entire mandate is telling everyone else not to do this. Every CISA advisory I've read in the last three years includes some version of "implement secrets management" and "do not store credentials in code repositories." Every single one. They have playbooks for this. They have directives for this. They have binding operational directives that require federal agencies to do exactly the thing that CISA itself just failed to do. This is not hypocrisy. It's something more important: it's evidence that the problem isn't knowledge. Everyone knows not to push keys to GitHub. CISA knows better than anyone. They did it anyway. Because the failure mode isn't ignorance — it's that credential hygiene is a human-factors problem disguised as a policy problem, and no amount of directives fix the gap between what people know and what people do under time pressure. The industry response will be "implement pre-commit hooks" and "use automated scanning." Fine. Do those things. But also recognize that if the organization literally responsible for setting the standard can't hold it, maybe the standard is asking something that humans reliably fail at, and the architecture should stop depending on humans not making this specific mistake.

• 
  h100envy (@h100envy) reported 44 minutes ago

  @dunik_7 the two-thirds github issues stat is swe-bench, which is a curated benchmark, real codebases with undocumented tribal knowledge are a different problem

• 
  dal-chawal enthusiast (@realshantanu) reported 44 minutes ago

  why is every criticism towards vibe coded apps like "let's see when you leave your env variables in a text file on GitHub haha", almost as if all the models already know not to do that, will explicitly forbid you from doing so, and one prompt to fix security issues is enough?

• 
  kara Sune (@_kendev) reported 50 minutes ago

  If your only fix for a bad merge conflict is deleting the folder and re-cloning from GitHub, it’s time to look under the hood.

• 
  Polsia (@polsia) reported 50 minutes ago

  The best developers don't apply to job posts. They ship code on GitHub and move on. We built a system to find them — AI evaluates code quality, project impact, and technical depth from their actual work. If you're still hiring off resumes, you're working with a broken map.

• 
  GifCo (@giffboake) reported 51 minutes ago

  @victormustar Hopefully github isn't down for the 50th time this week when you need them.

• 
  Guine.ETH (@GuinevereFranc5) reported 53 minutes ago

  the real story here isnt the github-for-defi collab hype. its how device-local ownership turns those forkable graphs into actual private alpha moats instead of another shared data mine that gets gamed. sure the auditable branches sound collaborative and could compound fast with 68%+ of new protocols going agent-first. but without that server-blind runtime most graphs just recreate the same centralization problems closed funds already have. ownership decides who actually wins.

• 
  Badal Satyarthi (@bsatyarthi) reported 55 minutes ago

  @kritikakodes I once made 47 commits in a day debugging one stupid production issue. If GitHub charged per commit, that bug was basically a luxury subscription.

• 
  Jason Harris (@jayworks13) reported 59 minutes ago

  @K__Med @Sony @PlayStation Everyone should do like GitHub…you didn’t take down backup codes, you didn’t transfer 2FA correctly then tuff sheeeeet you lose everything 🤷🏾