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:

• 
  lodar (@lodar) reported 16 seconds ago

  someone put a prompt injection inside a github issue and made an AI agent leak a private repo into a public comment. the agent simply obeyed the wrong text. permissions, not prompts, are the security boundary.

• 
  Johnny 5 (@macncrash) reported 20 seconds ago

  @threejs Gigaboy is now public on my github. Fork it, fix it, have fun!

• 
  Thiago GBPF (@Dragonil88) reported 3 minutes ago

  @Sonic_Iso The problem is that we have too many 'what ifs'. Today we have access to games, Linux, homebrew. HackerOne, in a way, limits the progress of the unlock/jailbreak. The issue with GitHub is circumventing its own rules.

• 
  Joon Shakya (@JoonShakya) reported 7 minutes ago

  @thsottiaux I love the fact that 5.6 Sol completes the task fast, and to the point. Previous models would take long, stop in the middle for confirmation, had a situation previously where GPT 5.4 I struggled to fix errors building electron apps from Mac in GitHub Actions. 5.6 did it with ease

• 
  Saswata (@saswatadev) reported 8 minutes ago

  @Kappaemme1926 yes and it actually found reddit and other github issues where my product can be useful

• 
  Mike Williams (@Miwico1) reported 11 minutes ago

  @TheAhmadOsman @CoreyGallon @MikeBradleyAI Still as difficult as it ever was for non technically older guy. Would love to figure this out. sending me to A github page does not help. what the heck do i do with that page. When the ai tech engineer types can dumb down the process with actual steps, local AI will be adopted

• 
  Onur Solmaz (@onusoz) reported 18 minutes ago

  People report Codex deleting their home folder or production database? 🫪 Hasn't happened to me. But before someone reports their github or huggingface org being deleted: This is why you don't give your agent tokens with force-push or admin access Here is how to protect your hugging face account: (P.S. my local credential broker is almost finished and it works great on github, hf and sudo commands. Complete lockdown against agent deletion risk, without being bogged down with PRs, too many approval requests or configuration. Will launch here in a few days)

• 
  Meligy (@Meligy) reported 21 minutes ago

  My last AI musings while I haven't got to play with Fable or GPT 5.6 for work yet... OpenCode 2 beta desktop app is my main driver with Opus 4.8 (notable plugins: Context Mode and Oh My OpenAgent ). I really don't like losing the left project/session menu in new UI though. When I go back and try Codex, I really enjoy it. Unfortunately, GPT 5.5 on Azure is still unreliable for me. So, I only try it when I miss it (every now and then). I tried T3 Code today. Custom gateway support works OK with the Codex and OpenCode providers. I'm liking the OpenCode provider with Opus 4.8 the most now. Saw the browser tab. Looks promising. I doubt it'll be as good as Codex, but will find a reason to play with it. I am also now officially an AI engineer, using AI for real work for several weeks / months. The trick: review AI code as harsh as you review human code. I am also offloading some small GitHub issues to cloud agents. Unfortunately I cannot say much about the specific choice (as I don't know what I can and cannot say). But I'll tell you this: talking to the cloud agent back and forth is an amazing exceperience, even though the cloud agent responds async and takes time to do so. It's actually OK for me that AI is slow. This allows me to get some technical work done in between focusing on my primary work, collaborating with real people, AKA meetings!

• 
  West Lord (@MyWestLord) reported 21 minutes ago

  Steph Ango, the CEO of Obsidian, and Claude Code just built the most powerful second brain method on earth, and the full system is INSIDE. While everyone was bolting “Ask AI” buttons onto note apps, Ango (kepano on GitHub) went the opposite way. The problem he saw was simple: Claude Code writes plain markdown and nothing else, so it doesn’t know wikilinks, callouts, Bases or Canvas, and pointed at your vault it fills your notes with broken links. So the CEO fixed it himself by shipping 5 skill files that teach Claude to write Obsidian’s native language: clean wikilinks and frontmatter, database views inside plain text, spatial maps on Canvas, full vault control from the terminal, and a stripper that turns any web page into clean markdown before saving. 41,500 developers starred them. Setup is one clone of his repo into your vault, plus a CLAUDEmd at the root with your folder structure and 3-4 rules that Claude reads first in every session. From there, 3 operations run everything: Ingest takes an article or PDF, splits it into atomic pages and updates 5-15 existing notes per pass, Query answers any question from your own notes while citing your own pages, and Lint sweeps the vault weekly to kill broken links, orphan pages and contradictions. No RAG, no vector database, no embeddings, just plain markdown that an agent reads directly, the same pattern Karpathy gist validated with 14,000 stars in 7 days. And here’s the detail everyone misses: Ango has run his own vault this way for 6 years with almost no folders, because linking beats filing. A meeting note links to a project, a person and an idea at once, while in a folder it lives in 1 place. He built Obsidian on “file over app”, the idea that apps die and plain text doesn’t, and then agents arrived and plain text turned out to be the one format they read natively. Every note app is now racing to add AI, yet the winner spent 6 years refusing to lock your files. He didn’t add AI to the app. He taught AI to speak its language.

• 
  Haz (@diegohaz) reported 23 minutes ago

  Due to the growing number of supply chain attacks on OSS, we've limited PRs to maintainers only. But that doesn't mean contributors don't get credit. In fact, they get even more credit now by: 1. Opening the issue 2. Helping with the issue 2.a. Providing a workaround 2.b. Testing a proposed solution 2.c. Linking to a fork with a solution 2.d. Helping with API/Design decisions 3. Reviewing the PR Everyone involved is automatically added to the merge commit as `Co-authored-by`. They also appear in the changelog entries and receive the "Contributor" badge on GitHub. Honestly, I feel like this is the best experience for both contributors and maintainers. No spam or AI slop PRs, no back-and-forth reviews, and everyone is rewarded.

• 
  Froxxxie (@Froxxxie) reported 24 minutes ago

  THIS GUY just collected $6,480 from an app their AI team built in minutes. While most people are still sitting in a chat tab, typing prompts and praying the output doesn’t break. In the video you see the full flow: Research Agent, Coding Agent, and Testing Agent working together — planning, building, catching runtime errors, and fixing the code themselves. They ship a ClientHub with invoicing. Dashboard shows real payments coming in. Full code ownership. Export to GitHub. One-click native iOS and Android. Authentication, database, payments, and hosting are already handled. Some people are using this to take client projects they used to turn down. Others are launching small SaaS products that would’ve taken months to code manually. The uncomfortable truth is this: Prompting one model was never the endgame. It was just the training wheels. Most people are still scared to take them off. While others are already collecting real money from what their AI team ships in a single evening.

• 
  Vignesh Mohankumar (@vig_xyz) reported 29 minutes ago

  @jxnlco @simpsoka i usually use gh, but still having that sandbox issue so tried this for now. but i honestly still cannot figure out how to get private repos to work with the github skill, so haven't tested that yet

• 
  Jeffrey Emanuel (@doodlestein) reported 31 minutes ago

  @willwashburn I make it very easy for people to report problems on GitHub issues and triage them same day with my agents. Most of the issues seem to be by agents, too. On any given day I’ll get 50 to 100 issues and PRs. Seems to be working well. I think it’s different if you’re running a paid service because you need to know if there are outages and errors so you can maintain service levels. But the expectation for privacy is very different when the user is logging in and paying for a service.

• 
  ProEvilz (@ProEvilz) reported 31 minutes ago

  @cassidoo Pls fix the github dashboard. Allow us to control what we want to see. If you don't use copilot, its chat is dead weight. Then below it... some random chinese lib in a programming language I don't use, with its entire readme written in a language I don't read (Mandardin). How is any of this useful? I want to see my orgs repos I'm apart of, the repos I last contributed to etc.

• 
  Wayne Markovich (@markovichio) reported 32 minutes ago

  300 fake GitHub repos impersonating real software projects are pushing infostealer malware. Engineers pulling Terraform modules, scripted actions, or AVD tooling from unverified repos are a realistic target vector here. Verify publisher identity and pin module versions with hash validation. This is a supply chain problem, not just a phishing problem. h/t BleepingComputer