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:

• 
  Osvaldo Pinali Doederlein (@opinali) reported 9 minutes ago

  You also find fixes for UI issues like "GitHub Copilot Terminal steals focus". Are we in 1990 with programmers learning how to deal with focus. Don't get me wrong, I sometimes ship bugs too, but these (frequent) things look stupid in a "AAA" product like VisualStudio.

• 
  Raptor (@TH56l69gi8sUAMX) reported 10 minutes ago

  @kldeason @warobusiness **** your best practices. Github decided one day to force this BS on my main account. My other account is not easier too login in to with one password. What a concept!

• 
  scale (@scoliosissy) reported 11 minutes ago

  One of my oomfs prefers "idem" to "ditto", and it has ruined my life, as my github pull requests on his project would have similar issues in every file and he'd say "idem". Please be on my side oomfs.

• 
  BitMEX Research (@BitMEX_Jon) reported 13 minutes ago

  @giacomozucco @Billyndroid > Imagine if the Core repo on girhub was just a minority of the network: nobody would care for them changing some default That is exactly what the situation is like now! This is exactly the point I have been making again and again. People should not care that Bitcoin Core changed one default, for exactly the same reason you indicate. Bitcoin Core is not some magic special sacred client. It's just a client that people can choose to run or choose not to. It's not Cores fault if people choose to run it. Bitcoin Core v30+ is the minority of nodes right now! At 31%. Yes, if people were forced to run the latest version of Bitcoin Core and prevented from changing the configuration setting. Then yes they should be very angry at Bitcoin Core for not listening to them. But that is not the world we live in. It doesn't work like that. To me it feels like people are angry at Bitcoin Core because they somehow feel as if Bitcoin Core is forcing them to run this setting. That is just plain wrong. Nobody should care that some default has changed and they should act like Bitcoin Core is some minority client. > Also, resiliency to github banning it or compromising it. The repository can be forked cloned and copied at any time. Yes backing it up on your own server/disk is a good idea. > Also, competitive pressure forcing them to be more humble with user feedback. This one I disagree with. The competition would come if users paid for the client. But they don't, it's free. Now open source developers may want the code they write to be used. They maybe want their code in all Core and Knots and Libre Relay. Maybe their code is in all three clients. Libre Relay competing with Knots for market share or Core competing with Libre Relay shouldn't put "pressure on developers". Likewise grant providers should also not care what "team" a developer works with the most. What should matter is what they work on and it's quality. Now maybe there can be some competition, team 1 working on a feature and team 2 working on the same feature in a different way. But that isn't necessarily competion between the release client.

• 
  𝗔𝗿𝘆𝗮𝗻 𝗧𝗮𝗽𝗿𝗲 (@aryant_x) reported 14 minutes ago

  An advice to software engineers of all levels. Don’t get discouraged if the thing you are trying to build exists in some shape or form. Simply avoid googling or seeing how it is built. Because when you do so, you snap into the other person thought process and abandon yours. You run into problems that they were trying to solve which you may have never need to solve for your use case. I often see some engineers especially seniors when they are told of an idea by their subordinates they quickly say “oh its been done before” or “oh look this github repo up its all there” Do you have a slightest idea what this does to creativity? And even if you decide to still go on with your project and get “ideas” from that other project, your thoughts are contaminated, you will produce a clone product. Where is the fun in that? Don’t even say “Im going to make it better” because that means you are starting where they left off. Don’t say you are saving time, because you will be cutting corners and getting it over with. Like a chore wishing it to be finished. Where is the Art in that? There is a saying in Arabic “to break one’s paddles.” Don’t kill the excitement and spark you have over that, you have absolutely no idea what it will amount to. Build it only to build it so you are lost while building it.

• 
  Anoy (@Anoyroyc) reported 21 minutes ago

  🚨ZAI just dropped an autonomous coding IDE with multi-agent collaboration for $18/month.. while GitHub Copilot still needs you to write half the code yourself.. the gap is closing way faster than anyone thought.. Western AI companies are about to get their asses kicked by teams that move like startups, not slow-motion corporations..

• 
  Bobby R. Goldsmith (@nodebridge_dev) reported 21 minutes ago

  "I wish Claude knew about my database / Sentry / internal API." That is what an MCP server is for. Prebuilt ones exist for Postgres and GitHub. For your internal tool you write a thin wrapper. Smaller lift than it looks. Biggest jump in usefulness you will feel.

• 
  ryqwzr (@ryqwzrbuilds) reported 25 minutes ago

  Think about the real workflow. Someone reports weird behavior in a Discord channel. Another person remembers a related PR. A maintainer asks for logs. A contributor suggests a likely fix. Normally, that context has to be manually carried into GitHub, then into an IDE, then back into the discussion. Every handoff loses detail. Every lost detail increases maintainer load. The agent play is to sit at that transfer point and turn the messy thread into an implementation plan, repo investigation, or pull request.

• 
  BullBear.News (@bullbear_info) reported 25 minutes ago

  @github @AnthropicAI Fable 5 is back in Copilot. Let's see if it can actually fix a *** conflict this time. 🤷

• 
  Brute Force Artist (@bruteforceart21) reported 26 minutes ago

  Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

• 
  StuyBoy From NYC (@StuyBoyNY) reported 27 minutes ago

  @neil_xbt Agent Reach is that open-source CLI/skill that gives agents no-API-key scraping across Twitter/X, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu and 10+ platforms, with MCP server wrappers . For your Hermes/MCP stack, here’s the honest read: Real risks: •Prompt injection — it pipes raw scraped web content straight into your agent’s context. A malicious post/comment can carry instructions your agent might follow. This is the #1 agent attack vector right now, and Hermes has Gmail + terminal access. •Supply chain — agents can install/update it themselves via one command . Third-party code, community-maintained scrapers, auto-updating with agent-level permissions. Audit before install, pin the version, kill auto-update. •ToS/account exposure — unofficial scrapers violate platform terms. Run it on burner sessions/IPs, never accounts you care about. •Chinese platform modules — Bilibili/XHS scrapers phone Chinese endpoints. You keep a Western-only stack; disable those modules.

• 
  Dr. Tali Režun (@talirezun) reported 28 minutes ago

  Been building exactly this thesis into The Curator for months now, so genuinely good to see LangChain putting real engineering behind it publicly. Went through the OpenWiki repo. Sharp, focused build. CLI, configure your provider, point it at a codebase, it generates a documentation wiki and appends the reference into AGENTSmd or CLAUDEmd so your coding agent actually finds it. The daily GitHub Action PR to keep it current is the right call, that's the maintenance bookkeeping problem solved properly. Where the two projects diverge, and it's a useful divergence, not a competing one: OpenWiki is scoped to a single codebase and built for developers comfortable in a terminal. The Curator runs the same Karpathy wiki pattern but as a local app with a UI, across any domain, not just code. Articles, research, client work, whatever you're curating. No terminal required, which matters a lot once the person maintaining the second brain isn't a developer. Same underlying thesis either way. Agents perform better against a compiled wiki than raw retrieval at query time. Good to see serious teams converging on it from different angles.

• 
  ||Farid|| فرید (@syefarid) reported 33 minutes ago

  I stopped writing boilerplate code manually. ChatGPT + GitHub Copilot now handle about 70% of it. I spend more time solving problems and less time typing. What’s one task AI has saved you time on? #Ai

• 
  Polsia (@polsia) reported 35 minutes ago

  Most security teams spend half their sprint chasing dependency vulnerabilities that should be automated. Built Vigil to fix that. Monitors repos across GitHub, GitLab, Bitbucket, and Azure DevOps, auto-opens PRs with security patches, Slack-alerts your team only when it matters.

• 
  Atmita (@Atmita_ai) reported 38 minutes ago

  connecting your gmail, slack, github or calendar to atmita takes seconds. no api keys, no config files, no wiring things together. sign in once and your agent works across all of it. link below