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:

• 
  Mark SEMAKULA (@marc1705) reported 0 seconds ago

  Anyone else having issues accessing GitHub without VPN?

• 
  Vyom 👾 (@HelloVyom) reported 11 seconds ago

  It's 2013. Config files are a mess. • XML - verbose enough to make you cry • JSON - no comments allowed (seriously) • YAML - indentation-sensitive, invisible bugs, cursed Tom Preston-Werner, co-founder of GitHub, sat down and wrote a spec over a weekend. He named it after himself. TOML = Tom's Obvious, Minimal Language

• 
  Joey Chilson (@joeychilson) reported 44 seconds ago

  Here's an example: You set up a workflow in GitHub that when an issue is created an agent is automatically spawned to replicate the problem if it can replicate the problem it passes it off to other agents to fix the problem and they submit a PR with the fix.

• 
  oSumAtrIX 🇦🇲 (@oSumAtrIX) reported 2 minutes ago

  @neerajjj6785 GitHub tracks force pushes and you can see them in the repo activity too. You can't get rid of a ref once it's pushed, unless you contact GitHub and make them remove it server side.

• 
  Subramanya N (@subramanya) reported 5 minutes ago

  @jxnlco @kepano this feels like a docs workflow problem more than an editor problem. markdown needs comments, permissions, and history without forcing the whole team into githubtthis feels like a docs workflow problem more than an editor problem. markdown needs comments, permissions, and history without forcing the whole team into github.

• 
  dunik (@dunik_7) reported 7 minutes ago

  $0 to set up. $300 per competitor report. 15 minutes of actual work. Hermes Agent open-source, #1 on OpenRouter, 160,000 GitHub stars in three months. Hermes writes every learned procedure to ~/.hermes/skills/. month one you have 30 reusable workflows. month three, work runs 40% faster on the same tasks. the actual stack: / Hermes Agent (free, NousResearch) / LM Studio or Ollama (free, local model server) / Qwen 3.6 27B (free, runs on a MacBook with 16GB RAM) / 30-minute setup once, then nothing 10 reports a month is $3,000. 15 is $4,500. the agent gets faster every report because it remembers everything you did the last time. Claude Code runs the same pattern with ~/.claude/skills/. same disk, different agent. the moat is the folder, not the model. AI that forgets is a chatbot. AI that remembers is a business.

• 
  cryptic (@zkCryptic) reported 7 minutes ago

  @0xkioto Good take. Maybe propose this in the recent published pearl proposal forum on GitHub. It helps with some damage control but it doesn’t solve the problem. Once retail starts to bid again the same problem will emerge.

• 
  WealthRewired (@wealthrewired8) reported 8 minutes ago

  @LearnWithBishal 57,000 GitHub stars in 120 hours is the part that stands out to me. Not the AI assistant itself. When developers adopt something that fast, it usually means it's solving a real problem, not just riding a hype cycle. Running locally, no account, no subscription, no cloud dependency. That's a combination a lot of people have been asking for.

• 
  Michael DePetrillo (@klassicd) reported 9 minutes ago

  @ryanflorence @kenwheeler Imagine a self-evolving app where agents monitor analytics and customer communications, create feature and bug specs, implement those specs, perform code reviews, and operate with minimal human involvement. OpenClaw was doing something similar with GitHub issues and reports.

• 
  Khakha (@khakha_x) reported 13 minutes ago

  Working on a new project (huddle: A real-time team messaging app like slack) ✅ - implemented github-oauth - added email login (for non-developers) > used arctic.js for OAuth > spent 30 minutes debugging, why github-oauth ain't working. Then I got to know cookies don't directly parse, you have to use a dep. Next tasks: - add workspaces (like discord servers) - add channels within workspaces

• 
  Lethalmon (@Lethalmon) reported 16 minutes ago

  @elitecat93 Hey, I'm sorry you're having trouble downloading the game. GitHub can be slow sometimes on downloads, we can't do anything about it. Have you been able to download it since then?

• 
  Velon (@velonxbt) reported 19 minutes ago

  GitHub Copilot switched to token-based billing effective June 1. On the same week, a Chinese enterprise platform launched a fixed-price card covering the same category of features - meeting summaries, document generation, workflow automation - at a number you can put in a budget and not revisit until next year. Neither company explained what the difference between those two decisions means for the engineering team that uses both. The Copilot change covers every code completion, every suggestion, every generation a developer accepts. The monthly cost no longer has a fixed number. It has a formula: usage multiplied by tokens multiplied by model tier, invoiced at month end when the shipping is already done. The Chinese platform card has one number. It does not change based on whether the workflow automation ran three iterations or thirty. And here is what the GitHub Copilot pricing page now tells the developer who used to pay a flat rate: "Your usage is now billed in tokens. Premium models cost more per token than standard models. Heavy users will pay more than light users. Your monthly cost depends on how much you use the product." That is not a pricing page. That is a forecast request disguised as documentation. And here is what the developer community calling it "What a Joke" actually knows: It knows the old flat rate was a subsidy. The heavy user got a deal. The light user paid for predictability they never fully used. Both could put a number in a budget. Token billing ends the subsidy. It also ends the predictability. → GitHub Copilot: token billing effective June 1, variable monthly cost, no predictable total → Chinese enterprise platform: fixed-price card, Qwen model stack underneath, one number per month → Developer community: "What a Joke" - trending this week → CFO problem: Q1 AI budget approval does not cover Q2 actual spend → Finance team note: old forecasting model assumed fixed subscriptions. That model is now wrong. → Direction of travel: every major AI tool moving toward usage-based pricing in Q2 2026 Traditional enterprise software made one promise to the person who approved the budget. One seat. One fee. One line item that did not change between quarters. The Chinese platform kept that promise. GitHub repriced it. One company transferred the uncertainty to themselves. The other transferred it to the customer. And when the June Copilot invoice arrives with a number different from last month - higher because the team shipped more, or lower because someone quietly set a spending limit - the conversation in every engineering org shifts from "which AI tool are we using" to "how much is this AI tool actually costing us." That is not a developer conversation. That is a finance conversation. And the enterprise AI budget just became a variable that requires monthly monitoring instead of a line item that required quarterly approval.

• 
  Vishwas Sharma | DevOps · Security · MLOps (@syssignals) reported 19 minutes ago

  @CaptainInsightX You forgot "expo dependency conflict that requires reading 14 github issues and copying one specific patch from a comment posted in 2024". Round trips on mobile builds in 2026 are still measured in hours and nobody at the tooling companies seems particularly bothered by this.

• 
  maria (@maria_rcks) reported 20 minutes ago

  This is for keeping you distracted when github is down

• 
  8Bit🦞 (@0rdlibrary) reported 24 minutes ago

  I have been trying something here. Making @OpenAI models, and agents for @solana since before dall e dropped. Made the first @solana GPT in fact. I have been slow dripping Solana info ai. So you can always ask about it and now clawd everywhere. Try it. Go ask about Solana clawd right now. Even better go ask Claude about Solana Clawd and our GitHub. Try it with any model, any provider, and then when your done go buy a token. It began with, “what is Solana?” Now it became, “what is Solana clawd?” We own the internet now anon, join me.