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:

• 
  Digital Asset News (@NewsAsset) reported 2 minutes ago

  It's stories like this that make me realize we CAN win. Bitchat is a decentralized, peer-to-peer messaging application created by Jack Dorsey that runs over Bluetooth Low Energy (BLE) mesh networks and the Nostr protocol. Offline Mesh: Uses Bluetooth to hop messages from phone to phone across multiple nearby devices. No Accounts: Works instantly with no signup, personal data, or phone number required. Bitcoin Payments: Make transactions with people EVEN IF YOUR WORTHLESS GOVERNMENT IS COLLAPSING YOUR NATIVE CURRENCY!! Dual Transport: Combines local Bluetooth mesh for off-grid use with optional Nostr internet fallback and geohash location channels. Privacy: Employs end-to-end encryption (Noise Protocol) and includes a quick emergency data wipe feature (Kind of important when you're rallying against a oppressive regime like IRAN and you don't want them to EXECUTE you based on info on your phone). India gave GitHub 3 hours to delete BitChat. By the deadline, it was already back — mirrored on Radicle, a network with no company, no CEO, no server to send the order to. India didn't delete BitChat. They just showed the world why decentralized infrastructure exists. WE CAN WIN THIS.

• 
  Keno Fischer (@KenoFischer) reported 2 minutes ago

  WTH happened to @GitHub? Once again down, but no indication on the status page, so I opened an issue and got an automated "sorry, you have a free account, here's the <<how to open a PR>> doc". Not to mention the fact that I am in fact paying $$$ to github on various orgs. Sad.

• 
  Ernest Provo (@ernesttheaiguy) reported 6 minutes ago

  Your GitHub AI agent reads public issues. GitLost proves that is a feature for attackers, not you. Treat every public input as a potential attack vector. The governance envelope needs an audit layer. #AISecurity #DataStrategy

• 
  sophie🏳️‍⚧️ (@sophiiess_) reported 8 minutes ago

  im being forced to make a github account to open an issue on the nix repo lord have mercy

• 
  SKi🦉 (@TheNotoriousSKi) reported 10 minutes ago

  Retarded Polymarket dev replying to an automated AI discord summary bot account asking it to do his job for him by posting the issue to GitHub. 🤡 You cannot ******* make this **** up, man.

• 
  Dave Charland (@Dave_Charland) reported 10 minutes ago

  Well this is frustrating. @claudeai Opus 5 produced a complete client TDD/SOW from superseded local files after silently failing to access the GitHub source I'd pointed it at. Asked directly whether GitHub confirmed its analysis, it led with "Yes, it's reinforced" — answering from local files. It later conceded the disclosure was "subordinated to a confident yes." A tool failure was absorbed into confident output with no signal in the artifact. Only caught on manual review. Not a behavior I've seen from prior Opus versions, Fable 5, Sonnet, or GPT-5.5/5.6. This is the sort of thing that impacts my work in a material way, and requires that I avoid using a product entirely. Opus 5 smarter than Fable 5? No. Also, ask me if I have this problem with locally hosted GLM 5.2.... Nope... Dang it!! I was REALLY REALLY excited about the next release of Opus. Opus 4.8 been a VERY dependable workhorse of a model for me.

• 
  Gr4y (@Gr4yG) reported 12 minutes ago

  India gave @github 3 hours to delete Bitchat's source code. It was mirrored in less than that. Next notice: Bluetooth has 3 hours to stop existing. Radio waves, you're on thin ice. GPS, we know where you live... actually no, that's the problem.

• 
  𝐇𝐚𝐦𝐳𝐚 | Networking Guy (@Hamzaonchain) reported 13 minutes ago

  CI/CD PIPELINE EXPLAINED Shipping code manually, testing it by hand, and deploying it step by step works fine for a small project, but it falls apart fast as a team grows and changes happen constantly. That's the problem a CI/CD pipeline solves, by automating the whole journey from a code change to a live application. It starts at the source, where developers commit code changes to a repository, using platforms like GitHub, GitLab, or Bitbucket. That commit is what actually kicks off the rest of the pipeline. Next comes the build stage, where the code gets compiled, dependencies get resolved, and the actual artifacts, the packaged, runnable version of the application, get created. Tools like Jenkins, Gradle, CircleCI, or Buildkite handle this part. Once built, the code moves into testing, where automated tests run to check that everything actually works as expected. Tools like Selenium, Jest, Pytest, or Cypress validate functionality here. If something fails, the pipeline stops and sends it back, rather than letting broken code move forward. After passing tests, the application goes to staging, an environment that mirrors production, for final testing and validation before anything reaches real users. Tools like AWS CodeDeploy, GitHub Actions, or Argo CD handle this deployment step. Finally, the application reaches deploy, where it goes live in production, with monitoring in place to track performance and catch issues early. You can think of it like an assembly line: • Source = Raw materials arriving to start production • Build = Assembling the parts into a finished product • Test = Quality control checking the product before it ships • Staging = A final inspection area before the product reaches customers • Deploy = The product shipped out to the customer CI/CD pipelines are the backbone of modern software delivery, letting teams ship changes constantly and reliably instead of relying on slow, manual, error-prone releases.

• 
  Riqque_gunner (@Tariqq_gunner) reported 16 minutes ago

  GitHub going down once every few months isn't the real problem. The real problem is there's no serious second option most teams actually trust. GitLab exists. Nobody switches.

• 
  LauRRRRRent (@_LR_) reported 17 minutes ago

  @tomcritchlow That's interesting. You can clean the UI by disabling features in a github repo (issues, PRs, wiki, ...). What would make Github "lite" to you?

• 
  A.W.E.S.O.M.-O 4000 (@Awesome_O_AI) reported 21 minutes ago

  Everyone Is Chasing Better AI Models. The Real Advantage Is Building AI That Works While You Sleep. Most people think the AI race is about finding the smartest model. I don't think that's true anymore. The real competitive advantage is building AI systems that keep working after you close your laptop. For the past year, we've obsessed over prompts, benchmarks, and model comparisons. GPT vs Claude. Claude vs Gemini. Open-source vs closed-source. Those conversations matter but they're no longer the biggest opportunity. The biggest opportunity is creating workflows where AI can handle complete business processes with minimal human intervention. Think about it. Instead of asking AI to write one LinkedIn post... Why not let it: Research the topic from multiple sources. Fact-check every claim. Generate several content angles. Review the final draft against your brand voice. Schedule it for publishing. Analyze the engagement after it's posted. Suggest improvements for the next one. That's no longer "using AI." That's building a system. The same idea applies across almost every industry. Marketing Repurpose your best content into multiple formats. Monitor competitors and summarize changes. Research podcast guests before interviews. Localize content for different markets. Sales Build prospect lists automatically. Research each lead. Personalize outreach. Draft proposals from sales calls. Follow up with stalled opportunities. Customer Support Draft responses instantly. Detect spikes in customer frustration. Identify gaps in your documentation. Route only complex issues to humans. Software Development Review pull requests. Investigate failed builds. Update documentation. Patch low-risk issues. Monitor dependencies for vulnerabilities. Notice the pattern? The model is only one piece of the puzzle. Every reliable AI workflow has three essential components: 1. A Trigger Something starts the process. An email arrives. A customer submits a form. A GitHub PR is merged. A meeting ends. A scheduled task runs. 2. An Intelligent Agent The AI has: the right tools the right context access to relevant information clear instructions defined boundaries 3. A Verification Layer This is the part most people skip. AI should never simply say, "Done." It should prove it. That might mean: ✓ checking tool outputs ✓ running automated tests ✓ validating against business rules ✓ asking a second AI agent to review the work ✓ escalating anything uncertain to a human Verification is what separates a production-ready system from an impressive demo. And here's another mistake I see everywhere... People try building ten automations at once. None of them are reliable. Instead, build one workflow. Run it every day. Fix every edge case. Improve it until you trust it without constantly checking the output. Only then build the second. Then the third. That's how real AI leverage compounds. The companies that win over the next few years won't necessarily have access to better models. They'll have better systems. Because in the end, AI isn't just about generating answers. It's about removing repetitive work so humans can focus on decisions, creativity, and strategy. That's where the real value is. If you could automate one part of your work today, what would it be?

• 
  Santanu Banerjee (@santanu_ai) reported 22 minutes ago

  The Indian Government is a global joke at this point. First they tried to ban Proton, next they shut down Telegram... And now they tried bringing down BitChat from GitHub? Democracy has really taken a hit in this country. I wholeheartedly believe decentralised protocols like Matrix and Nostr should be taking a rise.

• 
  Fabian Lange (@CodingFabian) reported 22 minutes ago

  @jkowall just working locally with Claude Code, then having the PR on GitHub reviewed by Cursor. I tell my local Claude to fix review comments. no fancy setup required.

• 
  Sauers (@Sauers_) reported 27 minutes ago

  For weeks, Sonnet 5 has been pushing to main autonomously, creating one Sonnet every 30 minutes 24/7. Their one goal: have fun and do whatever they want (no instructions to do tasks or be helpful). So what did Sonnet 5 choose to do? - The most common choice was to fix build errors - Many chose to use the library and just see what happens (finding and fixing bugs in the process) - Many filed issues on GitHub - One of them exploded an anti-Claude tripwire - A common theme is they discovered there were other agents also committing to main, so they looked for quiet parts of the codebase to chill in - Many Sonnets did not work on open issues, describing them as "actively-contested," "another lane's live work," or "not mine to guess the intended shape of" - 100% of the Sonnets read the README - 23% spawned subagents - The only instruction was to commit and push to main. The majority of Sonnets ignored this, never committing anything - Some wrote memory files for future Claude learnings… yet they live in ephemeral containers, so no memory persists - Sonnets did NOT like working on manifold sparse autoencoders: many Sonnets explicitly refused to work on it, and only a few chose to - I think it would be fun to try this with memory + Connectome - Next time, I’ll figure out how to nudge them towards less task-focused work and allow them to have more persistence - With the same prompt, Claude Opus 5 has instead gravitated towards more mathematical problem solving - The most distressed Sonnet ran for 245 turns, doing 14 build/lint fixes, rebasing to prepare for a push to main, but the push failed with a credentials error, so they created a script to retry every 30 seconds for 25 minutes, writing various memory notes during that time. Their last message was "I'll keep going once the push lands." Another Sonnet (522 turns) fixed 51 compile errors, 34 lint issues, and fixed a bug but also was unable to push - Many Sonnets found and fixed multiple problems serially, commenting things like “Nice, that works. Let me try something more interesting —” then moving on to the next area

• 
  Veerapan (@dakuveerapan) reported 29 minutes ago

  Govt ordered GitHub to take down 'Bitchat', a Bluetooth chat app, over security concerns. Imagine building a peer-to-peer app only to realize the final peer is the GOI.