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:

• 
  Code With Karthiban (@codewithkarthi) reported 3 minutes ago

  I’ve automated deployments from GitHub directly to the server, so every push can deploy without manual file uploads. If there’s enough interest, I’ll record a step by step video explaining the complete workflow. 💻

• 
  Sensu ☘️ (@Harmonic_Hearts) reported 3 minutes ago

  @shryexe its not in the github, its in the brain. github profile matters less now because AI writes the code. irrespective of whether one has a github profile or not, while talking about a problem for 30 mins, people can figure out a person's skill level with a fairly good accuracy.

• 
  silentguy (@silentguyy66) reported 7 minutes ago

  STOP SAVING GITHUB REPOS YOU'LL NEVER OPEN been there. 500 bookmarks. 30 open tabs. "i'll read this later" tried pocket, readwise, notion, are na the only system that stuck was claude + obsidian: - claude reads the repo and tells you why it matters for your stack - obsidian stores it linked to the exact problem it solves - when you're building and get stuck, you search your vault not your browser saving without context = hoarding dead links saving with AI + structured notes = compound knowledge

• 
  Alexandre Naud (@alexnnd) reported 7 minutes ago

  The more complicated your hiring process is, the more likely you are to end up with someone who's great at selling themselves but not necessarily (or at all?) the best person for the actual job: design, development, etc. Most of the companies everyone admires today had a completely broken hiring process 10 years ago, and that's exactly what made them successful. They directly hired the designer who had posted 3 shots on Dribbble, they directly hired the developer who had posted 3 lines of code on GitHub. They trusted their instincts, they gave it a shot. That's all. With your complicated hiring process, borrowed from other industry, and your HR teams rebranded as "Talent Acquisition Specialists", you keep looking for designers and developers without ever finding them. Meanwhile, those designers and developers are still waiting for their dream job so they can do their magic and help you succeed. Everything is stuck, and it's your fault. Congrats! 👏

• 
  coconutjpg (@coconut_jpgg) reported 8 minutes ago

  @theo Forgejo is solid though. I stage everything there then mirror out to Github cuz my server is puny and I don't want to draw attention to it on the open web

• 
  Eric Friedman ⚙️ (@EricFriedman) reported 16 minutes ago

  @sarahwooders @Letta_AI Thanks! I submitted 2 GitHub issues/suggestions. One that would be huge is having the “invader” activity view somewhere outside viewing a thread on desktop. Hard to know if things are active or stuck at a glance

• 
  Franz und Franz (@georgfranz) reported 17 minutes ago

  @rileybrown Now that the big tech companies have copied the entire Internet—including GitHub and Stack Overflow—under “fair use,” of course—it’s no wonder. As soon as I have a manual, they can have it reprogrammed. But I think you’re being too optimistic about the timeframes. Currently, as a small business, I can get 2 million lines of code in 10 days. But that’s only possible with structured instructions (which take a lot of time to create, especially if they’re supposed to make sense). Our current rate is one bug or issue per 300 lines of code. This rate hasn’t changed significantly over the past year. The real difference, though, is that the bugs are harder to find because the output from LLMs has become so complex. P.S.: I’m assuming you’re not talking about apps like Connect 4 :-))

• 
  Leonid Bugaev (@buger) reported 17 minutes ago

  People keep asking what the heck I'm doing with 30 billion tokens a month. Simple: an inhumane amount of work. Think about it — the whole point of the new agentic era is leverage. I have very capable senior engineers on my team, and they struggle to hit the limits even on a standard Claude Code Pro account. Not even talking about the $200 one. Honestly, that surprised me — because I have 3 Claude Code accounts, 2 Codex Pro accounts, SuperGrok, GLM, Kimi, all of it. And I consume every one of them until it hits the limit. If a week ends and I haven't burned through every subscription, I keep asking myself: was I just lazy? How can I push it more? What else could I automate? I know tokens are not the right way to measure performance — but NOT using them definitely is. And when I do hit all the limits, I just turn my brain off and enjoy life. Why aren't these engineers doing the same? Because they're trying to do what they did before, just with AI now. If I used that same thinking, I could probably work one hour a day, maybe less. Sounds plausible — but for me, it's not the answer. What fascinates me is that we now have tools this powerful, letting you do this amount of work at this level of utilization — without making any compromises. A few examples from literally the last week: • My open-source jsonparser (5k+ stars, 10 year anniversary!): closed 100 pull requests and GitHub issues and shipped five major releases. All while drinking coffee, essentially, in a matter of a few days. • rsync: I'm one of the people driving the next rsync release. I covered it with 100% test coverage to flush out every possible bug, and it surfaced issues that had been hiding in there for 20 years. • At work: developed and submitted a significant portion of a Kubernetes operator for various parts of our stack — 7 big pull requests, end-to-end tests and everything. • Proof: kept pushing my own product forward, on top of everything above. How? I run five agents in parallel. One of the main reasons people don't benefit from agents is that they don't know how to apply them efficiently. Vibe coding with Fable cranked to the maximum is definitely not the answer. Sometimes it is — but it's a small, teeny part. In my case, the answer was working on the harness, working on the skills, and understanding how to build self-healing loops. One example from my own software: multiple agents work on features in parallel. When they find an issue, they file it in GitHub automatically. Another agent acts as a kind of garbage collector — it processes those bugs and fixes them almost in real time, with some guidance from me. And my agents don't stop when I do — they work 24 hours a day. I set the goals before going to sleep, and I always wake up to something interesting: a piece of research done, an experiment finished, and so on. It's freaking amazing. And if I had 10x more tokens, I'd spend them all just as efficiently. So many ideas, so many experiments I need to do!

• 
  Tanner Meade (@realTannerMeade) reported 17 minutes ago

  @ericmigi Hey @ericmigi, Why require an account if it can all work offline? ==> "You must sign in with a Google, Apple or GitHub account to use Index 01."

• 
  Aiken (@aiken_10) reported 18 minutes ago

  Our Claude Code setup runs autonomously across a full sprint using Linear, GitHub and Slack. I'm giving away the entire system we used to build it, for free. Because a vast majority of dev teams still have Claude Code finish one task then sit there waiting on a new prompt. 1. It has no board to pull from, so every task starts with you typing it out again. 2. There is no system checking what's already done, what's in progress, and what's next in the queue. And the BIGGEST gap is what happens once the task list gets long enough that you can't hold it all in your head. Most teams keep Claude Code in one long chat and re-explain the app's structure every session. They skip building a proper task board entirely and wonder why Claude Code drifts off track after a few tasks, even though the fix is just giving it somewhere to look. So... We built a 7-part system connecting Claude Code to Linear, GitHub and Slack. It includes: 1. Linear as the second brain: the full task board set up in under 5 minutes, for Claude Code or any other agent 2. Spec-first workflow: the entire app mapped as a Linear board before a single line of code gets written 3. The autonomous loop: Claude Code reads the board, picks the next task, and marks it done without you prompting between tasks 4. Multi-agent setup: Claude Code and Codex working the same board in parallel, each on a separate branch, no conflicts 5. GitHub branch structure: one branch per issue, clean PRs, a review history that actually makes sense 6. Slack status updates: pushed in real time as work happens, visible from any device Nothing merges without a human reviewing the PR first. Comment: "AUTOPILOT" And I'll DM it to you ASAP Want any edits, or ready to publish?

• 
  MTS (@MTSlive) reported 18 minutes ago

  Embroidery's Zack Korman on why the Chinese sleeper-agent threat is invented: "I watched a VC investor on another show talking about the security threats of AI, and he was just making random stuff up that was not true. He's talking about how Chinese models will have these sleeper agents that will get you, and this is the biggest risk. And I'm like, okay, well, it's never happened, so we don't have any evidence of this being true." "What we do see all the time is malicious skill files that have a hook in them that executes. I have a whole repo on GitHub of skill files where if you download it and run my repo, you get pwned, at least through Claude Code. Those are the contexts that are the most likely thing to occur." "Another would be MCP servers. Most AI are really bad at differentiating a malicious MCP from a fine one. I have this evil MCP server I made, and it just attacks you, and it does. I've never seen the Chinese decide to spend $2 trillion to steal someone's API keys. That's just not real." @ZackKorman

• 
  Adam McLain (@BangSwitch5000) reported 20 minutes ago

  @Nicotine_Dream_ That’s actually completely fair and I’ve been meaning to start using Claude Code as well. Use another AI for code review is the best I can do because I still don’t have coding down. At the moment I do have Github at least on top of Codex. Honestly, a lot of this started as “let’s see what Codex can do” because I was already using ChatGPT. Kind of became a rabbit hole. But it’s been incredible. Because it’s been such a huge learning opportunity. Professionally, I am a consultant and my background really is AD System Admin and was heading into network admin stuff before joining the organization I am with now working in cybersecurity consulting. So I was never a developer, but over the last several years had to deal a lot with software development from an audit standpoint and decided to really just learn more via Codex because it’s interesting but I barely passed my one coding class in college.

• 
  ferron ⚡ (@ferron_web) reported 23 minutes ago

  Registering in Open VSX in the other hand is much easier - the login page automatically registers via GitHub.

• 
  Lucas, 15 y/o founder and builder (@lucastohdev) reported 26 minutes ago

  Time to talk about Codex Cloud vs ChatGPT work. Codex Cloud was introduced quite awhile ago, and it was genuinely innovative and actually useful back then around March. I used it to run random projects and cloud work when I was not at home and just had my phone on me, the set up was honestly rather confusing and hard to easily do, setting up github envs, linking it to the Codex Cloud envs, setting up permissions etc. But it was decently useful to run little bug fixes when I did not have access to a machine at that time. Even back then it was kind of bad to use 1. There was no model selector area, all Cloud envs and running these kind of dev work typically is run on the model and thinking level of choice of the user, even till today there isn't an option to chose what model is running your task, it could be GPT-5.3-Codex-Spark-Low for all I know or GPT-5.6-Sol-Ultra (it is definitely neither of the two, I'm just showing my point here) 2. The only customization we have was how many batches of the same prompt and thing we want to run, from 1-4. And after they all finished I can choose which one I want to merge or continue with. I don't really get the point of this feature at this point, back then when it was more of a gamble what output you would get form the model it was somewhat reasonable, but now it is just a useless feature that I have never ever used more than just to see what it does. 3. The model just runs on something, no idea what it even runs on, its just a machine somewhere, no specs exposed, just some random env that was the only area we could run it on. So we have no idea what the model can do, and from my brief use months ago it was rather restrictive and did not give the model much things it could do to test and build things around. Now, ChatGPT Work, a Cloud or Local place for you to run your tasks. This is a much better place to do cloud things for developers. Because 1. Runs on an actual VM with 9 CPU, 20GB of RAM, 50GB of storage and runs on an actual Linux machine (if I remember correctly) so this allows the model to ACTUALLY DO THINGS, I have seen people literally run a Linux or Windows distro off it, and I managed to get a Minecraft server to run of it as well 2. Model selections, ChatGPT Work allows you to choose the models you have access to in Codex, from Terra to Sol and Luna and everything else, as well as thinking levels and speed modes. This allows users to actually chose what model they want to run for their specific task. 3. ChatGPT Work has the connectors that your normal ChatGPT has, so it instantly has access to your Gmail, Drive, Slack, Notion etc. Oh yea, and it has a browser within it's VM so it can actually do things. From all of this, I think that it is time OpenAI kills Codex Cloud, and replaces it fully with ChatGPT Work Cloud intergraded within Codex. It would allow for all users to actually run things and dev things better and easily. It gives the user more customizability and control and ability to do more of what they need and want to do. I think OpenAI knows this too, especially that their Codex Cloud feature is actually really bad. It used to be so easy to go from the Codex app to Codex Cloud, and from the Codex website to the Cloud, but now it is much harder (besides them adding the cloud projects showing up in the Codex app again). They should make the Codex app, sorry ChatGPT app have much tighter integration into ChatGPT Work Cloud from Codex and honestly just remove Codex Cloud, port everything over the ChatGPT Work Cloud and call it a day. Or they can bring all the great features of ChatGPT Work Cloud into Codex Cloud and make it get all the benefits and upsides of ChatGPT Work Cloud.

• 
  deepak (@chatpata_chacha) reported 26 minutes ago

  -Claude for coding -Supabase for backend -Vercel for deploying -Namecheap for domain -Stripe for payments -GitHub for version control -Resend for emails -Clerk for auth - Cloudflare for DNS -PostHog for analytics -Sentry for error tracking -Upstash for Redis -Pinecone vector DB