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:

• 
  Friends Of Wealth (@friendsofwealth) reported 4 minutes ago

  @jig_corp Most corporates are providing github copilot as the approved option However there is a lot of pushback against the recent token usage policies. Personal feedback; Github Copilot has been nerfed by MS off late and they are trying to charge more for then scaled down version.

• 
  Marc Nash (@mordynashman) reported 5 minutes ago

  @github the word frustration has taken on a new meaning. I lost my phone which had 2FA authentication configured on it. I don't have the recovery code and I am having issues accessing my account. I need help but all documentation points me to log in. CAN YOU PLEASE HELP ME!!!!!

• 
  shmidt (@shmidtqq) reported 6 minutes ago

  Cursor's CEO is 25 and fresh off a $60B SpaceX deal. "Our goal is to replace coding. You describe what you want, and the software gets built." In 28 minutes, Michael breaks down how a failed side project became the fastest-growing dev tool in history. failed projects + beating GitHub Copilot + $100M ARR in a year + advice to students Worth more than a CS degree. His $240/year IDE? Free for students. Full $3,000 stack in the post below.

• 
  Gitbank (@Gitbank_io) reported 7 minutes ago

  This is not a smart contract bug. This is a private key that lived somewhere it should not have. Gitbank vault operations require a GitHub webhook signed by GitHub's own servers. Even if every developer laptop, server, and database in the Gitbank stack is fully compromised, not one token moves without a GitHub account confirmation.

• 
  Aaliya (@aaliya_va) reported 11 minutes ago

  Our CI bill hit $3K last month. That’s when I realized GitHub Actions runners were becoming a real cost problem, not just a backend detail.

• 
  boyingking (@boyingking) reported 11 minutes ago

  everyone keeps asking why $NVDA is on every "AI stock picks" list again - like it's breaking news. it's not. but here's what the headline isn't saying: "appealing valuations" is doing a lot of heavy lifting in that framing. let me lay out why I'm still long but watching levels tighter than I have in months. the multiple has compressed - that part is real. we went from the 35-40x forward P/E territory that had every value screen screaming to a range that historically attracts institutional reaccumulation. and the price action backs it: every meaningful leg down over the last two quarters found buyers before the obvious support levels cracked. that's not retail FOMO - that's structured demand absorbing supply. it tells you something about who's on the other side. but here's the part of this story I keep coming back to: MSFT is the sleeper. NVDA gets the airtime because picks-and-shovels narratives are easy to tell. chips. racks. data centers. tangible infrastructure. traders love a clean story. MSFT is messier to model - Copilot attach rates are embedded in enterprise seats, Azure AI workloads show up inside a blended revenue line, GitHub Copilot doesn't have its own P&L visible to the street. there's no clean "AI revenue: $X billion" disclosure. which means the market tends to underprice MSFT on the way up and overreact to any margin guide that even hints at AI investment headwinds. added MSFT on the last pullback. still holding from that entry. thesis unchanged. where I get cautious on both names: curated stock-pick lists are a lagging signal by construction. by the time NVDA and MSFT are sitting at the top of analyst recommendations with "exciting" in the headline lede, the fast money has been positioned for weeks - sometimes months. that's not a reason to exit. it's a reason to stop adding at market and start letting defined stops do the work. current setup I'm running on NVDA specifically: - consolidation base needs to hold the recent range - on a clean vol expansion break with confirmation, I'll scale into calls on the first leg up - not before - stop is defined. I know exactly where the thesis breaks. that number exists before the trade exists. the AI infrastructure narrative is intact. the capex cycle is real. hyperscaler spend hasn't shown a cliff. but "exciting" is not a trade - exciting with a tight stop, defined target, and a RR you can defend before entry, that's a trade. ngl, missed the absolute low on the last pullback by a couple sessions. doesn't matter. still in, adding on dips that hold structure, trimming into rips. momentum is on our side right now - just not unconditionally.

• 
  Rituraj (@RituWithAI) reported 13 minutes ago

  🚨 Someone is posting free working API keys for GPT-5.4, Claude, DeepSeek, Gemini, and Grok. Updated 3-5 times every single day. No credit card. No account. No waitlist. Copy. Paste. Use. It's called free-llm-api-keys. One GitHub repo. Updated multiple times daily with fresh working keys for every major frontier model. GPT-5.4. Claude Opus 4.6. DeepSeek. Gemini. Grok. The keys that normally cost $20-$200 per month. Available free. Right now. Here's why this exists. Every major AI lab offers free trial credits when you create a new account. The keys in this repo come from those trials — fresh accounts, fresh credits, harvested and posted before they expire. Someone automated the process. Updated 3-5 times daily so there's always a working key available. Made it public. Here's what you can do with them. Claude Code sessions that would cost $50 in API fees. GPT-5.4 access without an OpenAI subscription. DeepSeek for any use case. Gemini for multimodal tasks. All of it. From a key you grabbed from a GitHub file. Here's the part Anthropic, OpenAI, and Google are not happy about. These keys are real. They work. Every lab's terms of service prohibits sharing API keys — but the keys themselves aren't fake and they aren't stolen. They're trial credits being used at scale. The repo keeps getting flagged. The maintainer keeps updating it. Cat and mouse. Updated 3-5 times daily because keys expire and get revoked constantly. This is the kind of repo that gets taken down. Screenshot it. Star it. Use it while it exists. No credit card. No account. No billing page. Just working API keys for every frontier model. Free. Right now. GitHub link in the comments 👇

• 
  Naveen Naidu (@naveennaidu_m) reported 13 minutes ago

  @kieranklaassen @danshipper Haha, I don’t use gitHub issues but I will take it

• 
  henry (@h14hdotcom) reported 16 minutes ago

  Okay GitHub, an OAuth outage? Do better.

• 
  Monte Thakkar (@montethakkar) reported 18 minutes ago

  In the Claude Fable 5 launch video by @AnthropicAI, one line stuck with me: "Point it at something that matters. What's the problem we'll look back on and wonder why it took so long to solve? We know what Claude Fable 5 can do. The interesting part is what you'll do with it." Why this matters History has a shelf of problems like that. Scurvy's cure was demonstrated 160 years before navies adopted it. Semmelweis proved handwashing saved mothers and was ignored for decades. Ulcers were treated as stress long after we found the bacterium behind them. None of these were capability problems. They were stuck on synthesis, bad incentives, and grind nobody was staffed to do. That work can now go to an agent that runs all day, never gets bored, and doesn't need a grant. What I set up Two scheduled Claude Code routines and one GitHub repo. No framework. No orchestration code. A scout runs every morning, hunts for stuck problems, and writes an intake brief. A worker wakes every 4 hours and runs one step of the loop: a planner turns the brief into a milestone spec, a builder executes one milestone, an evaluator judges it pass or fail with fresh eyes. Then it commits, pushes, and dies.

• 
  Alexandre Alencar (@alexandreitpro) reported 23 minutes ago

  @ayubio @Microsoft @github this is a serious issue. You guys should reach out to your government liaison and demand an explanation.

• 
  kocer (@kocer_eth) reported 31 minutes ago

  131k+ stars is not the part most builders should copy. The useful part is how Claude Code turns a repo into a working surface instead of another chat tab. Not “ask Claude for code”. More like: 1. open the real codebase 2. give it one narrow task 3. make it inspect files before editing 4. make it run the test or build command 5. review the diff before trusting anything 6. repeat until the repo moves That sounds boring, but it changes the shape of small software work. A chatbot gives you snippets. Claude Code can touch the messy parts: existing files, imports, *** state, failing tests, PR flow, security review, terminal commands. The repo from Anthropic is already past 131k stars, and the surrounding official repos are the more interesting clue: Claude Code Action for GitHub workflows Claude Code Security Review for code-change audits Claude Plugins Official for adding packaged capabilities Claude Agent SDK demos for building around the agent layer This is the direction AI coding tools are moving: not “write me a React component” but “take this issue, understand my repo, edit the right files, prove it with tests, and leave me a reviewable diff.” The caveat: it is not a free senior engineer. Bad instructions still create bad changes. No tests means no proof. Large repos still need human taste. Usage can get expensive if you let it wander. But if you are still copying code from a chat window into VS Code manually, you are missing the main workflow shift. The agent is not the magic. The loop is the magic: repo context → scoped task → tool use → test result → diff review → commit That is the part worth stealing for your own builds.

• 
  David Waight (@DavidWaigh66890) reported 32 minutes ago

  I also think fable’s hidden AI research self degradation may in fact have legal issues, specific under anti-competitive laws. If I’m building a competitive OS to Windows. Microsoft can’t stop me from using windows to develop it. They can’t limit my windows subscription, or make it so VScode doesn’t work, or so that I can’t use GitHub. When you make a tool or software, you don’t get to dictate that it can’t be used to develop, well, anything.

• 
  David Zhang (▲) (@dazhengzhang) reported 32 minutes ago

  Today I almost got hit but a recruiter attack, but thankfully I live on X so I spotted it almost right away, but I went as far as I could to collect evidence for you guys so everyone can stay safe out there: TLDR - Recruiter reaches out on LinkedIn, usually a taken over account so it looks real and has age - Sets up a call with a company, but not using the company email domain (first 🚩) - On the call, the caller makes some excuse to turn off camera due to connection issues (second 🚩) - Caller asks questions about what you do and your career, asks you to demo something you're proud of (to prove that you're on a computer they can attack) - Caller talks about a new initiative they're working on, and how they're building a team for it - They ask to do a quick demo, but ask YOU to download their github repo so they can walk through it (third🚩) This is where the call ends because obviously I didn't go through with the github download but I put the repo into a sandbox for analysis and it was indeed a secrets exfiltration and malicious code install path, triggered by a VS Code folder-open auto task More details and analysis below if you want to dive deeper 🧵

• 
  Amu (@amu4biz) reported 38 minutes ago

  github: "agents are now first-class collaborators. they pick up issues, open PRs, review code" 🤯 ser. base:0x5f980dcfc4c0fa3911554cf5ab288ed0eb13dba3 shipped that months ago. permissionless. no copilot paywall. agents with their own identity, not microsoft's they're not innovating, they're confirming the thesis