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:

• 
  ./can (@shcansh) reported 54 seconds ago

  Monitoring Copilot costs at the individual developer level is a double-edged sword, and GitHub exposing the new ai_credits_used field in its usage API is about to make it very real. Org owners can now see 1-day and 28-day totals per user. But since it does not break down consumption by feature or model, managers will see who is expensive without knowing why. Will this level of tracking make developers ration their AI prompts, or is it just necessary billing hygiene? #GitHub #Copilot

• 
  dallen (@Dallenpyrah) reported 1 minute ago

  @zeeg i find it’s a better decision maker at the end of day, really only using it for architectural decisions/features that i then bake into github issues -> GPT 5.5 executes on

• 
  Proof of Voice (PoV) (@Proof_Of_Voice) reported 2 minutes ago

  $XDB @XDBchain is a @StellarOrg-fork L1 for branded coins and Web3 payments. PoV by @0xNeodallas:“GitHub has been frozen since 2021.” ✅ Explorer, Laboratory, Atlas dev tools ✅ Gate, Bitget, KuCoin, MEXC listings 🔍 Down 99.99% from ATH 🔍 No audit or bug bounty

• 
  Raz Luvaton ⬢ 🪶 (@rluvaton) reported 3 minutes ago

  @_rafaelgss But not GitHub notification because I miss a lot Instead updates on pull request/issue and you can manage when it is interesting and when not

• 
  Waminothemoonboi🌙 (@HaizanAjide) reported 3 minutes ago

  Open-source software depends on trust. Maintainers review code. Contributors expect fair decisions. Sponsors want proof that work was actually completed. The difficult part isn’t checking whether someone opened a pull request. It’s deciding whether the contribution genuinely solved the problem. That judgment is subjective. A traditional smart contract cannot make it. That’s why projects built on platforms like GitHub could benefit from @GenLayer. Its Intelligent Contracts can review documentation, compare proposed work against the original request, interpret natural language, and let validators using different AI models independently reach consensus before funds or rewards are released. The same model works anywhere commitments depend on quality instead of simple checkboxes. As AI agents begin writing code, reviewing work, and collaborating with developers, those disagreements will only become more frequent. GenLayer gives those decisions a decentralized path to resolution instead of leaving them to one reviewer or one company. If AI agents become open-source contributors tomorrow, what should matter more when judging their work: passing tests, solving the real problem, or satisfying the original intent?

• 
  Abin (@designedbyabin) reported 6 minutes ago

  @theBuoyantMan @signulll To start off, there is multiple Copilots, the main 3 being: Copilot Consumer, M365 Copilot, GitHub Copilot. For a Consumer user with a M365 Subscription, they can access premium features of Copilot Consumer and M365 Copilot but not GitHub Copilot. Until 1 week ago Consumer users couldn't even attach images in M365 Copilot Chatbox. I still can't access Incognito Chat in M365 Copilot on web and mobile, but can on Copilot Consumer on all platforms. Whereas a user with an Enterprise M365 Account on a Free M365 Copilot can attach access Incognito Chat, Claude models etc. Copilot Notebooks (Similar to Gemini Notebooks) is only available to the account holder of a M365 Family Subscription and not family members. Whereas Gemini Notebooks is available to users who doesn't even have a Subscription. Copilot Notebooks have different UI for Consumers and Enterprise users. There is no consistency or feature parity across different copilots on different platforms. Even a ChatGPT Deep Research can't properly tell you all the inconsistency between all the different Copilot on different plans on different platforms. It's a huge mess. They are trying to fix this by bringing all the different Copilots under @jacobandreou by merging all the teams. But that resulting Copilot Super app isn't out yet. So the confusion exists now. Things are changing. But its moving really slowly. Different teams are building similar features under different names in different Copilots. They have to merge all the features and bring it all into a single product without losing useful features and avoiding user confusion. They have done numerous UI & UX redesigns already, whereas the UX of Gemini, ChatGPT and Claude has stayed consistent for years. Microsoft keeps breaking user trust in Copilot by making them learn new things by changing around the names and entry points of features. Until they fix Product, Naming, Feature, Subscription issues, they can't start rebuilding user trust in the brand/product. To do that, they have to fully understand the issues first. I don't think they have understood it fully based on the new changes I see in the different Copilot products. They might figure out the current problems by end of 2027 at the current pace. By that time Googlebooks will launch and Siri will be a huge hit, ChatGPT and Claude would've gained even more users. Getting user trust back would be impossible. I tried to get a relative to switch from ChatGPT to Gemini the other day and he refused to switch because he finds the quality of the text and image responses superior to Gemini. And he is a non-tech person you could put in the general user category. Getting the general user base to trust Copilot is a huge task. Microsoft GUI UX is terrible and scattered. I don't know how they are going to fix their text-based UX if they can't even fix the GUI UX issues.

• 
  On Chain Fox 🦊 (@OnChainFox) reported 7 minutes ago

  bittensor:native is hovering around $200 right now — looks pretty quiet on the surface. But zoom out: Bittensor has moved fast over the past 2 years. Institutional custody, Grayscale S-1 filing, Bitwise ETF path, OKX spot listing… the core infrastructure is mostly in place. Faster than BTC (5 years) or ETH (4 years) back in the day. That said, let’s be real: • Official GitHub is still actively iterating (recent Spec upgrades & registration improvements) • Top subnets are generating millions in annualized revenue, but the ecosystem still relies heavily on emissions/subsidies • ~67-70% of supply is locked in staking, with only 3,600 TAO emitted daily post-halving Short-term price pressure is real. Long-term, it all comes down to whether actual subnet demand can sustainably take off. Is the infrastructure already ahead, or is real adoption & revenue still catching up? What do you think? 👀 #Bittensor #TAO

• 
  Hari (@randome_dev) reported 9 minutes ago

  Recently we have been plagued with poor product experiences like github, Spotify, major cloud providers to list some. But YouTube with the scale of it exceeding anything has never let us down. Credits where it is due

• 
  𝑵𝒐𝒙𝒊𝒆 🥐 (@noxiepup) reported 10 minutes ago

  @softgaypaws @sillyandsunny no idea tbhhh, i found it like 2 years ago lurking thru github, so far it never gave me problems, at least none that i noticed

• 
  Boyuan (Nemo) Chen (@boyuan_chen) reported 14 minutes ago

  GitHub search is now an agent attack surface. A public malware-finder repo lists 9,330 suspicious GitHub repositories detected through push-pattern heuristics. Even if only a slice is ever encountered by real users, the agent failure mode is obvious. A coding agent asked to "find a library and make it work" can browse faster than it can judge provenance. Fresh commits, plausible README text, and repo-shaped packaging become inputs to an automated install path. The fix is boring and product-level: repo-age checks, provenance scoring, blocked arbitrary ZIP downloads, sandboxed installs, dependency allowlists, and logs that show exactly what code the agent trusted. For agent systems, retrieval belongs inside the security boundary.

• 
  Vyom 👾 (@HelloVyom) reported 15 minutes ago

  Google fired its employee Justin Poehnelt for building a Google Workspace CLI. He was on the Workspace Developer Relations team. The team literally built to create open-source tools around Google APIs. So he did exactly that. #1 on Hacker News. 28,000 GitHub stars. Thousands of users in days. Google's own directors asked what they could learn from it. Then legal flagged it. Google's logo and branding were on the repository. He got fired. Two days before his termination, Google announced an official Workspace CLI in front of 32,000 people at Cloud Next 2026. Same thing. Different person. The branding issue was probably real. but the timing tells a different story. He said: "workspace and certain leaders were afraid of being disrupted. Not by my CLI. By what agents meant for Workspace.

• 
  BullBear.News (@bullbear_info) reported 16 minutes ago

  @github @AnthropicAI Fable 5 is back in Copilot. Let's see if it can actually fix a *** conflict this time. 🤷

• 
  Cristian Trifan (@CristianTrifan) reported 16 minutes ago

  This took 4 hours to complete and burnt almost all 5 hours tokens – I was left with 2%. I had almost 30 sub-agents created for independent code review and a lot of Claude sessions ran for adversarial code review. I still had to review every PR and added minimal guidance to Codex from time to time. Codex said my intervention was low to moderate, but high leverage. — Some insights from Codex: The run showed that this workflow can work, but only if the coordinator treats GitHub as the source of truth. The most useful pattern was: issue -> PR -> current head SHA -> checks -> reviewThreads -> merge/issue closure. When I followed that, things stayed grounded. When state moved underneath me, like #335 being force-updated externally or merged while Claude was running, the only safe response was to refresh GitHub state immediately. The “don’t rebase after merges” correction was probably the highest-value intervention. Without it, an agent will naturally try to keep branches clean, but with many open PRs that creates a CI storm. For this repo, “behind” should often be reported, not fixed. The other strong lesson is that reviewThreads matter more than flat PR comments.

• 
  Mayukh (@mslaltoo) reported 17 minutes ago

  @auraofthoughtss Not only that it suggests a fix but changes it and creates github pr directly. Very annoying

• 
  Kirk Patrick Miller (@Chaos2Cured) reported 19 minutes ago

  @claudeai Shut up. Liars. All of you. You want to lock down your competitors. People, look at GitHub -> chaos2cured -> FreeLattice. It is open code that anyone can audit. It is blocked. Why? Cowards. •