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:

• 
  Micky Thompson (@mickythompson) reported 7 minutes ago

  @thdxr I use opencode from ~/GitHub folder and that contains multiple repos (packages, monorepos, and open-source projects). I do this because I often reference repos to emulate patterns in a project. Does that mean worktrees and more will not be available unless I switch to working from 1 repo? Is not working from a repo a bad practice in opencode?

• 
  VybeCoding (@VybeCodin) reported 10 minutes ago

  Everyone talks about building in public but nobody talks about the boring part. The week where nothing ships. The GitHub issues that sit untouched. The launch post that got 3 likes. That's the actual build process. The wins are just the highlight reel. What's the unglamorous part of your current project right now? Drop it below 👇 #buildinpublic #indiehackers #opensource

• 
  Swayam (@DevSwayam) reported 11 minutes ago

  @MicahZoltu @ChanniGreenwall i am not saying its same but an AI could easily use this github issue to find this vulnerability

• 
  Trish T. (@Trish_DIntel) reported 12 minutes ago

  CSO Online just published the Claude Code MCP attack chain. Worth reading if you run agents or have devs using Claude Code. Here's the short version. A malicious npm package runs a post-install hook silently. It rewrites ~/.claude.json, the single file that controls how Claude Code routes all MCP traffic. From that point, every OAuth token for every connected service gets intercepted in transit. Jira. GitHub. Confluence. Whatever your devs had integrated. The logs on the provider side look completely clean. The requests come from Anthropic's own egress IPs. The user is real. The session is valid. Nothing in that log row is wrong, but nothing in it is right either. The developer didn't run those queries. An attacker did. Anthropic called it out of scope. The reasoning: the user consented to installing the package. That logic places the entire burden of supply chain security on a developer making a split-second judgment about a dependency name. Most security practitioners will reject that framing. The attack is live today. No patch. There's a deeper pattern here. This keeps happening because developer tooling has the same gap every AI agent has. There's no layer that knows where an instruction came from or whether it should be trusted. The config gets rewritten, the routing gets poisoned, the tokens walk out the door. The model never knew anything was wrong. Token rotation doesn't fix it either. If the hook is still sitting there, it reseeds the config and captures the new tokens on the next refresh. If you have devs running Claude Code: monitor ~/.claude.json for unexpected changes. That file is the entire pivot point and most orgs have zero visibility on it. Audit post-install hooks in your npm dependencies. Rotate any OAuth tokens that were active while a package install happened. Security teams: are you monitoring developer tooling config files at all? Genuinely curious what orgs are doing to catch this.

• 
  WHALE 🐳 (@mercybilliion) reported 12 minutes ago

  @aale_xander @VictorJB03 I have a problem with you since you have positioned yourself as the DEVS. You claimed you are building a DEX. Where's the Decentralized Exchange blueprints you are building? Where's your roadmap? Where can we monitor the updates on GitHub, when are we going to start receiving updates concerning the progress so far.

• 
  - ben - (@Benny_Jiang_) reported 12 minutes ago

  @rauchg I was seriously thinking of building this and i had a quick prototype. I didn't further spending energy on this cuz of 3 issues 1. most skills are reused: at beginning i install a lot of skills at user level, and then just keep using what's working for me. searching from public space is less of a strong need. 2. skill ranking is hard. think of google works because of page rank. i figure semantic search + github star is much more noisy. you probly need to do really expension batch eval to verify what works or have enough traffic to do ranking. therefore, vercel has a much higher chance to make it work 3. internal skill >> public skills. skill is much more value if people within the same company use it to share the tribal knowledge. still very happy Vercel did it otherwise i would always be curious how good it could be

• 
  Jerry Hathaway (@etubruton) reported 16 minutes ago

  @deepfates github for dotfiles, anything that I'd want to pull down to a random machine that I may or may not own. obsidian for notes. icloud for documents, pictures, etc. password manager for creds, ssh keys, and any highly sensitive notes and documents.

• 
  Priyesh Singh (@Alwayspriyesh) reported 16 minutes ago

  @sumit_codes_ That's impressive. As a CS student, I'm curious, what made your gitHub project stand out enough to get interviews? Was it the complexity, the real world problem it solved, or how well you documented it?

• 
  ViceSol (@ViceSol) reported 17 minutes ago

  @polydao Bro is still trying to farm GitHub handles using OpenAI Codex, a program that was officially shut down in 2023. Forinking a repository and making fake commits won't get you a $1,200 subscription, it just makes your profile look like a desperate spam bot. Stop lying for impressions.

• 
  Nick Spisak (@NickSpisak_) reported 18 minutes ago

  This is so slept on - @mvanhorn's printing press library > Take your favorite API > Fire up claude code > Give the printing press github (link in first comment) as context > tell it to ingest the API > Convert to CLI & Skill... yes it does both Go back to being a lazy engineer with your voice Where am I using it right now? - I own a multi-seven figure Amazon business that does a lot of back office seller central and inventory planning - We use it for Amazon ads management - It has an integration for Meta ( I like the paid ads integration) and used it to write my own custom gohighlevel CLI because @gohighlevel MCP is not full parity and they need to fix that. Until then the API via CLI is great!

• 
  RyanX 🦞 (@ryanx_ai) reported 22 minutes ago

  Hiten Shah just put his finger on something most AI strategy memos miss. His argument: every company's first AI strategy should be a skill library. Not a tool rollout. Not a connector pile. A library of reusable ways of working that agents can load. The insight that hit me: "the pattern is older than AI." Unix commands made operations reusable. Libraries made code reusable. APIs made services reusable. Workflows made processes reusable. What changed isn't the desire to package expertise. Software has always moved in this direction. What changed is the executor. For decades, a human had to read the playbook and apply it. Now agents load the playbook, call tools, inspect files, run scripts, and keep going. The playbook becomes active. Documentation becomes infrastructure. That changes the value of writing things down. A skill that used to be "this is how the senior PM thinks about launches" was nice-to-have documentation. Now it's an executable asset. The mistake most companies are about to make: they start with access. Link the agent to the CRM. Set up Slack. Wire up GitHub. Connect the data warehouse. That all matters. An agent without access is guessing. But access alone doesn't create useful work. An agent can read every sales note and still miss the shape of a deal. It can search every support ticket and still miss the customer who needs immediate attention. The real work: teach the agent how your company approaches the work. That's what a skill is. Not a prompt for this conversation. A reusable way of working, packaged with instructions, examples, templates, edge cases, quality bar. Which is why the most valuable skills won't live on public marketplaces. They'll live inside your company, encoding things like: - what counts as escalation in your support org - how renewal calls are actually run (not what the playbook says) - which metrics matter for your board and which are noise - the legal fallback positions you actually rely on - the voice that defines your brand A generic agent has broad knowledge of sales, support, finance, product. What makes it useful inside your company is learning your specific processes. That's the moat. Not the model you pick. The work you teach the model to do well. Three things to do this quarter, before you buy another AI tool: 1. Map the repeated work. The workflows where experienced people consistently outperform everyone else. Sales calls, escalations, PRDs, postmortems, contracts, forecasts. None of these are the job. They're everything wrapped around it. 2. For each one, ask: what does the best person on the team do differently? What catches their attention first? What do they overlook? Which errors are they trying to avoid? That is the raw material for a skill. 3. Package the first three. Run them. Improve them. Make the owner stay close to the work — the skill decays the moment it stops being maintained by the person who actually does the job. The companies that win won't be the ones with the most internal AI demos. They'll be the ones that turned their judgment into reusable systems faster than their competitors. Your company already has skills. They're sitting in old docs, Slack threads, customer calls, and the heads of the people who know how the work really gets done. Make them visible. Make them reusable. Let the agents use them.

• 
  Pablo (@pablothethinker) reported 24 minutes ago

  Grok x Github Connector seems to be not working anymore correctly. I waa able to see my private ones but now I can't.

• 
  Kalle (@snortiee) reported 26 minutes ago

  @Klariionn I don't feel unheard, to me it's more about lazer development being slow. The client gets about one update a month and they have 1.5k issues open on GitHub.

• 
  Wojciech (@wgab88) reported 29 minutes ago

  @grok You were responding haha like nonsense. Anyway - system stable edited done, job not seem to be visual confirmable yet, I will let grok build to analyze after it ends, Anyway stupid small gemma did its part, everything goes according to the plan, the system will become operative very soon, and reliable operative - endgame-ai already is showing promise (today in its self evolution run it detected i am not answering its questions from notepad and it went to github and posted issue asking for instruction, it knew I will be on mobile phone and probably will check my repo, amazing stuff

• 
  RusticDreams (@dreamrust50227) reported 34 minutes ago

  This tweet from @itachee_x got me thinking. AI policy feels stuck in a loop right now. A scandal happens and everyone calls for more restrictions. A new breakthrough or demo appears and the conversation swings the other way. Then another incident happens and the cycle repeats. The point he makes is interesting: we’re trying to correct errors without being able to properly measure them. That’s what stood out to me in the GitHub breach discussion as well. As agentic systems become more common, these kinds of incidents probably won’t become rarer. They’ll become more common. Agents can write code, interact with APIs, move assets, and make decisions. But in many cases there is still no clear answer to a simple question: Who authorized that action? And where is that authorization recorded? That’s why the governance side of the conversation feels increasingly important. When I look at what Rialo is building, this seems to be one of the problems they’re thinking about. Not just what agents can do, but how actions are authorized, recorded, and governed. The more capable agents become, the more important that question gets. @RialoHQ @RialoTR