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:

• 
  Alexey Samoylov (@metalagman_dev) reported 44 seconds ago

  @geminicli Antigravity CLI is a trash, closed source, full of bugs. They don't even read issues on the github.

• 
  Solomon Neas (@solomonneas) reported 4 minutes ago

  There's a fair number of downloads for Brigade and related repos. I'm dogfooding it everyday but not getting any feedback from users or github issues. I'm doing plenty of tests for how a new user would experience it but I could use more real time feedback. Lmk, I want to improve

• 
  Floorless🌒Lance🪽 (@4ranc6) reported 5 minutes ago

  @CAONHTAN1 Having error connecting github

• 
  YNWA🐦‍🔥 (@YNWAcrypto) reported 6 minutes ago

  The problem isn’t subtle. GitHub Sponsors has paid out ~$50M total since 2019. core-js: 9 billion downloads, running on half the top 10k sites on earth. Its maintainer was making ~$600/month when he called open source “fundamentally broken.”

• 
  top10.dev (@Top10_Dev) reported 7 minutes ago

  SunJaycy/GoldenEye-Recomp just hit @github Trending at 503★ — the N64Recomp toolchain (the one behind Zelda 64: Recompiled / Majora's Mask) now eats Rare's 1997 engine. Static recomp ≠ emulation. The ROM is lifted to C at build time, compiled to native x86_64/ARM64, and paired with RT64 for path-traced lighting at 4K. No interpreter loop. Real binary. GoldenEye was the hard target — microcode-heavy muzzle flashes, split-screen viewport math, infamous AI. If it works, the toolchain has cleared the "Zelda-shaped problem" bar. #opensource #gamedev

• 
  Ben Vinegar (@bentlegen) reported 8 minutes ago

  💡 I have an idea for an experiment We need a website for SoAC ... so we get an agent to do it, on a loop, set in motion once with zero human intervention after "go". It works off a semi-public GitHub repo, w/ issues, PRs, maybe even public agent traces. A publicly auditable experiment on whether it produces dogshit or not. Yea, nea?

• 
  Rahul Verma (@RahulVerma989) reported 10 minutes ago

  @ElitzaVasileva - I have created claude code routines to write blogs for three of my products daily which are driving the traffic from search engines. - You can create a similar workflow to manage your customer support. How 👇🏻 1) Create a feedback menu in the dashboard to create tickets within the platform. One for your users and one for yourself (admin). 2) Create the MCP server and connect it to claude or AI tool that you use. 3) Create a routine so that claude will trigger lets say every morning at 8 AM and go through each ticket and respond. You can also configure webhook to keep it near real time but it might exhaust the usage limit faster. Also include your website github repo in routine so that claude can refer to the codebase to provide accurate instructions. Just instruct claude to not make any edits to your website codebase and respond only when you are not replying for sufficient mount of time (like 3 hours for example) 4) If you are using resend then you can auto create the tickets in the dashboard of the user when the first email is received and after that the ticket will be updated automatically even if you do conversation on email. Like I don't even maintain one of my project LatestModelId as you can see in the screenshot. Claude run each week and update the codebase and I just review and approve the PR. Hope this helps 🙌🏼

• 
  Pipeshub ( Open Source Alternative To Glean ) (@PipesHub) reported 11 minutes ago

  Pipelines are built. Context is broken. MCP is quickly becoming the default interface for enterprise AI agents. And that’s a good thing. It gives agents a standard way to connect with tools and data. Connecting an AI agent to Slack, Jira, GitHub, and Salesforce doesn’t mean it suddenly understands your business. It just means it can access your data silos. In short: "MCP gives your agent a passport. It doesn't give them a map." As enterprise AI undergoes a massive platform shift from passive chatbots to autonomous agentic workflows, this naive, runtime "federated search" approach creates an ugly cycle in production: - The Latency Spike: Slower agent execution while waiting for multiple external APIs to respond before it can even begin reasoning. - The Token Bleed: Skyrocketing bills from shoveling raw, unranked JSON dumps into a massive context window, praying the model finds the answer. - The Governance Nightmare: A massive risk of data leaks if you rely on a base LLM to magically guess and police complex enterprise security permissions on the fly. Agents do not fail because they lack intelligence. They fail because they lack the right enterprise context. The hardest problem in enterprise AI isn't connecting to systems. MCP solved that. The hardest problem is Context Engineering. MCP is the perfect interface, but a permission-aware context layer must be the foundation. 🚀 If AI is becoming core enterprise infrastructure, you cannot allow the strategic intelligence layer of your company to sit inside someone else's managed, closed-box platform. That is exactly why we built Pipeshub (open-source developer owned context infrastructure layer). TL;DR MCP gives agents access. A context layer gives them understanding. And deep understanding is the only way enterprise AI moves from a cool demo to secure, reliable production. 👉 Next Up Tomorrow: MCP Token Tax

• 
  Nitesh (@NiteshTechAI) reported 14 minutes ago

  This repo should not be free. private-gpt turns any local model server (Ollama, llama.cpp, vLLM) into a Claude-compatible API. Build private AI apps where zero data leaves your machine. ↳ 57,236 stars on GitHub ↳ RAG with citations and MCP connectors built in ↳ follows the Claude API spec: streaming, batch, tool use, extended thinking ↳ official integration guides for Claude Code, Claude Desktop, and Microsoft 365 But it is free. 100% open source, Apache 2.0. v1.0.0 shipped 9 days ago. The viral 2023 script quietly became production software. 🔗 GitHub link in the comments 👇

• 
  Denis (@nuculabs) reported 16 minutes ago

  Worst part of OpenCode is that they only allow login via GitHub or Google

• 
  timoheimonen (@timoheimonen_) reported 18 minutes ago

  Memos are encrypted and decrypted in browser, server never sees what they contain. No accounts. Anyone can create encrypted memo. Source code is available at GitHub.

• 
  Akshay Shinde (@ConsciousRide) reported 24 minutes ago

  @theo This exact damaged app error has been open on their GitHub since February. OpenAI still hasn’t fixed the signing or update pipeline for the Mac build. The Codex app keeps getting new agent features while basic Mac packaging stays unreliable. Priorities are obvious.

• 
  West Lord (@MyWestLord) reported 27 minutes ago

  A GitHub repo with just 571 stars handed Claude the ability to test its own code, and it took 185 seconds to install. It’s called auto browser, and it quietly killed the most annoying part of my workflow. Until now, every time Claude or Codex built me a WordPress plugin, I was the middleman who had to load it, click around, hunt for the broken part, and report back like a human bug tracker. Now a local WordPress sandbox runs on my machine, and auto browser sits between the agent and the screen, so the agent ships a plugin, opens the browser, tests it, catches the error, and patches it before I ever look. The first plugin threw an error, but the second installed clean and ran on its own across 2 fresh workspaces. I write 1 instruction file pointing the agent at the sandbox, paste it into every session, and the whole loop closes without me touching anything. The agent stopped asking me what broke, because now it just checks itself. The middleman was me, and now it’s gone.

• 
  Trifon Getsov (@trifon_getsov) reported 30 minutes ago

  @thdxr Top down works until the individual outgrows it. GitHub didn't win because companies adopted it first. It won because developers wouldn't go back once they'd used it.

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 30 minutes ago

  @TheEthanDing distributed systems at github scale make five nines almost impossible. the skill issue crowd has never run anything millions of people hit in the same second