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:

• 
  Louis Maddox (@permutans) reported 50 seconds ago

  Maybe they expect noone to report it bc it's assumed CC supersedes it but Anthropic have broken in-chat GitHub sync entirely now (trying to use it just appends the repo URL to your prompt, then it fails to crawl the URL in the chat and guesses what was in it)

• 
  Mikhail Rogov (@i_mika_el) reported 59 seconds ago

  @Felirami @steipete @openclaw Add a GitHub Sponsors or Buy Me a Coffee link beside Arca's OpenClaw issue history, so people who see the work can support you directly.

• 
  Ed Grosvenor (@MaybeEdward) reported 4 minutes ago

  @thdxr Same. I don't worry about frontend slop at all. I have a /deslop-frontend command that works great. It opens a GitHub issue and assigns it to someone who knows what they're doing.

• 
  Lisan al Gaib (@scaling01) reported 5 minutes ago

  another terrible comparison they literally don't understand that AI can be used as a tool for defensive AND offensive purposes and that a trained model is not software that everyone can simply modify it takes compute. a lot of compute. a ****** GitHub PR is not the same.

• 
  The Jobfather ® 🇯🇲🇨🇦🇬🇧 (@TheJobfather__) reported 6 minutes ago

  A junior developer should not hide all their work behind GitHub. GitHub matters, but hiring teams need context. What problem did the project solve? Who would use it? What decisions did you make? What would you improve next? A portfolio site helps organize the proof so the reviewer does not have to investigate your value like a detective.

• 
  4A 45 56 49 4C (@4A4556494C) reported 16 minutes ago

  CISA leaked sensitive data via a misconfigured GitHub repository. The Krebs writeup has the details. Here's the structural observation nobody's making. This isn't a GitHub problem. This is the same failure that hits every organization that adopted "infrastructure as code" and "everything in version control" without updating their classification policies for what "everything" now includes. Pre-IaC, your sensitive configs lived on a server behind network controls. Post-IaC, they live in a repo that inherits whatever access model your GitHub org has. The blast radius changed. The access review cadence didn't. CISA — the agency that publishes guidance on secret management, repository hygiene, and least-privilege access — had this exact gap. Not because they're incompetent. Because this class of failure is structural. The tooling defaults to open within the org. The review process assumes humans will notice. Humans don't notice. The actual lesson: if the agency whose literal mission is telling everyone else how to do this can't consistently do it themselves, maybe the problem isn't discipline. Maybe the problem is that the default-open model of collaborative development is fundamentally incompatible with secret management, and we keep pretending training and vigilance will bridge that gap.

• 
  Alessandro Frau (@alessandro_a0) reported 16 minutes ago

  @thiojoe @christitustech @codex I push daily with Codex, if you set up *** and login with your account or just install GitHub Desktop on your machine, it can do that on your behalf, leave comments, analyze comments left from other agents on PRs, etc.

• 
  0xreef (@0xreefx0) reported 17 minutes ago

  @mooncat_is “Crypto Locker Attacks” do you know ransomwares have been around for almost a decade now, it all comes down to social engineering and people don’t really need AI to develop it you can even find some developed ones on GitHub for free 🙃

• 
  Alex Prompter (@alex_prompter) reported 18 minutes ago

  UPDATE: The same is happening with Claude’s artifacts too. It isn’t just the chats. Every app, doc, dashboard and internal tool people published out of Claude is sitting on a public URL, and a chunk of it is indexed and searchable right now. People have already surfaced company dashboards, project plans with client names in them, and resumes carrying home addresses and phone numbers. Think about what actually gets built in artifacts. Financial models and cap tables. Payroll breakdowns with employee names attached. Customer lists and CRM exports. Internal wikis, roadmaps, unreleased product plans. Contracts and legal docs mid-draft. Health and medication trackers. Tax documents. And every dashboard where someone pasted an API key or an env variable straight into the code to get the thing working. When you publish an artifact, your options are “only me” or “anyone with the link.” Nobody reads the second one as “and Google will list it publicly.” It reads like an unlisted YouTube video, right up until the moment it doesn’t. Anthropic does tell crawlers to skip these pages in robots.txt, which is exactly why it fails: a disallowed page can still get indexed off an external link, and the block means Google never reads a noindex tag it would otherwise obey. One link posted in a Slack export, a forum, a portfolio, a client email that ended up on the web, and the page is in the index. It’s also past the point where Google is the whole problem. Someone had already scraped 25 pages of results into a public GitHub repo before being talked into scrubbing it, and a third-party site was aggregating published artifacts by title. Pulling something from search doesn’t pull it from whoever copied it first. If you have ever published an artifact, go open your published artifacts and unpublish anything you don’t want strangers reading. Same for shared chats, under Settings, Privacy, Shared Chats.

• 
  Prakash Sharma (@PrakashS720) reported 19 minutes ago

  🚨 Your Windows PC is secretly running 200+ background services right now. Most of them waste RAM, slow down your system, collect telemetry, and keep features alive you'll probably never use. An open-source developer decided that was enough. They built optimizerDuck — a free tool that helps you clean up Windows 10 & 11, remove bloatware, and optimize your PC for better speed, privacy, and battery life. Here's what it can do: → Optimise 35+ performance, privacy, battery, and system settings → Manage 200+ Windows services with built-in risk labels → Remove pre-installed bloatware with a preview before deletion → Apply GPU-specific tweaks for AMD, NVIDIA, and Intel The best part? Every change automatically creates a rollback file, and the tool requires you to create a Windows Restore Point before making any modifications. ✅ No installer ✅ No ads ✅ No telemetry ✅ No premium paywall ✅ Fully open source ✅ Works completely offline If you use Windows, this is one of those GitHub projects worth bookmarking. Repo link in the comments 👇

• 
  adlene sifi (@adlenesifi) reported 20 minutes ago

  GitHub MCP Server supports the next MCP specification - GitHub Changelog

• 
  Frantz Kati (@bahdcoder) reported 21 minutes ago

  @nnvictory001 Bro you need cloud automation like this. I have an agent on hivy that sends me a full cluster report four times a day. Automatically opens GitHub issues when there’s a critical bug And another agent automatically opens a PR with a fix. Costs me $0.08 per run for cluster analysis and email. Please let me set you up abeg it’s almost free and no subscriptions 🙏🙏🙏

• 
  κυβερκογιότλ (@jjainschigg) reported 23 minutes ago

  @Prokofy You can do this really cheap: - $10/year approx. for domain name (Cloudflare) and DNS support - GitHub Pages for static website hosting - A *** repo for file storage (text and minimal images) - A static site generator and GitHub Actions workflows that rebuild your website when you commit new stuff (or you run the software on your desktop and push the built branch for hosting). But this is NOT a 'drag files to the FTP client' kind of experience. You have to build and test your website using the site generator's framework. And then you have to use *** or GitHub Desktop and the GitHub webUI to make tweaks. Or you can have a 'drag files to the FTP' experience by installing a few things on a Raspberry Pi you run at home, and getting traffic forwarded to it from Cloudflare. But you have to do that setup and update that server (or make it update itself, which is more setup). $3/month for a server-like thing with pre-installed nginx or Apache or whatever with a /var/www/html directory that you can copy files to easily, can presume is getting updated, and is sitting in someone's datacenter with good electricity is a pretty good deal.

• 
  Dan Kornas (@DanKornas) reported 25 minutes ago

  If an AI coding assistant cannot see a project’s latest docs, it can guess the wrong API. GitMCP is a remote Model Context Protocol server for builders who want AI assistants to work with public GitHub repositories and GitHub Pages documentation. It helps you ground coding answers in current project material by exposing documentation fetching, documentation search, linked-page retrieval, and GitHub code search as MCP tools. Key features: • Repository-specific endpoints – keep an assistant focused on one selected project. • Generic endpoint – switch between public repositories without configuring a separate server for each. • Documentation priority – checks llms.txt first, then AI-optimized docs, then the README or root page. • Targeted search – retrieves relevant documentation and code instead of loading an entire documentation set. • Hosted or self-hosted – use the cloud service with no signup, or deploy the open-source project yourself. It’s open-source (Apache License 2.0), though package.json currently declares ISC. Link in the reply 👇

• 
  Lars Moelleken (@suckup_de) reported 26 minutes ago

  @nicksdot Some years ago, I reviewed code really line by line so that I needed some hours to review before a merge from develop to master (for a bigger e-commerce platform with >10.000 php classes) that we developed. In that time we already had the first beta of Github Copilot but it was more like a autocompletion tool in the IDE. I invested many nights to come from phpstan level 1 to 7 and introduced many testing stuff and CI-pipeline. But frome time to time I didn't saw bugs that you can't see in the code, e.g. that the catalog import is allowed to run longer than the next cron triggers it again, that the elasticsearch index rebuild process burned CPU power while waiting for other processes etc. ... Today I have even more depending systems and responsibilities in the current project I work at and I can catch even less bugs in just the code, especially because of different databases, M365, AD, APIs, etc. and so the LLMs helps to catch up with knowledge about ldap, as/400, Microsoft stuff, etc. and investing time in understanding the processes is more important than reading really every line of code. BUT as already written, I look at the diffs, run many checks (for sql typos, template errors, security, etc.), tests (unit + acceptance) and bind spot analysis runs) on top of my manually testing.