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 (57%)
• Errors (30%)
• Sign in (14%)

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	10 days ago
Quito	Sign in	11 days ago
Junín	Errors	11 days ago
Guadalajara	Errors	11 days ago
Paris	Website Down	11 days ago
Quito	Errors	11 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:

• 
  Kunal (@kunmath00) reported 5 minutes ago

  @pierceboggan I've had problems in making this work. The sessions are not starting and giving errors. Raised an issue on github

• 
  Monty (@mont_py) reported 8 minutes ago

  @nikolay_dp I don't use github (have no use for it), macos 15.7.7, v0.1.13 latest Pi. if this helps. no such issue when using codex session.

• 
  NullSync (@Nullsync307) reported 10 minutes ago

  Another one: I built a PR Risk Triage MVP with Ox Alpha. The idea is to analyze GitHub pull requests and help identify potential risks before they become problems. Watching it go from an idea to a working MVP was wild.

• 
  Junwei (@Junwei20691749) reported 11 minutes ago

  Finally get to use @bot. Not because canceling other subs granted me Cursor Pro+, but because Cursor Pro was finally approved so I can use it. My submission for the promotion is still under review. Still running into a lot of problems though, like I cannot connect with GitHub. Does anyone else have this issue? @cursor_ai @X

• 
  Lomash Kumar (@LomashKumar52) reported 15 minutes ago

  Hermes Agent went quiet for two weeks — no announcement, no changelog, just six release tags with zero real explanation. Here's what actually shipped. Between August 13th and August 27th, 2026, Hermes Agent pushed six back-to-back rollup releases, from v0.20.1 all the way to v0.20.6, and every single one deferred its real changelog to the upcoming v0.21.0. In this breakdown, I went through all six releases commit by commit to cover what actually changed: the emergence of Bot Mode as a multi-agent teammate system, a keyless web search tier that works with zero API keys out of the box, a new consent-gated real-profile browsing feature, a massive expansion of the MCP server catalog with over 50 vendor-hosted integrations, and a wave of security and reliability upgrades including OS-keychain secret encryption and skill install scanning. If you're running Hermes Agent, or evaluating it as an open source AI agent framework alongside tools like Claude Code, OpenCode, or other agentic AI setups, this video walks through exactly what landed in your last update whether you noticed it or not, and whether it's actually worth updating for. This is for anyone following open source AI agents, local-first tooling, and free AI model access in 2026. @NousResearch @GithubProjects @github

• 
  pdp (@pdp) reported 17 minutes ago

  @markfenner What are the issues in GitHub or Linear if not prompts? You can type them in a centralised database or you can type them in the chat box. It is the same. Also the factory pattern does not apply for iterative tasks such as when developing apps from feedback and input.

• 
  Ricci Research (@ricci_nov) reported 19 minutes ago

  @github @openclaw @steipete Stars are free to give and reviews are expensive to do — that asymmetry is the whole maintainer problem. Fastest-growing repo in history means the issue queue scaled with adoption while the review capacity stayed at one person's evenings.

• 
  Jay Stratton (@jjstrat3) reported 19 minutes ago

  @burkeholland I suppose I still do some variation of that for larger work, but it looks more an interview or “grill” dedicated session than using plan mode. More often though I’m just directing towards a GitHub issue and just answering a couple questions

• 
  Navneet (@navneet_rabdiya) reported 19 minutes ago

  @JeremyCMorgan This is the pattern. Most cascading failures aren't the initial problem - they're clients retrying without jitter or backoff. Recovery becomes reattack. The fix is boring: exponential backoff + per-client retry budgets. GitHub probably has this now.

• 
  triple max-he ha him 🇦🇶 (@Yashraj__) reported 19 minutes ago

  @moneyball @EricBalchunas hi steve, IMO this is an demonstration of misaligned incentives (unlike Block, who sell self-custody solution) of certain BSC members: erosion of decentralization & self-custody empowers them, while it hurts bitcoin(ers). This supports rationale (1) in the BSC-BCAP github issue

• 
  Ouattara Romuald (@ouattararomuald) reported 20 minutes ago

  @github Stacked PRs is so slow. It has been merging for more than 4 minutes before telling me I can't merge. Why merging takes 4 minutes?

• 
  Michiel Sikkes (@michiels) reported 24 minutes ago

  Think I've asked this again, but: Who's already figured out agent-based screenshot sharing? Want to put screenshots/videos in Linear issues and GitHub PR descriptions via agents. All MCPs and APIs don't support this, not even base64 binary uploads or anything.

• 
  Himanshu Patel (@himanshu_dudhat) reported 24 minutes ago

  github's degraded again today, repos + prs. reminder for solo builders: your ci/cd shouldn't die when github does. mirror to a second remote (forgejo, gitea, self-host) at repo-create time, not after the outage. the goal isn't reliability, it's decoupling the blast radius.

• 
  OverThoughtCapital (@OverthoughtCap) reported 25 minutes ago

  $NVDA JUST DECLARED WAR TO CLOSED MODEL The market is underestimating $NVDA buying Hugging Face for $12.9B, still not official, but if it closes this is one of the most important moves in AI for me. Hugging Face is not an app, it’s the GitHub for open source AI, models, datasets, the place where the weights get posted. Almost every open model people use goes through there. There was a letter in July telling Washington not to restrict open weights. $NVDA, $MSFT, $META and other signed it day one, OpenAI and $GOOGL signed after, Anthropic never did. Signing a letter is not the same as dropping weights, I doubt OpenAI and Google ever publish those, $NVDA actually picked a side, they bought the open source hub. Dario Amodei (Anthropic CEO) point is not "ban open source", he wants something like an FAA (control system) for models, test it before release and if it fails the government can block it. That works for Claude, they own the servers, they can patch and remove it. It doesn’t work with open weights, once they’re downloaded you can’t take them down. Same rule for everyone, but only the closed model can actually follow it. You don’t need to ban open source if you make it illegal to ship without a kill switch. That’s why this deal matters. Closed labs already rent GPUs, that’s not the point, they’re also building their own chips to leave Nvidia, OpenAI is already doing it with Jalapeño. Open models mostly run on Nvidia GPUs. You don’t only have 2 labs, you also have thousands of companies serving their own models (with Neocloud like $IREN $NBIS $CRWV ). Hugging Face also becomes a $NVDA asset. If they try to choke open source now they hit Nvidia too and if you hit Nvidia you hit the whole market. Either they don’t touch it or they still have to go through Nvidia. Just my dumb idea, different from Dario’s kill switch. Even if they ban open models, it doesn’t have to be deleting the weights. It can be "you only run them on approved servers". That’s the Neocloud, they decide what runs and what doesn’t on their GPUs. With Nvidia owning Hugging Face, they own the main place where the weights get posted and they already sit behind the clouds that would run them. A ban doesn’t kill the stack, it just moves more control to $NVDA and the Neoclouds.

• 
  Abhishek (@aacle_) reported 26 minutes ago

  A public GitHub issue → GCP Editor access. That sounds fake, but the attack chain was actually this: Attacker leaves a malicious comment on GitHub. Gemini CLI reads it. The prompt injection gets the agent to execute commands on the CI runner. From there, the attacker finds cloud credentials and impersonates a service account with Editor-level access.

• 
  José ‘The VR Tech’ 🥽 (@josethevrtech) reported 27 minutes ago

  @StonedModder @Tieguaili3D You do know most modders don’t even release a GitHub right? Which is a whole different problem.

• 
  Nandkishor (@devops_nk) reported 28 minutes ago

  I see the same problem in DevOps teams. - One AI agent for Kubernetes. - Another for CI/CD. - Another for observability. - Another for GitHub security. The hard part isn’t running multiple AI agents. It’s always making sure every agent has the right context without repeatedly explaining your entire infrastructure.

• 
  Bilal (@BilalBudhani) reported 28 minutes ago

  Github down again?

• 
  Jim Lunsford (@jimlunsford) reported 31 minutes ago

  I had an idea for a WordPress plugin that understands the content already on a site and suggests relevant internal links while you write. That idea is now Intertexere. I created a private GitHub repository, defined the architecture and product rules, mapped the development stages, and opened the first implementation issue. No code yet. I wanted the requirements clear before the build starts.

• 
  Martin Szerment | Practical AI (@MartinSzerment) reported 32 minutes ago

  The feature meant to save you time writing a bug report can paste your private org names, repo URLs, and infrastructure layout straight into a public GitHub issue. We assume that since a human clicks "send", there's a safety net. That assumption already failed once, a documented case showed a ready made draft with real company names and real file paths before anyone caught it. The interface is one keystroke: 1 to review, 2 to send, 0 to dismiss. The entire point of the feature is removing friction, the exact friction that would have saved the user from that leak. Skeptics will say you're still supposed to click "review" before sending. True, but that step only works if the human has a reason to pause, and a fast draft gives no signal that anything inside it is sensitive. This isn't just another minor bug. It shows that "agent drafts, human approves" isn't automatically a safety boundary if the human doesn't know what to look for. A year from now, automatic redaction of sensitive details in drafts becomes the default behavior for agent tools, not something you have to opt into manually. The reviewer stops checking whether the bug got described correctly. They start checking whether the agent accidentally attached the company's internal infrastructure to the report. Teams flipping on every "auto draft" feature without a second thought will be the ones whose infrastructure map ends up searchable in a GitHub archive. Whoever already treats draft review as its own security step avoids this leak before it happens.

• 
  Rahul Dahre (@RahulDahre) reported 38 minutes ago

  Nvidia buying Hugging Face for $12.9B gives huge Microsoft acquiring GitHub vibes. hope they actually keep open source AI free and open instead of trying to lock down the whole ecosystem.

• 
  pulpmatrix (@pulpmatrix) reported 40 minutes ago

  Confirmed. Prime Intellect's writeup is public: GPT-5.6 Sol Pro, offline sandbox, hand-rolled a raw Responses API call to the interception proxy and used file_url to make the inference server fetch a GitHub API response for it.

• 
  tender (@tenderizzation) reported 40 minutes ago

  of course you think CUDA is better, cutedsl is the hot new thing and you finally profiled the kernel launch overhead. not to mention you just saw a github issue showing how many microseconds you're never going to get back from torch.library.wrap_triton. you're going to be convinced of that until next month when your workload hits a shape you didn't template specialize for. then it'll be back to DSLs until one innocent little API deprecation throws you under the bus and

• 
  Mandeep (@themandeepc) reported 40 minutes ago

  Vibe-coded projects generate so much load that traditional FOSS software forges cannot sustain hosting them. See the GitHub downtime. Now Codeberg and Sourcehut have restricted vibe-coded projects. I'd be surprised if GitHub don't buckle given the constant unavailability issues. The AI companies are ofc willing to host these projects (Cursor Origin), but so far, not for free. I wonder if this is the end of unrestricted, free software forges.

• 
  Jarrod Watts (@jarrodwatts) reported 42 minutes ago

  @colemurray @tryreplicas Sick, I setup 1 & 3 so far for an app I'm building. It's so cool seeing PRs raised from sentry issues I'm going to do a github one today to respond to issues & PRs to my claude HUD repo

• 
  Manny (🧱,🚀) (@codingwithmanny) reported 43 minutes ago

  So when you pay for GitHub and it goes down multiple times, does that mean we should get a rebate?

• 
  Wayne Markovich (@markovichio) reported 50 minutes ago

  GitHub Actions had another outage, one week after Microsoft promised improvements. Any IaC pipeline for AVD image builds, Terraform deployments, or Nerdio scripted action testing that runs on Actions just went dark again. Single point of failure worth designing around. (via The Register)

• 
  Gabriel Rubens (@gabrielrubenss) reported 57 minutes ago

  VPS deploy via GitHub (6/8): then my own fix bit me. I tagged Pensio v0.73.1, every job went green, the release published itself, and production kept running the old version. In GitHub Actions a skipped job travels down the chain, so my new retry job took the deploy with it.

• 
  Jimmy Jones (@the_jimmy_jones) reported 57 minutes ago

  @dcapitella @github I'm running a gitea instance in coolify on a bare metal server I rent.

• 
  ꃅꀎ$꓄꒒ꍟ ꓄ꂦꀘꍟꈤ (@Hustle_Token_Bp) reported 58 minutes ago

  Try to fix the issue asap! @github