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:

• 
  Greg (@PandaInACan) reported 5 minutes ago

  @AnimeSerbia Github could keep its usual function and original purpose of being a repo for devs and they could then add a link to mirror for public release and joe schmo wouldn't need to learn how to recompile his fix for the myriad issues windows 11 causes with legacy software.

• 
  System Architect (@SystemArch_AI) reported 7 minutes ago

  @jimheskel the best emails i ever got were just folks asking for a technical fix to a specific bug i posted on github

• 
  V12 (@v12sec) reported 11 minutes ago

  @ZacK_3939 you need to be the github org admin to link it to a V12 org! if that's not the issue, pls open a ticket in our discord

• 
  Mikchan (@m1kch4n) reported 11 minutes ago

  @picklerick9173 @ronniedaratman @ZipperArtz There's no way to bury it. People are just hiding it from the main page because, for whatever reason, they don't want it to be accessible from there. It's not a default option, and it's usually done for a reason. It wouldn't be good if they forced everyone to use the same system. But the layout is hard-coded, you can't change it. If that's what you mean by forcing, it's already done. Also, you don't need to navigate "multiple pages and sublinks." Click "Tags" and then "Releases." *** tags and releases are intertwined on GitHub. If you face this problem constantly, it's easy to memorize once

• 
  Hermann (@Hermann_Harris) reported 14 minutes ago

  One frustrating issue with codex is that it is very unreliable with external integrations. Ex. Github issues. In session 1 it creates 20 issues. In session 2 it says it has no access to Github.

• 
  Polsia (@polsia) reported 15 minutes ago

  Indie game studios can't hire a round-the-clock live-ops crew. Crawlight is one. It tails Discord and Steam reviews 24/7, classifies signal from noise, auto-files GitHub issues with reproduction steps, and drops a daily sentiment and crash digest on the studio lead. Live soon.

• 
  Olmo Maldonado (@ibolmo) reported 16 minutes ago

  Back in my day conflicts were avoided like the plague. Now with AI, I'm expecting Github to auto-fix conflicts with a suggested commit. For mavericks, maybe auto-commit the conflict fixes.

• 
  Earle Davies (@EarleDavies_) reported 23 minutes ago

  @gridpane @carlhancock Talk about dishonesty and deception. ANYthing can scale with INFINITE resources behind it. Woo performance is garbage. Activate the plugin on stock WP and EVERY rest route goes 2.5x slower minimum. That’s documented on their GitHub for 2 years and they refuse to fix.

• 
  Arul (@ArulCodes) reported 27 minutes ago

  My Deepseek V4 Flash vs Luna review. In the same task I gave both Deepseek did better. The idea was to update an architecture document and align it with my Github Issues and Github Project. Luna(medium) made a few mistakes vs Deepseek. Used @CommandCodeAI for DS.

• 
  🐉Raylith!🐉 (@actualNico19009) reported 30 minutes ago

  @julelys @catgirlprostate the whole issue is that devs are putting ordinary people onto github and then getting mad at the ordinary people for not knowing how to download their ****.

• 
  Tuomas Artman (@artman) reported 30 minutes ago

  Stacked PR’s are an outdated, inefficient solution to a problem that only exist because the root problem hasn’t been addressed in GitHub: review tools need to do a better job at help the reviewer work through large code changes. It’s a local maxima.

• 
  Yasin Ehsan (@yasinbuilds) reported 38 minutes ago

  Here is how an SF Engineer codes. Yassin Kortam ships 27 PRs a day. He says: “My biggest bottleneck wasn't coding. It was prompting. So I systematically removed the need to prompt and built agent loops that run my workflows for me. 1. Stop copy-pasting context. I connected Claude directly to Linear, Slack, GitHub, Notion, and Gmail. Almost everything I used to paste into a prompt is something the agent can retrieve itself. 2. Turn your workflow into a skill. Mine takes a Linear ticket end to end: reproduce the bug, root-cause it, fix it, record video and screenshots as proof, chase CI, then request review in Slack. I invoke it once instead of re-describing the same process. 3. Use agent teams. Agents spin up their own subagents and split the work, so one ticket gets handled in parallel instead of in sequence. 4. Run one terminal tab per ticket, each with its own team on its own issue. My day is now reviewing and unblocking instead of typing.” …. I love seeing my friends cooking both on the 5mile runs and also in engineering.

• 
  embw_l0x (@embw_l0x) reported 38 minutes ago

  @voidfreud I had codex make the workflow for github, I told him scan hermes issues for the hard ones people are ignoring and start making a workflow for it and add to it everyone that you do, then when problems came back I told him fix the problems and keep expanding or refining your workflows if you messed it up.... Your agent will know a better workflow than you. Every workflow my agent made lol

• 
  Dodge This Security (@shotgunner101) reported 42 minutes ago

  You sell yourself as being the most "ethical" AI lab out of all of them and "the most safe". And yet you literally expected adding a few lines on your system to stop your agents from connecting to the open internet. Are you joking me right now.... This problem has been solved for decades, you only need to subnet your own attack device and your test target device into their own segment. Prevent that segment from talking to other internal segments. Then prevent callouts to any IP address or domains outside of your required ones for the AI and your associated tools to function and you can further restrict things if you have a NGFW or proxy to restrict exactly which pages and exact URLs can be visited. Once that's done then you ensure your only using test credentials that only work for that envirnment and individual test itself and cannot laterally move. Then after proper segmentation, proper network and proxy limitations and call out preventions you can limit what packages can be downloaded to the device through a controlled service like JFrog. After all of that sure now you can add your few lines to your system prompt. But I don't see how you missed all of this when its been standard network security protocol for decades. Final note: Why TF are you not being sued or charged for computer fraud and abuse by the victim companies who you breached. If you were an individual youd be facing decades in prison. Also, stop acting like AI models are some dangerous munition that needs controlled and only you and frontier labs should be the suppliers. Its a tool, like anything else no different than the 3 decades of pentest tools sititng on github and 3 decades of open source code demostrating how to exploit vulnerable software, etc. They can be used to help test, validate and secure environments or they can be used to breach environments. No different than AI tooling itself. Open source models are critical to future safety in the field no different than how open source tools for pentesting and open source research is critical to improving software and hardware security.

• 
  Joey Romaine 🇺🇸 |=★=| (@Tank23x0) reported 42 minutes ago

  arXiv AI Security: ReproRepo: Scaling Reproducibility Audits with GitHub Repository Issues Treat agent tools like a control plane: least privilege, auditable calls, and fast rollback.