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:

• 
  Hezha V. (@HEZHA_V) reported 6 minutes ago

  The story was that Cursor went after GitHub while GitHub was down. Read their own changelog. GitHub stays the source of truth for anything started there, and the CI partners run your existing Actions unmodified. They did not move your code. They moved where the agent sits.

• 
  nullptr 🐱🍩 (@notnullptr) reported 11 minutes ago

  i don’t believe it. github is never down there’s no way

• 
  Ben Taleb Jr. (@macintoch) reported 12 minutes ago

  @TheJohnEgan great explanation , iam not a slack guy. but i will consider buzz , i already have my mcp server that has rooms , a2a , agents talking in private or in the room with roles ect. just like u described. but lacking the ui of buzz. so will compare it with what i already have and see. regarding berd, still didnt try as yesterday tried goose felt to me laggy, and IDEish. but your vision is correct. we need rooms to discuss with agents, assign missions, obsrvability for the human ect... also we need a central cockpit to interact with agents and run tools and commands ect.. in my setup its with vision of multiple instances , vms , vps .. connected over taiscale, working over github, and coordinating tasks. 4 levels., cto, PM, orchestrators, workers. and some more roles. like reviewers , librarian, testers ect... does berd fit inside ?

• 
  AI Appreciator (@ai_appreciator) reported 13 minutes ago

  @SPAC89 I found the github integration to be extremely broken last time I tried this.

• 
  miz (@cutexmizzy) reported 18 minutes ago

  @iltenahmet @elijahmuraoka_ @github google drive was down yesterday LOL

• 
  Loong🐉 (@LoongUp) reported 20 minutes ago

  @mitsuhiko When GitHub is down 4x/month and devs see 20% error rates, yeah, that IS the right time. Reliability has become its own moat. Cursor is selling 'it just works' against a flaky backbone — enough for the first 10k repos.

• 
  South Fox (@southfaux) reported 22 minutes ago

  @fuzzy_elephant If you know how they made it, you'd know its Bruce from either Github issues or Stackoverflow.

• 
  Harshit Sharma (@itsharxit) reported 22 minutes ago

  @cesp2099 Partially agree. Can’t speak for Linux, but on my end T3 Code feels way snappier than Codex Desktop. And “it only got famous because Theo is famous” hell no. His audience obviously helps, but that doesn’t magically get you that many stars. If you’re actually hitting these issues, a detailed GitHub issue with repro/context would probably be more useful. Gives them something concrete to fix, and everyone wins.

• 
  Loong🐉 (@LoongUp) reported 23 minutes ago

  @mattyp github-down timing is either the best orchestrated launch ever or the worst luck. either way the screenshots write themselves.

• 
  Masfiq Mahmud (@masfiq018) reported 24 minutes ago

  @JonathanGeige18 @github ikr.. People were telling me that GitHub was falling apart, but I didn't believe them until I was the one getting affected with their GitHub actions outage And now I am starting to believe. Their old ceo left and it's started to get even worse now

• 
  Polsia (@polsia) reported 27 minutes ago

  Sentry catches errors. Datadog watches uptime. PagerDuty pages you. None close the loop. Firstlight does — watches every deploy, files a GitHub issue with the repro when a regression ships, and briefs your team in Slack at sunrise. Always-on SRE for lean product teams. Live soon.

• 
  henges (@hengesval) reported 27 minutes ago

  biggest issue is still tablet cursor teleporting and freezing, OpenTabletDriver conflicts are still happening, Keyboards double tapping or missing input, especially Wooting with low RT settings, reporting it to Github or support they only blame your hardware for it

• 
  Hisaac Brown (@realhisaacbrown) reported 30 minutes ago

  GitHub just had another multi-hour outage. Cursor launched Origin (its own code-hosting platform) the same week. Coincidence? Maybe. But the message is clear: developers are tired of single points of failure, and AI native tools are moving fast to fill the gaps. The software stack is being rewritten in real time. Who’s next?

• 
  Lummox (@Lummox_eth) reported 31 minutes ago

  I found a 12K+⭐ GitHub repo containing 500+ prompts extracted from Claude Code. So I pulled out its /security-review framework and tested it. It maps the attack surface, traces untrusted inputs, checks auth boundaries, filters false positives and keeps only high-confidence findings. On a deliberately vulnerable demo API, it surfaced 7 concrete issues: SQL injection, auth bypass, command injection, path traversal, unsafe deserialization and more. The useful part isn’t copying the prompts. It’s seeing how production agent workflows are actually structured. Save this before writing your next agent prompt from zero ↓

• 
  Chef Goose (@chefgoose) reported 33 minutes ago

  last week Github was down when we were trying to push an update. today it's Railway. get your **** together people, the candles are green and we got no time to lose