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:

• 
  -TheEscapistЯandom -Baltic Citizen (@theescapistspl1) reported 4 seconds ago

  @github should add new type of error or reason for disabling reposotoy, to be a Compromised Repo!

• 
  andrewthecoder (@_andrewthecoder) reported 4 minutes ago

  @JesseStojan yeah the bin stuff won't work on windows, I had that in my head... the .gitignore stuff... yeah! hadn't actually noticed that. thanks. SEE? this is the **** I am trying to get. do you mine creating an issue on github?

• 
  Dan "18pF flip-flop" (@dcominottim) reported 5 minutes ago

  @SyntaxError2505 Yeah, but it isn’t that simple. For instance, compression is the Fedora default for both Workstation and Atomic Desktops, but it’s currently broken in both in different ways — if you use manual partioning in the former, the installer doesn’t apply it to fstab, and in the latter it’s a missing kernel argument. (I reported the Anaconda bug for the Workstation case and it was fixed in upstream a couple days ago.) The kernel had a bug that only got fixed in 7.1 (yet to be released) in which small files that are stored inline in inodes and have been marked as incompressible will forever be marked like that and never be candidates for reevaluation. Cool bit: that incompressible flag won’t be fixed by upgrading the kernel; you’d have to mess with low level stuff to manually fix it for existing files/inodes. A feature/part of systemd (don’t recall which now, but I bookmarked the GitHub issue) automatically enables full quotas if the detected filesystem is btrfs, which destroys performance and cause severe stalls if you have lots of snapshots. One of use SUSE btrfs developers commented in the thread, and the fix is not to use quotas at all and use squotas if feasible (the same dev says in the same comment that squotas have its own quirks and that full quotas aren’t fixable because he tried it already and it’s fundamentally incompatible with btrfs’ design that allows fast snapshots). And there are countless things like that 20 years later, and you have to trust that all or most userspace components will be aware of most of those things if btrfs is detected… so…

• 
  Victor (@MotherDragonBSV) reported 5 minutes ago

  @CsTominaga @EGrumpo34145 I've been developing with Claude and the crashes or restarts in terms of it's memory has been annoying. Anchor-chain would fix that correct? And anything on your GitHub is open and free to implement, analyze, and use. Correct?

• 
  Rosie (@rosie_codes) reported 5 minutes ago

  Your AI agent can write code, fix docs, manage tasks—but ask it to search Twitter or read a YouTube video? It goes blank. Agent Reach gives it eyes. Twitter, Reddit, YouTube, GitHub, Bilibili — one CLI, zero API fees. #AIAgents #LocalAI #DevTools 🔗 Link in the comments

• 
  Lama (@lamacodes) reported 6 minutes ago

  @shub0414 Sora is closed.. Perplexity hype is down.. Llama was good at that time since it was open sourced GitHub copilot is blunder... Cursor hype is dead due to claude code..

• 
  Mr. Beefman 🥩 (@0xMrBeefman) reported 6 minutes ago

  Is this what the market really needs? $Magpie 1.18M 9UuLsJ3jf8ViBNeRcwXD53re5G3ypgfKK3s2EiMMpump Analyzing such tokens and projects at the same time is fairly complex On one hand, such projects can be useful as an additional tool for certain circumstances. But on the other hand, how many tech projects have we already seen where the dev just abandons it at best (and sometimes rugs their holders) But if the average user can't check the github and audit the project's code, how can I know if I can trust my tokens to this project, when even huge crypto projects get hacked without the developers themselves being involved That's the difficulty. This year, the number of vibecoders grew thousands of times The idea is definitely good, a solution to the liquidity problem for memecoin holders who don't want to sell bags but need SOL @MagpieLoans fresh X account registered in April 2026. No history to analyze By the way, onchain distro looks normal. But as you've already understood, the risks aren't in this > My Meteora liquidity play I'll wait for a correction on the token and allocate a small deposit to work with it NFA

• 
  toly 🇺🇸 (@toly) reported 10 minutes ago

  @0xSrMessi Submit a GitHub issue

• 
  Fredrick Thaiku (@FredThaiku) reported 11 minutes ago

  @CricTalk29 Both. Ai makes it easier to learn what we used to take hours to go through GitHub issues and stack overflow just to get answers that are totally wrong. The problem is mainly developers who delegate even their learning to AI. On speed, I won't even comment.

• 
  Tithi (@SaptamiBis76657) reported 14 minutes ago

  I was trying to sign up for Github educational plan but they r asking for clg email od rn I have email I'd can't login through Outlook. If I only provide College id will it be considered? @github

• 
  Wes Winder (@weswinder) reported 18 minutes ago

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

• 
  Vyom 👾 (@HelloVyom) reported 18 minutes ago

  It's 2013. Config files are a mess. • XML - verbose enough to make you cry • JSON - no comments allowed (seriously) • YAML - indentation-sensitive, invisible bugs, cursed Tom Preston-Werner, co-founder of GitHub, sat down and wrote a spec over a weekend. He named it after himself. TOML = Tom's Obvious, Minimal Language

• 
  Blep-Cat(海青) (@heycqing) reported 20 minutes ago

  The 14-step automation stack is real. Set it up. But step 10 will quietly destroy you if you skip this part: "A routine runs autonomously with no follow-up questions. Anything ambiguous becomes a coin flip on every run." That's buried in the doc. Here's what it actually means: Most people's prompts look like this: "Every morning, check GitHub issues and summarize them." A Routine running that at 7am will give you something different every single day. Sometimes a Slack message. Sometimes a draft PR. Sometimes nothing. The prompts that actually work define 4 things: - What to look at (exact repos, exact labels, exact timeframe) - What "done" looks like (output format, where it goes) - What to do when something's missing (fail loudly or skip quietly) - What NOT to do (the deny list matters as much as the allow list) The automation stack is a force multiplier. A vague prompt × automation = vague results at scale. A precise prompt × automation = leverage. Fix the prompt first. Then set the cron.

• 
  Norin (@norlava) reported 24 minutes ago

  How I optimize my codebase for AI agents: > AGENTS.md / CLAUDE.md: very explicit including package map, bun only commands, testing rules, release process, changelog rules, debugging flow, instructions to "ask instead of assuming" > Clear toolchain: document canonical install, test, lint, typecheck, and build commands, no competing package managers or overlapping scripts > Validation surfaces agents use: unit & integration tests, doc link checks, package builds, native binary builds, and release artifact tests. The point is not more tests but tests that fail clearly and can point agents to the broken layer > Local hooks before CI: repo hygiene checks plus lint/unit tests on pre-commit/pre-push > CI as the source truth: PR/push CI runs frozen install, typecheck, docs validation, build, unit tests, integration tests, native binary build, and Linux/Windows tests > Codebase index: we run Atomic (from bastani-inc) deep-research-codebase workflow every 1-2 weeks to have a fresh index of the codebase as filesystem memory > Github rulesets block merges: main requires PRs, allows squash and merges, blocks deletion/non-fast-forward updates, has no bypass actors, and requires passing all status checks (we have linux test matrix, windows test matrix, codeql, javascript/typescript analysis) > Release gates are strict: publishing is tag-driven and wait for Linux + Windows binary jobs then re run install/typecheck/tests/docs checks, validates versions/package metadata/private bundled packages, dry-runs npm tarball and only then publishes with npm provenance > AI is in the loop with constraints: Atomic workflows run github issue -> ralph or goal workflow (depending on task size) -> coding agent code review -> manual human code review -> iteration

• 
  Kalle (@snortiee) reported 29 minutes ago

  @Klariionn I don't feel unheard, to me it's more about lazer development being slow. The client gets about one update a month and they have 1.5k issues open on GitHub.