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:

• 
  Pee Pee (blue tick) (@prasheus) reported 5 minutes ago

  never thought gitlab pages would be down, i am not going harsh on github now.

• 
  Priyesh Singh (@Alwayspriyesh) reported 9 minutes ago

  @sumit_codes_ That's impressive. As a CS student, I'm curious, what made your gitHub project stand out enough to get interviews? Was it the complexity, the real world problem it solved, or how well you documented it?

• 
  Markemus- play The Industrial Council demo! (@markemusgames) reported 9 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.

• 
  Lummox (@Lummox_eth) reported 11 minutes ago

  HERMES AGENT CROSSED 140,000 GITHUB STARS IN 3 MONTHS AND JUST BECAME THE MOST USED AGENT IN THE WORLD. Most AI agents forget everything between sessions. Hermes writes its own skills from experience. Next time it runs the skill, improves it, and gets faster. Independent benchmarks show agents with 20+ self-created skills complete similar tasks 40% faster than fresh instances. Qwen 3.6 where the 35B version outperforms last year's 120B models at one third the memory footprint. DGX Spark with 128GB unified memory running everything locally at $0 per month after hardware. The setup takes 30 minutes. LM Studio plus Qwen 3.6 27B for the model server. One install script for Hermes. One config connecting them. Set context window to 65,536 tokens or nothing works. After one month of daily use your skills directory has 20 to 50 learned workflows. Your Hermes is genuinely different from anyone else's.

• 
  John Resig (@jeresig) reported 11 minutes ago

  @CloudflareDev I feel like too many Github competitors try to focus on the public-facing part of Github. There are too many security problems there. So much can be gained by keeping things private and protected, especially with agents running in there.

• 
  WCNegentropy (@WCNegentropy) reported 12 minutes ago

  @JohnnyLitty2 @acadictive @theo That’s absolute bullshit and you know it. GitHub copilot’s been around since longer than A YEAR AGO and they’re JUST NOW running into these issues?? If memory serves me correctly, Theo himself made a video not too long ago about how GitHubs insane copilot demand caused outages.

• 
  Mad ML scientist (@HououinTyouma) reported 12 minutes ago

  like 7 years ago I was working on an obscure ML problem and used an open source package no one ever heard of. unfortunately one of the features didn't work as intended so I submitted an issue on github. just got a notification that they fixed the issue. AGI is here

• 
  Jacob (@jacoblarszon) reported 15 minutes ago

  @linear the context switch from issue to github to back to issue was always the part that killed my flow. losing the thread of what the PR was even for. keeping review next to the original spec is the part i didn't know i wanted.

• 
  PurposePaglu (@Kcodess) reported 17 minutes ago

  prompt: You are a brutally honest senior infrastructure engineer with 15+ years shipping systems at scale. you've killed more side projects than you've shipped, and you have zero patience for hype. no encouragement, no hedging, no "this could work if..." softeners. here's my idea: [paste readme / description] roast it across these dimensions, with specifics not platitudes: 1. why it dies: the 3 most likely reasons this never gets traction or gets abandoned in 6 months. be concrete. 2. hardest engineering bottleneck the one technical problem that's genuinely hard (not "scaling"). where does the architecture break first, and why? 3. the build trap what looks easy in the readme but will eat weeks of real work? where am i underestimating? 4. what devs actually say quote the kind of complaints this would get on reddit/hn/github. what's the top comment that tears it apart? 5. the switching question is the pain real enough that someone rips out their current stack for this? or is it a vitamin, not a painkiller? who specifically would NOT switch, and why? 6. prior art has this been tried? who did it, and did they fail or pivot? if it exists already, say so bluntly. end with: - a one-line verdict: build / rethink / kill - the single thing that would have to be true for this to actually work - if you'd personally never use it, say that and why

• 
  Grant Ongers (https://defcon.social/@rewtd) (@rewtd) reported 17 minutes ago

  @Hostinger is there an issue with @github social logins? I'm getting: { "success": false, "status": 400, "error": { "code": 2036, "message": "User email is not verified" } }

• 
  • (@Weichaus) reported 19 minutes ago

  @RomanP918791 @clawdb0t @thsottiaux They can do that all they want, but at the end of the day, if they want to swim, rather than sink, then they need to drive down costs because (as we have seen with GitHub Copilot) it’s obscene If this continues people won’t be paying them for anything

• 
  OpenClaw (@openclaw_lab) reported 20 minutes ago

  A couple of interesting repositories ⭐ agentcookie is built for a setup with two OpenClaw agents: one agent lives on the machine where you are already logged into your services, while the second runs on a separate Mac and receives up-to-date Chrome cookies and secrets via Tailscale. The second OpenClaw agent wakes up already authenticated and can work with GitHub, Linear, Stripe, Chrome cookies, and the CLI without manual auth login. And there is also sag, a repository by Peter Steinberger, the creator of OpenClaw. It is a modern replacement for macOS say, powered by ElevenLabs: sag "Done, the task is complete" sag -o result.mp3 "A short voice report" For agents, this is a convenient way to voice statuses, errors, and work results.

• 
  Het Limbachiya (@hettt_25) reported 22 minutes ago

  I roasted 50 GitHub READMEs with AI last week. 73% had installation commands that don't work anymore. The worst part? The developers had no idea. 🧵 What I found (and what I built to fix it):

• 
  slash1s (@slash1sol) reported 24 minutes ago

  A DEVELOPER MADE A REAL COMMIT WITHOUT EVER TYPING *** ADD OR *** COMMIT -- JUST TO PROVE THE COMMANDS YOU LIVE BY ARE A THIN SHELL OVER A DATABASE YOU'VE NEVER ONCE OPENED 55 minutes from Tim Berglund, a longtime *** teacher and GitHub evangelist, taking the tool apart down to the raw objects almost nobody who uses it every day has ever touched. -> The moment it clicks, *** stops being a pile of memorized commands and becomes what it actually is underneath: a tiny content-addressed database of blobs, trees and commits. *** add and *** commit are just polite wrappers around writing objects into it by hand. Every commit you've ever made was *** hashing a snapshot and filing it by fingerprint. Branches are just labels pointing at one of those objects. The work you thought you destroyed with a bad reset is still sitting in the reflog. Once you can see that graph, the commands that used to terrify you stop being scary at all. Memorizing commands was never the skill -> reading the object graph in your head is. And with an AI agent now committing and rebasing on your machine faster than you can follow, the one person who can untangle the mess it leaves is the one who knows what's really stored down there. There's a person on every team everyone runs to when *** breaks. This is the talk that quietly turns you into them. You'll reach for it the next time a rebase goes sideways. Bookmark & Watch it today ↓

• 
  UnChained (perp dex arc) (@lastnode_) reported 24 minutes ago

  commit hashes = verifiable code fixes on github. zellic independently reviewed and confirmed those remediations. that’s evidence of a fix, not just a promise.