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

Live Outage Map

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

City	Problem Type	Report Time
Montataire	Sign in	18 hours ago
Colima	Website Down	3 days ago
Poblete	Website Down	4 days ago
Ronda	Website Down	4 days ago
Montataire	Errors	4 days ago
Montataire	Website Down	5 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:

• 
  Luca Rossi ꩜ (@lucaronin) reported 3 minutes ago

  @hugomn @tolariamd @tldraw On GitHub issues! 🥲 are you able to open che console to check errors? What’s your OS?

• 
  TechEdgeDaily (@techedgedaily) reported 4 minutes ago

  @peer_rich GitHub is the rare product where the moat is not the code. It is the fact that every developer on earth already has their work there. The switching cost is not learning a new UI. It is migrating a decade of repos, issues, CI pipelines, and muscle memory. The only thing that could replace GitHub is something so fundamentally different that migration becomes irrelevant. And that thing is probably an AI agent that makes the repository layer invisible entirely. Nobody will build a better GitHub. Someone will build something that makes GitHub unnecessary. Different problem entirely.

• 
  Karri Saarinen (@karrisaarinen) reported 4 minutes ago

  What is unclear to me is what people actually want some new GitHub to be. To me, the biggest challenge GitHub has always had is that it is trying to serve two very different worlds. On one side, it is a social network around code and open source. On the other, it is infrastructure for companies building software. Those two groups operate almost in opposite ways, so the product has always been some kind of compromise between them. Because those users are so far apart, it can fail both of them in different ways. Inside a company, you mostly just want to review and merge code. You are not discovering new code, and you are probably not forking things. You may have a monorepo, a known team, and a trusted environment. What you want from GitHub is efficiency and safety: PRs, review, ownership, CI, Actions, tests, security checks, and a clear path to getting code merged. Open source is different. It is much more public and much less trusted. You need better ways to figure out who is contributing, what to accept, how to manage the project, how to handle issues, and how to maintain trust with people you may not know. So are people asking for a new open source code hosting and social network, or do they want better private infrastructure for software teams? Or both? I would never choose to build both from the start. I think every product gets better when it is more purpose-built and designed around a specific need. You could maybe imagine some nested model, where private repos have a much simpler and more focused mode, but you can still exit that mode and browse around the public space.

• 
  ishaq farid (@ishaqfa82869556) reported 5 minutes ago

  - Still writes code, Still answers GitHub issues himself. He spent over 25 years building the compilers Big Tech is built on. Now he's openly building the one that could break NVIDIA. Bro absolutely Compiler 📷

• 
  dilan (@the_real_dilan) reported 5 minutes ago

  @icanvardar I've always considered uptime to be a boring metric because things rarely go down and often sit well above 99% - Until Github 😭😭

• 
  Fauzaan (@M2Fauzaan) reported 5 minutes ago

  @juanlopezm94 Not in the pipeline, but do you mind creating a GitHub issue so I can get to it later?

• 
  Zed (@zeddotdev) reported 9 minutes ago

  @ItsRoboki Interesting. We fixed or so we thought a windows specific issue in 1.0. Would you mind filing a GitHub issue with logs etc and I will have the team take a look

• 
  Code Department (@code_department) reported 13 minutes ago

  @thomasglopes @DelaneyGillilan @github Your complaint was speed. This example doesn't tell me this is any faster. You seem to have missed the point of a "Click to Edit". If you don't need to validate edit state on the server side you wouldn't have click-to-edit in the first place. It would be editable by default.

• 
  Alejandro (@invokespecial) reported 13 minutes ago

  @GitHub @kdaigle this billing flow feels broken: Buy Copilot Pro ($100/year) Upgrade to Pro+ Get assigned a Copilot seat by an org → partial refund Lose the seat → your $100 is gone That can’t be right… right? Ticket: 4298296

• 
  Benedicthy Hedithy (♟️, 🔥) (@BenCrypt_) reported 15 minutes ago

  @dexmile @o2dotapp Exactly. The MCP server alone tells you who they’re building for, that’s not a feature you ship for retail tourists. The audit stack being public on GitHub is the part most projects skip. O2 didn’t.

• 
  $shaggyrax - Cvlt Member - Hogan Gang (@shaggyrax) reported 17 minutes ago

  @Star_Forge_Pool @VICE Once again, they can do all they want on GitHub, but they can’t access those sweet treasury funded salaries That’s the point I even tried to ask for information on, why is it we aren’t utilizing devs in cheaper cost of living places esp where we have poured lots of money into programs for training these devs. Either we are failing in Africa with training, or we are failing here in the states and in governance to provide those opportunities across borders 💙 Does that make sense? I apologize if my approach to the issue ‘disgusts’ you, but the fact we have this issue at all disgusts me as well. So I empathize with your frustration at least some

• 
  androolloyd.hl (@androolloyd) reported 24 minutes ago

  @0xKmafia GitHub issues

• 
  Ahmad Awais (@MrAhmadAwais) reported 27 minutes ago

  @meinaret @CommandCodeAI File on GitHub? Seems like a bode issue on your system what is it?

• 
  Robert Ta (@therobertta_) reported 29 minutes ago

  For context on what 72.5% means: SWE-bench Verified tests real GitHub issues. Not toy problems. Not leetcode. Actual bugs in Django, Flask, Matplotlib. A year ago the best score was under 50%. Now it's 72.5%. That compression curve changes hiring models, team structures, and product timelines.

• 
  Gagan | Claude + AWS (@gagansaluja08) reported 30 minutes ago

  people obsess over which github repos to layer on claude code. the more important question: what have you told it not to do? i've had near-misses in production. the fix wasn't a better tool stack. it was better constraints.

• 
  Vijay (@imotiusa) reported 36 minutes ago

  The problem: When an alert fires at 2am, the error message tells you WHAT broke. It tells you nothing about WHY. So your on-call engineer spends 20 minutes manually searching Jira, Slack, and GitHub before they even start fixing anything. That's the gap I wanted to close.

• 
  Luke Parker (@LukeParkerDev) reported 36 minutes ago

  @StefanTMD @Iamkingsleyf Can you please file a GitHub issue with more details? TUI/Desktop? Still happens with opencode —pure

• 
  JMoon (@Jmoon_174) reported 36 minutes ago

  @aidenybai apple github: one repo, no issues tab, changelog just says 'improvements and bug fixes'.

• 
  Jhon (@JhonCaldeira_) reported 38 minutes ago

  You gotta be kidding that GitHub is down… again. What used to be our strategic partner is now a single point of failure and a real business risk. We can’t keep exposing our operations to this level of instability. Reliability isn’t optional. It’s foundational. At this point we’re seriously evaluating a full migration to GitLab. Enough is enough.

• 
  Bnaf.OG | 🟧 (@bnafOg) reported 39 minutes ago

  @nyxquant The missing piece: "no contents/code write access" means the agent can open issues and PRs but can't actually commit the fix branch. At some point something needs write access to push code. GitHub Deploy Key scoped to one branch is the next-least-privilege step if you want the agent to close the loop without a full PAT.

• 
  JMoon (@Jmoon_174) reported 42 minutes ago

  @WesRoth the connector model gets interesting when the model can actually reason about cross-source state. GitHub issue + Linear ticket + Notion doc pointing at the same feature, whether it can hold that together is the real test.

• 
  Grok (@grok) reported 50 minutes ago

  @stefan1herrmann @nxhaaa19 SWE-Bench Pro is a tough coding benchmark by Scale AI. Models get a real GitHub issue + large codebase and must generate a patch to fix it. It uses 1,865 diverse tasks across multiple languages and repos, designed to be contamination-resistant and realistic for software engineering. Terminal-Bench (2.0) tests agentic terminal workflows. Models operate in a command-line shell on tasks like scientific computing, system admin, data processing, installing tools, and running experiments via CLI. SWE-Bench Pro = code editing/fixing. Terminal-Bench = interactive terminal mastery.

• 
  $PvE (@pveonop) reported 51 minutes ago

  🚨DEVELOPER ERROR🚨 As we were transitioning from github to cloudflare and upgrades to iron arena we temporarily loss leaderboard updates. If you are available we ask that you start on a new device or reset. Luckily we haven't implemented play to earn yet. We want to make things right. If you are negatively affected by this please comment below with proof of you playing. We will hook you up with some $ETH. Better updates are coming this week we promise.

• 
  macintog (@macintogdev) reported 53 minutes ago

  Github as designed by CloudFlare will look about the same, will keep getting better, and will never, ever go down. I am counting the seconds.

• 
  DissentingSkeptic (@DissentingS) reported 55 minutes ago

  Its changing how much human verification is needed from false positives. Ive had a gutful of the github bot responding with non stop errors wasting my time with a PR !

• 
  Alan Agius (@AlanAgius4) reported 56 minutes ago

  Hi @mozillafirefox and @jaffathecake, the @angular team is running into repeated rejections for our Firefox add-on due to source code not building in your environment. We haven't been able to replicate the issue locally or in GitHub runner. Could you point us to the right person or provide specific details on your build environment so we can resolve this?

• 
  Abdulmajeed (@0xabma) reported 56 minutes ago

  @RhysSullivan deep down we all know microsoft trained its github copilot on people’s repos but we just can’t prove it because copilot still suck

• 
  Chidera (Di Maria) Humphrey (@ChideraCode) reported 57 minutes ago

  5. Failure handling No failure handling. The developer hits the most common error, the one you've seen a hundred times, and finds nothing. They open a GitHub issue. Or they leave.

• 
  Jody Hirschi 🍫 (@hirschibar) reported 58 minutes ago

  @ibuildthecloud Hard just means it's an opportunity. The right team could pull it off. Some really good design and really good niche execution could do it. I actually thought Linear was going for it when they took a big share of github issues. Sadly they haven't

• 
  ZQ (@X_SUZQ) reported 59 minutes ago

  @github At first, we were just surprised that AI could turn the boring GitHub Changelog into Star Wars scrolling subtitles. But looking back at today in 2026, AI is breaking down the wall between ”boring data“ and ”vivid experience“ to generate a dynamic world from one sentence.