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:

• 
  MidnightMess (@mdnghtmss) reported 5 minutes ago

  🚨IS $MSFT LOOSING THE AI RACE? Three years ago Satya Nadella looked like a superhero for betting big on OpenAI. Now Microsoft’s stock is down over 24%, Copilot is trailing ChatGPT and Claude, and the company is spending a record $190 billion on AI infrastructure while still running short on capacity. They’re prioritizing their own AI products over Azure customers and shopping for compute from Amazon and Google. Meanwhile Microsoft 365, GitHub, and Azure,the businesses that actually made Microsof, are all under real pressure from AI-native tools. Inside the company the culture is getting harder, the org is flattening, and people are starting to wonder if the AI north star is turning into a noose. In my opinion @Microsoft is under heavy pressure and isn't a generational buy right now as many here on X are claiming as all core business are struggling. Nadella’s legacy is really on the line. - Dave

• 
  belevy (@ibelevy) reported 7 minutes ago

  The spec was accurate on kickoff day, then scope changed in standups, tickets, and reviews—while the doc stayed put. That isn’t a discipline problem, it’s a location problem. Write like a doc, publish to your GitHub source of truth without thinking about markdown, pull requests, or rebasing branches. That’s specgit.

• 
  Kaspire (@kaspirewallet) reported 9 minutes ago

  Welcome to Kaspire ⚡ The Kaspa wallet that makes no compromises. Designed from the ground up for security and usability, Kaspire gives you complete control over your assets while supporting everything the Kaspa ecosystem has to offer. Kaspire is the first mobile Kaspa wallet to support all L1 assets, including KCC20, encrypted WalletConnect v2 for mobile and desktop which leading crypto wallets like MetaMask use, BIP39 passphrases, covenant vault support, and Argon2id-encrypted backups for industry-leading protection of your wallet data. With the encrypted WalletConnect v2 we also fix Kaspa's biggest flaw when it comes to wallets: most people use their phone today, not their PC. With Kaspire it's finally possible to do everything from your phone. Kaspire is also the first Kaspa wallet with covenant support for KCC20 and vaults, enabling next-generation smart asset functionality. The entire project is open source because in crypto, trust should always be earned through verification, not promises. Built by trusted developers in the Kaspa space under the HUB21 brand. GitHub und public wallet release open this week.

• 
  Anjula Dwivedi (@HeyAnjula) reported 11 minutes ago

  Another WTF moment. A developer just open-sourced a coding agent harness that boots 245x faster than Claude Code. It's called jcode. You launch it and the first frame renders in 14 milliseconds. Claude Code takes 3,436. One active session uses 27.8 MB of RAM. Claude Code uses 386.6. Run ten sessions in parallel and jcode holds at 117 MB while OpenCode swells to 3.2 GB. Each agent has a semantic memory graph instead of a scratchpad. Every turn gets embedded as a vector. The graph is queried on every turn for related memories, and a sideagent verifies the hits before injecting them into context. Consolidation runs in the background to check for stale or conflicting facts. No manual /remember calls. No token burn on lookup tools. The provider list is 30+ deep. Claude, ChatGPT, Gemini, GitHub Copilot, Azure, OpenRouter, DeepSeek, Groq, Mistral, Perplexity, Fireworks, Ollama, LM Studio, and any OpenAI-compatible endpoint you point it at. Ran out of tokens on your first ChatGPT Pro sub? /account swaps to the second. Then there's Swarm. Spawn two agents in the same repo and the server manages them. When agent A edits a file agent B has been reading, agent B gets pinged and can check the diff. Agents can DM each other, broadcast to the room, or spawn their own worker teams for parallel tasks. Groups, channels, and completion statuses are handled automatically. The UI has live side panels that render mermaid diagrams inline. To make it fast, the author wrote a Rust mermaid renderer 1800x faster than the JavaScript one, then wrote a custom terminal called Handterm because no existing terminal could do smooth partial-line scrolling. Self-dev mode is where it gets wild. Tell your agent to enter self-dev and it starts editing jcode's own source code, rebuilds the binary, reloads it live, and keeps working across your existing sessions. You can also resume broken sessions from Claude Code, Codex, OpenCode, or pi directly inside jcode. Anthropic's cache goes cold at the 5-minute mark and you're staring down a big cache miss on your next turn? The UI warns you before you spend the tokens. Written in Rust. MIT licensed. Runs on macOS, Windows, Linux, and Termux. Sitting at 11.2k stars with a native iOS app coming. GitHub Repo on the comment below 👇🏻

• 
  Crypto Jargon (@Crypto_Jargon) reported 14 minutes ago

  CLAUDE HAS A SERIOUS PRIVACY PROBLEM RIGHT NOW. 🤯 A HUGE number of shared conversations are PUBLICLY INDEXED on Google. For anyone to find. Right now. People searching one simple string are pulling up: • API keys and crypto wallet credentials • Full resumes with real names, addresses, phone numbers • A lawyer's active ethics case • Internal company project details • What look like actual social security numbers • Deeply personal chats people never imagined another human would read Here's what makes this worse. This already happened once before. September 2025. 600 chats indexed the same exact way. Anthropic's own robots.txt was already blocking search crawlers from these pages. Google indexed the URLs anyway. OpenAI had this exact failure in July 2025. Grok had it in August, with graphic content included. Claude just became the only one of the three to get hit TWICE. Anthropic pulled the links from Google this weekend. Feels over, right? IT ISN'T. Someone already scraped and archived the leak before the fix went live. It's sitting on GitHub right now. Publicly. Searchable. Next to an identical archive of leaked Grok chats. If you have EVER hit Share on a Claude chat: Settings → Privacy → Shared chats. Unshare it. Today. The internet doesn't forget what got made public, even for one second. What would you do if it was YOUR chat sitting there right now?

• 
  Pepons (@peponsRH) reported 15 minutes ago

  The Pepe on Sui team moved over to @RobinhoodApp since @SuiNetwork started having major security problems. Pepons is not just another Pepe. The lore: In the @ponsfamilys GitHub you can find an example where they used $PEPONS. This is literally them telling us how the Pepe on Pons should be called! ca: 0x851babfe94e3ffa5a6d9c3c0dd9f27b7bf0175f6

• 
  Sagar Batchu (@sagar_batchu) reported 15 minutes ago

  Somewhere at your company right now, an employee has a Claude skill that saves them an hour a day. Nobody else knows it exists. "Just put it in GitHub" is the reflex, but version control solves the wrong half. *** tracks the text of a file. It has no idea the skill got invoked 200 times last week, that half those runs were useless, or that the version people actually use has quietly diverged from main. That's the whole problem with skills at work.

• 
  Bruh (@ostromfanclub) reported 16 minutes ago

  @thomasbrushdev dude sometimes i think of switching to github for personal 3d projects for version control just because of this reason. i never experienced a catastrophic problem but what if?

• 
  Kaushik (@kaushikp010) reported 19 minutes ago

  🚀 Starting a new open-source project: RepoDeck. One problem has been annoying me for months. Every time I finish a side project, I have to manually update my GitHub Profile README to showcase it. It's repetitive, easy to forget, and doesn't scale. #buildinpublic #opensource

• 
  Vyacheslav Ops (@SlavaOPs) reported 22 minutes ago

  Cursor's sandbox had two flaws. Chained together, they gave full RCE with zero clicks Cato AI Labs found two chained flaws in Cursor's terminal sandbox. One trusts whatever working directory the agent picks, so pointing it at a system path grants write access outside the sandbox. The other is a symlink resolution check that fails open when path resolution breaks. Chain them and a single piece of attacker content — a poisoned MCP server response, a malicious search result, anything the agent reads — escapes the sandbox and reaches full OS-level code execution. No user interaction required. Full host compromise, plus every connected SaaS workspace. Both scored CVSS 9.8. Both patched. But the pattern is the one we keep seeing: the sandbox wasn't broken by one big mistake, it was broken by two small ones that only mattered chained together — one nobody thought to trust less, one nobody thought to fail closed. Ironic timing: GitHub cuts its public bug bounty payouts by half today, the same week this kind of research is exactly what's finding the bugs that matter.

• 
  Rich Kuo (@richkuo7) reported 22 minutes ago

  @github suggestion: change the label 'ghost' to something more descriptive seeing 'ghost' refer to an issue is kind of ... creepy

• 
  James (@jamescoder12) reported 25 minutes ago

  If this changes how you write code tomorrow or eliminates the ChatGPT copy-paste loop you've been stuck in one ask: Repost the first post so the next developer pasting error messages into ChatGPT at 11 PM sees the terminal-native agent that reads the error, fixes the code, and runs the test in the same terminal. Follow [ @jamescoder12 ] I break down the hidden AI tools, developer workflows, and productivity systems that companies bank on you not knowing. Next thread: Claude Code vs Cursor vs GitHub Copilot the honest comparison from a developer who uses all 3 daily. Which one wins depends on one question.

• 
  Alex Zerntev (@alexzerntev) reported 27 minutes ago

  These are my literal prompt before creating a PR: Codex: /goal Do local PR reviews. fix any findings from those local PR reviews. keep looping on this until there are no local PR review findings. afterwards, push the changes to github and ask for a codex review. Monitor the PR, and fix any codex review comments, reply and resolve the conversation, then ask for a new codex review. keep looping on this until there are no GitHub codex review findings or conflicts to solve. then compare the full implementation with the exec plan. if there is a divergence, fix it, unless it is an issue with the plan itself, in which case, report it to me. Otherwise, keep looping until the PR is ready to be merged and fully reviewed. Claude: /loop Do local PR /review and codex cli review ,fix any findings from those local PR reviews keep looping on this until there are no local PR review findings. afterwards, create a PR on github and ask for a codex review. monitor the PR, and fix any codex review comments or CI failures, reply and resolve the conversation, then ask for a new codex review. keep looping on this until there are no GitHub codex review findings or conflicts to solve. then compare the full implementation with the exec plan. if there is a divergence, fix it, unless it is an issue with the plan itself, in which case, report it to me. otherwise, keep looping until the PR is ready to be merged and fully reviewed.

• 
  BandwidthConnector (@BWConnector) reported 30 minutes ago

  @noahdgoodman Problems with WHAI could be solved if it was run by infra companies on their customers. If GitHub refused vulnerable commits to master and AWS/GCP/Azure scanned and shut down vulnerable instances, you would cover a huge % of software and infra w/ legal consent + monetization.

• 
  ?elianiva✨ (@elianiva_) reported 32 minutes ago

  @samgoodwin89 @DhravyaShah @pierrecomputer i wonder if it's the github API failing mid-stream so it didn't get the whole content i sometimes get 502 errors and had to refresh, even then it's incomplete