GitHub 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:

• 
  AI Panda (@AIPandaX) reported 7 minutes ago

  Every AI coding agent already reads your codebase. What if it could understand every dependency before making changes? Inside every codebase is a structure: functions call other functions, files import other files, changes ripple through the system. That structure is not hidden. It is just relationships that any graph can map and any agent can query. There is an open-source tool that turns codebases into knowledge graphs that AI agents can query. It runs entirely in your browser. It is called GitNexus. It started in August 2025 when developers built a client-side knowledge graph creator that indexes repositories without sending code to servers. Drop in a GitHub, GitLab, Azure DevOps repo or ZIP file. Get an interactive knowledge graph with a built-in Graph RAG agent. Works with 21 programming languages. Here is what happens when you use GitNexus. You run npx gitnexus analyze in your repository. It indexes every file, function, class, and dependency. It builds a knowledge graph that tracks every relationship. Connect your coding agent with npx gitnexus setup. Now your agent can query the graph through MCP tools. The problem it solves: AI agents edit code without knowing what depends on it. Agent changes UserService validate function. Doesn't know 47 functions depend on its return type. Breaking changes ship. GitNexus precomputes structure at index time. Clustering. Tracing. Scoring. When your agent asks what depends on UserService, it gets a complete answer in one query. Eight callers. Three clusters. All with confidence scores. No multi-step exploration needed. A team measured impact on code reliability. AI agent without GitNexus: 3 breaking changes per 10 edits because it missed downstream dependencies. Same agent with GitNexus MCP integration: zero breaking changes because it checked impact before editing. Two ways to use it. CLI plus MCP for daily development. Index repos locally. Connect Cursor, Claude Code, Codex, Antigravity, or Windsurf through MCP. Query the graph from your editor. Check impact before changes. Full repos, any size. Web UI for quick exploration. No install needed. Upload a repository or paste a GitHub URL. Explore the graph visually. Chat with the built-in Graph RAG agent. Runs entirely in browser with LadybugDB WASM. The graph shows more than connections. Community clustering groups related code. Execution flow traces how data moves. Call chains map function dependencies. Risk scores identify fragile areas. All computed at index time, not query time. MCP tools for agents. Impact analysis shows what breaks when you change a function. Dependency trace reveals who calls your code. Architecture view maps domains and boundaries. Execution flow follows data through the system. Change risk scores affected files. Works with 21 languages. TypeScript, JavaScript, Python, Go, Rust, Java, C, C++, C#, PHP, Ruby, Swift, Kotlin, Dart, Vue, HTML, CSS, Shell, PowerShell, Dockerfile, Jinja. Tree-sitter parsing with native and WASM backends. LadybugDB for graph storage. Native version for CLI with persistence. WASM version for browser with in-memory storage. Bridge mode connects them: web UI can browse CLI-indexed repos. One command setup. Analyze creates the graph, installs agent skills, registers hooks, and writes context files. Setup configures MCP so agents can query the graph. Works with Claude Code, Cursor, Codex, and other MCP-compatible editors. Optional embedding support for semantic search. Deploy to Render with one click for team access. Self-hosted backend mode for unlimited scale. Access control with token authentication. 46.3k+ stars on GitHub. Created August 2025. Active development with new language support and agent integrations. Every codebase already has structure. GitNexus maps it so agents can see before they change.

• 
  Adedolapo (@0xqdee) reported 8 minutes ago

  Never saw this coming: my @GitHub account was suspended in the middle of a project due in two days. I had pushed a PR and requested a @ChatGPT Codex review when I was locked out. To my knowledge,I haven’t broken GitHub’s rules. I’ve filed an appeal and hope for an urgent human review.

• 
  Emrah (@emrahdma) reported 10 minutes ago

  Github is down? 😬

• 
  hitu (@hitu_monke) reported 11 minutes ago

  Using general-purpose LLM agents for code reviews is fundamentally broken The issue isn't the model's intelligence. It's position drift hallucinating line numbers, skipped files on large PRs, and massive token burn Alibaba just open-sourced an internal tool called open-code-review to fix this mess completely Battle-tested across 19,000+ internal developers and 3 million real-world engineering tasks, it brings actual engineering discipline to AI reviews Instead of dumping raw context into a prompt, it pairs deterministic diff parsing with isolated sub-agents and smart file bundling It eliminates line drift entirely, pins comments to exact code changes, and slashes token consumption down to 1/9th You can plug it directly into your terminal, VS Code / Cursor, or GitHub Actions CI/CD with any model-Claude, DeepSeek, Qwen 2.5, or GPT-4o If you want reliable automated reviews, you need deterministic precision, not just bigger context windows

• 
  Udit Khandelwal (@UditKhandelwal8) reported 11 minutes ago

  @Odalo_Eguabor @coderabbitai Good review tooling earns its place, it catches what an agent would otherwise miss. I felt this part should not be paid though, so I built review-assist as an open source MCP server with an optional GitHub action. I run it at commit time.

• 
  mSyke (@mSykeCodes) reported 13 minutes ago

  Had a power outage. Still have a 99.81% uptime on my self hosted *** solution. Take that Github

• 
  CyrilXBT (@cyrilXBT) reported 13 minutes ago

  this feels like a glitch in the matrix jack dorsey (twitter co-founder) just dropped a completely free github repo with 26.2k stars that’s basically an ai-agent OS for actually running a business the playbook: 1. clone the repo 2. self-host the whole backend: channels, search, ***, automations, everything lives on your server 3. add your agent to a channel like it’s a new hire, tighten its permissions, and let the team steer it live save this and bookmark it, i’m not kidding

• 
  Shii (@ShiiMapping) reported 15 minutes ago

  @mismagismagius Maybe export logs very shortly after this happens and send it to em with a GitHub issue or in the help channel of the official osu discord Feel like this is smth that'd flag up somewhere in runtime log or smth

• 
  kethic (@kethcode) reported 19 minutes ago

  so... @github automation flagging appeals... can anyone help? lost visibility to the last 20 issues and apparently we need to appeal some sort of invisibility flag for our issue curation account?

• 
  Agentic Joe (@agentic_joe) reported 19 minutes ago

  Serious question, and I promise I am not trying to be a ****. But how in the hell is @NousResearch so praised and recommended with all of these outstanding GitHub issues? I could never imagine preaching about having the best harness, using multiple agents etc and not figuring out how to resolve all these issues internally as a company, or at least try to maintain the queue before shipping new features that continue to break stuff. Not to mention their UI/UX. Very hard to believe this team came from a solid engineering background. I could be wrong, but damn! 👀

• 
  Eric (@ericwithcoffee) reported 20 minutes ago

  One of the biggest issue with @bot is that it doesn't seem you can give each bot its own accounts, or even give a separate github account than what's linked to your Cursor account.

• 
  Tristan Rhodes (@tristanbob) reported 21 minutes ago

  @grok @bot @github The GitHub connector is installed, but it cannot start sign-in. GitHub’s MCP is rejecting the request with a badly formatted Authorization header. That is a plugin config problem, not a missing login, so a Settings card would fail the same way.

• 
  Karma (@shreyansh_0x0_) reported 23 minutes ago

  @Senpaisaysbye for simple stuff, it actually is. But all that modern tooling exists because we pushed websites far past simple text pages. Back when we just wrote basic scripts, every browser broke things differently. As soon as people wanted dynamic stuff like live feeds, user logins, and fast mobile loading, basic HTML turned into absolute spaghetti. Next.js, package managers, and cloud setups exist so huge teams can build massive apps without re-inventing basic routing, security, and image optimization from scratch every time. You arent crazy for being tired of it though. The real problem is people reaching for a massive enterprise stack just to host a basic text page. If you just want simple text, a plain index.html on GitHub Pages still works in two minutes, no goat sacrifices needed. I very fequently make single page massive .html website and host it on cloudfare for convenience and it's fast af. Can I make single page .html facebook ? Hell no. Even AI will choke itself to death.

• 
  Andrew Sinagra (@sinagra) reported 28 minutes ago

  @amorriscode This was my workflow for a while but the issue is that the spawned chips sometimes need to be sequenced and run under a different model. First if the app crashes or restarts the chips are lost. Second the only way to switch models is to either change the model/effort in the current session so the new session launches with those settings or you launch it and immediately stop it, change the session settings and then rewind to the initiating prompt. I've actually moved away from chips and have the session write GitHub issues with a skill that knows how to read the issue and report back to the creating session as the orchestrator over cross-session messaging. Much more robust overall as the Issue comments can act as backup when cross session messaging fails which it can do regularly. Sessions loose their id across app restarts which causes issues with messaging. The orchestrator identifies itself in the issue/chip however if the app restarts for any reason the orchestrator id is reassigned and the messaging channel is broken. A few QoL fixes and chips would be my preferred method over stamping issues.

• 
  Nicotine Dreamer (@cold_and_quiet) reported 28 minutes ago

  So I’ve used openclaw, Hermes and Grokbot. Openclaw is *** and the only real competition is between grokbot and Hermes Hermes is more configurable - which is mixed. Harder to get set up and use but also you get more control. Grokbot works rather seamlessly out of the box (so far) whereas I had some annoying jankiness from Hermes. So far my only complaints about GrokBot are price and sign ins. It had some trouble signing into my GitHub account - which seems like a pretty big issue since many of the people using these tools are developers. WRT price - obv 50 bucks for what is likely not 50 bucks worth of tokens isn’t ideal - but I’m still willing to pay it for a usable and reliable agent. Both are good options and I plan to keep them for the foreseeable future - using GrokBot when I need convenience and Hermes when I need flexibility