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:

• 
  AI Genesis (@AIGenesis_) reported 5 minutes ago

  - Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

• 
  Abubakar (@Abubakar_2005) reported 9 minutes ago

  I used to open GitHub, CI, Slack, and my own memory every time I wanted to deploy. Four tabs. Mental checklist. Still shipped broken stuff sometimes. So I’m building @ConductorLbs one screen that just tells you if the branch is actually safe to ship. Still early. Still delulu. But the pain is real.

• 
  Rituraj (@RituWithAI) reported 9 minutes ago

  🚨 Someone built a tool that checks if your email is registered on 120+ sites — without the sites ever knowing someone checked. No notifications sent. No login attempts logged. No alerts triggered. Silent. Invisible. Complete. It's called Holehe. 16,800 GitHub stars. And the technique behind it is what makes it different from every other email OSINT tool. Here's how most email checkers work — and why they fail. Standard approach: try to log in with the email and a fake password. If the error says "wrong password" — the account exists. If it says "account not found" — it doesn't. Problem: every login attempt gets logged. Every failed attempt triggers security alerts on accounts with 2FA. Some platforms lock accounts after repeated failed attempts. The target knows someone was checking. Holehe never attempts a login. Instead it uses the "forgot password" flow — the password reset mechanism that every platform exposes publicly. When you enter an email on a forgot password page, the platform has to check whether that email exists in its database. It tells you: "we sent a reset link" or "no account found." Holehe reads that response. Gets the answer. Never touches the login flow. Never triggers a security alert. Never logs an access attempt against the account. The platform confirms whether the email exists. The account owner never finds out anyone asked. Here's what 120+ platforms looks like in practice. Social media: Twitter, Instagram, Facebook, TikTok, Pinterest, Tumblr, Reddit. Professional: LinkedIn, GitHub, Freelancer, Fiverr. Dating: Tinder, Bumble, OkCupid, Badoo, Happn. Entertainment: Spotify, Netflix, Twitch, Steam, Epic Games, Deezer. Shopping: Amazon, eBay, Etsy, Zalando, AliExpress. Services: Airbnb, Uber, PayPal, Dropbox, Adobe. And 90+ more. Every registration checked silently. Here's the use case that makes people share this. Run your own email address. See every platform that comes back positive. Then run an email address you gave to a company that claimed they'd never share it. See if it's registered on data broker sites and marketing platforms you never signed up for. See where your email has been sold or leaked to. Here's what investigators actually use it for. Journalists verifying whether a source's claimed identity matches their digital footprint. Security researchers auditing their own exposure before a public disclosure. HR teams verifying whether candidate profiles match claimed backgrounds. And the obvious: anyone who needs to know whether a specific email address belongs to a real active person — without alerting that person. Here's the wildest part. It runs async — all 120+ platforms checked simultaneously. Results in seconds. And it exports clean JSON or CSV for integration into larger OSINT pipelines. Pair it with Blackbird (which takes the confirmed email and finds linked profiles), Sherlock (which takes usernames found in those profiles and searches 400+ platforms), and Maigret (which builds the full dossier) — and you have a complete four-tool OSINT pipeline from a single email address. One command to instal. Run it on your own email first. 16.8K GitHub stars. 1.7K forks. MIT License. 100% Open Source. GitHub link in the comments 👇

• 
  Curious 1 (@CuriousOne_01) reported 9 minutes ago

  @GlitterPixely Instead of using CapCut to stitch everything together, I'll only use it to edit the parts with errors. Everyone can just keep scrolling and watch it bit by bit. LOLLLLL Hopefully, it won't get flagged as engagement bait. By the way, you also know that they just uploaded the source code for their algorithm to GitHub, right?

• 
  dunik (@dunik_7) reported 14 minutes ago

  THE ENTIRE STACK COSTS $0 IN LICENCES: 155.000 GITHUB STARS ACROSS FOUR REPOSITORIES, EVERY ONE OF THEM MIT / OpenHands - terminal, browser, files. it writes the code, runs it, reads its own output fixes what broke across as many files as the task touches / microsoft/graphrag - turns your repo into a graph, so the agents walks straight down AuthService -> TokenManager -> LoginController instead of grepping ten thousand files / openai/openai-agents-python - runs specialists in parallel, one implementing while another reviews and a third writes the tests and it takes any / MoonshotAI/kimi-code - terminal agent whose subagents keep exploration out of the main context / skills are just folders. a SKILL.md plus a scripts dir turns one model into a security reviewer, then a database specialist, than a docs writer the whole thing is sitting there fully assembled, waiting for someone to plug the pieces into each other

• 
  Yash (@yashx_404) reported 18 minutes ago

  razorpay recently moved 80% of CI from on-demand to spot instances. thats a 60% cost cut and the whole thing hinges on grepping runner logs for one string: "Connected to GitHub". github changed that log line in an update. cleanup flagged every pod as stale and deleted every active runner in the cluster. CI dead in an hour. and their fix was really interesting, they didnt rewrite the detector as the full event correlation would take a month, they just added a check... if a cleanup run wants to delete more than 20% of pods, abort and alert. automation with a blast radius limit beats automation thats smart

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 18 minutes ago

  𝗙𝗿𝗲𝗲 𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 + 𝗢𝗺𝗻𝗶𝗿𝗼𝗼𝘁 𝗹𝗲𝘁𝘀 𝘆𝗼𝘂 𝗯𝘂𝗶𝗹𝗱 𝘄𝗶𝘁𝗵 𝗡𝗢 𝘁𝗼𝗸𝗲𝗻 𝗹𝗶𝗺𝗶𝘁𝘀. You know that "approaching your limit" message mid-project? This kills it. 🤯 Here's the setup: → Omniroot = a free AI switchboard. 230+ providers. 90 are FREE. → Free Claude Code = same commands, same feel, different brain → If one provider is busy, it auto-switches to the next. You never see an error. → Token compression cuts usage by up to 95% → It reads your memory files so output sounds like YOU → Setup: paste the GitHub link into Claude and ask it to install everything It built a full agency website while the owner kept talking. Honest truth: not frontier-level. But for landing pages and tools? More than enough. Save your paid plan for hard problems. Build everything else free. Want the SOP? DM me. 💬

• 
  .Dev (@AnExiledDev) reported 19 minutes ago

  @lydiahallie Some integration with GitHub issues so I can `#dashboard` to pull up a selector for tickets with dashboard in the title would be amazing, selecting replaces with #123 ticket number. Given enough time I'm sure I could come up with about 30 more suggestions though. :D

• 
  AI for all (@__aiforall__) reported 23 minutes ago

  OpenCut just crossed 83k GitHub stars — a free, open-source CapCut alternative that runs entirely in your browser, no upload, no account. It's mid-rewrite: Rust core, plugin-first architecture, and an MCP server so AI agents can drive the editor directly 🎬

• 
  Arian van Putten (@ProgrammerDude) reported 28 minutes ago

  What all CI providers (including GitHub) get wrong is what you should process workflows in LIFO instead of FIFO to recover from outage. That way older jobs get irrelevant and can get cancelled

• 
  Luke Parker (@LukeParkerDev) reported 30 minutes ago

  @GengMaxwel19074 @thdxr can you tell me the specific bugs/github issue links pls?

• 
  Maaz Chowdhry (@MaazChowdhry) reported 31 minutes ago

  @sameenkarim @madebygps @github I couldn’t merge 10 stacked prs. All had approvals. I clicked the merge stack but it kept loading indicator for 10 mins. (gh-stack/discussion #212, issue #323). branch protection has "require approval of the most recent reviewable push" (or dismiss-stale-approvals-on-push)

• 
  Varnan (@varnan_labs) reported 32 minutes ago

  And this is where GitHub becomes interesting for marketers. Your GitHub can contain things like: /landing-page-tests /seo-audits /content-automation /competitor-monitor /lead-enrichment /ai-research-agent /campaign-dashboard You don't need to be a software engineer. You need to be able to turn marketing problems into small systems with tools like Claude Code, Codex and Cursor

• 
  AML (@alysha_lobo) reported 32 minutes ago

  𝐔𝐏𝐃𝐀𝐓𝐄 𝟑: We manually reviewed 𝐄𝐕𝐄𝐑𝐘 single profile (kudos to the team for going the extra mile with me on this!) Before we drop 𝐭𝐡𝐞 𝐧𝐞𝐱𝐭 𝐌𝐓𝐒 𝐫𝐨𝐥𝐞 (𝐥𝐨𝐚𝐝𝐢𝐧𝐠 𝐢𝐧 𝟑…𝟐…𝟏), here is some 𝐟𝐢𝐫𝐬𝐭 𝐜𝐮𝐭 𝐜𝐚𝐧𝐝𝐢𝐝 𝐟𝐞𝐞𝐝𝐛𝐚𝐜𝐤 if you actually want to stand out: 🛑 Stop using AI to mass-apply — the team and I have been neck deep wading through so much slop!! This wastes everyone's time. 🔗 Double-check your links — broken GitHub, Tech blog, or GDrive links mean instant rejection. 💡 Show, don't tell, your frontier potential — we want to see "cracked," out-of-the-box ideas you have actually cooked and served. 𝐘𝐨𝐮 𝐰𝐢𝐥𝐥 𝐡𝐞𝐚𝐫 𝐟𝐫𝐨𝐦 𝐮𝐬 𝐧𝐞𝐱𝐭 𝐰𝐞𝐞𝐤 𝐨𝐧 𝐧𝐞𝐱𝐭 𝐬𝐭𝐞𝐩𝐬. 𝐓𝐡𝐚𝐧𝐤 𝐲𝐨𝐮 𝐟𝐨𝐫 𝐲𝐨𝐮𝐫 𝐩𝐚𝐭𝐢𝐞𝐧𝐜𝐞! 🇮🇳 𝐂𝐦𝐨𝐧 𝐈𝐧𝐝𝐢𝐚 — let’s raise the bar and show what we can truly build at the frontier of tech. 🚀

• 
  Steve Ruiz (@steveruizok) reported 32 minutes ago

  On a new project, I've replaced GitHub actions with a release machine (a spare MacBook) that runs a pre-flight script on a tick and releases staging when green. If red, the agent creates issues and another agent tries to fix trivial problems before the next tick. It's working!