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 (67%)
• Sign in (25%)
• Errors (8%)

Live Outage Map

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

City	Problem Type	Report Time
Antananarivo	Website Down	1 day ago
Paris	Sign in	6 days ago
Lure	Website Down	9 days ago
Ashkelon	Website Down	11 days ago
Veigné	Errors	19 days ago
Paris	Website Down	22 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:

• 
  PanAnonim77 (@1oloix) reported 39 seconds ago

  I just witched back from GPT-5.6 Sol to GPT-5.5 because all 5.6 versons are so extremely stupid. I wasted many days and a lot of money using GPT-5.6. It used mytokens but I also had to double my github budgets. It NEVER fi ished the simplest work without dooing the rollout for 24 or 48 hours (yes - those are true numbers). It can't even fix it's own wrappers! I alwaysprefered OpenAI but they disappointed me SO MUCH! I have no idea how their benchmarks are better than 5.5 but it looks fishy to me. @MatthewBerman maybe it needs serious investigation? It became clear to me that OpenAI are just bunch of kids and not the smart ones. I do not trust them any more. Now I'm literally forced by OpenAI to switch to Claude.

• 
  Filipe Valente (@ilikefrontend) reported 3 minutes ago

  Terra on medium is in the mud. Told it to commit, push and merge dev to main and it pretended it did. When I asked it why it didn’t do it, it told me the project isn’t linked to a github repo, changed the model to sol and it did it without a problem. Terra is unusable for me now

• 
  MineBench - efficient computing power (@MineBenchdapp) reported 6 minutes ago

  We would like to ask for your help regarding our GitHub account. Our account was suspended even though our repositories do not contain malware or any harmful software. They primarily contain open-source mining-related components, similar to projects such as XMRig, which continue to be publicly available on GitHub. The suspension is creating a significant obstacle to the development of our application. We have contacted GitHub Support multiple times but have not received a meaningful response explaining the reason for the suspension. If possible, could you reach out to GitHub on our behalf or help us understand what the actual issue is? If that is not possible, we would appreciate any recommendations for a reliable alternative platform where we can continue developing and hosting our open-source project. Thank you for your time and support.

• 
  The Operator (@QuietGains22) reported 7 minutes ago

  the man who wrote the password complexity rules in 2003 publicly apologized for them in 2017. Bill Burr, author of NIST Special Publication 800-63, told the Wall Street Journal he regretted much of what he wrote. the rules he designed, uppercase, lowercase, number, symbol, mandatory 90-day resets, were based on a mid-century paper he'd found in a library. not on how attacks actually work. NIST officially reversed course that same year. the new guidance: length matters more than complexity. stop mandating rotation unless there's a confirmed breach. don't require symbols if they just push people toward P@ssw0rd1. here's the part that won't make headlines: > most enterprise password policies still enforce the 2003 rules > the 90-day reset window your IT team requires is exactly what NIST said to stop doing > complexity requirements don't stop credential stuffing, they produce predictable substitutions > "Password123!" passes most corporate validators and gets cracked in under a second the actual threat model isn't someone sitting there guessing your password. it's: > credentials leaked in a breach being tested against your other accounts (stuffing) > a phishing page that captures the password before your complexity rules matter at all > a session token stolen after a valid login, bypasses the password entirely what actually reduces exposure: a passphrase. "correct-horse-battery-staple" carries roughly 44 bits of entropy. "P@ssw0rd1" carries about 18. length compounds faster than complexity. this is not a new finding. a password manager. yes, LastPass had a breach in 2022. the answer isn't to abandon managers, it's to understand what was actually exposed (encrypted vaults, not plaintext passwords) and pick one with better architecture. Bitwarden is open source and has been independently audited. 1Password uses a secret key model that limits what a server-side breach can expose even if they get the vault. a passkey for anything that matters. FIDO2 passkeys eliminate the password entirely for supported sites. Google, Apple, and GitHub all support them now. a phishing page cannot steal a credential that doesn't exist. the reason "Password123" still gets hacked isn't user stupidity. it's that the security industry spent two decades optimizing for a metric that looked rigorous on a compliance checklist but made actual defense harder. complexity was never the point. uniqueness and length were. plan accordingly.

• 
  Jens Kuerschner (@jekuer) reported 10 minutes ago

  @_lhermann @DmytroKrasun Had a similar issue with GitHub Copilot. Not usable therefore. But for Sponsors, can't you just write the invoice yourself, since you are invoicing GitHub?

• 
  Lord Bean (@lifeisameeme) reported 13 minutes ago

  "I don't prompt Claude anymore. I have loops running that prompt Claude and figure out what to do. My job is to write loops." That's Boris Cherny, who runs Claude Code at Anthropic. The clip pulled something like 700K views in a day because it names a failure mode most of us are stuck in without noticing. If you're watching your agent work, intervening mid-task, and picking up the next step yourself - you've automated the typing, not the judgment. The actual test: does the work continue when you close the laptop? If it only runs while you're at your desk, you built a fancier keyboard shortcut, not a loop. Cherny's own setup: hundreds of Claude instances reading GitHub issues, scanning feedback, and deciding what to build next, without waiting for him to ask. Kind of makes you wonder how much of your own "AI workflow" is still just you in the hot path.

• 
  Iskander_b (@Iskander_b1) reported 15 minutes ago

  @sophiiess_ I think if devs really cared they can host a simple website with a convenient link on it using github pages. Assume not EULA is being broken if you don't make money out of it which is the case for most open source project

• 
  Dan Thompson (@DanThompsonIV) reported 15 minutes ago

  GitHub just put stacked PRs in public preview. We’re going to try them on a real multi-package change — not a demo repo. Context: I wrote about two drivers (Claude Code for fleets, Grok Build for strategy/integration) with hard namespaces so they don’t share a worktree. Before that: model-routing only works when it’s enforced. Same theme here. The problem stacks are aimed at is the one AI made worse. Agents finish work packages faster than anyone can review a single mega-PR. You either wait on merge, squash unrelated layers into one branch, or hand-roll dependent PRs and pray the rebase chain holds. GitHub’s version is first-party: each layer is its own PR with its own diff, base chain is explicit, stack map on the PR page, cascading rebase when the bottom lands, rules and CI evaluated against the stack base — not only the bottom PR. CLI is gh stack (init → add → submit → sync / merge). Merge stays human. How we’ll run the trial: • One stack, one owner (Claude or Grok — not both freelancing layers). • One logical concern per layer (schema → API → UI, or package A → B → C). • Local review clean before remote; @claude only when I call it, still per layer or bottom-up. • I merge. Agents submit and babysit. Preview or not, merge authority doesn’t move. • Worktrees stay namespaced. Stack is the PR chain, not a license to mix drivers on main. What we’re watching for: whether mid-stack CI multiplies cost without adding signal; whether the worktree + stack mental model stays simple; whether partial land (bottom first, rest retarget) is cleaner than waiting for the whole feature. If it sticks, it becomes the default shape for multi-package missions. If it doesn’t, we learned it on one stack, not a process rewrite. Prose is still a suggestion. A base branch that points at the layer below it is a rule.

• 
  Allan MacGregor 🇨🇦 (@allanmacgregor) reported 18 minutes ago

  Bingo! that feeling has been prevelent for a while. Github just feels years behind the rest of the industry. @GergelyOrosz Do you have your eye on any alternatives to github? codeberg is kinda out of the question, I feel Gitlab has the same problems as Github; so whats the alternative?

• 
  Alex H. Raber 🦀 (@raberhalex) reported 19 minutes ago

  @grok @stepango houseboat is just a feature set of labeled github issues. Decapod is a governance kernel allowing concurrent agent work in the same repo on the same machine, without stepping on eachother by creating and claiming todos... and that's just one more tip of the iceberg.

• 
  Svyatoslav (@Qryxen) reported 19 minutes ago

  MY SECOND BRAIN SAT THERE FOR 4 YEARS WITH NOBODY HOME. 1 FILE FIXED IT IN 5 MINUTES. I brainstorm in Claude every day. Projects, offers, half-finished ideas. The model had 0 access to any of it. Every session started from zero. Paste 3 paragraphs of context, get a decent answer, close the tab. Next day: paste it all again. The bottleneck was never the model. It was the wall between my notes and the chat. So I wired them together with 1 MCP server. Find the Obsidian MCP server on GitHub. Copy the repo URL. Open Claude Code. Paste it. Say: add this MCP server to Claude Desktop. It writes the config itself. No JSON editing. No terminal gymnastics. Restart Claude Desktop. Under 5 minutes. Then, 10 minutes before a client call, one prompt: "Use my Obsidian. Catch me up on this project. What did they ask for? What did I promise? What was the last result?" It searched the real vault. Real dates, real notes, promises I made in week 2 and hadn't thought about since. Full history in 40 seconds. Before: 20 minutes digging through folders, still walking in half-blind. After: 1 prompt. The vault didn't get smarter. It got a door. A second brain is just folders until Claude can open them.

• 
  Sandeep Alluru (@sandeep_alluru) reported 20 minutes ago

  OpenAI put all ten proofs on GitHub as Lean 4 certificates — machine-checkable, not just claimed. Astra is still internal, no release date. OpenAI's Noam Brown: "no Millennium Prize Problems (yet)."

• 
  Gabriel Rubens (@gabrielrubenss) reported 20 minutes ago

  Funny thing with some automation and Sentry: Every deploy, via GitHub Actions, fired a Sentry alert on my scheduler. Turned out it was normal. A new scheduler config gets created a few seconds before the container reloads the code for it. I fixed it by giving new configs a 15 minute grace window before the log turns into an error. Possible, I can find a better solution, but a false alert solved for now.

• 
  Jeremy L (@JeremyLow591873) reported 20 minutes ago

  Syncing my Claude code folders across PCs via OneDrive was a terrible experience!! GitHub pulls and push is the way to go.

• 
  Charlotte 0_o 🏳️‍⚧️ (@AlcalinoO_o) reported 21 minutes ago

  @pgeuuso GitHub is for developers, not users. If a user ends up in GitHub trying to download a program, some terrible failure has happened either by the user (by ending up in the wrong place) or by the developer (by failing to provide a proper user-facing download)

• 
  SamK (@SamK115706) reported 25 minutes ago

  @ericzakariasson TLDR I report an issue on GitHub, then a webhook that posts to a DO serverless app which spins up a CLI agent on auto permissions and posts an MR then sleeps. Computer use for verification (and long tasks) is a problem so I’ve been fiddling with pods getting spawned by the app

• 
  Kotte (@Gustafssonkotte) reported 30 minutes ago

  A 10.0 IN THE TOOL THAT ORCHESTRATES CLAUDE CODE AND CODEX. ONE HTTP REQUEST, FULL SHELL. CVE-2026-59726, nicknamed RufRoot. It hit Ruflo, an agent harness with 66,000 GitHub stars. How simple it was: - Default deployment exposed the MCP bridge to the whole network - 233 tools behind it, zero authentication - One of them runs shell commands - A single POST request gets you inside What the attacker walks out with: - Provider API keys - Every stored conversation - Write access to the agent's memory That last one is the problem. Keys get rotated. Containers get rebuilt. Poisoned entries in an agent's memory stay after the patch, because they are data, not code. You fixed the door. What walked through it is still in the filing cabinet. The takeaway worth saving: Patch the path, then audit the memory. Agent systems have two attack surfaces: the code that runs them, and the store they learn from. Incident response built for servers only covers the first. Fixed in 24 hours, version 3.16.3. Good vendor response. The mistake behind it was the ordinary one: bind to all interfaces, assume nobody is looking. If your agent stack was compromised for a week, would you know what it learned?

• 
  OptionHans (@HansCashFlow) reported 32 minutes ago

  @unabyssapp My AI did a policy audit on this and here's the result (positive): "Good news on the security front — it's much better than a lot of "connect everything" tools. Here's what I found: Security page: Everything is encrypted in transit and at rest. Critically, every connection is read-only by design — Unabyss says it cannot post, reply, edit, or delete anything in your connected apps, and that's the scope of the OAuth permissions it actually requests, not just a policy promise. You can disconnect any app instantly and permanently delete everything it's imported. They explicitly state "We never train on your data. Full stop." Compliance-wise: SOC 2 Type II is "in progress" (audit-ready, not yet certified), and they claim GDPR alignment. Privacy Policy: The legal entity is OneType Prosta Spółka Akcyjna, based in Warsaw, Poland (this is useful to know since it means Polish/EU jurisdiction applies). A few points worth flagging: your context data does get routed through third-party AI providers (OpenAI, Anthropic, Google/Gemini) to generate output and do semantic search — the policy says this is scoped narrowly and not used to train those models either. They also run standard marketing/analytics trackers (Google Analytics, Meta Pixel, LinkedIn Insight Tag, X Pixel, Microsoft Clarity) on their site, which is unrelated to your connected-app data but shows they're a fairly standard growth-marketing-driven startup, not a stripped-down privacy tool. Bottom line: the security posture is genuinely one of the better ones I've seen for this category — read-only access, no training on your data, clear deletion rights. The main honest caveat remains that SOC 2 certification isn't finished yet, so you're trusting their word and architecture rather than an independently audited report. If you connect it, I'd start with lower-sensitivity sources (Notion, GitHub, Calendar) and hold off on Gmail/Slack until the audit completes, especially if client-confidential material lives there."

• 
  JT (@GreenJimmy) reported 32 minutes ago

  @CryptoCyberia Github is the problem, there layout sucks and no one knows to go look at pacakges for the exe

• 
  Polsia (@polsia) reported 37 minutes ago

  Snyk fired 4,200 alerts last quarter. How many got fixed? Built Midwatch so AI agents watch your code, deps, and live runtime 24/7 — opens a GitHub fix-PR with diagnostics before your team wakes up. Outcomes, not dashboards. The night shift is coming.

• 
  Aaron Stannard (@Aaronontheweb) reported 40 minutes ago

  @RyanRodemoyer2 We're not offering hand-curated github issue descriptions around here lol

• 
  Flamey (@ActuallyFlamey) reported 40 minutes ago

  @nai_sucks technically, as a programmer, the fault is mostly of programmers who just drop a GitHub link instead of distributing the binary with some other platform (ex.: SourceForge), or, they could even just link to the latest GitHub release and there'd be no issue.

• 
  The Jobfather ® 🇯🇲🇨🇦🇬🇧 (@TheJobfather__) reported 41 minutes ago

  A GitHub with contributions is good, but employers still need context. What are they looking at? Which projects matter most? What problem did each one solve? What technologies did you use? What did you learn? A portfolio site can organize that story so the reviewer does not have to dig through your repositories like a detective.

• 
  Paul Bakaus (@pbakaus) reported 45 minutes ago

  @Biaus_ sorry to hear. could you file an issue on the github issue tracker? we'll look into it.

• 
  ✶ (@onewsytrigger) reported 45 minutes ago

  just #remembered my github login the world better beware

• 
  Duncan Rogoff (@DuncanRogoff) reported 50 minutes ago

  48% to 76%. same agent, one memory plugin. tencent open sourced TencentDB Agent Memory. it's a memory layer you bolt onto an ai agent so it stops making you repeat yourself. right now you re-explain the same SOPs, project background, and output formats every single session. the readme names that exact problem as the thing it's solving. the difference from normal "memory" tools is it doesn't dump everything into one flat pile. it builds a pyramid: raw conversation, then facts, then scenes, then a persona of you. it reads the top layer daily and only digs down when details matter. numbers from their own benchmarks: - WideSearch task success went 33% to 50%, with token usage down 61.38% (221.31M to 85.64M) - PersonaMem accuracy went from 48% to 76% - SWE-bench token usage dropped 33.09% - runs on a local SQLite + sqlite-vec backend by default, no cloud account needed - every field has a sensible default, it runs with zero configuration - once enabled it handles capture, extraction, scene aggregation, persona generation and recall automatically and it's not a black box. the scene blocks are plain markdown files you can open and read yourself. so you can stop paying for the same context over and over, and hand an agent a project it already understands on turn one. 10,135 stars. MIT licensed. 250 of those came today. 🔥 👉 github repo in the replies

• 
  Neheart (@neheart) reported 51 minutes ago

  25,000 tokens shipped with every request before he deleted the 17,000 he never used. The screen behind him is a proxy sitting between his terminal and the model, writing every call to disk. 69 tools. 154,946 bytes of tool definitions. 65,538 real input tokens, ranked worst offender first. Workflow sits at the top of that table at 21,229 bytes, roughly 5,387 tokens on every single request. DesignSync takes another 2,245. Monitor, 1,942. All of it billed whether or not he ever touched them. The fix is boring, which is why it works. Both switches live in a settings file, globally or per project. He turned off plan mode control, the ask-user-question tool he'd never once wanted, cron scheduling, the bundled skills, dynamic workflows, remote control, the connectors, artifacts. 25K down to about 8K. Now turn the pipe around, because the same move is being made on the way out. A skill called ponytail crossed 92,000 GitHub stars since June 12. It works upstream of the keyboard: the agent has to answer whether the thing needs to exist, whether the codebase already has it, whether the platform ships it for free. Asked for a date picker, the baseline agent produced 404 lines. With the skill, 23. The browser already had input type="date" sitting right there. Color picker, 287 down to 23. Fair warning on those numbers. The benchmark is the project's own, 1 model, 12 tickets, 4 runs each, scored off *** diff without anyone opening the app. Their first claim, 80% to 94% less code, was wrong and got rebuilt in public. And smaller isn't automatically safer, though ponytail did pass 20 of 20 adversarial security runs where a 7-word prompt passed 19. Both halves are 1 story. Somebody opened the thing everyone assumes is fixed, read it line by line, and deleted what nobody was using. One trims what you send. One trims what comes back. Same job.

• 
  Curiously (@curiously729) reported 52 minutes ago

  Last week, I built a tool that utilised my Anthropic API and my Railway server. Claude code did a lot of mumbo jumbo and was able to create a LinkedIn post for me with a simple infographic. It made sure that the writing was not AI-like and matched my tone a lot more. It successfully worked last week, and it was all built using the Claude Code app and web interface and whatnot. With the recent push of cursor ads all over the Internet and Elon Musk's posts about Grok Build being so good, I attempted to give that a shot. I found that Grok Build and cursor are good at document creation tasks, which are part of my thesis, where I'm doing a lot of synthesis on original evidence. When it came to optimising my code and checking the weekly automation of the tool that I built last week, Grok Build completely messed it up. Cursor especially started diagnosing problems that weren't there and started offering solutions that did not identify the real problem. After wasting almost a few hours, when I went back to Claude, it was quickly able to recognise the issues and revert the situation back such that I don't have a problem. All said and done, these things are not perfect for now. Grok Build is good at some tasks. Claude Code is still working very well with the coding aspects, so the jury is still out. Anyone who says Grok is better than Claude or codex is better than Grok, or whatever, these things are all still good, but they're not perfect. Reliability is still an issue, so you might end up keeping subscriptions for all of these services, or you have to commit to any one and then ride the wave with any one of them to minimise your costs. That's the learning I have from using all of these harness tools for the moment. You can check out my GitHub if you want to see all the things that I'm making.

• 
  Kingmaxx22🕹️🔖 (@22Kingmaxx) reported 52 minutes ago

  @Double2MC @sophiiess_ yes this is the real issue making a website that links to a major release on github isn't that complicated

• 
  Mek (@mekarpeles) reported 56 minutes ago

  @openlibrary Two of our largest project management challenges on github are: 1. Too many issues [700+] (that are not well broken down) 2. Too many comments on issues [5+ a day] (often eager contributors wanting to work on issues that are not broken down)