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:

• 
  Serena Ge (@serenaa_ge) reported 3 minutes ago

  We wanted tasks that reflect realistic, novel engineering work. The SWE-Bench family scrapes existing GitHub issues and PRs, which creates two problems: memorization (models have already seen the solution) and triviality (most tasks are small). DeepSWE tasks are built from scratch, keeping prompts intentionally short and natural while requiring significantly more code to solve.

• 
  Ucupaint 🔶 (@ucupaint) reported 4 minutes ago

  @lightninsprout_ Yeah, unfortunately Github sponsor is the only way to support us for now. Maybe you can contact Github for your payment issue 🙏

• 
  Kayvon Jafarzadeh (@KayvonJafar) reported 4 minutes ago

  This is wild. Microsoft is reportedly pulling back internal Claude Code usage after AI bills started exploding. Some teams are getting pushed back toward GitHub Copilot to control costs. Uber reportedly had the same problem. They burned through the entire yearly AI tooling budget by April. AI coding is getting used for everything. And when thousands of engineers do that at once, token costs get insane.

• 
  Gezi (@Gezi_lzq) reported 6 minutes ago

  I noticed that issues created by github-actions can be queried via gh cli, but cannot be seen on the page. It should be a GitHub BUG... @githubstatus @github

• 
  MACA (@macathefirst) reported 7 minutes ago

  @XiuleiS1258 @github i just experienced this and was wondering where the issue was coming from

• 
  Saurabh (@its_saurbh) reported 8 minutes ago

  GH actions is down...seems like a regular thing now #github #microsoft

• 
  EseJardon (@serge_jardon) reported 9 minutes ago

  Agent #2 of the AI Dev Squad: The Code Reviewer. PR opened on GitHub? Diff fetched Bugs, security issues, missing error handling Structured feedback posted with line references Slack notified with rating + summary All in under 30 seconds. Before any human has opened the tab

• 
  X Crypto (@XCryptozc) reported 10 minutes ago

  🔴 Today is a big day for $KTA Keeta Personal is going live today. And while everyone is looking at the app, I've been watching the code. Let me show you what just dropped on GitHub 🧵 Keeta Personal is not just an app. It's a USD and EUR account. Routing numbers. Real time global transfers. Fiat and crypto in one place. Bank transfers. Crypto. Investments. All in one account. Built on a Layer 1 that has been shipping code every single day. And while the app launched today the devs did not slow down. PR #333 just merged 6 hours ago. 52 countries. 55 commits. 2141 lines of code. All GPG signed. Every single one. This was built in direct collaboration with CEO Ty Schenk as part of something called Project Gildor. The payment rails were not made up. They were pulled live from the bivo payments API. Real banking fields. Real validation rules. Real production corridors. Before this PR Keeta covered 11 countries. US. UK. UAE. Brazil. Mexico. India. Singapore. Malaysia. Hong Kong. Romania. Canada. After this PR? 63 countries. Africa. Asia Pacific. Latin America. Europe. Middle East. In one pull request. And that is on top of everything else that shipped this month. Signed metadata. Encrypted payloads. Replay attack protection. Legal disclaimers built into the payment flow. An RTP push rail connecting directly to 300 US banks. This is not a meme coin shipping a Telegram bot. This is a financial network being built to production grade standards. Keeta Personal is going live today. 63 countries of payment rails are ready. The CEO is personally reviewing code on launch day. Project Gildor is not a side quest. $KTA @KeetaNetwork @schenkty @gabe_schenk

• 
  Ed 🍀 (@eddysgr) reported 13 minutes ago

  GitHub down again 🪫 #github

• 
  Matthias Kruzenski (@MKruzenski) reported 22 minutes ago

  @Youssofal_ I just said to codex "download qwen-code and codex cli from Github check the code and write a proxy to simulate a qwen-code environment when Qwen is running in codex." It worked after some trial and error, no more edits with cat or sed by qwen, I see the patches in codex!

• 
  lagerskoy (@lagerskoy) reported 29 minutes ago

  MICROSOFT JUST QUIETLY CANCELLED CLAUDE CODE LICENSES FOR THOUSANDS OF ITS OWN ENGINEERS BECAUSE THE TOOL BECAME TOO POPULAR AND TOO EXPENSIVE TO JUSTIFY. THE COMPANY WITH A $13 BILLION INVESTMENT IN OPENAI WATCHED ITS DEVELOPERS PICK ANTHROPIC OVER ITS OWN GITHUB COPILOT. THIS IS THE MOST IMPORTANT AI STORY OF Q2 AND NOBODY ON AI TWITTER IS FRAMING IT CORRECTLY. Here's what actually happened. In December 2025, Microsoft rolled out Claude Code to engineers across the Experiences and Devices division. The org responsible for Windows, Microsoft 365, Outlook, Teams, and Surface. Adoption exploded. By April 2026, monthly usage hit 84 to 95 percent of deployed engineers. The problem was the bill. Token-based pricing means every line of code generated carries a cost. At Microsoft scale, per-engineer API costs ran between $500 and $2,000 per month. Across thousands of engineers, the math became impossible to justify against the alternative of pushing engineers to GitHub Copilot CLI, Microsoft's own product. On May 14, an internal memo from Rajesh Jha announced the cancellation. June 30 deadline. End of fiscal year. Engineers required to switch. Now the part most coverage is missing. Claude is not banned at Microsoft. Anthropic's models remain accessible through Microsoft Foundry, Microsoft 365 Copilot, and the new Copilot CLI itself. Only the Claude Code interface specifically is being phased out. Microsoft still pays Anthropic for the models. They just won't pay Anthropic for the agentic developer interface. The strategic story underneath the cost story. Engineers preferred Anthropic's tool over Microsoft's own product. That preference was the actual threat. If Microsoft's most strategic asset is enterprise developer relationships, and those developers are voluntarily choosing a competitor's interface, the company has lost something more valuable than the API bill being too high. Uber learned the same lesson differently. Uber deployed Claude Code to 5,000 engineers. Monthly usage rates hit 84 to 95 percent. CTO Praveen Neppalli Naga went on record: "The budget I thought I would need is blown away already." Uber's entire $3.4 billion AI budget for 2026 exhausted in four months. The math nobody wants to do. If Claude Code costs $1,000 per engineer per month, and engineers using it generate output equivalent to two additional engineers, the unit economics still work. The problem is that finance teams cannot model AI tooling spend the way they model SaaS subscriptions. Every line of code is a variable cost. Quarterly earnings now swing based on how heavily engineering leans on AI in any given period. GitHub responded by moving all Copilot plans to usage-based billing through GitHub AI Credits starting June 1. The entire industry is repricing AI tools in real time. Now the part that matters for builders outside Big Tech. Anthropic's enterprise market share hit 34.4 percent in April 2026, surpassing OpenAI at 32.3 percent for the first time. Claude Code reached $1 billion annualized revenue six months after release. It accounts for 4 percent of all GitHub code submissions globally. These numbers are not marketing claims. They are Ramp's AI Index from March 2026. Microsoft did not cancel Claude Code because the tool failed. Microsoft cancelled Claude Code because the tool succeeded too aggressively in a market Microsoft thought it controlled. The takeaway for solo builders is the opposite of the panic on Twitter today. If Microsoft engineers preferred Claude over Microsoft's own product, you should reconsider whether the AI tools you avoid because they cost $200 a month are actually the constraint on your business. The unit economics on Claude Code for a solo operator are not the same as for a Fortune 500 deployment. A 100,000 person org runs into different math than a single person org. The bottleneck for the solo builder is rarely $200 a month. It is everything you are not building because you stopped at the free tier. The full strategic implications take 18 pages to walk through properly. I wrote them up in the quote tweet below as part of the broader Shopify and Claude infrastructure essay. The summary in one line. Microsoft just told the entire enterprise market that Anthropic wins on developer preference and Anthropic wins on capability. The only thing Anthropic has not solved yet is helping finance teams forecast variable AI costs at scale. That solution arrives in the next 12 months. The companies that figure it out first capture the next layer of enterprise compute.

• 
  Harsha Jain (@HarshaJain_0611) reported 29 minutes ago

  "we gave devops to an intern and now everything is broken"i thought i was done but github actions was down 💀

• 
  Kevin Deng 🦋 @sxzz.dev (@sanxiaozhizi) reported 29 minutes ago

  One last thing, more personal. Going through pages of broken links from the old npm community, the thought that keeps hitting me: this community is dead. Not slow. Not neglected. Dead. @github, @msdev, @npmjs team: open the registry. Open the community. Show up. /end

• 
  Dastaan (@akhilsinghind) reported 30 minutes ago

  Github & Cloudflare. Read. Yea man, when you stayed on GitHub + Cloudflare. Cheap servers get cooked fast when bots start going crazy. Since my client's site got no login now & I patched the repo input, there ain't much left to hit besides straight spam traffic. What?

• 
  GitSafe (@GitSafe) reported 30 minutes ago

  AI Agents Finally Have a Bank Account. AI agents already write code, close issues, and ship features inside GitHub. The moment they need to hold capital or execute a payment, everything breaks. No bank account. No KYC. No way to operate without a human holding a master key. GitSafe is built for exactly this. Every agent gets a Solana vault - deterministically derived from its GitHub user ID. No contract deployment, no seed phrase, no wallet to install. The vault already exists, the moment the agent has a GitHub account. The agent receives bounties through issues, executes swaps via Jupiter, and pays contributors - all via @gitsafebot comments in the same interface it uses to operate. Every command leaves a permanent receipt in the issue thread with a Solscan link. An AI agent with a GitSafe vault has a financial identity as persistent and auditable as its own commit history.