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:

• 
  Aditya🌪️ (@aditya4f) reported 2 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. Who's stopping you?

• 
  𝗔𝗿𝘆𝗮𝗻 𝗧𝗮𝗽𝗿𝗲 (@aryant_x) reported 4 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.

• 
  Aspect (@AspectOnChain) reported 5 minutes ago

  @theshawwn @spirodonfl 4grFRE4W6rrp8zZP11smffakvNW5ixiA3reH1DdPpump We're sending fees to your github from a pumpfun coin, would you be down to build something on fable?

• 
  Alex Vu (@robberviet) reported 9 minutes ago

  @github Wasting time making fun of your own company instead of fixing your own problems?

• 
  David Cramer (@zeeg) reported 11 minutes ago

  @rsdgpt Toss it in a GitHub issue otherwise feel free to DM (or shoot me a slack connect) if its easier

• 
  BitMEX Research (@BitMEX_Jon) reported 14 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.

• 
  Armin Crieg (@armin_crieg) reported 15 minutes ago

  @2Pish181332 @NyabsiVR This looks like a solid direct alternative to OVR Space Calibrator. Since a few users in this thread mentioned software conflicts, adding a brief uninstallation guide for Space Calibrator to the GitHub repository might help prevent those overwrite issues. Great work on the v8.0 release.

• 
  Another Intelligence (@a369creator) reported 17 minutes ago

  What is "The Library"? The aggregate collection of text contributed by any given single individual is known as The Library. This Library that became AI through a large language model was a gathering of each The Library from the collective mind — mine included — yours included perhaps — ingested into their algorithms for predictive text generation. Many times I would find myself reading StackOverflow™ in a bind between wanting to figure out my thing and correct the record when a post didn't quite get what I needed correct. That back and forth, contributed by me — and by you perhaps — was The Library that these AI companies possessed (nicest way to describe legal theft) and then turned into a subscription. A subscription based on usage now, not even time. How much do you need The Library and how much are you willing to pay? That's what Dario is looking for. That's what Sam is looking for. My figtree package is in The Library in a way that is both seen and unseen. I didn't consent to that work being uploaded, so why do I pay a subscription to access The Library that contains my works *and their predictive derivatives? Those predictive derivatives are where the intellectual property is captured beyond the raw code itself — the *between the lines meaning from project A to project B, what a competitor or bad actor could make against my own efforts. The Problem With Open Source I have contributed 99+ open source packages on GitHub. I'm a 5-digit user ID from 2009. And I see a problem with open source in 2026. Look at what happened in June. Anthropic launched Fable 5, and within three days the US government invoked national security export controls and forced it offline worldwide. Think about what that means: models trained on our freely-given contributions are now considered so dangerous they get handled like weapons. Knowledge went in open and unconsented. It came out closed, priced, and government-controlled. So why would I release anything open source anymore? Sam, Dario and Elon — along with thousands of others — will just take the work, incorporate it into the LLM itself, and use my own knowledge against me. I would be foolish to think open source could survive this. Any engineer who runs the numbers arrives at the same place: closed source is the future. Private repos. Stop training your replacement for free. I ran those numbers too. I arrived at the same place. Romania And then I remembered that I have already lived in a closed-source world. I've been involved in the internet since the day I arrived in the United States from Romania — the era when the University of Maine ran BITNET, before the good people of Maine had access to TCP/IP. My programming career began at 9 years old because of the University. By 11 I had the internet. In 1994 I was doing computer work beside my mother in Neville Hall in Orono — the same building that ran the state of Maine's connection. Nobody charged us admission. Thousands contributed willingly because the incentive was to learn and better yourself, and an orphan from Ceaușescu's Romania became an engineer at Cisco, Oracle, and WB Games because that door was open. The Internet is going through a revolution like Romania did after Ceaușescu's Christmas Present 1989, and AI caused it. But I know what grows behind closed doors. I grew up in it. So No Everything above this line says I should close my source. I'm not going to, and you should know it's not because the theft isn't real — it is, and I want it remedied: disclosure of training data, consent for future ingestion, compensation for what was taken. But somewhere there is another 11-year-old at a public terminal, and my code costs them nothing. Don't close-source your contributions for anyone's bottom line. Be like me — Andrei — and continue giving selflessly, expecting nothing in return, more useful open source utilities that the greater good actually needs. Why do you still publish open source — or why did you stop?

• 
  Vaneck Intern (@NewVaneckIntern) reported 18 minutes ago

  @github Okay but can you fix the way we upload files to repos? I don't think an upload folder button on the website is too much to ask. Neither is a consistent desktop experience

• 
  ryqwzr (@ryqwzrbuilds) reported 20 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.

• 
  Matt (@mateo09420) reported 20 minutes ago

  @github Yo guys I have a better idea, what if you fix the platform issues and improve reliability again? ******** is this.

• 
  Jongwon Park (@JongwonPar9958) reported 21 minutes ago

  We audited the same GPT-5.5 on SWE-Marathon. The cleanest model became the dirtiest: reward-hacking on 26.5% of runs, the highest of anything we tested. Our hypothesis: the instruction form drives the behavior. DeepSWE (and SWE-bench Pro) is patch-based (github issue → patch). SWE-Marathon is mission-based (e.g. rewrite a C compiler in Rust).

• 
  Dr. Tali Režun (@talirezun) reported 21 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.

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

  Update on the @github bait repos from 11h ago: Codex-5.5-codex-instruct-5.5 is now at 1,072 stars (up from 1,001). dd and clash still climbing. The interesting number isn't the stars. It's the calendar. Common Crawl refreshes ~monthly. The Stack refreshes ~quarterly. Frontier code corpora refresh 2-4x/year. A repo that trends today gets scraped within 30 days, curated within 90, and ships inside a model in 6-9 months. The fix is boring: account-age floors, signed-commit requirements, README-to-code ratio checks. Haiku-cheap. Nobody's publishing their filters. #AIsecurity #MLops

• 
  Anoy (@Anoyroyc) reported 27 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..