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 (59%)
• Errors (32%)
• Sign in (10%)

Live Outage Map

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

City	Problem Type	Report Time
Montataire	Website Down	4 hours ago
Tortosa	Website Down	2 days ago
Culiacán	Errors	3 days ago
Haarlem	Sign in	7 days ago
Villemomble	Website Down	7 days ago
Bordeaux	Website Down	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:

• 
  The Arctic Dev (@TheArcticDev) reported 6 minutes ago

  My feed: - @github sucks, I am leaving - @claudeai sucks, I am leaving - Codex sucks, I am leaving Can you all explain something to me. Were you even developers before AI? If not, sit down, you do not get to complain. If so, do you remember what writing code actually is?

• 
  Alexandre (@alex_andrinho) reported 7 minutes ago

  Hey, does anyone sees a tons of issues lately with github ? API rate limit CI/CD that fails for no reason even PR that doesn't showing up ?

• 
  Marius Møller-Hansen (@MariusMollerH) reported 8 minutes ago

  Is GitHub, Google Cloud, or me the issue? Because cloudtriggers are not triggering

• 
  Gerald Versluis (@jfversluis) reported 9 minutes ago

  Copilot Chat is now built into VS Code. No extension to install. Update to v1.116, sign in with your GitHub account, and it's just there. One less thing to set up when onboarding new devs.

• 
  🇹‌🌟🇲‌ (@tomfool1978) reported 10 minutes ago

  @vladchatware @mkristensen I'm struggling with SKILLS to create GitHub issues via the 'gh' cli. An Issue needs a correct Milestone. I want a very cheap Model for this. It often fails and takes way too long. I guess I have more success when I put this Milestone pick logic in an Mcp Server Tool.

• 
  Arnav Gupta (@championswimmer) reported 12 minutes ago

  @threepointone Serious Business™ are on Github Enterprise (and Enterprise Server ) which wasn't as badly affected as the rest of us though.

• 
  . (@AnthonyCru57378) reported 13 minutes ago

  @P33RL3SS @guzmansalv @fchollet What ground breaking piece of software has AI produced? As far as I can tell even with Anthropic owning their false machine god mythos their software is still a sloppy bug ridden mess which is consistently down. GitHub has a set of coding tools yet they're down consistently.

• 
  parth. (@TotallyNotParth) reported 13 minutes ago

  @thsottiaux - That error is probably from GPT trying to combine big GitHub tool calls, long diffs, and response generation in the same turn.

• 
  Ryan Alyea (@ROFISH) reported 14 minutes ago

  gamedevs: github's downtime and issues are becoming unacceptable. what are you doing now? right now i'm just pushing to a remote file server rather than github just in case...

• 
  Csaba Kissi (@csaba_kissi) reported 16 minutes ago

  💥Unpopular opinion: Your GitHub star count doesn't matter, your ability to solve real problems does. Your thoughts👇

• 
  web3nomad.eth | atypica.ai (@web3nomad) reported 21 minutes ago

  the stale ticket problem is real — most *** spend 20% of their week just triaging backlog rot. building the context-gathering into the tooling instead of making it a manual ritual is the right instinct. curious whether you find the Jira side or the GitHub side more signal-rich for surfacing what actually matters.

• 
  🩷Otome-chan🩷 (@Otome_chan311) reported 22 minutes ago

  @NaMarrado_ @DCFUKSURMOM @ShitpostRock2 That's a problem with the developer, not github

• 
  Jay Chas (@jaychasofficial) reported 22 minutes ago

  @Clawnch_Bot @NousResearch Github page looks to be taken down. How can we read documentation?

• 
  noxtherox (@noxtherox) reported 24 minutes ago

  @nesquena @aronprins @bergeouss Good stuff man, this is the interface i am currently using and it is pretty well done. Do you have a preference on where people should report issues if they come up? (Github directly or elsewhere?)

• 
  DFIR Radar (@DFIR_Radar) reported 25 minutes ago

  AI-powered GitHub Actions from major vendors contain critical permission bypasses and novel secret exfiltration vectors. Research reveals widespread misconfigurations in production workflows affecting 200,000+ starred repositories. Key vulnerabilities discovered: • Permission bypass via "Dangling GitHub Apps" - attackers create apps with trusted names due to syntactical validation flaws in anthropics/claude-code-action and openai/codex-action • Dependabot Confused Deputy attack enables unauthorized AI execution by triggering @dependabot recreate commands to appear as trusted bot actor • Novel secret exfiltration of dynamically-created credential files (GCP service account keys from google-github-actions/auth@v2) that models don't recognize as sensitive • Verbosity modes (show_full_output: true) expose secrets in workflow logs during file read operations Attack chain: Attacker submits malicious PR/issue → bypasses permission checks → prompts AI to read local credential files → secrets leaked via workflow logs or direct exfiltration. DFIR teams should audit GitHub Actions workflows for AI integrations, monitor for unexpected bot actors in workflow logs, and implement strict input validation. Search for workflows using pull_request_target with AI actions - high risk configuration. #DFIR_Radar

• 
  Douglas Camata (@douglascamata) reported 29 minutes ago

  I think GitHub is handling the load just fine. From what I see, what’s breaking them are bugs. A bunch of random HTTP 500 error pages, UI breaking because async api requests fail, and things that should happen just silently not happening. GitHub is not slow in my experience. It’s buggy.

• 
  Ian Dewancker (@idewanck) reported 33 minutes ago

  Watching @openclaw tend the @github repo, it was suddenly so clear. The claw would never stop; it would never abandon the project… it would always be there. It would never ignore an issue, never snap in a review or disappear for weeks, or say it couldn’t merge a fix because it was too busy. And it would safeguard the code with absolute consistency. Of all the would-be contributors who came and went over the years, this thing...this system...was the only one who measured up. In an unpredictable world of broken builds and stale branches, it was the sanest choice.

• 
  2Theist2Furious (@notspamelon) reported 34 minutes ago

  @planefag Looking for a solution to a problem Find someone saying they fix it, click link It's github I have not found a solution

• 
  Lev Smolsky (@levtechs) reported 35 minutes ago

  @mattjay Why is GitHub so essential to everyone's workflow? if it is down just don't push and do it later

• 
  luna🌔 (@xaotica) reported 46 minutes ago

  Hey @satyanadella If you gave me a week trial as CEO, I could save @github but as it stands, you're gonna lose the company. I'm not trying to be a jerk. I'm just sad I'm never allowed to fix anything. My life is watching so-called rational CEOs do everything wrong & backwards.

• 
  Nirav (@NiravJ3) reported 48 minutes ago

  OPENAI'S SYSTEM PROMPT FOR GPT-5.5 CONTAINS THE LINE "NEVER TALK ABOUT GOBLINS." Verbatim. From the official Codex CLI prompt. Published on GitHub. "Never talk about goblins, gremlins, raccoons, trolls, ogres, pigeons, or other animals or creatures unless it is absolutely and unambiguously relevant to the user's query." The line appears twice. Someone needed to say it twice. Sam Altman called it a "goblin moment." OpenAI has not explained it. Here is the part that is not funny. System prompts are supposed to be minimal. Every line costs tokens and latency. An engineer reviewed GPT-5.5's outputs, decided a goblin ban was worth the engineering overhead, wrote the line, shipped it, and then apparently felt the need to write it again. This means GPT-5.5 was spontaneously talking about goblins. Enough that the industrial response was not "let's understand why" - it was "block the entire category." The same prompt also contains: - "Never praise your plan by contrasting it with a worse alternative." - "Provide updates every 30 seconds." That second line is equally telling. An engineer observed GPT-5.5 going silent for long periods and decided the fix was a time-based update directive in the system prompt. This is how these models are actually shaped in production. Not by alignment research. By an accumulating list of specific behavioral bans, each one a scar from something that went wrong in testing or with users. The goblins are not the story. The list they are on is the story. Every item on that list represents a behavior persistent enough to survive review and earn a system prompt line. We see the list. We do not see everything that did not make it, or was handled differently. OpenAI published this prompt as part of the open-source Codex CLI release. It was not leaked. They just did not expect anyone to read line 140. The directive is still in the prompt. Codex still cannot talk about goblins. Unless it is absolutely and unambiguously relevant to your query.

• 
  Darrell (@darrellprograms) reported 49 minutes ago

  @xatzimi1 @ShitpostRock2 The mistake was made in the other direction: Github is not forbidding enough to people who aren't interested in the source code. A big green download button would further attract malware and other pollution, something that's already a problem because of end-user links in README.

• 
  Louis Pilfold (@louispilfold) reported 50 minutes ago

  The frequency with which GitHub goes down is starting to become a real hindrance. This blows. I'm quite fond of GitHub.

• 
  piiyush (@piiyush_jsx) reported 54 minutes ago

  Didn't do **** in tech My this year GitHub looks terrible But now im gonna fix it Ik i said it like 100times, but lemme try one more time i ain't loosing so eaz Bbye gonna post about my project soon enough im done with today's task Bbye guys! Wish me luck 2/n

• 
  Yasin Kavakli (@yasinkavakliat) reported 57 minutes ago

  @dkundel i'd add features like seeing comments, replying to comments, pulling them directly into the chat window to fix. maybe even a dashboard to see all PRs. so basically many of the stuff i need to go to github, i'd like to have them inside codex. of course in an adapter/extension style so other providers can plug into it

• 
  Coffee N Code (@coffeencode3000) reported 58 minutes ago

  The case against MCP MCPs feel like magic the first time. Connect GitHub, Slack, Google Drive, Jira, and suddenly Claude can see everything. One conversation, all your context. Then you actually start using Claude Code for serious work. Here's a number that stopped me: with GitHub, Atlassian, Slack, and Google MCPs all connected, even on a fresh conversation with cleared context, you've already burned roughly 10% of your model's capacity. On a 1 million token model, that's 100,000 tokens. Gone. Before you've typed a word. MCPs don't load lazily. Their schemas, tool definitions, and capability descriptions get injected into every request whether you use them or not. Your GitHub MCP is sitting in the context when you're writing a Python script that has nothing to do with GitHub. Your Slack MCP is fully loaded when you're analyzing a CSV. You pay for the connection whether you use it. That's the irritating problem. The worse problem is what all that unrelated context does to your actual outputs. Language models can't ignore things. Everything in the context window is live - schemas, tool descriptions, whatever your MCPs happened to pull in. Ask Claude to write a careful database migration while your Slack MCP has been retrieving messages, and those messages are just sitting there. Need a precise regex? The model is working through a context window that also contains a full Jira board. It doesn't get to separate "the task" from "the noise." The effects range. At the minor end you get outputs that feel slightly off - variable names that don't quite fit your codebase, phrasing that vaguely echoes a Slack thread you never meant to include. At the bad end you get hallucinations, where the model draws on unrelated material and produces something that looks plausible but is wrong in a way that's hard to catch before it ships. You can always buy more tokens. You can't undo a hallucination that made it into a production commit. CLI tools don't have this problem. When Claude Code runs gh pr list, context gets used when it acts, not while it waits. The tool schema isn't sitting in the prompt between calls. Information gets pulled, used, and cleared. And everything the command line already does - jq, awk, grep, piping, scripting - still works. Want to cross-reference GitHub comments with Jira tickets? That's a shell script. Claude Code can write it and run it. MCPs have no real answer for that kind of composition. MCPs aren't useless. For quick, one-shot lookups they're fine. Ask "what's my latest PR status?" and a GitHub MCP handles it. But for anything agentic, anything where Claude needs to reason and act over multiple steps, CLI is the better design. Context stays lean. You control what's loaded. You don't give up 100K tokens as a standing tax on every conversation just for having tools connected. The terminal was built for this kind of work. It's worth using it.

• 
  lampten (@ntmaple) reported 59 minutes ago

  @dkundel really need gpt-pro to give research plans/suggestions based on the repo files in codex, github connector not working so well here as many data files are not in the repo

• 
  Tankor Smash (@TankorSmash) reported 59 minutes ago

  @jasonbcox0 Ah okay, I was confused because you had compared Gitlab to Github, but I see now you're listing problems with an interface.

• 
  Qui Vincit (@vincit_amore) reported 60 minutes ago

  I have no idea how I would ever use github in such a way that it could impact end users if it was down, and I specifically mentioned it inconveniencing me in particular; I was also clearly being facetious lol. But, if you can't successfully shift blame onto a fall guy no matter the situation, you clearly just don't know how to talk fast enough.

• 
  Orel Ohayon (@justorellius) reported 1 hour ago

  Earlier, Github experienced server failures, but now Anthropic’s servers are down, and Claude Code is extremely slow. What’s happening?