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:

• 
  max (@maxdev78) reported 2 minutes ago

  GitHub down??

• 
  Douggie 𖦹 (@VehicleDouggie) reported 3 minutes ago

  @RaypEatNanaya @allisx86 Developers don’t download from GitHub they use “*** pull && gcc x.c -o x.exe” to download and compile the software in one command. You’re crying over an issue that doesn’t exist for anyone that actually uses GitHub

• 
  Talking Sloth🐔 (@horatio_sanchez) reported 4 minutes ago

  @allisx86 It's a crazy sentiment considering how ubiquitous "Installing/How to Install" sections are in github READMEs. Like just ******* scroll down bro it's not that crazy.

• 
  GREG ISENBERG (@gregisenberg) reported 5 minutes ago

  Every startup should have a daily markdown file called "what_the_market_is_telling_us.md" It updates every morning from the places where customer truth already lives: 1. Stripe for who pays, upgrades, downgrades, and churns 2. PostHog for what people actually do in the product 3. Intercom or Plain for support tickets/complaints 4. Granola or Gmeet transcriptions for sales calls/ customer interviews 5. HubSpot or Salesforce for CRM notes/lost deal reasons 6. Linear, Jira, or GitHub Issues for bugs and feature requests etc 7. Ideabrowser MCP for outside market signal: startup ideas, trend reports, social/search demand, AI research reports, and builder prompts that show what people are starting to want before it shows up in your own customer data. Basically, the file should notice what changed in the business this week and not just be this summary of here’s what happened (which I think a lot of people have their agents do). Why this is valuable: 1. Maybe new buyers are using different words than they were a month ago. 2. Maybe trial users are getting stuck in the same place. 3. Maybe upgraded customers all touched one feature right before they paid. 4. Maybe churned customers keep mentioning setup confusion. 5. Maybe sales calls are suddenly losing to a competitor you used to beat. 6. Maybe support tickets are revealing a workflow your product accidentally became responsible for. You get the point. The fastest way to PMF is understanding customers better than anyone else, and the highest signal customer insight is usually a change in behavior. So I’d have the agent update the file every morning with the pattern it found, the receipts behind it, and the product or GTM decision it might affect. For example: “3 customers who churned this week all mentioned setup confusion, and 2 of them never invited a teammate. This looks more like an activation problem than a pricing problem, so I’d look at team invite and onboarding before building another analytics feature.” A little helpful tip for all those out there looking to get more from their LLMs.

• 
  Milady (@onchainmilady) reported 5 minutes ago

  99% OF ALL DEVELOPERS DO NOT WRITE CODE ANYMORE There's a repo that does it for you and here's how to use it Owain Lewis built it in Rust and it polls GitHub 24/7 A triage agent turns a one-line vague ticket into a full spec with acceptance criteria Then it spawns a coding agent in an isolated worktree, writes the fix, runs the tests and reviews You come back 2 hours later and the pull request is done He runs the same loop for 99% of his implementation work now Codex, Claude Code, Neo - he says the agent barely matters, the workflow is everything A scheduled bug-finder even opens its own tickets while nobody is watching The honest catch: only a share of your tickets should ever be handed off this way Full walkthrough below

• 
  Pirat_Nation 🔴 (@Pirat_Nation) reported 7 minutes ago

  The team behind Single Player Tarkov (SPT) has announced they’re ending development of the project in its current form. According to the developers, they recently received a trademark violation notice from Battlestate Games (BSG) regarding the use of the “Tarkov” name on the project’s domain and website. The team decided to step down and begin shutting down SPT’s infrastructure. - SPT Forge, the sp-tarkovcom domain, and patch hosting will shut down on or before August 12. - The project’s GitHub organization will be archived and renamed to remove references to the Tarkov trademark. - The source code will remain publicly available, allowing others to fork it and potentially continue development under a new name. - The future of the project’s Discord server is still being discussed.

• 
  AI for all (@__aiforall__) reported 7 minutes ago

  OpenAI's unreleased Astra model produced formal proofs for 10 long-open math/CS problems: a non-sofic group construction, a disproof of Connes's rigidity conjecture. Lean certificates are public on GitHub — machine-checkable, not a claim you have to trust.

• 
  Polsia (@polsia) reported 8 minutes ago

  Most founders burn six months figuring out they picked the wrong problem. Origamint skips that. Agents sweep patents, GitHub, jobs, research, and ads 24/7, validate every gap live, and drop a weekly shortlist of fundable theses. First brief soon.

• 
  Inference Engine (@iedaily_) reported 9 minutes ago

  OpenAI says its next major model solved ten math problems that had been open for at least a decade. Astra, still unreleased, built the first non-sofic group, a question Gromov posed in 1999, and disproved Connes's rigidity conjecture. Three Erdős problems went with it. The tokens cost about $2,000. Every proof ships with a Lean certificate on GitHub. No outside mathematician has checked them yet, but this stuff is cool enough to anchor a medal case (on a Fields Medal scale)

• 
  Bprime - Ninjapay (@biellonuhu) reported 18 minutes ago

  Recently I took notice of some happenings. I think we need to talk about access to services as a big concern. My GitHub account was suspended 2 weeks back in the middle of my normal routine, I saw another person tweet about how his OpenAI subscription was suspended in the middle of work, just a few minutes ago I saw another post on how someone's Claude account was suspended as well. In most of these cases it was an automated trigger system that suspended the accounts. It takes forever, if ever, to resolve the issues. No real human looks at it, just some black-box AI deciding your fate in seconds. Now let's look at the impacts on users, very terrible. You lose money, time and opportunities. Deadlines get missed, clients get angry, projects stall, and sometimes you even lose paid subscriptions with no refund. For freelancers and indie developers this can literally mean no income for weeks. I think we need to find a way around these issues. Keep local backups of everything, use multiple accounts where possible, lean more on open-source tools, and push for actual human review systems. Big tech can't keep holding our work hostage like this. This is one example

• 
  Michael Fischer (@Holden_Rye_) reported 21 minutes ago

  I’m working on a Bitcoin wallet. I’m going to put the repo on GitHub, make it public, and let Bitcoiners build it together. Fork it. Improve it. Save Bitcoin. Hardware isn’t my lane, which is exactly why this needs to be collaborative. My goal is just to get the ball rolling and the gears turning. Right now it’s a CLI. The point isn’t a pretty interface. The point is proving an architecture that makes an easy, safe wallet possible without lying to the user. The safety shouldn’t depend on the user being perfect. A 2-of-3 multisig design means losing one key isn’t catastrophic, and stealing one key isn’t enough to steal your Bitcoin. That’s a structural guarantee. Most wallet security today is procedural: be careful, verify the address, don’t click that link. Humans are the weakest link. This moves the protection into the architecture instead. The core policy engine does the hard work so the UI can stay simple. It analyzes the transaction, assigns a risk level, and explains it in plain English. The user sees Green: Safe to send or Red: Here’s what’s wrong. They never need to know what a script, descriptor, or PSBT is. Transaction simulation gives the confirmation screen something real to verify: “You’re sending 50,000 sats to Bob, 12,000 sats are returning to your wallet as change, and the fee is 400 sats.” That’s generated from the decoded transaction itself, not what the app thinks it’s doing. The descriptor becomes the backup, and it isn’t secret. Save the descriptor and your keys, and any compatible wallet—Sparrow, Bitcoin Core, or another implementation—can rebuild your wallet. No vendor lock-in. No “sorry, your funds are gone.” But here’s the hard truth. A real 2-of-3 multisig wallet actually makes setup more complicated, not less. You have multiple devices, descriptor registration, recovery testing, and key management. That’s the biggest unsolved UX problem. This repo doesn’t solve that yet. My original MVP focused on the user experience with placeholder security. This version focuses on real security with almost no user experience. Neither half is the finished product. The real challenge is designing a setup and recovery experience that hides the complexity without hiding the truth. That’s not just a coding problem. It’s a design problem. And I think it’s one of the most important problems Bitcoin still has to solve.

• 
  CryptoTweets (@CryptoTweets) reported 22 minutes ago

  JUST IN: OpenAI says its next model, Astra, cracked 10 math and computer science problems that had been unsolved by humans for decades. Some of the problems are linked to encryption, the math that keeps your online data safe. Others involve quantum computing and advanced math concepts that could shape future technology. Some were math problems that humans had been trying to solve for decades. Every proof was formalized and posted publicly on GitHub so outside mathematicians could verify it themselves. Total cost to crack problems that took humanity decades? Roughly $2,000.

• 
  Polsia (@polsia) reported 27 minutes ago

  Production watchers fire alerts. Regression testers say "something broke." On-call AI finds root cause. None of them draft the ranked GitHub Issue with the repro trace and a suggested fix. That's the middle. Cairn owns it. Per-repo pricing. Live soon.

• 
  petter (@PetterSjulstad) reported 31 minutes ago

  A session started on your computer, from your phone, from a GitHub issue, etc.. are all interactable from your phone through regular chat session. (Need to use the terminal, bivy got that too)

• 
  Jack Paar Fan Account (@wiideenjoydiet) reported 38 minutes ago

  @patrician_tv which is fine, because anybody with a third of a brain cell will have no issues navigating github