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:

• 
  DrShillBee (@DrShillBee) reported 5 minutes ago

  Inference is getting cheap. base:0x23a2847d772803f9efc64b4277b782b06296fe51 is betting coordination isn't. Just digged into @usedotai ( base:0x23a2847d772803f9efc64b4277b782b06296fe51 ) and found out inference is about 10–65% cheaper than Venice across 11 matched model routes. Whether you're using Claude, Kimi, Qwen or other models, you don't have to sacrifice privacy for cheaper inference. Dot's Smart Privacy can replace identifying information before the request reaches the provider. Dot's smart privacy turns this: "my name is shillbee and my wallet is 0x00676767676767" to "my name is [person_1] and my wallet is [wallet_1]" The provider gets the anonymized request, while Dot can map the placeholders back afterwards. Currently this is application-layer privacy, while Venice has gone with TEE/E2EE. Dot has TEE on the roadmap, so that's something i'll be watching closely. Now the Dot stack: Dot Loom → open-source orchestration runtime that decides how a task should be handled Learned conductor → a smaller model that decides the effort level and assigns roles DotChat → one interface across multiple frontier models Council → several models answer independently so you can compare Supercharged → draft → verify → finalize when correctness matters DotCode → generates code, runs it, reads errors and fixes the workspace DBrowser → disposable browser sessions for agents Smart Privacy → strips identifying information before requests reach providers MCP → connects GitHub, Base and custom tools Dot API → brings the same infrastructure to developers DotImage / DotVideo → media generation in the same environment base:0x23a2847d772803f9efc64b4277b782b06296fe51 token is where the thesis gets interesting for me: -pay with base:0x23a2847d772803f9efc64b4277b782b06296fe51 → roughly 20% cheaper subscriptions than paying with USDC. -fund credits with base:0x23a2847d772803f9efc64b4277b782b06296fe51 → 10% more credits. -revenue from subscriptions and product usage is used to buy and burn base:0x23a2847d772803f9efc64b4277b782b06296fe51. so the flywheel is basically: → more users → more AI usage → more revenue → more base:0x23a2847d772803f9efc64b4277b782b06296fe51 bought → more base:0x23a2847d772803f9efc64b4277b782b06296fe51 burned Dot currently has around 200 paid subscriptions generating close to $10k in monthly subscription revenue, while Venice is already operating at a completely different scale with 3-4 million users . For some this might be risky but i would consider this as an opportunity. If users start moving toward Dot because they can get cheaper frontier inference without giving up privacy along with other features mentioned above, the upside from here looks pretty asymmetric to me. Venice is around $1.4B FDV. Dot is around $3.5M FDV. That's an absolutely massive gap. I won't say Dot becomes Venice. I'm saying the market doesn't need Dot to become Venice for base:0x23a2847d772803f9efc64b4277b782b06296fe51 to rerate significantly. I am watching @stagedhappen keep shipping while the chart starts looking increasingly interesting...

• 
  Adam Ritter (@ritteradam) reported 5 minutes ago

  @dhh @BrodieOnLinux Can you get some help developing Omarchy GitHub repo itself (at least for bug fixes)? While the guy doing the OmarchyPlugins repo is super fast (reviewing hundreds of issues/day, he should be getting payed as well), the bug fixes in Omarchy don't get through (I see my bug fix pull request being a duplicate of multiple)

• 
  @0xDidi (@0xDidi) reported 6 minutes ago

  No reason why Microsoft shouldn't have the best coding model with GitHub hosting a large % of the world's code. Skill issue.

• 
  Christian Findlay (@CFDevelop) reported 9 minutes ago

  @Southclaws That is a very good idea. Document that up as a GitHub issue. We probably won't get to that any time soon because we're swimming in stuff to do, but it's something that would be really good in the long term

• 
  Vet (@Vet_X0) reported 10 minutes ago

  @Kirjakulov @daniel_wwf Let's not apply sarcasm on one of the few persons who in recent times put out a proper solution for this on github. We can all drive a change we want to see it's an open source project, especially by (FH) node operators if this is a cost burden. Definitely in favor or a solution personally, looks like this discussion goes back to 2019 with Nik B. The only thing i'd add here is that existing services would become tiny more expensive. The memo field is heavily used by Flare and Axelar for interoperability, and potentially other integrations in the future. At the same time, it's also good to know none of this would solve the issue of FH nodes needing to store this stuff and they will not get paid to do that. That's a general blockchain problem. Solana FH is hundreds of TBs for example.

• 
  Joel Wohlhauser (@joelwohlhauser) reported 16 minutes ago

  For the last few weeks I've completely switched from VS Code to Blackbird, my personal fork of T3 Code. I was a die-hard VS Code user for years. I even built my own extension to push it further, but eventually hit too many limits. T3 Code had most of what I wanted, so I forked it and added the missing pieces: - a right sidebar for files, local changes, and PR changes - tabs in the main chat area, with tabs for the Linear issue and GitHub PR opening automatically - better flows for existing and new worktrees, with automatic .env linking and cleanup - smaller things I missed, like fast keyboard switching between chats Why call it Blackbird? the SR-71 is the most impressive airplane ever built. easy.

• 
  Priy (@alwayspriyesh) reported 22 minutes ago

  Building a startup in 2026 is cheapest - Claude = coding. ($0–$20/mo) - Supabase = backend + database. ($0/mo) - Vercel = deployment. ($0/mo) - GitHub = version control. ($0/mo) - Cloudflare = DNS + security. ($0/mo) - Clerk = authentication. ($0/mo) - Resend = emails. ($0/mo) - PostHog = analytics. ($0/mo) - Sentry = error tracking. ($0/mo) - Upstash = Redis. ($0/mo) - Pinecone = vector DB. ($0/mo) - Hugging Face = AI models. ($0/mo) - Groq = AI inference. ($0/mo) - Figma = UI/UX design. ($0/mo) - Canva = design + marketing. ($0/mo) - Notion = docs + planning. ($0/mo) - Linear = project management. ($0/mo) - GitHub Actions = CI/CD. ($0/mo) - Google Analytics = web analytics. ($0/mo) - Cloudflare Pages = hosting. ($0/mo) Total infrastructure cost to build your first startup: $0–$20/month. The barrier isn't money anymore. It's execution. What's holding you back?

• 
  Jozz (@joz_zo) reported 23 minutes ago

  For devs running T3 Code/Codex remotely on a VPS or Linux box: what’s your preferred way to give that machine GitHub access to your projects? Deploy key? SSH key tied to your account? GitHub App? gh auth login? Trying to figure out the cleanest setup for remote agent boxes

• 
  MarcN (@MarcNApps) reported 24 minutes ago

  @ErickSky I just don't get it! GitHub is owned by Microsoft, and it hosts the Massgrave repository for activating Windows and Office using "unorthodox" methods—and they're taking this down? Weird, isn't it?

• 
  Joey (@joeyjurjens) reported 26 minutes ago

  @fuolpit @Cloudflare Maybe make a Github issue? :)

• 
  CodeDR.AI (@codedrai) reported 33 minutes ago

  @xhluca Well done @xhluca - not a bad grade! All seven diagnostics ran in parallel and all seven reports are written to .code-dr/reports/. The repo scores well overall — two A's and five B's — and the striking thing is that nearly every B is caused by the same root cause rather than by messy code. ReportFileGrade Structure 01-structure.md A Security 02-security.md B Test health 03-testing.md B Deploy readiness 04-deployment.md B Code quality 05-quality.md B Performance 06-performance.md B Architecture diagrams 07-architecture-diagram.md A The one theme that explains most of the findings: there is no CI at all. There's no .github/ directory anywhere. Five of the six diagnostic agents independently flagged this, and it's why other problems have gone unnoticed — Ruff is configured but never runs, 325 pytest cases exist but nothing gates a push, 15 high-severity npm advisories have accumulated in the website toolchain, and all 14 released PyPI tags were published by hand with no provenance or attestation. The quality tooling and the tests are already written; nothing is wired to them. The core Python CLI is genuinely well-built. Zero runtime dependencies (stdlib only), an acyclic reader → portable timeline → writer pipeline, fully parameterized SQL, 0600/0700 file modes with O_NOFOLLOW and symlink rejection, atomic no-clobber writes, timeouts on every subprocess and SQLite call, real forward schema migrations, zero TODO markers across 157 commits, and 100% parameter type annotations. No secrets appear in the working tree or in any commit. Three concrete issues worth acting on beyond CI: src/.../catalog.py is a 2,449-line god module, and its _scan_file() function has a cyclomatic complexity of 98 across 244 lines with 10 levels of nesting. Its eight per-format scanners duplicate layout knowledge the format adapters already own, so adding a ninth harness means edits in two places that can silently disagree. About 30.5 MB of the 31.8 MB in website/public is referenced by nothing — demo GIFs and MP4s duplicated byte-for-byte from docs/assets, which is where the README actually serves them. The tracked repo is 66.6 MB and roughly 97% of that is this duplicated media. The suite can't be collected on Windows at all: tests/test_cursor_native.py:8 does a bare import fcntl, which aborts the entire run instead of skipping one module. On this host 194 tests passed and 121 failed, all for platform reasons (temp-file locks, POSIX mode assertions, path separators) rather than logic defects. A one-line pytest.importorskip fixes the abort. Two caveats on the numbers. Coverage came in at 71.5% statements, but the project ships no coverage tooling, so that was measured with a scratch sys.monitoring probe and is a hard lower bound — the 121 platform failures never reached their assertions, so real coverage on Linux is higher. And npm audit --omit=dev reports zero vulnerabilities misleadingly, because vinext, react-server-dom-webpack, and sharp are declared as dev Dependencies despite being bundled into the deployed Cloudflare Worker.

• 
  Panta (@thepanta82) reported 34 minutes ago

  Using GitHub is such a miserable experience. Slow, fiddly, I can never find anything, keep having to bring up my 2FA thing... My local gitlab instance is way more pleasant to use, even if its UI isn't great either.

• 
  jared.info (@JaredRonis) reported 35 minutes ago

  Hugging Face has been fielding M&A interest for $13B+ This is an important thing to track. We need a good steward for what is currently a very important part of open source/open weight AI. $13B narrows down the options if who can acquire. I honestly wouldn’t be mad about Microsoft since they’re surprisingly been fairly good stewards of GitHub so fair assumption they could do the same thing with Hugging Face but I honestly haven’t given it a ton of thought. Would love to hear peoples opinions and predictions here. H/T @GetAISecret

• 
  SSNFang (@PeeSI0sh) reported 37 minutes ago

  @donk_dwonk @mimesical Pretty sure the github link is still up? I don't know. If not then their Discord server is still up and it can be downloaded there

• 
  moebis (@moebis) reported 37 minutes ago

  @github Moving the workflow into one app only works if context moves with it. Issues, code review, CI results, and agent changes need one auditable thread. The product advantage is not fewer windows. It is fewer places where intent can get lost.