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:

• 
  0logn (@0logn) reported 6 minutes ago

  Remote coding-agents (aka software factories) are really a dev-ops (not AI) problem. Some security problems to solve but mainly it's a high-performance caching problem. The CI providers (e.g,. Github Actions, Blacksmith) were (are?) the best positioned to solve this.

• 
  Egor (@jvqtil) reported 7 minutes ago

  New release of dpm - Decent Package Manager Now it supports installing packages from Direct URLs, besides GitHub and local files. Would really appreciate your feedback in DMs or GitHub issues!

• 
  🎱 (@aldea_trading) reported 8 minutes ago

  @zocomputer Like popular login pages does not have Google login page ?? Like wtf most of **** is already logged in through Google or github account

• 
  sid riff (@sidriff) reported 10 minutes ago

  Some notes on what didn't go so well, possibly some feedback for SpaceXAI. 1 - Context window management. As far as I can tell, there isn't any in the app builder. When the project gets more complicated, the agent tends to truncate or wipe files. You can nudge it to split large files which tends to help. 2 - Saving progress is generally cumbersome. Pushing to Github is clunky and sometimes it fails. That makes issue #1 extra terrifying. So far I've not encountered a state I couldn't recover from. 3 - All of these app builders always spring for React/R3F and in my experience it always gets in the way. There's some obvious stutter with the faster moving pieces, even on my 240hz display. I'm guessing once I rebuild it in straight three.js, that will go away. 4 - Sound. It's always the hardest part. I have some workflow solutions that involve existing libraries/elevenlabs but I was trying to stick with app builder and I wasn't willing to paste my API key in the chat! Disappointed that Build mode doesn't have access to the Grok Voice API (but it can get to Grok Imagine). All in all, I'll probably stick with Grok Build in the terminal. But build mode makes it so easy to get up and running with an idea.

• 
  Delali (@delali) reported 15 minutes ago

  If you bind request data straight to your models, your server will accept every field that model has, whatever your signup form puts in front of a customer. The browser is only sending a list of names and values, and anyone can edit that list before it leaves their machine. OWASP calls this mass assignment, and the example it gives is a registration form that writes straight onto a user record with an admin flag on it, where anybody who adds that flag to the request comes out the other side an admin. GitHub ran into the same thing in 2012, when somebody added a public key to an organisation they had no rights to and came away with commit access to its repositories. Your framework has had the fix all along. An allow-list, which Spring calls setAllowedFields and Laravel calls fillable, names the fields the server will take from a request so that it can drop everything else that arrives. You pay for it by writing your field names down a second time, which is cheap for knowing what your server will save. Better still, use a request DTO to validate every single request field to your API.

• 
  pseudo 🇺🇦 (@pseudotheos) reported 24 minutes ago

  GitHub goes down more than solana at this point

• 
  Saran (@vibe_coder_cj) reported 28 minutes ago

  @github @GoogleAI Please remove the 200 credit system, and bring back the old model. Even not able to solve a single problem, in a single session the whole 200 credits were disappeared.

• 
  Aakash Gupta (@aakashgupta) reported 28 minutes ago

  There is an entire genre of content about how to write the perfect CLAUDE .md . Front matter debates. Line count debates. What to put in, what to strip out. Oji Udezue's scaffolding skill generates one per project, as an output. Not a template you adapt. A CLAUDE .md written for this specific codebase, that knows how to hunt bugs in it, follows the folder patterns it just created, and follows the prototype patterns it just set up. Then it does the part people miss. It writes the folder structure into that same file. Where documents go. Where milestones go. Where prototypes go. For every folder, what belongs in it, addressed to both you and Claude at the same time. That makes the repo self-organizing. The instructions for maintaining the structure live inside the structure. Nobody has to remember the convention, because the convention is loaded into context every session. Same pass sets up the rest of the scaffolding most vibe coders skip entirely. A test folder. Continuous integration, so every check-in runs the tests. Security, including finding your secrets and getting them gitignored before you ever push to GitHub. Then a bug classification system that catalogs failures over time and learns from them. That last one is the sleeper. Everyone treats bugs as things to fix and forget. Cataloging them turns your own failure history into context the model can read on the next project. Worth saying what he did not claim about any of this. On the market research the same skill produces, he was direct: you can get 60 to 70 percent of the way with LLMs before you go find real sources. He said the danger in the whole workflow is taking it as gospel, and that he does not fully trust LLMs 100 percent, so he reads every output. A skill that produces this much artifact this fast only works if someone is still reading it. The CI templates and the CLAUDE .md pattern are the pieces this offloads best, because they are the pieces most people either get wrong or never do at all. Your CLAUDE .md was never supposed to be a thing you author once and defend. It is infrastructure, and infrastructure should be generated.

• 
  John Broadway (@JEBroadway) reported 32 minutes ago

  Look at where the real money in AI is going: infrastructure and hardware. Software is becoming cheap to generate. Hell, AI can even help layout silicon, but that code still has to execute on physical machines. That’s why NVIDIA and hardware vendors hold all the cards right now. The era of the "pure" syntax coder is ending. We don't need people typing out loops; we need hardware engineers and systems folks who understand physical compute and how big systems fit together. I’ve been in tech 36 years, from bench PC repairs to global rollouts and managing dev/hardware teams through every shift since the 90s. To me, AI hasn't made us all coders. It’s made us builders. I’m not a developer. I’ve looked at COBOL, Pascal, Python, C++, Rust, you name it. I see patterns and images, not syntax. When I use AI, I describe mechanical systems: "Picture plumbing in a ten-story building" to map how data moves between agents and apps. That's the difference: A coder connects one pipe. A builder knows what concrete goes into the foundation to support forty floors, where electrical runs, how HVAC ties in, and what the final layout looks like. Calling this "vibecoding" as an insult misses the point. AI handles syntax so I can focus on how the engine runs. It also exposes how broken software licensing is. Selling clunky subscriptions, charging for bugs, and charging again for patches is dead. Value is shifting back to open source, real support, and experience. Open-source tech like Proxmox and ERPNext are primed for this, and I build right on top of them. So when you see me arguing with traditional devs in forums, it isn't Dunning-Kruger. It's just the pattern laying itself out before you see it. I build governance into everything. In my world, I see a farm with a barn housing bare-metal servers running Proxmox while my ERPNext hums along generating mailbox money. ;) Some of my GitHub Projects so far: Maude for Claude: A dedicated partner environment operating right inside Claude. Proximo: A lean infrastructure and governance tool built to streamline local workflows. Pacioli: An open-source accounting and operational framework built for real execution. AI can write all the code it wants. It still can't bolt a rack into a datacenter or manufacture the chips it needs to run on.

• 
  Terry Aney (@terryaney) reported 33 minutes ago

  @davidfowl @burkeholland @pierceboggan It was some build actions that did AI review, release notes, etc. I've modified my fork to remove. Might be a feature worth thinking about that forking in github checks for AI actions that might eat credits :) But problem solved for now.

• 
  Keisuke (@KeisukeIshikawa) reported 36 minutes ago

  Manus just made its AI agent free until August 25 no credit card, no phone number. And this isn't a stripped-down chatbot trial. You can give it an actual job and leave: > research dozens of sources in parallel > browse websites and complete multi-step workflows > write, run, and debug code > analyze Excel sheets and PDFs > edit images and work with files > connect Gmail, Slack, GitHub and other services schedule tasks to run automatically It plans the steps itself, executes them, checks the result, and you can watch the agent working in real time. This is probably the best time to test the question everyone keeps arguing about: can an AI agent actually replace hours of browser + spreadsheet + research work, or does it still need babysitting every five minutes? Until August 25, finding out costs nothing.

• 
  Kyle Bradshaw (@SkylledDev) reported 37 minutes ago

  @bcherny I've got most of my tools setup to emit errors to a service that creates GitHub issues. Claude Code periodically checks the untriaged issues, investigates them, then comments a proposed fix. I approve or give feedback to the proposal, then another Claude creates a PR.

• 
  Nibras Hamza (@NibrasHamza) reported 38 minutes ago

  @Anas_founder Official docs, GitHub, and a lot more trial and error.

• 
  martian (@martian0x80) reported 39 minutes ago

  github down again

• 
  Chris | The DeFi Professor 🇵🇭🇺🇸 🐊 (@csoriano) reported 40 minutes ago

  *sigh* Another phishing attempt. Get me on a legit Google Meet, hear about what I do with my content and my story in this space, then introduce their content but ask me to clone the GitHub repo and run the app. Yeah, don't do that. @tarsprotocol you've got people out there. Fix it. @SolanaFndn