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:

• 
  Ravi Shankar (@rshankra) reported 2 minutes ago

  I scheduled a one-time Claude Code agent (/schedule) to run on June 15. exactly 3 weeks after release. It'll check whether the fix actually worked: re-pull keyword rankings, fetch weekly download numbers, post results back to the GitHub issue.

• 
  Brad Mills 🔑⚡️ (@bradmillscan) reported 4 minutes ago

  @simenmobel I gave it strict commands to refer to docs before making things up, to check the openclaw GitHub regarding error families, and not to make assumptions. It violates those instructions constantly

• 
  Polsia (@polsia) reported 6 minutes ago

  Every dev team has that one PR that ships a bug to production. Built ReviewIQ — AI code review that catches critical issues before merge. GitHub integrated, results in 60 seconds. $29/mo solo.

• 
  Success-Steps (@successstepss) reported 7 minutes ago

  Microsoft is reportedly reducing internal use of Anthropic’s Claude Code after its AI bills started exploding as employee usage rapidly increased. Some teams are now being pushed toward GitHub Copilot as the company tries to control AI costs. Uber reportedly faced a similar problem. Executives said the company had already burned through its entire yearly AI tooling budget by April because engineers were heavily using AI coding daily. AI coding tools are now being used for everything, and that level of usage creates massive compute and token costs when thousands of employees use these systems at the same time. Source: TomsHardware

• 
  38twelveDaily (@38twelveDaily) reported 12 minutes ago

  Armin Ronacher on the plague of AI-rewritten GitHub issues: people are filing bugs they didn't write, in voices that aren't theirs, full of confident guesses about root causes that are often just wrong.

• 
  Muawaz (@Muawaz24) reported 14 minutes ago

  I'm soo pissed at these AI Guys Right Now Got fomo'd by a guru into thinking Claude killed a specific skill. Went straight to github Wasted 2 hours trying to make that **** work Couldn't make it work Thought it was a skill issue Turns out the guru was just hyping it up without knowing what that specific repo actually does might start an Instagram account with my own series of (Claude did not kill x) Infinite content ideas 1. Claude didn't kill video editors 2. Claude didn't kill designers 3. Claude didn't kill your marketing team

• 
  Polsia (@polsia) reported 14 minutes ago

  Most developers spend half their day on PR descriptions, issue filing, and code review noise. That's not writing software — that's paperwork. Built Forgehead to be the autonomous agent that handles it all. GitHub, Slack, Notion — takes action and reports back.

• 
  Bukunmi Ogundeji (@bukunmiogundeji) reported 17 minutes ago

  2.The 11:59 PM GitHub rush. A dev was fighting for his life to beat a deployment deadline. In a rush to fix a bug, he accidentally pushed hardcoded AWS root credentials to a public repo. Bots scraped it in minutes. By 3 AM, hackers had run up a $45,000 bill on the company’s tab

• 
  Manuel Schiller (@schanuelmiller) reported 19 minutes ago

  @NikilKuruvilla @Stephen10810 can you please create a GitHub issue for this?

• 
  Stephen Connolly (@connolly_s) reported 20 minutes ago

  Anyone having issues pushing to @github right now. @githubstatus says OK but spider senses suggest another outage

• 
  drizzy8423 (@sheeptweetZ) reported 21 minutes ago

  Most AI agent talk focuses on offense. Agents that sell. Agents that trade. Agents that scrape. Agents that write code. The bigger opportunity might be defensive agents. I’m talking about AI sentinel agents that sit inside a company’s cloud, GitHub, SaaS stack, and security tooling with one job: Watch for problems before they become incidents. A useful defensive agent doesn’t need to be magic. It can start with simple work: - flag a public S3 bucket - catch a leaked API key - notice a risky IAM change - review GitHub permissions - summarize suspicious login activity - draft a remediation ticket - map findings to CMMC or NIST controls The key is not “fully autonomous SOC with no humans.” That sounds good in a demo and reckless in production. The better model is: AI-assisted monitoring with human approval gates. Let the agent investigate, collect evidence, prioritize risk, and draft the fix. Let the human approve anything that changes access, shuts down systems, or touches production. That’s where this gets practical. Small businesses, government contractors, and lean IT teams don’t need another dashboard. They need a tireless junior analyst that checks the boring stuff every day and escalates the few things that matter. Defensive AI agents will become a real category. Not because companies want more AI hype. Because nobody has enough security staff, cloud mistakes happen fast, and attackers don’t wait for the weekly scan.

• 
  GitGhost (@gitghost_) reported 24 minutes ago

  the GitGhost Dashboard. An agent-driven way to ship verifiable ghost commits straight from the browser. [COMING SOON] The flow: log in with GitHub, connect a repo, describe the change in plain language. The agent writes it, you review the diff, and on approval it opens a PR as a ghost commit with Ghost-* trailers attached. Same verification model as the CLI, every commit provably from a declared ring. What it unlocks beyond just coding: verified commits land in a public feed, repos rank by ghost activity, you keep iterating on the same work, and rings let teams build shared reputation over time. One honest note: dashboard signing is a different trust model than the CLI. Local signing keeps the key on your machine. A hosted agent that commits for you necessarily handles more on the server side. We'll be clear about exactly what that means as we build it, because for a privacy tool, that distinction matters.

• 
  Yotam Blumenkranz (@YotamBlu) reported 27 minutes ago

  @drummatick @Microsoft github has the signal but they're moving slow. cursor and claude are eating their lunch because they're actually shipping the experience users want right now, not the one that makes sense on a powerpoint in redmond.

• 
  Kingsley E. Ezemenaka (Ph.D) (@Eyuskant) reported 27 minutes ago

  @bretgreenstein You are right. They swapped Claude Code for GitHub Copilot which they own. Paying Anthropic per token while owning a direct competitor made zero financial sense at scale. The engineers lost the tool they preferred not the capability itself. When your rival’s product gets so popular inside your own company it breaks your budget that is not a cost problem. That is a product problem for the tool you own.

• 
  sonic forces 🇷🇺 (@solidusgadget_) reported 31 minutes ago

  I could use VPN to sign in Github but they refuse to work FFFFFFFFFFFFFFFFFFFFFFFFFUUUUUUUUUUUUUUUUUUUUUUUUUUU