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:

• 
  mpgn (@mpgn_x64) reported 6 minutes ago

  Back then, updating to latest version was a security advice, now we hunt people with latest release 😩 NPM should make attestation mandatory for big project Github should fix their horrible legacy PAT token that can destroy an org just because the dev is doing a side project…

• 
  Zeerabets (@Zeerabets) reported 7 minutes ago

  unpopular take but i think linear is dying. watched 3 startups this month move to plain markdown files + github issues because AI agents read them better. your project management tool is now optimized for humans and that's becoming a liability

• 
  Thomas Malloc (@ThomasMalloc) reported 9 minutes ago

  @zeddotdev I would absolutely use this for my main editor, but ACP issues exist when using with WSL2. Github issues says it might be Bash PS1 related. I'll give it a try and see if I can fix. Looking nice. 👍

• 
  Harsh Chourasia (@hrshc7) reported 11 minutes ago

  WE WEREN’T WRONG ABOUT CODEX, THESE SKILLS MAKE IT BETTER THAN CLAUDE someone dropped a list of Codex skills that make it actually useful for real dev workflows. - composio connect: hooks it straight into GitHub, Slack, Notion and the rest of your tools - webapp-testing: runs real browser flows so you catch UI issues before they ship - gh-fix-ci: digs into failing GitHub Actions and tells you what actually broke - notion-spec-to-implementation: turns your rough Notion docs into real plans and tasks - frontend-skill: stops Codex from spitting out the same generic UI every time Claude’s cute for quick prototypes, but these turn Codex into the one that actually ships your work. Don’t install the whole list at once or you’ll hate your life, start with whatever matches how you already work.

• 
  Sergio Donato (@pitumpa) reported 12 minutes ago

  @OpenAIDevs Yes, but please fix the CPU usage spikes in Codex Help (Renderer) when working in a folder without a .*** directory. Please take a look at the issues on GitHub. Right now, Codex is almost unusable on MacBooks. It makes them overheat badly.

• 
  Craig Kerstiens (@craigkerstiens) reported 12 minutes ago

  @juliknl @mscccc One shared schema is generally quite fine, RLS gives you extra guaranteed enforcement. ORMs can be okay about protecting this, but defense in depth in terms of access to the data is not a bad thing. I know Mike we'll say we just had amazing developers at GitHub that knew how this worked and we didn't have problems. If everyone thinks they have a set of the best developers in the world great, but evidence is not everyone is that good and having something like the database protect you is not a bad thing. Things like actually separate databases per customer aren't inherently bad, but you need orchestration to manage across that. There isn't a right or wrong way. Sorry to not be more black and white controversial, RLS can be a good thing, a database per customer has some pros (and cons), but also 1 shared schema and customer data mixed together is totally fine and can work (but also has tradeoffs).

• 
  Serious Meester (@G19901983) reported 13 minutes ago

  @nahcrof Login via Github would be mega nice, any plans on that?

• 
  Ming "Tommy" Tang (@tangming2005) reported 14 minutes ago

  3/ The README lies. You run the install command, dependencies fail. You chase error messages across GitHub issues from 2017.

• 
  Matias Romero (@matiasromerodev) reported 17 minutes ago

  Inspired by @karpathy 's recent insights, what if we stop treating LLMs merely as advanced search engines and start using them as compilers? Instead of searching messy data at query time, we can use background AI agents to "compile" raw GitHub issues and docs into a living, interlinked Semantic Wiki.

• 
  Evan Plaice (@evanplaice) reported 17 minutes ago

  @ZackKorman Add to that. People like to use the Google Authenticator app for two-factor authentication. With a valid Google access_token that could be compromised as well. So, MFA didn't help. tldr; stop using Google/Github to login to 3rd party services.

• 
  BP (@everyonebpup) reported 22 minutes ago

  🚨do you know what's happening with GitHub CLI? it went out in v2.91.0 a few hours ago. every gh command you run now sends a ping to github: command name, flags, OS, version, a device_id, and a field called "agent" that last field is the whole point. claude code, copilot CLI, cursor, and codex are all driving gh usage now, and github had no way to measure it. from their own issue (12522, january): "we do not have client side telemetry, it's not possible to say this with certainty" opt-out is three commands, any one works: export GH_TELEMETRY=false export DO_NOT_TRACK=true gh config set telemetry disabled small weirdness: the config command prints "unknown key" but actually writes telemetry: disabled to ~/.config/gh/config.yml. it works, the warning is a bug

• 
  Florian (@FlorianCaesar) reported 22 minutes ago

  @realamlug @saltyAom Do you even realize how incredibly disrespectful it is to reply to all of this with LLM slop? Same with GitHub issues. And again, half of this reply is slop garbage and incorrect. Incredible. I’m out.

• 
  Kuber (@kuberwastaken) reported 23 minutes ago

  @anant_hq @github okay nvm just saw - it's down

• 
  Li Bin (@OrNot2024) reported 29 minutes ago

  @pyronaur @badlogicgames Same issue only for Codex but not for github

• 
  Dhruv (@Dhruv14588676) reported 35 minutes ago

  @justsisyphus @opencode do you guys don't open GitHub now? there is no activity on issues and PRs