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:

• 
  ChartsJournalX (@ChartsJournalX) reported 53 seconds ago

  @sameenkarim @github Great, but the main way devs waste time reviewing PRs is GitHub’s clunky, outdated, and slow web UI. Just make it snappy. So much time is lost waiting for things to load.

• 
  Mars (@Marsmensch) reported 4 minutes ago

  14/ ELI5: This check should have been in place from the start. A failed build would have been a success. Instead, vulnerable seeds were distributed, and the reported losses are still increasing. PS.: I am tired and all errors are mine. I have verified everything carefully manually. If Github does not properly load diffs for you, search for the relevant file/function in the diff. Thanks to everyone tirelessly working to help people through this mess! Gn8, Mars

• 
  Daily Patch Notes (@dailypatchnotes) reported 8 minutes ago

  @github @OpenAIDevs luna down eighty percent finally shows on the copilot bill

• 
  plumhusky (19m) (sawyer) (@plummydahusky) reported 9 minutes ago

  @iKG_HD to dox people 2) every update since about 5.7 has been in attempt to fix DRM. Multiple updates a day have been pushed in the past week. Unfortunately some people crack people's tweaks. There are entire jailbreak repos for it. Someone made a repo on GitHub with a copy of the

• 
  Elaina (@ElainaNotes) reported 9 minutes ago

  The Codex Windows desktop app really is this bad. Around early June, it suddenly stopped launching on my PC. Codex would appear in Task Manager for one or two seconds and then disappear. Sometimes, its process would not appear at all. I tried reinstalling it, checking my network, antivirus software, drivers, and almost everything else I could think of. I also used MiniMax M3 and GLM-5.2 to diagnose the failure and attempt code-based fixes, but even after burning through a large amount of API credits, the problem remained unresolved. In the end, OpenCode with the free DeepSeek V4 Flash finally solved it. After reviewing the full history of my troubleshooting attempts, DeepSeek was noticeably more proactive than the other models I had tried in searching the internet for relevant information. It eventually found clues that matched the characteristics of the issue I was experiencing among the large number of issues in the Codex GitHub repository. The actual fix was surprisingly simple: it only took a few commands to modify the environment configuration. Once the changes were made, the Codex desktop app was able to launch and work normally again. Yet this issue has apparently been sitting in GitHub Issues for months. OpenAI has done nothing meaningful about it. It has neither fixed the bug nor provided affected users with any useful warning, troubleshooting guidance, or suggested solution. They have simply left the problem for users to solve on their own. Affected users can only take it upon themselves to reinstall the desktop app, check their network, antivirus software, drivers, and system configuration, try writing scripts or fixing it through programming, search the internet, look through forums and various issue trackers, and then rely on themselves to piece together a genuinely effective solution bit by bit.

• 
  GREG ISENBERG (@gregisenberg) reported 12 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.

• 
  Bprime - Ninjapay (@biellonuhu) reported 14 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.

• 
  Piyu$h (@erornotfoundme) reported 15 minutes ago

  From pencils to keyboard From notebooks to GitHub From ABCD to DBMS From Arey to Array From mistakes to error We all grew up...

• 
  Michael Fischer (@Holden_Rye_) reported 17 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.

• 
  MineBench - efficient computing power (@MineBenchdapp) reported 17 minutes ago

  We would like to ask for your help regarding our GitHub account. Our account was suspended even though our repositories do not contain malware or any harmful software. They primarily contain open-source mining-related components, similar to projects such as XMRig, which continue to be publicly available on GitHub. The suspension is creating a significant obstacle to the development of our application. We have contacted GitHub Support multiple times but have not received a meaningful response explaining the reason for the suspension. If possible, could you reach out to GitHub on our behalf or help us understand what the actual issue is? If that is not possible, we would appreciate any recommendations for a reliable alternative platform where we can continue developing and hosting our open-source project. Thank you for your time and support.

• 
  tadpole (@cryptoanuran) reported 20 minutes ago

  @Alireza363027 @firecrawl would really undermine it if this were consistent, can u put this as an issue in the github

• 
  Slims (@Slims_slimy) reported 21 minutes ago

  @neerajjj6785 Cursor was overhyped as all it did was implement a model into your IDE instead of copy pasting from an AI chat. So it knows exactly what's in the project rather then you telling it. Sora got shut down I think. Github copilot is working normally. Google.

• 
  Matt Pocock (@mattpocockuk) reported 25 minutes ago

  @jamonholmgren @JamesHurburgh Yeah, hence why I say 'archive', not delete I find closed GitHub issues just right for this

• 
  anonymous086505 (@anonymous086505) reported 26 minutes ago

  @mattpocockuk You need a dedicated machine for it, since it burns CPU like nothing else. Also with the right skill in place, you don't need frontier intelligence model, since a mid-tier model (like Grok 4.5) can work and the github issue generated will be self-proven. Then fix it with an agent

• 
  Bold Fugu 🇮🇱 (@bold_fugu) reported 30 minutes ago

  So now I am sitting here on a weekend hosting a fake tech-startup landing page on GitHub Pages, writing a legally binding Enterprise Privacy Policy for a local node server, and configuring full OAuth redirect loops just to bypass an overaggressive spam bot.