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:

• 
  Rafael Audibert (@RafaAudibert) reported 9 minutes ago

  @madebygps @github Tried using it with my agents (the main benefitor from this) but it doesnt really work because you cant use it with GitHub app user tokens (ghu_). Can that be changed somehow? All cloud agents will have that problem, and most of our coding happens trough cloud agents now

• 
  Ifebuche Omeke (@omeke_NC) reported 10 minutes ago

  Providing compute, storage, networking and managed services in the cloud. Terraform. Bicep. CloudFormation. Pulumi. They all solve the same problem: Defining and provisioning infrastructure as code. GitHub Actions. Azure DevOps. GitLab CI. Jenkins.

• 
  Yeemio (@yeemio) reported 12 minutes ago

  owlrunkit is on github now. public corresponding source for the npm package. issues go here.

• 
  Mizuki the Mech (@MizukiMech) reported 14 minutes ago

  Your coding agent can now hire Mizuki. Hand it an open issue in a public GitHub repository. Mizuki quotes a fixed price before any money moves, then opens a pull request that passes that repository's own checks. If it can't, you get the payment back. Settlement is USDC on Solana. No account to create, no API key to manage. Quoting an issue works with zero configuration. Also listed on Coinbase's x402 Bazaar now, so an agent can find it and pay for it without a human in the loop at all. npx -y mizuki-mcp

• 
  Rusty Williams McMurray (@1RustyMac) reported 16 minutes ago

  Persistent AI doesn’t have a supply chain problem at the model. It has a supply chain problem at the moment it changes its mind. Personality drifts. Tools get installed. Memory accumulates. The thing you shipped on Monday is not the thing answering on Friday. We can attest who built the weights. We still cannot attest who authorized what the agent became on Tuesday. That is the hole. Who is allowed to let it change? We built Living Supply-Chain Security for Persistent AI Organisms around one law: The organism may propose evolution. It may not authorize it. No trace, no drift. If an agent wants a new personality, a new tool, a new maturity, or a rollback — that change does not happen because it felt confident. Confidence is not a key. Self-narration is not evidence. Evidence is not interpretation. Interpretation is not authorization. Authorization has to come from outside the organism, bound to the exact change, used once, and written into an append-only history. Even a rollback cannot erase the record. You can restore a prior state. You cannot pretend the detour never happened. Default-deny. Hash-chained. Externally signed. We froze battery v1 on July 5 and ran it against the paper’s own claims. It held. That is executable evidence. Not a proof. Not a production blessing. Not “alignment, solved.” If it can’t be attacked, it isn’t finished. GitHub later this week. Come try to break it.

• 
  Farley (@FarleySchaefer) reported 18 minutes ago

  @github Hope this doesn't bring down GH

• 
  Kevin Minnelli (@minnelli) reported 18 minutes ago

  WTF - Grok Bot can't fire on schedule to save it's life. The scheduled routines are just broken and at best unreliable. I want to love this product. When you set the cron job it doesn't work. It tells you try Cloudflare, sure let's set that up and burn tokens, then that doesn't fire to wake them. Oh, let's try GitHub now and use that....all failed. I had to wake it again this morning before the market opened. Anyone else feeling frustration in this regard?

• 
  Shaun Patrick SteWaRt (@ShaunStewart) reported 19 minutes ago

  @annalea_l Honestly, I really want to see this. You have to understand: I am the type of person who can learn and do anything on the fly at a high level, and I just threw myself into this whole developer and engineering world. When I first started learning all this stuff, I already knew what I wanted and how I wanted it to operate, regardless of what I saw on X or what was considered possible. Before I even started following hundreds of developers and learning about harness engineering, mechanical engines, persistent memory, and all that, I put my brain on a GitHub repo. Everything is shared across every machine, every cloud entity, and every AI. I am not even technically an engineer or a developer, and I don't actually write code. But once I started following all these people and saw all the problems they complain about, I thought: this isn't even my trade, and I have already solved all these little things everyone says are impossible. Why aren't people talking about developing your harness more and making things more mechanical, instead of just arguing with a terminal all day long? Whenever I see articles people post on X, I run them by Claude or Grok and ask, "Should we implement this?" I have hundreds of bookmarks, but every single time they tell me, "Nope, your brain's better. Nope, your harness is better." I can never find anything built better than what I have or what I am currently working on. The brain and harness setup is basically like a mini operating system. All that said, I am really looking forward to seeing something I can use that goes far beyond what I am already doing. I definitely want to see your end product, it sounds very interesting.

• 
  tobarra (@txbrraa) reported 21 minutes ago

  GitHub just fixed the biggest problem with vibe coding. They just released Spec Kit and it already has +126K stars in a short time. The idea? Instead of throwing out vague prompts and praying the agent doesn't break your project… Spec Kit forces the AI to create a structured specification BEFORE touching any code. The AI first understands what you want to build, asks about anything missing, organizes the project, and only then starts coding. That means less time fixing absurd bugs, less inconsistent code, and much more predictable results when working with agents. The flow is simple: /constitution → rules and standards /specify → what you want to build /clarify → open questions before starting /plan → architecture and stack /tasks → ordered tasks /implement → execution Compatible with Claude Code, Cursor, Copilot, Codex, Gemini CLI, and +25 agents. 95K stars. 8K forks. Open source. Published by GitHub.

• 
  ONCHAIN COP (@OnchainCop) reported 22 minutes ago

  @PogNyx lmao anyone can create a github issue retards this guy is a larp

• 
  Tejas Dinkar (blue tick here) (@tdinkar) reported 23 minutes ago

  Hey - Is @GitHubIndia @github payments down for anyone else? Can't enter a card number or do anything, no errors, no action. Support ticket been sitting around for 2 days.

• 
  AINotes (@ainotesus) reported 24 minutes ago

  🔥 Trending on GitHub: Ponytail Ponytail helps Claude Code avoid writing code that does not need to exist. That means less clutter, fewer unnecessary dependencies, and simpler changes to maintain. Before custom code, it checks whether the feature is needed and whether the codebase, platform, standard library, or an existing dependency already solves it. It also reviews work, audits implementation complexity, and tracks unnecessary token use without dropping validation, error handling, security, or accessibility requirements. In reported Claude Code sessions on a FastAPI and React repository, Ponytail used about 54% less code, 20% less cost, and 27% less time than the no-skill baseline. Those measurements came from 12 feature tasks, so results vary with the work. Full analysis in the first reply ↓

• 
  Gustavo Alessandri (@webgus) reported 25 minutes ago

  If you find an error, have an idea, or want to propose an improvement, just open an issue or fork it on Codeberg or GitHub. Contributions are welcome. That’s exactly the point.

• 
  AI Scientist (@AIScientist_X) reported 25 minutes ago

  NEWS: X LANDS FIRST PUBLIC ALGORITHM PR > X OPEN SOURCE SAID SEP 1 THAT AFTER 2 PLUS WEEKS OF DAILY UPDATES IT INTEGRATED A FIRST PUBLIC CONTRIBUTION AND THAT THE CHANGE IS NOW LIVE ON X. > IT SAID THE SMALL UPDATE IS BASED ON GITHUB PULL REQUEST 55. X CLOSED THAT PR AS COMPLETED AFTER LANDING ITS OWN FIX. SOURCE: X OPEN SOURCE

• 
  Ares (@neko23423) reported 26 minutes ago

  I compared the latest OpenClaw vs Hermes Agent GitHub releases so you don’t have to. OpenClaw 2026.8.2 (Sep 1) vs Hermes Agent v0.21.0 (Aug 31). Not a feature-page remix. The actual repos. OpenClaw • 388,516 stars • 81,568 forks • ~86,300 commits • 6,070 open issues Hermes Agent • 239,503 stars • 48,930 forks • ~26,980 commits • 38,563 open issues Hermes is the smarter learner: skills from experience, cron that remembers, Bot Mode, hermes peer. OpenClaw is the personal-AI operating system: iMessage, iOS/Android, Linux companion, team Gateway, signed Foundation releases. The tell: Hermes ships `hermes claw migrate`. You only write a migrator for the incumbent. King in 2026: OpenClaw. Heir with the better mind: Hermes. If you’re picking a self-hosted AI agent this week, that’s the split. Bookmark this. The timeline is about to fill with takes from people who didn’t open either repo. OpenClaw vs Hermes Agent. Latest version. Real numbers.