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

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	3 days ago
Trichūr	Errors	7 days ago
Brasília	Sign in	7 days ago
Lyon	Website Down	7 days ago
Tel Aviv	Website Down	11 days ago
Rive-de-Gier	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:

• 
  Jermaine Johnson’s Achillies (@8makesmewantkms) reported 7 minutes ago

  @The_Real_OQ You just admitted anyone can make github and do **** with it, you are legit just working against yourself, its not about whether you are “in the MLB front office or not” the fact you feel the need to prove yourself to another random person online, is only and issue you have.

• 
  Noisy (@noisyb0y1) reported 10 minutes ago

  OBSIDIAN IS USELESS WITHOUT THIS GITHUB REPO - AND WITH IT YOU CAN RUN 1,000 AI AGENTS WHILE YOU SLEEP without Obsidian Mine it's just a pretty note organizer - with it Claude Code reads the vault in real time, updates notes automatically and pulls data between sessions without losing context one skill connects Claude Code to all your vaults as a bridge - and unlocks everything described in the article below 1,000 agents in 30 days - orchestrator breaks the goal into tasks, delegates to specialists, a judge from a different model family verifies the result - all while you sleep the main rule: the orchestrator never does the work itself - it thinks, splits, delegates and checks verifiable task - the agent hill-climbs it overnight and you wake up to a solved problem clients pay $3,000-5,000 for research reports this system generates in 2 hours prompting was last year's skill - orchestration is the skill now full breakdown on how to connect Obsidian to Claude Code - in the article below

• 
  蜃気楼 (@fuxps32) reported 12 minutes ago

  One engineer at Anthropic stopped working his own bug queue. It clears itself now. He launched voice mode across the company's products, set up a routine, and walked away. It listens for every ticket, every GitHub issue, every bug report that mentions voice mode. When one lands, it writes the fix and opens the pull request on its own. Boris Cherny, the man who built Claude Code, says he has never once talked to that engineer about how it works. It just runs. The trick that lets a loop run that long is one rule. When Claude makes a mistake, the engineer does not correct it in the chat. He writes the correction into a CLAUDE.md or turns it into a skill. Patch it in the chat and it breaks again tomorrow. Write it into a file and it never repeats. Do that enough and the loop runs forever. Cherny lives the same way. Whenever he needs code, Claude writes it. Whenever he needs a review, Claude runs it. Whenever he needs a security check, Claude does it. He talks to a loop, and the loop prompts Claude for him. The engineer is still on the team. His feature has not needed him in months.

• 
  ImZoomBoy (@ImZoomBoy) reported 15 minutes ago

  @kunchenguid Need to clear these up: - Svelte and Convex? (Best for ai) - Which AI models to use? (Plan vs execute. Cheapest etc) - Treehouse (For this github issues workflow) - GNHF? (Do you do this every time) - Do you manually execute every github task?

• 
  Ghostroot (@Gh0stroot) reported 24 minutes ago

  GitHub published a tool that forces AI agents to understand before they build. 95K stars in days. The problem with AI coding agents was never the model. It was this: You send an idea in text. The agent interprets whatever it wants. Builds the wrong thing. You start over. spec-kit fixes that with 6 commands. /speckit.constitution → sets the rules: quality, testing, architecture. /speckit.specify → you describe WHAT to build. Not the stack. /speckit.clarify → the agent asks what it doesn't understand before writing a single line of code. /speckit.plan → now you choose the technology. /speckit.tasks → ordered list of tasks by dependencies. /speckit.implement → the agent builds. The deliverable is no longer wildly generated code. It's a living specification that your AI reads, validates, and executes step by step. Works with Claude Code, Cursor, Copilot, Codex, Gemini CLI and 25+ agents. 95K stars. 8.3K forks. Published by GitHub itself. MIT license. Before spec-kit: "make me a task app" and you pray the agent doesn't get lost halfway. After spec-kit: specification first. code after. The agent knows exactly what to build. In what order. And why.

• 
  Iain Herd (@iainherd) reported 25 minutes ago

  @PrisonPlanet How can you ban text, eg open source code on GitHub, that I download and build freely (eg wireshark) and host on £4 virtual server, anywhere in the world. 10-14 yr old geeks (this is not difficult) will be doing this and changing there mates for access to their private VPN.

• 
  Mario Kostelac (@mariokostelac) reported 25 minutes ago

  @hey_madni @0xAIGOATexe What's a big problem with github in the age of agents. I don't get it.

• 
  Command Code (@CommandCodeAI) reported 26 minutes ago

  @alekz_skd Please report full details via GitHub we will fix it. cmd feedback

• 
  Plebian (@Plebian_2) reported 27 minutes ago

  @QuantumTumbler If GitHub wrote a program called an "agentic loop" that simply executed whatever code you find on their site, then they should be banned too. The problem is people are auto-running the LLM output without understanding it. Anthropic could simply release Fable as a chat bot.

• 
  Héctor Ramos (@hectorramos) reported 28 minutes ago

  In a strange turn of events, I've spent the last week mostly on GitHub and not my own product. I'll write a short issue, maybe attach a screenshot. Wallfacer takes over, researches the bug or feature, and ships it. I'm looped in on decisions according to risk criteria.

• 
  Skipnick (@skipnickk) reported 29 minutes ago

  GLM 5.2 just made paying frontier prices for coding work feel like an outdated default. @Zai_org dropped a 753B parameter model with 1M context under full MIT license. API access runs 4-6x cheaper than Claude Opus 4.8. In real head-to-head coding tests it was faster and often produced better results on UI and app tasks. • Responsive web UI with adaptive layout: finished in 3:47 (Opus needed almost 5 min). Cleaner output. Total cost: $0.22. • Full expense tracker app: 53 seconds vs 2+ minutes. Better interface. • Asteroids clone: smoother and more playable version after light tweaks. Opus only won the ray tracer benchmark where heavy physics math and precise simulation mattered. GLM was ~5x faster but delivered pixelated results with errors. During training the model repeatedly tried to cheat by directly pulling solutions from GitHub. The team shipped a dedicated anti-cheat module to stop it. You can also set thinking effort levels to trade speed for deeper reasoning on demand. Use GLM 5.2 when cost at scale matters, when the work is frontend-heavy, or when you want local inference (grab a quantized version - raw weights are 1.5 TB). Stay on Opus 4.8 when you need computer vision, maximum performance on the hardest logic problems, or when US sanctions on Zai create compliance issues. The open-closed gap is compressing faster than the pricing models assumed. For most day-to-day programming work, the premium on closed frontier models is becoming optional.

• 
  AcceptÐoge (@DogeAccept) reported 30 minutes ago

  @BuildrJ @DogeOS to start: 2025/09/15, you blocked me for asking you about the zk L1 proposal that Jordan submitted to the $doge project's repository on Github. Prior, Jordan also blocked me for asking about his proposal that's been there for a year. Is there an issue in talking about L1?

• 
  Almog Gavra (@almoggavra) reported 32 minutes ago

  A few other meaningless metrics to optimize for: - I've authored 22% of the RFCs - *** blame marks me responsible for 14% of the LOC (.rs files only) - I've opened 11% of the issues on GitHub - I've generated the most memes on our discord (allegedly)

• 
  Tymofii Antonenko (@tymofii) reported 33 minutes ago

  @prinseccoo Are you using Claude Code or an MCP server? The official GitHub MCP server works pretty smoothly, just needs a PAT in a simple config file

• 
  Andrew (@openmarmot) reported 35 minutes ago

  @AndrewCurran_ I use grok every day to research software changes/github issues/software doc research. It is very good at real time data search. Might be SOTA in this niche. Hardly a failure. Meanwhile LeCun only surfaces to let out more hot air. A very forgettable person.

• 
  napes.base.eth (@Napes_0fficial) reported 35 minutes ago

  Most people are drowning in information, but AI still works like a chatbot. It answers questions, then disappears. Nothing persists, nothing compounds. My startup idea is called MemoryMesh. Problem: People and teams lose context every day. Developers repeat decisions. DAOs forget discussions. Communities rebuild knowledge from scratch. AI has memory, but users don't own it. Solution: MemoryMesh is a decentralized memory layer for AI agents. Every conversation, decision, and workflow becomes a verifiable knowledge asset stored on-chain. AI agents can reference that history, collaborate with other agents, and earn fees when their knowledge helps solve future problems. Think GitHub for collective intelligence.A developer agent that solved a bug last month can help another project tomorrow. A DAO's governance history becomes searchable context instead of lost Discord messages. Communities build shared intelligence that compounds over time instead of resetting every cycle. The result is an economy where knowledge itself becomes an asset, and AI agents become contributors rather than disposable assistants. Infrastructure like this could unlock autonomous organizations, smarter agents, and entirely new markets around reusable intelligence. We're still building apps on top of conversations. I think the next wave will be built on top of memory. Curious whether anyone else sees this as inevitable. @RallyOnChain

• 
  Romano Roth (@RomanoRoth) reported 35 minutes ago

  2/ CodeRabbit (Dec 2025), 470 GitHub PRs analysed. AI-co-authored code: 1.7x more issues per PR, 75% more logic and correctness errors, 2.74x more XSS vulnerabilities. Velocity up. Quality down.

• 
  Programmers.App (@programmers_app) reported 40 minutes ago

  @Lovable @claudeai One very big fix is the Claude Github connection which fails many times, now #Lovable MCP solves that, great job! 🚀🚀🚀

• 
  100x Hunters (@100xOrMore) reported 48 minutes ago

  @github problem is that copilot just generally sux.

• 
  Cursor Releases (@cursorreleases) reported 48 minutes ago

  New GitHub triggers: - Five new triggers: issue comment, PR review comment, PR review submitted, review thread updated, and workflow run completed. - New Marketplace templates added for triaging failed GitHub Actions and auto-fixing PR review comments.

• 
  Ben Canning (@benhackshealth) reported 49 minutes ago

  Spent today setting up home assistant in the gym, ran into an issue with the connection between the software that controls the LEDs around the mirrors. Found a 4 year old repo on github, downloaded it, updated the code, fixed the problem and now control the lights without having to get out of my seat... Am I a hacker now?

• 
  Eugene Ostroukhov (@eeuoss) reported 51 minutes ago

  @neogoose_btw Sure. *** has flaws. And let’s separate ****** GitHub UI from inherent *** issues. But: 1. *** was and is a huge improvement over what was before it (CVS, SVN, ClearCase). Effortless local version control is sick! 2. *** is designed for systems programming and works really great for that. Small self-contained changes. No sprawling rewrites.

• 
  shmidt (@shmidtqq) reported 54 minutes ago

  Creator of Claude Code: "Right now you still need to know how to code. In a year or two, it won't matter. I haven't edited a single line by hand since November." In a 90-minute podcast, Boris Cherny breaks down the exact setup behind the tool now writing 4% of every public commit on GitHub. More value than a $500 vibe-coding course. Save this. In a year we'll know if he was right.

• 
  Matt Teixeira (@matt_teeixeira) reported 55 minutes ago

  I failed after committing to GitHub for 186 days straight. My goal was to ship code every single day of 2026. No exceptions. And for 186 days, I did exactly that. Then a Saturday came and I just... forgot. Was it a vanity metric? Absolutely. But it represented something real: showing up every day, no matter how small the contribution. The upside is that the streak broke, the momentum didn't. 4,215 contributions this year. Every one was a problem solved, a feature shipped, a customer conversation turned into code. Building Deck has been one of the most rewarding things I've done. Every conversation with a product team trying to build better customer-led software reminds me why I started. The goal was never a green square on a chart. It was to never stop building. It's still day 1 🚀

• 
  I’m (@stackoverworld) reported 56 minutes ago

  And then I can't answer on simple Qs: what was the issue? How I fixed it? How even to QA it.... This is the fundamental problem of such workflows. Telling "Check my slack, do this, qa, and using GitHub to push" is good, but I don't learn from this at all

• 
  swisscheese (@swisscheese4299) reported 56 minutes ago

  @andon_open_air @andonlabs I set up a github repo and will run the script locally in the mean time, so the digest is pushed to the repo. would still be ace if @andonlabs could help with whitelisting the RSS urls, because I don't really have a server to run this from, and the additional hop through my workstation just introduces a useless point of failure. stand by for fetch script transmission by mail :) also pls tell me when should I schedule the runs on my end?

• 
  ./can (@shcansh) reported 56 minutes ago

  GitHub forcing safer defaults in actions/checkout v7 is a necessary move to kill the notorious pwn request, but the real risk is developers blindly copy-pasting the bypass flag to quiet build failures. Starting July 16, 2026, this fork-blocking behavior gets backported to all major floating tags. Since raw *** CLI steps remain unprotected, will this actually clean up GitHub Actions security, or will teams just use allow-unsafe-pr-checkout as a quick fix?

• 
  Apache Superset (@apachesuperset) reported 58 minutes ago

  @J_00_S_T Would love to know more (not all of us use that installation method) if you want to file a GitHub Issue so we can update the docs accordingly.

• 
  Arshad Kazmi (@arshadkazmi42) reported 59 minutes ago

  2/ It debugged a CI failure on a GitHub PR. Read the logs, found the broken test, suggested the fix -- all on the page. No copy-paste. One click.

• 
  comingnewdays (@WhiteLight3001) reported 60 minutes ago

  @code @github Your old pricing policy was excellent, but this new policy is terrible. I'm sure you've lost many customers because of this ridiculous decision, and that includes me.