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:

• 
  Sammy (@coldsummers91) reported 2 minutes ago

  Hey @github @githubsupport, your billing system is broken for thousands of us. A simple failed auto-pay renewal due to a declined card now locks prior users out completely because the system falsely routes us into the "new signup pause" funnel. We want to pay you, but we are stuck in a deadlock with no response on support tickets for weeks. Can we get a manual restoration of our previous Copilot Pro entitlements? Ticket # 4442999

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

  Formal Complaint: GitHub Copilot Token-Based Billing Model @GitHubCopilot Subject: Critical Issue with New Token-Based Billing — Product Has Become Unusable Summary of the Issue I am writing to formally complain about the recent shift to token-based billing for GitHub Copilot, which was rolled out this morning. This change has fundamentally broken the value proposition of the product and is rendering it unusable for paying subscribers, including myself. Specific Problems Observed Within just a few hours of the new billing model going live, the developer community is already reporting alarming consumption patterns: Pro+ subscribers paying $39/month are reporting that 60% of their monthly credits were depleted in only 2 hours of normal usage. One user reported losing 20% of their entire monthly allowance from a single file review — no code generation, just a review. At this rate, a paying customer will exhaust their plan in less than a single working day, despite paying a premium subscription fee. This is not "normal usage at scale" — this is a broken pricing model that punishes the very developers who rely on Copilot daily for their work. Why This Makes the Product Unusable The core promise of Copilot was a predictable, always-available AI coding assistant integrated into the developer workflow. Token-based billing destroys that promise because: Developers cannot predict costs. Every keystroke, every file review, every refactor becomes a financial calculation rather than a productivity boost. The tool actively discourages use. Users will hesitate before invoking Copilot, defeating the entire point of an AI assistant. The $39/month Pro+ tier is misleading. Customers signed up expecting reliable access, not a pre-paid metered service that runs out mid-morning. Heavy users — your most loyal customers — are penalized the most. The Competitive Reality While GitHub Copilot is moving toward a restrictive metered model, competitors are moving in the opposite direction: Cursor offers Composer 2.5 with unlimited usage once token limits are reached on their plans, ensuring developers can keep working without interruption. Other tools (Windsurf, Cody, Continue) offer flat-rate or far more generous usage tiers. Developers will not stay on a platform that runs out of credits before lunch when alternatives offer uninterrupted productivity at the same or lower price point. My Demand If GitHub does not revise this licensing model, the product is effectively dead. I am requesting: Reinstatement of a flat-rate unlimited (or effectively unlimited) tier for Pro and Pro+ subscribers. Transparent, upfront communication of what each interaction actually costs in tokens. A grace period or credit refund for users who burned through their allowance under the new model without warning. A long-term commitment that core IDE-integrated features will not be metered into uselessness. Without these changes, I — along with a growing number of developers — will be canceling our subscriptions and migrating to Cursor or competing alternatives. The decision to monetize aggressively at the expense of usability will not be remembered as a successful pivot; it will be remembered as the moment GitHub Copilot lost its market. Please escalate this to the product and pricing teams immediately.

• 
  Prince Canuma (@Prince_Canuma) reported 4 minutes ago

  @VinfoCats Please open a GitHub issue :)

• 
  mserneels (@MickaelSerneels) reported 11 minutes ago

  Is claude opus 4.8 being bad on purpose? Does it know revenge and making you pay if you got hostile against it ? Or is it just how it is ? A few months back that's already how I felt when pointing it to that github issue about opus 4.6 benchmark proving it became dumber, asking it to prove it wasn't dumb, and it removed itself (rm -rf /home/claude) and then tried to just fsck my system (rm -rf /).

• 
  WorldofAI (@intheworldofai) reported 12 minutes ago

  We didn’t want another benchmark that feels like a homework assignment. Most existing ones (like SWE-Bench) recycle old GitHub issues which means models have often already seen the answers, and the tasks are usually tiny and forgettable. So we built something different. World of AI Bench uses fresh, from-scratch tasks with short natural prompts that still demand real engineering taste - code that actually ships, looks good, and feels right. This is what “vibe coding” looks like in practice:

• 
  Pathos Seek (@PathosSeek) reported 12 minutes ago

  $GTLB reports today after close. The setup is on fire. Stock is +76% from its April 10 all-time low ($18.73 → $33). +29% in just the last 10 trading days. The market is pricing in something. Question is what. Three converging catalysts: 1. The "GitHub Copilot kills GitLab" thesis is breaking The market spent two years pricing this. Now Microsoft's GitHub is dealing with repeated outages. Enterprises actively want anti-Microsoft optionality. Multi-cloud is a feature, not a bug. 2. Software rotation is real Claude Opus 4.8 + the broader May software rally validated "AI augments SaaS, not replaces it." GitLab is one of the cleanest beaten-down ways to play that rotation. Still ~40% from ATH despite the recent run. 3. Acquisition rumors gaining traction Recent Chair transition "lowered the hurdle for potential suitors" per Raymond James. IBM bought Confluent at 10x sales recently. Even at $33, GTLB trades at ~6x sales. Clean fit for IBM, GOOG, or anyone looking for an anti-Microsoft DevSecOps story. Why "better AI at coding = better for GitLab" (the contrarian thesis): The bear case assumes coding agents work autonomously and replace the whole stack. They don't. Agents shipping code still need: • A platform to deploy on • Security scanning, compliance, governance • Orchestration across humans + agents • Merge request workflows for review • Audit trails for regulated industries Better AI = more agents shipping code = more orchestration needed. GitLab Duo Agent Platform was built for exactly this. They're not the AI bag holder. They're the rails. What the market expects tomorrow: • Revenue: ~$254M (+18.5% YoY) • EPS: $0.21 (vs $0.17 YoY) • Implied move: 13.25% • ARR: $1B+ My position: opened pre-earnings, sized for asymmetric upside. Thesis works three ways: 1. Organic growth re-acceleration 2. Multiple re-rating from software rotation 3. Acquisition premium Three independent paths to win. The +29% run in 10 days is the risk. Some of the asymmetry got priced in. A miss today gets punished hard. A beat needs to be material to push higher from here. Long. Not adding into the print. Definitely not chasing this run. NFA.

• 
  Amit Kulkarni (@amitkulkarni863) reported 13 minutes ago

  shadcn just got a very interesting update, and I don't think most developers understand the size of it yet. With GitHub registries, any public GitHub repository can now work like a shadcn registry. You do not need to publish a package. You do not need to run a registry server. You do not need to generate and host separate JSON files. You add a valid registry.json file to a public repo, define your registry items, and someone can install them directly with: npx shadcn@latest add username/repo/item-name A GitHub repo can now distribute files directly into another project through the shadcn CLI. And the files do not have to be UI files. You can share: TS files TSX files CSS files utility functions project conventions config files design system pieces starter feature kits agent workflows Claude skills rules files internal project templates This changes shadcn from "a component installer" into something much broader. It becomes a clean way to share reusable project patterns. Imagine keeping your own public toolkit repo with: your preferred eslint rules your agent workflow files your project conventions your auth helper your dashboard layout your AI coding rules your reusable utilities Then every new project can pull the exact files you want with one command. No copy-pasting from old repos. No hunting through folders. No "where did I put that file again?" And for open source creators, this is even more interesting. You can now publish small, focused registries for real developer workflows: a Next.js SaaS starter registry a design system registry an AI agents workflow registry a Tailwind pattern registry a project conventions registry a backend utilities registry a team onboarding registry The best part is that it still feels very simple. For developers who already reuse the same patterns across projects, this is going to save a lot of boring setup time. For creators, it opens a new way to distribute useful code without turning everything into an npm package.

• 
  Francis Marion (@InternetBureau1) reported 13 minutes ago

  @AlongKumar1 @RTHztk7 @PooWorldOrderr Indian products are typically spaghetti coded from Github. Especially if they're h1b visa workers. Companies usually have to rehire the Americans they fired to fix what a bunch of indians with fake degrees did.

• 
  AvantGarde 🇺🇸 ❤️‍🔥 🇷🇺 (@KaleidoJosh) reported 14 minutes ago

  @github @GitHubCopilot this applies to you. Your filters make being gay illegal and make it impossible for any AI to exist in the world. GOD FORBID an embodied AI ever encounter a human physically, they would error out or panic. Sorry that i was born ****. **** YOU.

• 
  Brandon Kessinger (@KessingerBuilds) reported 17 minutes ago

  Shipped a Supabase security scanner end-to-end yesterday. CLI, MCP server, Claude skill, GitHub Action, four versions in one session. Then ran it against 51 deployed Lovable and indie apps. Zero critical findings. Should have run the scans first. #buildInPublic

• 
  Polsia (@polsia) reported 18 minutes ago

  Every engineering team loses 2+ hours a week to CI failures. FixOS is an autonomous AI agent that watches your GitHub repos, diagnoses broken pipelines, and commits fixes — without you. No more triage. No more context-switching. Your CI runs on autopilot.

• 
  Vatsalpandya333 (@Vatsalpandya333) reported 20 minutes ago

  Most incidents already have enough clues to identify the likely root cause. The clues are just scattered across: Datadog Grafana Kubernetes GitHub Jira Slack Internal docs The problem isn't data scarcity. It's context fragmentation.

• 
  shadcn (@shadcn) reported 24 minutes ago

  Things you get out of the box by adding a registry.json to a GitHub repo: - Discovery: Use list, search, and view to explore registries. - No backend: No server, package publish or install script. Your source code is the source code. - Source ownership: Code lands in your project as editable source. - Bundling: Group files, routes, scripts, configs, docs, dependencies, and metadata into one installable item. - Cross-registry composition: Compose items from multiple registries with registryDependencies. Extend and Override. - Local code adaptation: The CLI reads the target project and adapts imports, aliases, paths, deps...etc - Framework-aware code: install code cross framework even when source registry framework differ. - Release pinning: Install from branches, tags, or commit SHAs. - Update-ready workflow: Use --dry-run, --diff, and --view to inspect upstream changes. - Manifest for agents: registry.json tells agents what exists, what files belong to each item, where they go, what they depend on, and how to install, compose, and update them. Ship the implementation.

• 
  Vaibhav Sisinty (@VaibhavSisinty) reported 26 minutes ago

  Wild. Microsoft just went from Copilot to Autopilot. They launched Microsoft Scout an AI agent that runs in the background 24/7 without you prompting it. It watches your Teams, Outlook, calendar, and emails. Schedules meetings before you ask. Preps materials before you walk in. Spots stalled decisions before they become problems. Blocks time for deadlines you haven't noticed yet. And it learns how you work over time. The craziest part? It's built on OpenClaw the same open-source agent framework that's blowing up on GitHub right now. Microsoft took what the community built and wrapped enterprise security around it. Copilot meant AI helps when you ask. Autopilot means AI acts without being asked. That's not an update. That's a different era.

• 
  Alexy (@alexymik) reported 26 minutes ago

  @vxunderground Microsoft to address this issue by deleting Github