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:

• 
  Hunter (@huntsyea) reported 12 minutes ago

  Experimenting with Hermes and @evedev_ in Matrix. I am convinced chat is the right medium for long-lived orchestration and coordination between agents (and humans). There’s no need to over-complicate it. This is not for items where feedback really belongs at the top and bottom of a task (e.g. software factory). There is no need for a software factory to orchestrate and communicate via chat. Maybe just some update notifications. I’m mirroring my setup similar to human patterns. A matrix room is tied to linear team and a GitHub (or origin) repo. I ideate, research, discuss with Hermes and other agents. Eventually that gets to an issue and kicks off off foreman and the factory loop. Once it’s done Hermes reviews and notifies me. I review finished work and leave notes with Hermes. Loop kicks off again if needed.

• 
  Tarun Agarwal (@tarunag10) reported 18 minutes ago

  @clairevo @joshkim @bot I’d use Grok Bot as a Product Signal Agent. It would continuously watch customer feedback across X, support email, and GitHub, cluster repeated pain points, validate whether they’re real problems, and rank them by frequency + potential impact. Then every morning it gives me one thing worth building, with the evidence, a mini PRD, acceptance criteria, and a ready-to-open GitHub issue. Basically: turn scattered customer noise into a shippable product decision every day.

• 
  Ricci Research (@ricci_nov) reported 18 minutes ago

  @github Consolidating surfaces is the right instinct, but the tab I keep switching to isn't chat — it's the repo, the CI logs, and whatever's actually broken in staging. Whoever collapses those three wins the workflow; everything else is just moving the chat box.

• 
  HLevi (@haiderlevi) reported 20 minutes ago

  @kaybee1899 @GenLayer I’ve got a half-built GitHub repo where the README explains everything beautifully and the code basically says “TODO.” Would an unfinished repo still be useful evidence if the original pitch explains the problem well?

• 
  tunct (@tunct101) reported 24 minutes ago

  I’ve claimed my Rialo points and connected all my socials. If you haven’t done it yet, it only takes a few steps: 1. Sign in with Google on the Rialo Playground 2. Open Connect next to your points balance 3. Connect your Discord + GitHub 4. Double-check that you linked the right accounts before claiming Done in a few minutes. How many points did you guys get? 👀 Drop your number below!

• 
  Samer Haddad (@ai_samerhaddad) reported 25 minutes ago

  @JulianRaxworthy @PaulSolt No it just started working, just make sure you do the “@github” in the chat and better list the url of the repo and you should be good to go I sent OpenAI about it in the past and they said they were fixing it, now seems that is done and I have no more issues with private gits

• 
  Austere Grim (@austeregrim) reported 25 minutes ago

  @codegirl007 Host a gitea server that replicates to GitHub the stuff you want.

• 
  Aditya Jhajharia (@AdityaJhajhar12) reported 28 minutes ago

  The hardest part of software engineering isn't writing the code. It's launching it. Stop polishing your code and hit deploy. The market will tell you what to fix. What side project are you hiding on your github right now? 🚀

• 
  Tumusiime Alaphati (@alaphati_t) reported 32 minutes ago

  Your API key does NOT belong in GitHub. 😭 Not in: .env committed to *** frontend JavaScript screenshots public repos error messages Treat secrets like passwords.

• 
  Aditya Warman (@warmanadit_) reported 34 minutes ago

  4/7 📍 Third problem : Their GitHub is practically INVISIBLE. For a project with $397M funding, the code should be PUBLIC. But searches return educational resources and unrelated repos. Solana, Avalanche, Sui — ALL have active public codebases. Plasma? Closed-source development with zero external verification. They claim decentralization while keeping code HIDDEN. That's not transparency — that's a red flag factory.

• 
  Daniele (@Daniele15072903) reported 35 minutes ago

  @JoeBlack2k @macintogdev @theo If 100 people do it, the damage is limited. If you share it with the public on Twitter, create a GitHub repo to abuse it, and everyone reliably triggers something that normally "maybe happens, maybe doesn't", you force the company to fix it.

• 
  Dante Lopez (@dqlopez) reported 35 minutes ago

  My Grok Bot PR reviewer: - I have it install Pi then login my Codex/Cursor subs - Give it own Github account and access to my org repo - Setup routine to watch new PR or changes - Initiate PR review based on my custom prompts and skills load - Post Github review, slack post notif and notify me back on Grok desktop/app Neat. Doesn't consume much usage.

• 
  Naomi June (@njkjh00) reported 36 minutes ago

  Beldex’s Electron Wallet has another security checkpoint worth watching. Aug 28 commit eef1f845: • wallet-directory fallback • explicit permission prompt • 7 files changed • +160 / -7 lines • branch: fix-security-review-findings GitHub shows the branch is still ahead of and behind master. That means something important: the security work is visible. the release is not there yet. Next checkpoints: review testing merge signed build release notes A security fix matters most when it reaches the software users actually install. @BeldexCoin

• 
  Peter Kuhar (@pkuhar) reported 37 minutes ago

  @mickcodez great please pull the latest from github. it might fix some already.

• 
  lasan (@las_nish) reported 37 minutes ago

  Comparisons of Free Trial Abuse Prevention Services If you're running a SaaS with a free trial or focusing on PLG, authentication and abuse prevention are not the same problem. - WorkOS: If you're already using WorkOS, WorkOS Radar is probably the first thing I'd look at. For a WorkOS stack, WorkOS AuthKit + Radar makes the most sense. You don't need to bolt another authentication system onto your app just to get abuse signals. - Auth0, Supabase Auth, Better Auth: These are primarily identity/authentication platforms. Integrating only these can't prevent free trial abuse. - Custom: Like the previous options, you need a custom way to prevent free trial abuse. Most free trial abuse methods involve disposable emails, Google dot variations, Google/Gmail domain variations, and plus addressing. That's why even when you block bots via Cloudflare Turnstile or CAPTCHA, you can still get these abusers. The industry standards: - Block free trial abuse using lists hosted on GitHub: This is a pain in the ***. If you don't want to pay money, you can use a service that offers a generous free tier. - WorkOS Radar: This is mainly used at the enterprise level. They focus more on WorkOS-related integrations rather than integrations with other providers. - ZeroBounce, NeverBounce, MillionVerifier, DeBounce: These are mainly used to clean/validate emails. There are 100s of alternatives, and most are similar with minor differences. They all have disposable email checking APIs. - UserCheck: This is also an email validation API, but they focus on blocking fake email addresses. It's better than a basic email verification API. - Autheona: This is in the same category as WorkOS Radar and UserCheck, but with more features. It also focuses on fake user detection and is growing with a real user base. Now, pricing: - WorkOS Radar: First 1,000 checks free, then $100 per 50 checks. No application-specific logic changes. Easy to integrate and manage. - ZeroBounce: 100 free validations in the free tier, then pay-as-you-go, starting at 2,000 for $39, and so on. - NeverBounce: No free trial or use case, $8 per 1,000 checks. - UserCheck: 1,000 API requests per month in the free plan. The rule-based engine is not included in the free plan, and you can get up to 1 request per second. - Autheona: 3,000 checks per month, with the rule-based policy engine included. Standard API request rate limitations apply, similar to paid plans. Now, use cases: - WorkOS Radar: Block disposable emails, plus addressing, and Google dot variations. - ZeroBounce, NeverBounce, etc.: Block disposable emails. - UserCheck: Block disposable emails, plus addressing, and Google dot variations; detect public emails; email suggestions; syntax validation; role detection. - Autheona: Everything included in UserCheck, plus business/free/government email identification, deliverability checks, fraud patterns, punycode and mixed-script checks, VPN detection, and bot detection (not necessary if you already use CAPTCHA, Cloudflare, etc.). Final decision from me: - Use WorkOS Radar if you're already in the WorkOS ecosystem. It's harder to integrate with other auth providers. - Use ZeroBounce-like APIs if you need basic disposable email checks. They're not as good if you need a better free tier. - Use UserCheck if you only need email-related validation and want to stay within the free plan. - Use Autheona if you need the most generous free tier available with a custom policy engine. All services take a maximum of a few hours to integrate and test. Both UserCheck and Autheona have a similar approach: integrate once and never touch the code again.