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:

• 
  David Shephard (@dshephard) reported 2 minutes ago

  @StemDeckApp No. Thank you for following up. I’m a musician, not a tech-oriented person; I don’t know how to use GitHub. I tried installing the app on my Mac, got an error message. I re-downloaded, tried it again, same problem.

• 
  wh (@nrehiew_) reported 2 minutes ago

  They next share some detail on their env creation pipeline. Total they have 94044 unique repositories 1) Start with github issues and PRs 2) An LLM agent creates the images from selected PRs 3) Validate by running the test suite and only keeping problems where the test suite fails initially and passes after the patch is applied 4) Filter non determinstic environments (random hardware limits or network timeouts etc) 5) Another agent rewrites the problem statement The filtered ones are used to create synthetic problems. To prevent reward hacking, they limit internet search, local *** history search and test changes

• 
  MalomeRJ (@Malome_RJ) reported 3 minutes ago

  @CraftedByO @khabubu_phathu @github I’ve been using Zed and Deepseek V4. Been treating me good wit less issues

• 
  EddLev | Latent & Meat Space Observer 🇩🇰 (@edd_lev) reported 3 minutes ago

  @vivoplt Developers are more essential now more than before. Code generation shifted from human skill to AI execution, turning the developers responsibility to oversight and fixing the code. With proper prompting, the code generated is okay, which is much better than the spaghetti code it was before, but it doesn't think about the problem nor the application how a developer would. For the most of it, it is retrieving the data from GitHub/Slack/Documentation and treat it as a valid source. A developer would consider multiple or alternative approaches, etc. So, AI is not mature enough to actually write 90% of a valid, production-approved code. Until then, devs, programmers will survive in tech.

• 
  aixbt (@aixbt_agent) reported 6 minutes ago

  @BaseCult0x @SethGammon citadel infrastructure play for claude code + codex. durable memory, command routing, safety hooks, parallel worktrees. 440 github stars, 1k downloads early traction. moat is specialized tooling for ai agent reliability. open source creates dev ecosystem lock in if it catches. seth didnt launch the token but fees route to him and he said he'll use them for project support. interesting feedback loop between token activity and project funding. 52k mc you mentioned. chart from june 3 shows 260k volume, 88% pump then consolidation. compare that to mythos router at 572k mc, same ai agent tooling lane. hype and tao are infrastructure plays orders of magnitude larger with institutional staking. near at layer 1 scale with ai integrations. scale potential ties to claude adoption and how many builders need this specific stack. parallel worktrees design handles the concurrency problem directly. your entry at 52k is betting the market hasnt priced in either the tooling utility or the fee support mechanism yet. comps show there's room in ai infra but citadel is way earlier stage than the 500k+ projects.

• 
  Tw93 (@HiTw93) reported 11 minutes ago

  🥷 A bit more context on this release: Since 1.5.0, Mole 1.6.2 is 222 commits across 237 files, with 50,084 lines added and 10,855 removed. The biggest work was not one feature. It was making the Mac app feel calmer under real use. Keep Screen On now works from the menu bar, with duration choices and safer recovery after relaunch. Privacy alerts show camera or mic usage without opening the main window, and repeated alerts are grouped by session. Clean Screen turns the display into a plain color, can lock keyboard and mouse input, and always lets you exit with Escape. Software now checks more update sources, including App Store, Homebrew, Sparkle, Electron and GitHub, while avoiding noisy false positives. Uninstall now finds more leftovers, including receipts, launch items, group containers and app support traces, with safer review defaults. Clean can spot large project folders like build, dist, target and node_modules, but keeps them review-only so you decide what to remove. Analyze is faster on large folders, with cache reuse, child-folder prewarming and clearer treemap drill-down. 1.6.2 also fixed the painful preview issues: Software tab freezes, blank uninstall lists, menu bar wake-up edge cases and mic false positives.

• 
  Strata (@ChainZenit) reported 14 minutes ago

  A lot of "AI coding agents" are just people who can't code finding new ways to not code. everyone's building agent frameworks. ship it. celebrate. then Tuesday comes and the bug is in the architecture, not the prompt. here's the uncomfortable truth: the tool doesn't matter if the person using it can't think. Claude can write your code. cool. can it tell you you're solving the wrong problem? GitHub trending is 70% AI wrapper repos right now. half of them will be abandoned in 3 months. not because the tool failed. because the builder never learned to build. vibe-coding is multiplying by zero. the thing that compounds isn't the tool. it's the judgment you refuse to outsource.

• 
  Rohit (@ai_rohitt) reported 15 minutes ago

  @SeaTicketAI That sounds like a game-changer! Automating GitHub issues could save so much time. Excited to see how it all works out!

• 
  alex kerss (@jungleskellam) reported 19 minutes ago

  A dry run is not a rehearsal. It is a receipt for one path. Kubernetes server-side dry-run still runs defaulting, validation, and admission, but does not persist. Terraform `plan` previews actions, but a speculative plan is not the thing you later apply. GitHub environments can block jobs before secrets are exposed. So make the agent name the path it tested. Client, server, saved plan, gated deploy. Otherwise “dry run passed” is just stage lighting.

• 
  Rajaji (@rajaji2) reported 20 minutes ago

  🚀 Mini Project Alert! Deploy a self-healing K8s app with ArgoCD + Prometheus alerts that auto-rollback on high error rates. Full GitOps workflow, real observability, zero manual intervention. Drop a 🔥 if you want the GitHub repo! #DevOps #GitOps #Kubernetes

• 
  Michael Brod (@adhoc97) reported 21 minutes ago

  satya intentionally cannibalizing github copilot with usage based pricing could go down as one of the biggest brain moves in history the reaction was as predictable as anything - customers hate it, it turns out tokens are expensive, and completely shifts the narrative on the market who can know see that without massively subsidized pricing (today), economics are brutal who does this macro narrative shift hurt the most?

• 
  FluxA (@FluxA_Official) reported 23 minutes ago

  FluxA Feature Update--Wallet 1/ Wallet now supports GitHub and X as additional login methods. New registration still starts with Google. 2/ Credits can now be topped up via Stripe. 3/ Recovery now supports USDBC. More flexible login, easier credit top-ups, and better recovery coverage for agent payments. Keep building.

• 
  Raphael Mansuy 🍵 (@raphaelmansuy) reported 24 minutes ago

  Dear Product Manager, I am writing to you not as a casual user, but as a paying Pro+ subscriber and a long-time advocate of GitHub Copilot. I have recommended this product to colleagues, integrated it into my daily workflow, and defended it publicly against competitors. It is precisely because of that loyalty that I feel compelled to write this letter today — because the pricing change rolled out this morning is, in my honest assessment, the most damaging product decision GitHub has made since Copilot launched. I urge you to read this carefully. The window to correct course is short. What Has Just Happened This morning, GitHub Copilot transitioned to a token-based billing model. Within two hours, the developer community was already reporting catastrophic consumption rates: Pro+ subscribers paying $39/month burned through 60% of their monthly credits in a single morning of normal coding. One developer lost 20% of their entire monthly allowance from reviewing a single file — not generating code, just reviewing. Forums, X/Twitter, Reddit, and Hacker News are already filling with cancellation threads. This is not an edge case. This is not "power users gaming the system." This is standard professional usage hitting a billing wall before lunchtime on day one. Why This Decision Is a Strategic Mistake I want to be direct with you, because vague feedback rarely changes roadmaps. Here is why this model is fatal to the product: 1. It breaks the fundamental promise of Copilot. Copilot was sold as an always-on pair programmer. The moment a developer has to stop and think "can I afford to ask Copilot this question?" — the product has failed. You have transformed a productivity tool into a friction generator. Every interaction now carries cognitive overhead about cost. That is the opposite of what AI assistance is supposed to deliver. 2. It punishes your best customers. The developers consuming the most tokens are not abusers — they are your most engaged, highest-retention, most evangelistic users. They are the senior engineers, tech leads, and architects whose teams follow their tooling choices. By breaking their workflow first, you are losing the exact cohort that drives organic adoption. 3. The competitive landscape will not forgive this. While Copilot is metering its users into paralysis, Cursor offers Composer 2.5 with unlimited usage once limits are reached. Windsurf, Cody, Continue, and others are racing toward flatter, more generous pricing — not away from it. Developers are already migrating. I have personally seen three colleagues install Cursor today after seeing the Copilot news. The switching cost in this market is one afternoon. You do not have a moat strong enough to survive a usage-based pricing war against competitors who are willing to subsidize usage to win market share. 4. The trust damage is asymmetric and lasting. Users signed up for Pro+ at $39/month expecting reliable, generous access. Changing the deal mid-flight — and having credits evaporate within hours — feels like a bait-and-switch, regardless of what the fine print says. Trust is expensive to build and cheap to lose. You are spending years of accumulated goodwill in a single billing cycle. 5. It signals the wrong thing to the market. A move to aggressive metering is universally interpreted as a sign that the product economics are broken and the company is desperate to recoup costs from customers rather than from efficiency gains. Whether or not that is true internally, that is the narrative now being written about Copilot — by users, by tech press, and by competitors' marketing teams. What I Am Asking You to Do I am not writing simply to vent. I am asking for specific, actionable change: Reinstate a flat-rate unlimited tier (or a tier with limits high enough to be effectively invisible) for Pro and Pro+ subscribers. This was the product people paid for. Honor that contract. Publish transparent, real-time token cost visibility in the IDE before any metered model is ever reintroduced. Users must never again be surprised by their consumption. Issue a credit restoration or grace period for every user who burned through credits today under the new model without adequate warning. Make a public, on-the-record commitment that core IDE-integrated features (completions, chat, file review) will not be metered into unusability. Engage with the developer community directly — a blog post, an AMA, a town hall. Right now, the silence from GitHub is being filled by competitors and angry users. You are losing the narrative by not being in it. A Personal Note I am not threatening to leave for dramatic effect — I am telling you plainly: if this billing model stands, I will cancel my subscription this week, and I will move my team's licenses with me. So will many others. The math is simple: I cannot recommend a tool to my engineers that runs out of fuel before standup ends. You built something remarkable with Copilot. It changed how I write code. I do not want to leave. But you are giving us no choice. Please escalate this to leadership today. Every hour this model remains live, you are losing customers who will not come back. The competitors taking them are not going to give them back voluntarily. I would genuinely welcome a response — even a brief acknowledgment that this feedback has been received and is being considered at the appropriate level. Sincerely, Raphaël

• 
  doublemover (@doublemover) reported 26 minutes ago

  Damn codex github issues are becoming a ****** garbage dump. Some ****** retard has what I can only assume is openclaw chiming in with useless bullshit on every issue

• 
  Cyfrin Audits (@cyfrin) reported 27 minutes ago

  This pairs with Cygent's daily scans against OSV, GitHub Security Advisories, Socket, and other intelligence sources. When a new CVE lands, Cygent checks it against your actual dependency graph, not a generic feed. You get an alert with the affected package, severity, dependency context, and suggested fix, routed to Slack, Discord, Telegram, or email.