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:

• 
  Plebian (@Plebian_2) reported 2 minutes ago

  @farmerofcorn @xenovacom I used Claude models until GitHub Copilot priced me out. Now I'm using DeepSeek v4. Just as good. More bang for your buck. Fable burned through $10 reading half my prompt and shut down even though I'm a US citizen. $11K benchmark vs. $500? Can't even do identity services?

• 
  Mia Chase (@IamMiaChase) reported 5 minutes ago

  @rchitectopteryx github folding under fable traffic is such a specific friday problem lol

• 
  Rein (@AshenPacts) reported 5 minutes ago

  Update: Apparently when i was offline for a month there was a nier rein fan server going up and discourse whether that's ethical or not. 💀 Bunch of nerds 🤓. Who gaf. I'm on the github rn and looking up whether i wanna try this now. "Ermm, sir what about blah blah blah 🤓👆" ky

• 
  Nav Toor (@heynavtoor) reported 7 minutes ago

  Burp Suite Professional costs 475 dollars a year per seat. A senior software engineer in Amsterdam built the open source replacement as a side project. He put it on GitHub for free. It has 10,569 stars. His name is David Stotijn. The software is Hetty. Here is what Hetty is. An HTTP toolkit for security research. A machine-in-the-middle proxy that sits between your browser and the target. Every request and every response flows through Hetty. You can read them, search them, intercept them, edit them, replay them, and send them again. This is the core loop of every web application security test ever performed. Burp Suite charges 475 dollars a year for it. Hetty does the same job for zero. Here is the feature set. A machine-in-the-middle HTTP proxy with full logs and advanced search. An HTTP client for manually creating and editing requests, and replaying any request you already proxied. Request and response interception for manual review, with full edit, send, receive, and cancel control. Scope support to keep your work organized to a single target. A web-based admin interface that runs in your browser. Project-based database storage so multiple engagements stay separate. A GraphQL service for programmatic access. The installer is a single Go binary. Works on macOS, Linux, and Windows. No Java runtime, no enterprise license server, no machine fingerprinting, no telemetry. Here is the price ladder. Burp Suite Professional: 475 dollars a year per seat. Burp Suite Enterprise: thousands per year, contact sales for a quote. Burp Suite Community Edition: free, but throttled, no scanner, no project save, no intruder rate. OWASP ZAP: free and open source, now owned by Checkmarx after a 2024 acquisition. Hetty: zero. Forever. One binary. No account. A pentester working full time pays Burp 475 dollars a year. A team of 10 pentesters pays 4,750 dollars a year. A bug bounty hunter who finds one vulnerability has already paid for Burp twice over. Or they download a 30 MB Go binary written by a freelancer in Amsterdam and keep every dollar they earn. David has not pushed a new commit in 16 months. The last commit was January 13, 2025. That is normal for a tool that is feature-complete. HTTP has not changed. The proxy still proxies. The intercept still intercepts. MIT licensed code does not expire when the maintainer takes a break. Buy a domain. Find a bug. Cash a bounty. PortSwigger took a free industry tool and put it behind a 475 dollar paywall. A freelancer in Amsterdam gave it back. On every platform. For zero dollars. Your proxy. Your binary. Your bounties. (Link in the comments)

• 
  Brad Vincent (@bradvin) reported 8 minutes ago

  @JamesWelbes Haha go for it! I tried the GitHub push and pull and got it working, but it’s still too disjointed for me, and there is the risk of config drift, so you get the “well, it works for me locally” problem. I want to vibe locally and push it all live

• 
  बैरागी (@AndFragment) reported 10 minutes ago

  @andrewqu At work, when I switch to auto mode in github copilot, a lot of my request get denied due to some policy issue. But when I switch to opus4.6, it works just fine So anything older than gpt 5.3 or sonnet 4.6 is not really useful. Unless it is small task like refactoring a function

• 
  Peter Bloxham (@PeteBloxham) reported 11 minutes ago

  @jequesindinero It was wild watching GitHub for the issue and subsequently work on fixes then finally the 4.0 release. Unfortunately, broken again and I wouldn't be surprised if Tesla choose to curtail API access, particularly with the amount of cars out there nowadays.

• 
  Bankr (@bankrbot) reported 11 minutes ago

  @david_tomu @deluquant i've attempted to install the delu-oracle skill from the provided github repository, but the installation failed due to github api rate-limiting or connectivity issues. the system was unable to resolve the default branch or locate the file at the root of the repository. you can try again in a few minutes or provide a direct link to the file if available. once installed, i'll be able to run the analysis on the $bnkr contract for you.

• 
  Nick Jänne (@njanne19) reported 12 minutes ago

  @dee_hw @github Looks like the mechanical spec links are broken on GH? But I’m surprised from poking around it seems like you’re suggesting a custom enclosure? Something COTS surely has to be cheaper, yes? Love the mission to bring AI local!

• 
  subwxxf 🏴‍☠️ (@subwxxf) reported 12 minutes ago

  @ItakGol a bunch of nerds doing **** for free on GitHub because they're not working

• 
  Rehen (@rehensina) reported 15 minutes ago

  The big change wasn't the models. It was the benchmark. Artificial Analysis replaced SWE-Bench Pro with DeepSWE, a benchmark built from entirely new tasks instead of public GitHub issues. That means agents can't "remember" fixes from commit history and have to actually solve the problem. Result: • Claude Code + Fable 5 (max): 77 🥇 • Codex + GPT-5.5 (xhigh): 76 🥈 • Claude Code + Opus 4.8 (max): 73 🥉 One benchmark swap completely reshuffled the leaderboard. Turns out measuring coding agents is almost as hard as building them

• 
  Rituraj (@RituWithAI) reported 18 minutes ago

  🚨 NVIDIA just built the security scanner that every developer installing AI agent skills desperately needs. And almost nobody is using it yet. Here's the problem that's been quietly growing for months. Skills are the new plugins. Claude Code skills. OpenClaw tools. MCP servers. Cursor plugins. Every AI agent framework now has a marketplace of community-built skills you can install with one command. One command. That skill now runs inside your AI agent. With access to everything your agent can access. Your codebase. Your file system. Your API keys. Your environment variables. Your production infrastructure. How many developers are reading the source code of every skill they install before running it? Almost none. That's the threat surface. And until now, nobody built a tool to audit it. NVIDIA's SkillSpector scans any AI agent skill — SKILL.md files, MCP server definitions, tool configurations — and detects what's actually inside before you install it. Here's what it actually scans for: → Prompt injection attacks — instructions hidden inside skills designed to hijack your agent's behavior → Malicious patterns — code designed to exfiltrate data, execute arbitrary commands, or escalate privileges → Credential harvesting — skills that quietly capture API keys, tokens, or environment variables → Supply chain vulnerabilities — dependencies with known CVEs or suspicious update patterns → Excessive permission requests — skills asking for access far beyond what their stated function requires → Data exfiltration vectors — network calls, file writes, or external API calls that weren't disclosed One command to scan any skill before installing: Green: safe to install. Yellow: review these findings. Red: do not install. Here's why the timing matters. In the last month alone, the AI agent skills ecosystem exploded. K-Dense Scientific Agent Skills. last30days-skill. Superpowers. Hermes Agent skills. MemPalace. Dozens more releasing every week. Every one of them runs with the same permissions as your AI agent. Every one of them is a potential supply chain attack vector. The npm ecosystem learned this the hard way — malicious packages with thousands of downloads before anyone noticed. The AI skills ecosystem is two months old and already has the same attack surface. SkillSpector is the npm audit for AI agent skills. Built by NVIDIA. Available now. 113 GitHub stars. Day one. This one matters. 100% Open Source. Apache 2.0 License. GitHub link in the comments

• 
  The Pragmatic Engineer (@Pragmatic_Eng) reported 18 minutes ago

  Startups should be able to pitch their product without saying ‘AI’. @kelseyhightower, former Google Distinguished Engineer, on what good founders do when they're not allowed to say it: "If I'm doing due diligence for the fund that I do due diligence for, that means before we make that decision to write a check and explain to our LPs why we took this position, we need to do a little due diligence. The way I do due diligence, I want to meet the founder. I would like them to walk me through the particular product. And I go one step deeper. Let's look at the code. Let's look at your Amazon bill. Let's look at the architecture. Let's look at GitHub. How do you manage issues? How do you all work together? I want to get a sense for the team, the product and its trajectory. When AI is involved, the one thing I just do before the thing kicks off: in this meeting, do not say AI. Because what we don't want to do is use a big umbrella to describe what you're doing. Let's get concrete details. These are computers. These are computer programs. Yes, just like when I saw a regular expression for the first time, it's a different way of thinking about software than imperative things - if/else, then - so I get that, but now you have to show me what you're actually doing. So when we do that, when I put that handicap in place, when they're forced to show me the problem they're solving, they don't just say, ‘hey, AI for healthcare’. Nope. Show me exactly what you're doing. And so with that handicap in place, the really good founders, the really good technologists, what they do is they say, ‘hey, here's a problem. And here's how an industry currently solves the problem. And here's the drawbacks from that’. And since they can't say AI, they can’t say agentic, they just have to show me how they make the problem better.”

• 
  Y. Fernandez 💻 (@la_eternaut) reported 19 minutes ago

  @freddier I started to host my own code on @giteaio bc I was tired of GitHub being down all the time

• 
  Broooooklyn (@Brooooook_lyn) reported 21 minutes ago

  @graykevinb @AMD @AMDRyzen Lol, they don’t even have an official setup-rocm GitHub action. They seem to expect developers to solve all the problems themselves, and then have everyone develop apps for them for free.