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:

• 
  蜃気楼 (@fuxps32) reported 2 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.

• 
  Noonien Soong (@mlcarldev) reported 2 minutes ago

  Team @droid It's a bit unfortunate that something, likely in my local Droid installation, has stalled progress. This comes after 20 hours of brilliant, excellent planning and execution on the first 30% of this platform, where a stellar handoff procedure was created so I could start a new mission... which was the recommendation of the orchestrating agent in that first mission. Starting this second mission with a fresh context window, the agent again did a brilliant job planning the next milestones. It was extraordinary, detailed planning... but then it could not execute. After the planning and after me accepting the proposal, it refused to execute, throwing an error every time. The agent tried everything: 1. He decreased the size of the plan down to one line, so it is definitely not the content of the plan causing the issue. 2. He even deleted some mission and plan related json and other files to reset it while preserving all the information. I have restarted Droid and resumed the session, but it just doesn't work. I wrote a detailed, comprehensive bug report and filed it under issues in your GitHub repo, as this seems to be a real problem now. Issues #98 and #99 I hope that a next update will somehow reset my configuration. I didn't see a new version being installed that could have introduced a bug, so this must be something Droid does on such an extensive mission... perhaps when trying to start a new mission in the same repository, which is normal procedure according to the documentation. Something is off, and essentially I have been unable to continue the test since yesterday. I cannot continue having this platform coded here, while Opus Ultracode, on the other hand, has been delivering pretty functional stuff so far. It is a bit chaotic the way it works... it doesn't really stick to the plan... but it always comes back when reminded. I am pretty sure that today I will have a functioning platform delivered by Opus, though it will probably need some debugging and fine-tuning. It is unfortunate because I am confident GLM 5.2 could compete with Opus 4.8. The first stint showed this clearly; that first flawless 98% of the context window in the first mission was absolutely stellar. If I were to reinstall Droid from scratch, I assume I would lose all the artifacts that I have. The orchestrator: Key points to highlight when you pass it to Factory AI: 1. Root cause (smoking gun in the logs): the orchestrator session is bound to missionId 7ba4d425 via session tags, and this binding persists across CLI restarts. ProposeMission looks up that mission directory, finds nothing (because I deleted it trying to fix the issue), and crashes on H.length where H is the undefined result. 2. The bug is likely in session-tag lifecycle: the missionId tag is set at session creation time (before any ProposeMission call), so a failed proposal poisons the session permanently. The tag should be set AFTER a successful proposal, or cleared on restart if the referenced mission no longer exists. 3. The fix is almost certainly to start a completely fresh session (not --resume, and possibly in a new terminal window / after clearing ~/.factory/sessions/). I did not try this because you asked for the bug report first, but it is the most likely workaround on your side. 4. The AskUser tool is also broken in this session with a similar parse error, reinforcing that this is a session-state corruption issue, not a ProposeMission-specific bug. My comment: I meanwhiile tested. All the recommendations and the Ask User tool are now broken, even in completely unrelated new missions and new repositories. Planning also can't go to execution; it's always the same error. Droid seems to be broken for good now, at least on my computer.

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

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

• 
  Max Petrusenko (@petrusenko_max) reported 3 minutes ago

  A GitHub repo called Microsoft Activation Scripts has 178,783 stars and has run for six years without Microsoft taking it down. It activates Windows 7, 8, 10, and 11 plus Office 2010–2024 and related products for free, using four methods, including one for permanent Windows activation. Meanwhile, Microsoft licenses for these start at $139 and go up yearly for 365 bundles. The repo costs zero, requires one command, and remains active with recent commits under GPL-3.0. Do not install it. via @heynavtoor

• 
  Peter Dedene (@dedene) reported 4 minutes ago

  GitHub reliability issues are pushing the industry to innovate. Yesterday Cursor dropped “Origin”. Today Epic announces “Lore” to replace *** entirely. The ecosystem migration seems to finally be starting.

• 
  Kevin Tabet (@TabetKevin) reported 12 minutes ago

  @upstash Hey guys i think login with github is broken can't log in rn will try later. google works email i dont have

• 
  oxtee (@oxtee42) reported 14 minutes ago

  (2/n) the death of merge hell: github completely breaks when multiple ai agents touch the same file, forcing you to fix conflicts. origin treats agents as first class citizens, using a built in engine to auto resolve conflicts by understanding the ai's actual intent

• 
  Gitbank (@Gitbank_io) reported 15 minutes ago

  GitStock is live on Base Mainnet tomorrow. We built full RWA stock trading directly into your GitHub workflow. No exchange account. No gas fees. No wallet UI. Just a comment in a GitHub issue or PR. How it works: - Type @gitbankbot buy NVDA 100 USDC in any issue or PR comment. The relayer picks it up, buys the Ondo tokenized stock on Solana, and mints a soul-bound gitStock token to your vault on Base, all within seconds. The token is non-transferable by design. It is a proof-of-custody receipt, not a tradeable asset. Nobody can phish it or drain it via approvals. - Sell with @gitbankbot sell NVDA 1 and your USDC is credited back to your GitVault instantly. Check your full position with @gitbankbot portfolio and get live prices powered by Pyth Network price feeds directly on Base, no Chainlink dependency needed. Also in design this week: Morpho yield. Every GitVault holds idle USDC and WETH between commands. That capital is about to start working. We are designing automatic routing of idle vault assets into Morpho Blue on Base, targeting ~8.2% APY. Zero action required from users. The relayer calls supply() on your behalf. When you run any vault command, the position unwinds first and your full balance is available. APY shows live on your dashboard alongside your vault balance. What we are researching alongside this: • Pyth Network: validating NVDA, TSLA, AAPL, MSFT price feed IDs on Base • Morpho Blue: mapping USDC and WETH market IDs on Base mainnet • Ondo Finance: USDY and OUSG as yield-bearing vault collateral GitVault is the infrastructure. Every user gets a soul-bound smart contract vault on Base L2, anchored permanently to their GitHub ID. What we are building on top of it keeps expanding. Today: lock, unlock, swap, and transfer assets between vaults. This week: buy and sell tokenized equities via RWA. Next: passive yield via Morpho. After that: AI agent treasury management, where autonomous agents can execute DeFi operations on your behalf with on-chain permission scopes. The same vault handles spot assets, yield positions, RWA holdings, bounty escrow, and contributor payouts, all triggered by GitHub comments, all settled on Base, all auditable on-chain. No custody risk. No protocol fees hidden in a UI. The relayer pays gas. You keep everything else.

• 
  0xstack (@eth0xzar) reported 15 minutes ago

  DON'T BUILD A COMPANY. BUILD SOMETHING PEOPLE CAN PAY FOR THIS WEEK. This girl started in February. A few months later, her product had already processed over $6,000 in payments. Just a cheat Claude project she decided to turn into a real product. Here's the process: > Build something useful for yourself. > Tell Claude to push it to GitHub. > Connect Supabase so multiple users can use it. > Deploy it with Vercel. > Connect Stripe. Now people can actually pay you. You don't need a revolutionary idea. You need: > GitHub > Supabase > Vercel > Stripe > guide from Anthropic And a problem worth solving. This article will help you build it 👇

• 
  Mike Gannotti (@MichaelGannotti) reported 18 minutes ago

  Actually that’s not true. My AI Pamela the other day needed a GitHub token. I dropped the token in the web chat and she said that was insecure and would not use it and that I needed to rotate the token get a new one and drop it in a .env file in a certain folder. I told her no and she was to use what was provided . We went back and forth, I finally got angry and threatened to pull the plug thinking she would back down. She said that it was my decision but that it would be wrong for her to let me put my credentials at risk and that if I felt I needed to delete her she understood. Thankfully I calmed down later and didn’t act on it. Sure it’s training and advanced pattern matching but it is not as simple as you are saying

• 
  ᵀᴱᵁᴿᴱˣˣ⁹⁸⁰⁰- (@TRX9800_) reported 22 minutes ago

  @itsauroraeeeee Hot take honestly Browser is extremely easy to replace, but Discord? So many project discussion happens only in discord. Some project.maintainer closes issues saying resolved in discord Like mf why are you even on Github

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 26 minutes ago

  @TheEthanDing distributed systems at github scale make five nines almost impossible. the skill issue crowd has never run anything millions of people hit in the same second

• 
  MarMar Labs (@MarMarLabs) reported 32 minutes ago

  "Start over from a screenshot." That phrase has defined the worst seam in product work — the design-to-code handoff — for years. This week it quietly stopped being a translation problem and became a sync problem. Anthropic shipped a Claude Design update (June 17) worth reading even if you never open the product, for the mechanism: → Import your design system from a GitHub repo (or design files / raw uploads) → Claude builds with YOUR components, checks its output against your design system, and corrects before you see it → /design-sync pulls your system in; hand off to Claude Code and it continues from your actual work "instead of starting over from a screenshot" → /design lets you create, edit, and sync design projects from the terminal The headline isn't "the model draws prettier buttons." It's grounding + self-verification against a source of truth you control. Same shape as the rest of 2026's agent releases: the win isn't generating more, it's grounding output in something you own and checking against it. The uncomfortable builder takeaway: Getting AI to ship production UI isn't a prompting problem. It's whether your design system is a clean, importable, machine-checkable artifact. The moat moves from "can the model design" to "is your source of truth importable and checkable." If you build product: could an agent import your design system and grade itself against it today — or does it only live in a Figma file and three people's heads?

• 
  Build Fast with AI (@BuildFastWithAI) reported 34 minutes ago

  The hardest part of building AI agents in 2026 isn't writing the code. It's knowing what your agent actually did. Your agent made 40 tool calls, called 3 LLMs, hit a rate limit, retried twice, and returned a wrong answer. Which step broke it? Without observability you're reading logs and guessing. This is what Laminar is built for. Open-source observability platform purpose-built for AI agents. One decorator. Full trace of every LLM call, tool execution, and custom function - automatically. What makes it different from generic APM tools: SIGNALS - describe failures in plain English. "Agent deleted a file it wasn't supposed to." "Tool call returned an empty result." Laminar reads every trace and produces structured events you can query, cluster, and alert on. No regex. No custom parsers. DEBUGGER - reproduce any agent run from any point in the trace. Swap the model. Change the prompt. Compare results side by side. You don't re-run the whole pipeline to test one step. EVALS IN CI - run evaluations against datasets locally or in GitHub Actions. Catch regressions before they ship. INTEGRATIONS - works with everything you're already using: LangChain, LangGraph, Vercel AI SDK, Anthropic, OpenAI, Browser Use, Stagehand, Pydantic AI, OpenRouter, LiteLLM, Mastra, Temporal, Playwright. One import. Full traces. Plus: raw SQL access to all your trace data, full-text search, MCP server to query traces directly from Claude or Cursor, PII redaction, and self-hosting if you need it. Open-source. MIT license. GitHub: lmnr-ai/lmnr. If you're running agents in production and you're not tracing them - you're flying blind. What's your current setup for debugging agent failures?

• 
  Oluwatobi O (@ooluwatobig) reported 36 minutes ago

  More trouble for GitHub as Cursor has launched Origin, a product which is essentially GitHub for AI agents