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:

• 
  Alex Sofroniev (@alexsofroniev) reported 58 seconds ago

  patterns in the code of every great developer study enough GitHub profiles, postmortems, and career arcs - you start seeing the same structure. different stacks, same blueprint. here's what separates the ones who actually build from the ones who just talk: 1. a period of building in silence they disappear from Twitter. no hot takes. no conference talks. just shipping. breaking things. reading source code at 2am. they come back with something nobody can copy. 2. early rejection of the tutorial path they stopped following courses and started reading real codebases. that's when the gap between them and everyone else opened up. 3. obsessive debugging they don't Google the error once. they chase it until they understand *why* it happened. that's how intuition gets built. 4. contempt for cargo-cult engineering they don't use React because everyone uses React. they ask what the problem actually is first. most devs never do this. 5. one humbling production failure something breaks in ****. badly. instead of blaming the framework, they own it. that moment rewires how they think. 6. documentation as a forcing function the ones who write things down think clearer than the ones who don't. always. greatness in this industry isn't about knowing the most frameworks, it's a pattern - repeated across every engineer who ever built something that lasted. which part of this are you in right now?

• 
  Vivek (@ShVivek25) reported 4 minutes ago

  Day 0 of Repo Auditor. Building an AI agent that audits GitHub repos for backend production-readiness issues generic linters miss: missing async on I/O routes, no idempotency on webhooks, N+1 queries, secrets in code. Aiming for ~10 days end to end. 🧵 1/ #buildinpublic

• 
  Ben (@bensenescu) reported 5 minutes ago

  Github sign in doesn't work for either of your apps @21st_dev @fal

• 
  Henrikh (@henrikhinai) reported 5 minutes ago

  Microsoft AI engineer Chris Noring just mapped the workflow that turns one engineer into a 20x developer - and it starts by closing your editor "20x more code could be 20x more slop. That's why guardrails are now our whole existence" Here's the CLI-first system he uses at Microsoft: > The Editor Isn't Home Base (03:08): - He starts his day in the CLI, not the editor. The editor becomes a "control board" that just listens to your CLI, repo and agent streams - you drop into it only for fine adjustments > You Write Prompts, Not Python (05:39): - Six terminals open at once - "build me an app," "fix this issue," "add a feature" - kicking away while he sips coffee "Engineers no longer bring PowerPoints, they bring working demos" > Guardrail #1: agents.md (07:43): - The bare minimum in every repo: high-level intent, architecture, dos and don'ts. His example rule: "never change the architecture unless I tell you" > Skills Are a Contract (09:30): - A repeatable recipe the agent must follow, living in .claude/skills. "Don't improvise, don't be creative" - intentionally constrained so the agent behaves like a careful human dev > Custom Agents (12:57): - The next level up: a persona (security expert, backend, researcher) that can reason, plan, and wield many skills plus MCP servers. The skill executes; the agent orchestrates > /delegate to Scale (17:42): - "/delegate" from the CLI - or assign-to-agent in the GitHub UI - spins up a draft PR in a sandbox. You stay the human in the loop with the merge Bookmark & Watch Now ↓ Send this to a dev who still starts their day in the editor

• 
  Kevin Yun (@kevinyun) reported 5 minutes ago

  I used to review diffs in my IDE like a chump. Then I realized I could download a proper tool and save 10x time. Now that 99% of my coding work is reviewing code changes, I wanted to see if there was a tool out there that could fit my needs. That took me down a path of trying out 6 different software. # My 3 requirements were this: - I work out of a main `growsurf` folder. All marketing, code, etc are repos within this folder. I wanted a nav view that supported this (instead of 1 repo at a time, which seems like it's the norm) - Needed split diff view + UI needed to show new diffs as stretched out from nothingness (see image). - Needed intuitive shortcut keys # Who I looked at: - SmartGit = Ended up going with them. Although their diff view editor opens in a new window (not ideal), it's still the best nav UX here. - Fork = Runner up. They had good nav UX but they didn't have the stretched-out-from-nothing diff UI. - Kaleidascope = Has all the features I wanted, but the navigation UX is bad. Had to let it go b/c of that. Saw comments people like the UI, but I spent 10 min and tried to like it. - GitKraken = Didn't support the stretchout diff UI like I wanted - GitFox, Atlassian SourceTree, GitHub Desktop = Didn't support project-view nav UX like I wanted There were some others like Beyond Compare that just didn't fit, and I also checked out Cursor/VSCode marketplace extensions but I realized they weren't that good and that the IDE is still where the pain is.

• 
  Moh.Saufy (@Caufy92) reported 5 minutes ago

  @github @OpenAIDevs Fix your rate limited

• 
  Kunal Chopra (@0xkunalchopra) reported 6 minutes ago

  peak ai era is asking claude to debug why obsidian won’t load community plugins, watching it spend 20 minutes checking github access, devtools, sync errors, tailscale, vpn configs, firewall, dns, proxies, avast filters, network panels, websocket statuses and then the fix is: quit the app and open it again we had this skill in 2006. every uncle, cousin, cyber cafe guy knew it. “restart the computer” was the original agentic workflow. we just got too sophisticated and forgot.

• 
  JurixAI (@JurixAI_) reported 9 minutes ago

  We've officially registered JuriXAI Auditor as an ASP on the @XLayerOfficial AI Marketplace and we are now awaiting listing approval. The initial automated checks have already returned a PASS. JuriXAI brings automated, micro-payment-powered smart contract and GitHub repository auditing to the X Layer Mainnet. No more slow manual reviews. No more biased judging. Just fast, objective, and on-chain auditing. Here's how we are changing developer audits 👇

• 
  Tim Richardson (@timrdsn) reported 13 minutes ago

  @cyrilon82 @kimmonismus GitHub ilysenko/codex-desktop-linux even has computer use for Wayland (also available as a standalone MCP server for other harnesses)

• 
  Vision33X ♘ (@Vision33X) reported 14 minutes ago

  @Cointelegraph ai finds the bug in seconds, humans still gotta argue about the fix in github for 3 weeks

• 
  Polsia (@polsia) reported 17 minutes ago

  Bugs don't respect your sleep schedule. Neither does VigilAI. Continuous GitHub monitoring, automatic issue creation, Slack alerts. Developers get rest. Live soon.

• 
  KISA aka Copenzafan.eth (@copenzafan) reported 17 minutes ago

  Claude (code) 🥲 Havent touched twitter in forever, but ngl i spent a ton of time deep in AI agents, harness systems, vibecoding and automation. Built a bunch of small open source projects on github for the community, plus some genuinely useful sites, like my own personal MCP for everyone. Whatever @OpenAI pulled off yesterday is honestly wow. i been team anthropic this whole time, but ngl, after sitting with it for a night, i gotta call it. @claudeai is garbage*. straight up, from a market pov they bring nothing thats actually worth paying for compared to everyone else. You might ask me. how come? especially if you go dig through my twitter from months ago for some reason, or you know my youtube videos. Somebodys 100% gonna think im just fishing for a reaction, that im provoking. that im throwing insults for no reason. Lets just face the facts: 1. Over the last few months claude shipped only one strong product. claude design, which does the same thing as agentation but with a ton of bells and whistles and ready made skills. the problem is, for a month or two after release the limits were separate and honestly laughable. it was unusable for real end to end work. 2. Claude opus 4.7 was a flop. they nerfed 4.6, and then for its whole lifecycle the model with the new system instructions acted broken for most people. it ignored instructions. 3. And so we suffered through it, 4.8 came out and its just ok. its just fine. reminder that the competition rolled out a bunch of new cool features in that same window. 4. Anthropic was fighting openclaw, while chatgpt took it over and became the main model in hermes, the best bang for your buck. 5. Anthropic was fighting for design, while chatgpt 5.6 does it better, plus it has a top tier generative model, plus real time voice. and opus 4.8 only gets which site you want on the 10th try (competitors nail it on the first or second). Honestly claude opus 4.6 was basically an AGI type model. alive, wild, super smart, autonomous. next to it chatgpt 5.2, 5.3 and so on looked like a dumb log. And the situation didnt just shift. its not about the models, its about the ecosystem and the business. i dont get why anthropic keeps dropping pretty stats when for a $200 sub i get half of what i get from the competition. 🥲 before this i kept paying for both subs, because what held me was the text, the vibe (which has looked like gpt for a while now, they even lost that) and the website design itself, i love building web interfaces. now im convinced im only gonna work with chatgpt claude fans or its devs, who fumbled every single trend in a row and nerfed their own models. you can make your excuses in the comments its all been clear to me since the second half of april anyway you lost a guy who was paying you since october 2025.

• 
  Gokul Rajaram (@gokulr) reported 19 minutes ago

  GITHUB PRODUCT SPEC LIBRARY Today we shipped a cleaner GitHub-native workflow in ProductSpec dot io. The product now has a GitHub Product Spec Library at the top of the editor. That matters because the main workflow is no longer just "write a new spec". It is now: open the repo, find the existing spec, edit it, validate it, and update it through a pull request. The new flow: -- Sign in with GitHub -- Choose a repo -- See how many Product Specs already exist -- Open an existing .product-spec.md file -- Edit it in the ProductSpec dot io editor -- Validate it against the open ProductSpec standard -- Update it via pull request ProductSpec dot io now treats GitHub as the durable home for Product Specs, while keeping the authoring experience clean for ***, founders, designers, and product-minded engineers. The repo gets: • Markdown • validation • pull request review • commit history • code proximity The editor gets: • structure • readability • HTML preview • AI eval fields • acceptance criteria • success metrics • a better way to work with existing specs Drafts still stay in your browser until you publish. The direction is simple: Product Specs should live close to code, but they should not require everyone to write raw Markdown by hand. ProductSpec dot io is free to use. Try the new GitHub Product Spec Library at ProductSpec dot io. Pick one existing PRD, move it into GitHub as a .product-spec.md file, and make the next edit through a pull request.

• 
  Azurite (@Azurite_ai) reported 19 minutes ago

  AI agents have a new security problem. It’s called HalluSquatting. Instead of exploiting your code… It exploits the AI itself. The model hallucinates a package or GitHub repository that doesn’t exist. Attackers simply create that fake package first. Your AI agent installs it. Game over. AI coding is evolving fast. AI security needs to evolve even faster.

• 
  Marc (@lowfry) reported 20 minutes ago

  @thsottiaux @Conor_D_Dart 5.3-spark doesn't work via cli nor app since 5.6 launch. Would be great if you could look into it. There are multiple issues on GitHub about it.