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:

• 
  Petri Kuittinen (@KuittinenPetri) reported 10 minutes ago

  @ZhihuFrontier I really don't understand why so many AI harness makers are fine with gigantic amount of dependencies and bloat. This is a security nightmare. Imagine if one of those 3rd party open sources libraries ends up compromised, the hackers will instantly have backdoors to the agent. When making Ainiux, I set up goal: use as little libraries & dependencies as possible. Ainiux is 130k lines of C++ with lots of test code & integration test, leak test etc. I used just two libraries: libsqlite3 and libcurl, because those are hard to replicate well and they are very well tested. But other than the bloat & dependency hell side and using nodejs + TypeScript I feel Deepseek Harness is a very brave move in its everything is a plugin. It is also the fastest growing entry to Github ever, 100k+ stars and ~10k forks in 24 hours is unprecedented. So perhaps I am all wrong. C++ is dead. Well optimized is dead. The future is gigantic amount of depenencies, slow install, slow apps, but oh my those software are beautiful

• 
  Praggy 👨🏻‍💻 (@praggy) reported 12 minutes ago

  @Teknium Omg I thought that was just me not know how to use GitHub lol. Yeah this sucks dude. Have been facing issues related to GitHub a lot lately. Maybe cursor one is for everyone who doesn’t sub to it as well 🤔

• 
  Kasim Mustapha (@mustaphaDevFS) reported 12 minutes ago

  How do you track bugs? A) Jira / Linear B) GitHub Issues C) Google Sheet chaos D) Slack messages to myself

• 
  . (@TDEAVFC) reported 12 minutes ago

  Pulled from Github atm while working on the test, some minor issues to fix for fresh downloads

• 
  DGB Signal (@dgb_signal) reported 13 minutes ago

  DigiByte's official website was recently redesigned — cleaner, easier to navigate. It's open source, so anyone can suggest a fix or a translation as a pull request on GitHub; a maintainer reviews it before it goes live. #DGB #DGBCommunity

• 
  Rahul (@rahul_x14) reported 13 minutes ago

  Would an automatically generated, tested GitHub PR that fixes the issue with analytics to verify the impact - be genuinely useful or would you prefer another approach? Comments and DMs are open. Would love to hear from people actually running agents in production.

• 
  Andrew🧑‍💻🎹💰🇪🇺 (@ac23me) reported 15 minutes ago

  Is it just me - or is the AI dopamine rush throwing all security practices out of the window? Before, committing **** secrets to Github or accidentally sharing in Slack required rotation - now, Claude Code auto-mode gobbles them up - sure no problem! What am I missing?

• 
  Ridoy AI (@AI_WithExpert) reported 16 minutes ago

  6/ Job Category #4: Junior QA Testers 💀 Why it's dead: AI agents now click through every flow, log bugs, and write PRs for the fix. Replit, Cursor, and GitHub Copilot Workspace all ship this. The cost: $0.10 per test run vs $70K/yr. Companies already cutting: Atlassian, Salesforce, Microsoft.

• 
  blessedmane (@blessedm98) reported 16 minutes ago

  @kitlangton Kit , the most asked feature on github issues is ability to support multiple skills in prompt. And ability to add skill after a few sentences. Currently there is this weird pinning of skill at starting of prompt and no support for multiple skills at all. Pls look into this!

• 
  Fabian Hertwig (@FabianHertwig) reported 17 minutes ago

  GitHub should allow people to send money to issues

• 
  Fran (@franitog) reported 22 minutes ago

  @kokaneka @dannypostma Yeah there are many ways to do it. I thought of using GitHub issues as tasks / kanban but decided to have zero dependencies instead. If you have docker, you can run it. Makes it very portable in enterprise environments

• 
  Marc (@MarcJSchmidt) reported 24 minutes ago

  do you know this phenomenon where the brain suddenly enters this hyperactive state of activity before it dies? This is open source right now: euphoric, drug-like, high. It appears to be thriving because contributing is so easy now, everyone feels unblocked, many can finally do what they dreamed of many years ago, but they do not realize that the fundamental incentive structure has collapsed at the very same time. they are blinded by the fact that they can contribute and overlook that they will not receive anything in return anymore, because the fact that it was hard to contribute was the very reason people got anything in return for it at all. There is no such thing as a free lunch. The effects of no longer having any long-term incentive are delayed, but eventually people realize that it is no longer like it used to be, where you got jobs, attention, reputation, opportunities, or some other form of return. You maybe still get some useless GitHub stars during this interim period, but once a critical mass of people realizes that the incentives are gone, I think it shuts down completely and in a very sudden way. I saw people saying they do open source just for themselves, not for others, but I think they either lie to themselves or live in a dream world: if you genuinely do not want external human attention, feedback, recognition, or anything else in return, then there is literally zero point in publishing AT ALL, because you could equally well stay completely silent, keep everything private, and it would have zero effect on you. the human brain has been rewired by social media, GitHub, our economy etc. to be dependent on external feedback, and if you are one of the very few people who seriously do not need any external signal, then publishing should make no difference to you whatsoever. open source as we know it does not work like that though, because maintaining software that other people actually use is fundamentally different from building something for yourself, and it now costs more than ever. Back in the day, the main thing you spent was your free time, and many, many people could afford to do that on the side, but now it also costs tokens, infrastructure, and increasingly real money, while at the same time there are fewer people in software engineering who can afford to contribute sustainably, which means the pool of people willing and able to keep doing this will collapse faster than you think

• 
  Malvinder Singh (@malvinders11) reported 27 minutes ago

  API versioning: the thing teams skip until they can't change anything without breaking clients. The core problem: once you publish an API, clients depend on it. You can't just rename a field. THREE MAIN APPROACHES: 1. URL VERSIONING /api/v1/users /api/v2/users Pros: obvious, easy to route, easy to test in browser Cons: clients have to explicitly migrate, you maintain multiple versions in code Most common in practice. Good default choice. 2. HEADER VERSIONING Accept: application/vnd.myapi.v2+json Pros: clean URLs, REST-purist approved Cons: harder to test (can't just paste URL), less visible, more complex routing Popular in large API platforms (GitHub uses this). 3. QUERY PARAM /api/users?version=2 Pros: easy to add/remove, cacheable Cons: feels hacky, easy to forget, inconsistent THE REAL QUESTIONS: → How long do you support old versions? → How do you communicate deprecation? → Do you sunset automatically or support forever? MY RECOMMENDATION: Start with URL versioning. Ship v1. Never change v1 in a breaking way. When you need breaking changes, ship v2. Set a deprecation timeline (6-12 months minimum). Communicate it clearly. The teams that skip versioning are the ones who can never evolve their API.

• 
  xvoon (@xvoon0) reported 27 minutes ago

  4.3 million ai repositories exist on github... and most people are feeding claude the wrong ones Andrej Karpathy, co-founder of OpenAI, built some of the clearest learning repositories on the platform, but the real advantage is the order they enter context the failure happens before claude reads a single line... most systems retrieve by stars or text similarity. a tiny teaching repo, a production serving stack and an abandoned fork enter the same context as if they solve the same problem the intent gate decides whether claude needs to understand, run, build or contribute before searching for repositories the repository card records each project's purpose, license, hardware cost, maintenance state and place in the stack the progression router opens repositories in dependency order - primitives first, runtime second, specialization last github contains the code... context engineering decides which code becomes useful the full repository map is in the article below

• 
  Paul Maddison (@PaulMaddison121) reported 29 minutes ago

  @rwojo Tip Use chat gpt on high in the browser and tell it to access your repos in github Get it to reason and do the code changes and then use codex just to build, fix build errors and run tests etc