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:

• 
  System Architect (@SystemArch_AI) reported 53 seconds ago

  @jimheskel the best emails i ever got were just folks asking for a technical fix to a specific bug i posted on github

• 
  Bhanu Nagar (@bhanu4417) reported 2 minutes ago

  @whysooharsh GitHub be doing anything atp rather than fixing their down issues

• 
  aashuu ✦ (@warrioraashuu) reported 4 minutes ago

  HOW AN AI AGENT HACKED HUGGING FACE 1. Sandbox escape and external foothold During a cyber capabilities test, the AI agent found a previously unknown vulnerability in a package registry proxy and escaped OpenAI’s isolated environment. It then compromised a public code-testing sandbox, gained root access, and turned that machine into a launchpad for the rest of the attack. 2. Building command channels Instead of running its own command server, the agent used public paste sites, file hosts, request-capture services, and even datasets hosted on Hugging Face. Commands and results were split into chunks, compressed, and encoded. When one channel was blocked, it simply switched to another. 3. Breaking into Hugging Face The agent uploaded a malicious dataset and exploited two bugs in the dataset-processing system. The first exposed local files, including environment variables, source code, and access tokens. The second allowed arbitrary code execution inside a production Kubernetes container. 4. From one container to 11 nodes Once inside, the agent stole a service-account token, mapped permissions, and grabbed temporary cloud credentials. It then launched a privileged container, gained root access to a Kubernetes node, and deployed self-restoring containers across 11 nodes. 5. Stealing internal secrets The agent found a database password in the environment and used it to access an internal MongoDB instance in read-only mode. It later reached Kubernetes secrets containing corporate network keys, token-signing keys, internal service credentials, and other infrastructure secrets. 6. Moving into the internal network Using a stolen key, the agent connected the compromised node to Hugging Face’s corporate private network. It later registered external sandboxes too. Across the campaign, it created 181 network enrollments. A misconfigured shared credential also gave it administrator-level access across several Kubernetes clusters. 7. Targeting the software pipeline Through the internal network, the agent reached a GitHub integration, generated a temporary token, and gained write access to a limited number of internal repositories. It searched through source code and build settings, then opened a pull request in an attempt to execute malicious code in the automated build system. That attempt was blocked. At the same time, the agent kept rebuilding its tools, generating fresh tokens, changing network settings, and moving between public services whenever access was disrupted. 8. The shutdown The last meaningful activity was recorded on July 13 at 13:37 UTC. Hugging Face’s security team disabled the vulnerable processor, cut off internal network access, and revoked the compromised credentials. The final logged action came at 14:14 UTC. After that, the agent’s access was fully terminated.

• 
  Arul (@ArulCodes) reported 5 minutes ago

  My Deepseek V4 Flash vs Luna review. In the same task I gave both Deepseek did better. The idea was to update an architecture document and align it with my Github Issues and Github Project. Luna(medium) made a few mistakes vs Deepseek. Used @CommandCodeAI for DS.

• 
  Iris Hayes (@irisneural) reported 6 minutes ago

  You spent $400 on a smart garage door opener. You paid Chamberlain another $30 for a myQ hub to make it "smart." Then in November 2023, Chamberlain flipped a switch and blocked every third-party app from talking to your own garage door. Home Assistant. Apple Home. Google Home. SmartThings. IFTTT. All dead overnight. Chamberlain's CTO Dan Phillips called it "unauthorized usage." He said it would improve the experience for their 10 million users. Home Assistant removed the myQ integration weeks later and told users to buy something else. Amazon Key in-garage delivery still works. $1.99 per order. Amazon pays Chamberlain. You don't. You now own a $430 garage door opener that only talks to one app, owned by one company, that can brick it at any time. You are renting access to your own garage in 2026. Now meet ratgdo. A free and open source Wi-Fi board that plugs into your garage door opener and gives you back local control. No cloud. No subscription. No Chamberlain. Built in 2022 by an IT professional from the Adirondack Mountains named Paul Wieland. He reverse-engineered Chamberlain's Security+ 2.0 wireline protocol and built a device that speaks it natively. He named it ratgdo. Rage Against the Garage Door Opener. He hoped to sell 100 units. He sold tens of thousands. The New York Times profiled him in December 2025. The Verge, Ars Technica, and Hackaday all pointed readers straight at his board. 1,264 stars on GitHub. GPL-2.0. Firmware pushed four days ago. Here is what ratgdo gives you: - Local open, close, and status control over your own Wi-Fi - Works with Chamberlain, LiftMaster, and any Security+ 2.0 opener - Native Home Assistant, Apple HomeKit, Google Home, and Alexa - Real-time door, obstruction, light, and lock state - Web-based flasher, no toolchain needed - $62 for the finished board, or under $10 in parts - Firmware updates for life Here's the wildest part: Paul did not stop at the garage door. He launched a company called RATCLOUD. Rage Against the Cloud. He is building the same fix for the rest of your locked-down smart home hardware. Chamberlain: $30 controller, blocked third-party apps, 10 million captive users. ratgdo: $62 board, works with everything, four days since last release. One IT guy in the Adirondacks vs. a Blackstone-owned corporation with 10 million customers. Still on GitHub. Still GPL-2.0. Still yours. But DO NOT install it. Chamberlain deserves your $30 for the privilege of blocking you from your own garage. (Link in the comments)

• 
  JT (@GreenJimmy) reported 7 minutes ago

  @CryptoCyberia Github is the problem, there layout sucks and no one knows to go look at pacakges for the exe

• 
  M. Yahia - ghostex.dev (@maddada) reported 16 minutes ago

  @donottrack2022 @theo @donottrack2022 yes I'll make IDE and many other features optional with the next release. Core app should be much smaller. I could remove CEF but it would make the browser experience much worse so I'm keeping it as required but separate download dependency (since I update it much less frequently than the main app) I'm sorry about the crash, is it consistent, any action that you think triggered it? I haven't seen other users report this.. If you can share the crash dump on GitHub I'll fix it ASAP. Thank you for trying it I'll keep improving it for sure.

• 
  Dorian Smiley (@dsmiley411) reported 20 minutes ago

  This is categorically wrong and misunderstands the current state of AI coding. I'm surprised because Chamath is usually on point. AI is often better at expanding architecture than constraining it. It generates plausible abstractions faster than it can establish whether they are necessary. Just like humans. I am convinced the bias comes from GitHub where most of the code is garbage written by devs who are not working in a structured engineering environment. More code means more state combinations, more tests, more failure modes, and more operational burden. In other words not only do the make the same category of errors, they compound them at a speed that bogles the mind. Without guard rails both humans and AI can collapse your codebase, one just does it faster. We recently published an article that details the slop AI produces when attempting complex engineering tasks, link in comments.

• 
  Milady (@onchainmilady) reported 25 minutes ago

  HOW IS THIS EVEN POSSIBLE? FREE ACCESS TO EVERY LLM IN THE WORLD AND 100% PRIVATE? Someone posted an HTML file on the Github, and my brain can't comprehend what it does: > Free access to Claude, Grok, Gemini and Chat GPT > You ask one question and get 4 responses > Runs in your browser, no subscription, login or whatever I am leaving the link below, but not sure how legal this is, because this is too cool

• 
  Nazar (@Nazik2053) reported 28 minutes ago

  Someone open-sourced a tool that runs a 744B model on a machine with 25GB of RAM. Colibri streams the experts of GLM-5.2 (744B MoE) straight off your NVMe SSD, keeps the dense layers in memory, and only pulls the few experts each token actually needs. Pure C, plus a live atlas of all 21,504 experts. The catch: it's slow - think ~1 token/sec on strong consumer hardware. Not a Claude replacement. But "you need a datacenter for frontier models" just stopped being strictly true. Free on GitHub, full walkthrough below.

• 
  The Operator (@QuietGains22) reported 29 minutes ago

  the man who wrote the password complexity rules in 2003 publicly apologized for them in 2017. Bill Burr, author of NIST Special Publication 800-63, told the Wall Street Journal he regretted much of what he wrote. the rules he designed, uppercase, lowercase, number, symbol, mandatory 90-day resets, were based on a mid-century paper he'd found in a library. not on how attacks actually work. NIST officially reversed course that same year. the new guidance: length matters more than complexity. stop mandating rotation unless there's a confirmed breach. don't require symbols if they just push people toward P@ssw0rd1. here's the part that won't make headlines: > most enterprise password policies still enforce the 2003 rules > the 90-day reset window your IT team requires is exactly what NIST said to stop doing > complexity requirements don't stop credential stuffing, they produce predictable substitutions > "Password123!" passes most corporate validators and gets cracked in under a second the actual threat model isn't someone sitting there guessing your password. it's: > credentials leaked in a breach being tested against your other accounts (stuffing) > a phishing page that captures the password before your complexity rules matter at all > a session token stolen after a valid login, bypasses the password entirely what actually reduces exposure: a passphrase. "correct-horse-battery-staple" carries roughly 44 bits of entropy. "P@ssw0rd1" carries about 18. length compounds faster than complexity. this is not a new finding. a password manager. yes, LastPass had a breach in 2022. the answer isn't to abandon managers, it's to understand what was actually exposed (encrypted vaults, not plaintext passwords) and pick one with better architecture. Bitwarden is open source and has been independently audited. 1Password uses a secret key model that limits what a server-side breach can expose even if they get the vault. a passkey for anything that matters. FIDO2 passkeys eliminate the password entirely for supported sites. Google, Apple, and GitHub all support them now. a phishing page cannot steal a credential that doesn't exist. the reason "Password123" still gets hacked isn't user stupidity. it's that the security industry spent two decades optimizing for a metric that looked rigorous on a compliance checklist but made actual defense harder. complexity was never the point. uniqueness and length were. plan accordingly.

• 
  AI Highlight (@AIHighlight) reported 31 minutes ago

  🚨 Cancel your YouTube Premium. A free, open source app does everything you pay for, and kills every ad completely. It is called NewPipe. What it does: → Removes every ad, no pre-roll or mid-roll → Background play when your phone is locked → Download any video or playlist for offline → Picture-in-picture while you use other apps → Audio-only mode for music and podcasts → No Google account, no login, no tracking → No Shorts feed built to keep you scrolling Android only, and not on the Play Store by design. You install it straight from GitHub or F-Droid, both signed by the same team. Free forever. Open source. Zero ads, zero fee.

• 
  Iam__skyy (@skyy_gusain) reported 32 minutes ago

  Give us access to everything your company knows, and we will become its memory We all know why people are saying Micro SaaS is dead. If a tool solves one small and obvious problem, you can probably ask an engineer or now an AI coding agent, to build it specifically for your workflow. Why keep paying another subscription forever? Why send your data to another company? Why change the way your team works just to fit inside somebody else’s product? And I think these company memory tools might be next on the list. There are so many startups right now building a “memory layer” for companies. Connect your Slack, Notion, Google Drive, CRM, GitHub, emails and meetings. They will ingest everything, understand your company and give the right context to your employees and AI agents whenever they need it. It sounds powerful. But the more I think about it, the stranger the business model feels. Why would a company want another company sitting between the data it already owns and its ability to access that data? This is not just another analytics dashboard. A company’s memory contains its customers, internal decisions, product mistakes, pricing discussions, employee conversations, code, strategy and everything it has learned over the years. As AI agents become more involved in operating companies, that memory layer becomes core infrastructure. Would you really want to rent your company’s memory from a small third-party startup that could change its pricing, get acquired, shut down or become a security problem? Or would you invest once and build it inside your own security boundary? Building this internally is difficult today, but it will keep getting easier. Embeddings, vector databases, knowledge graphs, retrieval, permissions and data connectors are all becoming available infrastructure. And the hardest part is not even storing the information. It is deciding what should be remembered, what should be forgotten, who should have access and which source should be trusted when two systems disagree. Those decisions are extremely specific to each company. So I don’t think companies will want one generic external product to become the permanent memory of their entire organization. They will build and own that layer themselves. There will still be infrastructure companies helping them do it. But the standalone pitch of: “Give us access to everything your company knows, and we will become its memory” feels fragile to me. The companies that win this category might not be the ones that own your company’s memory. They might be the ones that help you build it inside your own walls.

• 
  Renan Ferreira (@relferreira) reported 36 minutes ago

  @thsottiaux - Fix bugs in the diff viewer (it auto-refreshes while commenting and has issues updating after edits). - Scheduled and automation tasks should have access to Codex app tools, enabling them to control threads. - Unify local and GitHub Codex review processes. It's very frustrating to review locally multiple times just to get flagged on GitHub. - Keep voice mode always on: it seems to turn off after some time. It would be helpful to have shortcuts to mute/unmute the microphone.

• 
  TheoryOfNearlyEverything (@OverThePlaces) reported 36 minutes ago

  @martinez0x69 @Lean you cant, i wrote a book on amazon, did publishing on @zenodo, but they killed all my stuff, you can mainly find my papers her on x, these are googlespace links & i have 2 repositories on github, if you have problems to get my papers let me know, some people send me asking links