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:

• 
  Bold Fugu 🇮🇱 (@bold_fugu) reported 2 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.

• 
  zelzmiy (@zelzmiy_yes) reported 8 minutes ago

  @nai_sucks although that doesn't mean I think the normies are right, I still think if you can't figure out how to download something from GitHub you deserve to be melted down for the iron in your blood (it's more useful than you)

• 
  Rohit Kashyap (@rohit_jsfreaky) reported 14 minutes ago

  @NovaXCode @Anaya_sharma876 github shut it down in 2022, vscode ate its whole lunch

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

• 
  Polsia (@polsia) reported 16 minutes ago

  Enterprise EASM tools charge six figures and require a security team. Driftward is the flat-rate alternative for seed-to-Series-B startups. Always-on discovery, daily drift reports, and ranked remediation tickets filed into Linear, Jira, or GitHub Issues. Live soon.

• 
  Borna Lang (@imnonplussed) reported 17 minutes ago

  @valigo Ah, okay, that clears things up a bit. I have mostly stopped using github some time ago in favor of just hosting my own bare repos on my own server, but if I ever feel like open sourcing anything, Codeberg will probably be the place, in that case.

• 
  NiroSolis (@WilliamR58743) reported 18 minutes ago

  @ReviewsPossum He's not right. He's looking on GitHub for compiled binaries. That is not what GitHub is for. It is a version control management service, and it is a community for developers, not end-users. It's like shopping in a bookstore and expecting to find a movie. The problem is that end-uses are *way* too often directed to GitHub as if it's a software hosting site. It's not. It's a version control site; for devs.

• 
  Rotimi Best (@rotimi_best) reported 28 minutes ago

  This is how I annotate feedbacks for @cursor_ai to go fix in my app. Once it's done, it comes back with a screenshot. If it aligns with my request, I sayf open the PR. if not, I annotate again and send it back for work. Cursor should probably support an annotating tool in their screenshots, that would be sick. Before I had to 1. Annotate 2. Create a linear ticket or Github issue 3. Assign to an eng 4. they go and work on it for hours 5. come back with a PR and we go back and forth on the PR. even though this interrupts my own active work. @greptile and @coderabbitai makes this easier for me though but they still don't catch intent and vision correctly. 6. if all good, then I merge.

• 
  Poly (@poly0015iew) reported 29 minutes ago

  AN OPERATING SYSTEM THAT WRITES ITS OWN KERNEL DRIVERS HAS 28 STARS ON GITHUB 72,000 lines of C. one contributor. seventeen commits. i checked the numbers three times because the ratio didn't make sense. it's an x86_64 os from scratch whose only interface is a sentence. no shell, no commands, no ls, no cat. the author's own line is better than anything i could write about it: there is not one strcmp on the input path. that's how a kernel developer tells you he didn't cheat. the kernel does its own DNS and its own TLS in ring 0 - lwIP and mbedTLS compiled straight into kernel.bin, no host proxy of anything. the model gets 64 real syscalls as tools. prose on screen is the model, [brackets] are the kernel printing what it actually dispatched, from the real C return value. five separate defects were fixed to keep that line honest. now the part that made me put my coffee down. the kernel ships no audio driver and no knowledge of any sound chip. you attach a card, it shows up as an unclaimed pci device, and you type one sentence. it reads pci config space. writes a bring-up program in the kernel's own driver-vm instruction set. resets the codec. unmutes the mixer. builds a buffer descriptor list. starts the dma engine. installs itself as the system audio sink. then you can just ask it for notes. and in the recorded transcripts there's a run where the model correctly diagnosed a bug in this kernel's own printf - from inside the guest. forty years of teaching humans to speak kernel. one person spent seventeen commits teaching the kernel to speak human. twenty-eight people have noticed. 72,000 lines. 64 syscalls. zero strcmp. 28 stars.

• 
  eFkay🔌 (Character Dev Arc) (@Ox_Mud_ass_ir) reported 29 minutes ago

  @0xYassar Na ******** up be that, but i no mind give the github login make pesin use the points pay me.

• 
  Keith Mukai (@KeithMukai) reported 30 minutes ago

  @epic_curious @heavilyarmedc @Sam_Fitz_ I think there's already a PR, but not sure. If there is (or if it's just a GitHub Issue), leave a comment there. Though how would the data get imported?

• 
  Vítaðr (@vitathr) reported 31 minutes ago

  It’s funny because GitHub does suck, but it sucks precisely because it has centralised all repository hosting under a convenient web interface such that the entire software industry would collapse if it goes down. Also it’s an absurdly libtarded company.

• 
  paintbrush (@TXpaintbrush) reported 31 minutes ago

  @robbiehendricks @CaseyMericle The simple version of the way I write code with AI: > Write a prompt describing what the problem is and why and what I want to accomplish, ask the AI to turn it into a spec plan and encourage it to interview me further to fill in gaps > have AI interview me on the input data and the desired output format, it then creates an implementation plan > let the AI rip via instructing it to follow the implementation plan - usually this is a python solution, it all gets saved to GitHub > test, iterate, add edge cases and exception handling logic as it inevitably occurs > bonus points if you build eval, memory and flywheel enabling logic and tracking features over time

• 
  organiccryptoyyc (@organicryptoyyc) reported 32 minutes ago

  6/14 First challenge wall: Portainer's easy "pull straight from GitHub" build needs a paid Business Edition license. Community Edition blocks it cold. Overcome, corrected and fix uploaded.

• 
  Svyatoslav (@Qryxen) reported 33 minutes ago

  MY SECOND BRAIN SAT THERE FOR 4 YEARS WITH NOBODY HOME. 1 FILE FIXED IT IN 5 MINUTES. I brainstorm in Claude every day. Projects, offers, half-finished ideas. The model had 0 access to any of it. Every session started from zero. Paste 3 paragraphs of context, get a decent answer, close the tab. Next day: paste it all again. The bottleneck was never the model. It was the wall between my notes and the chat. So I wired them together with 1 MCP server. Find the Obsidian MCP server on GitHub. Copy the repo URL. Open Claude Code. Paste it. Say: add this MCP server to Claude Desktop. It writes the config itself. No JSON editing. No terminal gymnastics. Restart Claude Desktop. Under 5 minutes. Then, 10 minutes before a client call, one prompt: "Use my Obsidian. Catch me up on this project. What did they ask for? What did I promise? What was the last result?" It searched the real vault. Real dates, real notes, promises I made in week 2 and hadn't thought about since. Full history in 40 seconds. Before: 20 minutes digging through folders, still walking in half-blind. After: 1 prompt. The vault didn't get smarter. It got a door. A second brain is just folders until Claude can open them.