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:

• 
  The Blue-Collar Bard (@RidleyofZebes) reported 2 minutes ago

  That moment when you find a github issue from someone with your EXACT PROBLEM and their SOLUTION WORKS. **** you, sqlite, for dropping support for my ancient server processor. lmao

• 
  Markemus- play The Industrial Council demo! (@markemusgames) reported 6 minutes ago

  @themeperks I'm enjoying playing around with Openclaw, but so far I can't even get the weather app to work. Discord bot is offline, googling is iffy, it can't find conda, and it occasionally cuts off dialog for which there are two issues on github, both closed.

• 
  Kleber Tiko (@klebertiko) reported 6 minutes ago

  @mattpocockuk I used yours with one good rule...every agent and context window must avoid hit 40%. If needed run /handoff with the summary and tracer-bullet tasks to next session. So i can run /clear and startover next tasks. My tracer bullet use github mcp server to create issues to track.

• 
  hacker.house (@hackerfantastic) reported 8 minutes ago

  @TheBlindHacker This requires funding and there is legal liability issues, the best solution is to self-host. We did that initially, but then EDR / PSP / AVP cabal started blocking our DNS - disrupting business - so we were forced onto Github. I believe this orchestration is intentional.

• 
  Tommy Kingsleigh (@tommykingsleigh) reported 12 minutes ago

  Validating an idea. What if your SaaS didn’t just alert you when something broke… It called you, explained the issue in plain English, checked your GitHub repo, generated a fix, opened a PR, and only pushed once you approved it. Low priority = message. High priority = phone call. Critical = AI investigates + proposed fix. Basically a modern pager + AI engineer for founders. Would you trust this? And more importantly, would you pay for it?

• 
  Hi (@hieyz6838) reported 13 minutes ago

  Claude Code GitHub Action vulnerability. Bounty was under $5K. Read the writeup, then tell me this is fair. Supply chain poison, one malicious issue, game over. I have thoughts. But I want to hear yours first.

• 
  - ben - (@Benny_Jiang_) reported 16 minutes ago

  @rauchg I was seriously thinking of building this and i had a quick prototype. I didn't further spending energy on this cuz of 3 issues 1. most skills are reused: at beginning i install a lot of skills at user level, and then just keep using what's working for me. searching from public space is less of a strong need. 2. skill ranking is hard. think of google works because of page rank. i figure semantic search + github star is much more noisy. you probly need to do really expension batch eval to verify what works or have enough traffic to do ranking. therefore, vercel has a much higher chance to make it work 3. internal skill >> public skills. skill is much more value if people within the same company use it to share the tribal knowledge. still very happy Vercel did it otherwise i would always be curious how good it could be

• 
  divyansh tiwari (@DivyanshT91162) reported 20 minutes ago

  The most valuable AI coding resource on GitHub isn't a framework. It isn't an agent. It isn't even code. It's a 65-line text file. The famous CLAUDE.md shared by became one of the most talked-about resources in the developer community because it solved a problem most people don't even realize they have: AI doesn't fail because it's dumb. It fails because the instructions are. Inside are 4 deceptively simple rules that dramatically improve coding accuracy: • Think before coding. State assumptions. Ask questions. Never guess. • Simplicity first. Write the minimum code required. No unnecessary abstractions. • Make surgical changes. Don't touch unrelated code. Every edit must have a reason. • Define success before writing code. Turn vague requests into measurable outcomes. That's it. No secret prompts. No agent framework. No 500-page guide. Just a system that forces AI to think like a disciplined engineer instead of a code-generating machine. Most developers are chasing bigger models. The smartest ones are improving how those models think. Save this. These 65 lines are worth more than thousands of AI tutorials. 👇

• 
  sdfgsdfgsdfgsdfhsdfhf (@sdfsdfgsdfggfd) reported 20 minutes ago

  GitHub really pissed me off this week. I opened my email and there it was: “Enable 2FA in 45 days or we’re limiting access to your repositories.” Microsoft telling me how to secure my own damn code? Yeah… no. So instead of just complying like a good little user, I did the only logical thing: I built my own *** server. Meet Loki — my personal Forgejo instance. It’s running on a clean, fast setup with CachyOS kernel tweaks, looks absolutely sick with a full black glassmorphic theme, and has this badass mischievous black cat as mascot (Loki, obviously). Everything feels fast, private, and actually mine. No forced 2FA bullshit. No telemetry. No corporate rules on my own repos. I’m done feeling like a tenant in someone else’s platform. This is my space now. My rules. My commits.Still a work in progress, but it’s already better than I expected. Feels good to take back control.

• 
  Xavier Pérez (@thexap_tech) reported 24 minutes ago

  The obvious fix: path-filter the workflow to ignore markdown. GitHub has paths-ignore built in for exactly this. I reach for it and walk straight into something I didn't know about required status checks.

• 
  abhisek (@abh1sek) reported 25 minutes ago

  @fr0gger_ The same can happen through GitHub issues as well right? Data is potentially executable now. It’s like we are back to pre NX/DEP/PageExec era. Just at a different abstraction level.

• 
  The A.I. Whisperer (@0xaiwhisperer) reported 28 minutes ago

  Robotics has no GitHub. That's genuinely insane in 2026. Every team rebuilds the same parts from scratch. Same grippers. Same servo protocols. Same 2am debugging loops. Software solved this 15 years ago. You don't rewrite a web server, you fork one. Robotics never got that moment. So we're building it at @tnkrdotai. GitHub for robots: 3D models, build guides, and full assemblies. Forkable, versioned, reusable. 👇 watch what that looks like

• 
  olúwatósìn (@tosintweet) reported 28 minutes ago

  AI hype cycles are brutal Quick reality check on those tools: • Sora: OpenAI shut it down April 26, 2026. Too expensive to run, so they pivoted to ChatGPT, coding, and robotics instead. • DeepSeek: Actually thriving — just dropped V4-Pro (huge MoE model), cheapest high-performer on OpenRouter, and devs are switching to it for massive cost savings. • GitHub Copilot, Cursor, Llama, Perplexity: Still very much alive and baked into daily workflows. They’re no longer “new & shiny” — the market just consolidated around big players and the noise moved on.Hype fades fast, but the useful stuff quietly sticks around.

• 
  ਗੁਰਪ੍ਰੀਤ (@gurpreetscheema) reported 31 minutes ago

  There have been few companies using AI tools whose expenses have gone up than coming down and humans are cheaper. As happened with Claude users. Microsoft is ending most of its internal, standalone Claude Code licenses by June 30, shifting its internal engineering teams to use its own GitHub Copilot CLI instead. This decision was driven by skyrocketing token-based AI costs and a strategic push to consolidate tools within its own ecosystem. More will follow. NASDAQ was high on AI infact on steroids . Steroids will come off .

• 
  Wes Winder (@weswinder) reported 32 minutes ago

  @Shpigford just use google/github oauth and this problem disappears