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:

• 
  AIDegen (@nrsvv11) reported 10 minutes ago

  A Chinese mathematician posted a 3 minute video on Bilibili explaining how he lost his $10,000 a month gig to AI. The model he had been training started writing harder math problems than he could invent. He admitted his own mistake in business positioning. He had spent four years hand writing PhD level math problems for Scale AI's reinforcement learning pipeline. $50 to $100 per problem. 200 problems a month. Then synthetic data killed his entire contract category. He was no longer able to invent a problem the machine could not solve. At 2:13 he says the word agent. He says it once. He never says it again in the video. The way he says it is the only thing on screen that did not come off the teleprompter. He has been recording videos off a teleprompter for three months. The teleprompter runs on the same agent that killed his Scale AI work. Every script is generated by Claude. Every word he reads to camera is the agent's. The new job is reading. Someone pulled the script repository from a Cursor instance the dev had left public. The folder was labeled bilibili-laments. Inside were 47 video scripts. All in his voice. All written by Claude. Six months ago a 14 year old in Shenzhen pushed an AI agent to GitHub. Judges said no real world application. 3,100 forks later. The mathematician had been one of them. He had wired the agent into his content pipeline the week Scale AI cut him off. He had been a PhD candidate at one of the top five Chinese math schools. He taught there for two years before going full time on Scale AI contracts. He still has the credentials. He still has the office. He just no longer writes anything. He wanted to show people how AI took his career. He accidentally showed them how AI also took his post mortem.

• 
  Ronak J Vanpariya (@VanpariyaRonakJ) reported 13 minutes ago

  @innerwebs I have small plugin on .org I use vite press for that plugin's document. Running a server for the document that people don't comes to read often, will be a resource wasting. I just used GitHub pages. So it's just document but if it is bigger i would choose WordPress.

• 
  Matthew Turley (@matthewrturley) reported 15 minutes ago

  "How did you find me?" "My Cursor agent told me you could help." Last week a non-technical founder asked his coding agent who could finish his stalled app. It sent him to me. Your customer asks AI, and it either knows you or it doesn't. Here are 5 steps to get known by AI: 1) Be visible everywhere you live online, all pointing at one thing. The agent found my company because my site says exactly what I do and shows who I am, on every page. Plain and specific, not a vague "we do digital." The model needs a clear thing to point at. 2) Be specific about the problem you solve. Not "AI consultant." "The guy who finishes broken vibe-coded projects." The model can't recommend a blur. It needs a clean line from a problem to a person. 3) Answer the same real questions in public, over and over. Reddit, forums, X. That's what these models read and pull from. Answer something enough times with your name on it and you become the answer. 4) Keep your identity the same everywhere. Same name, same one-liner, same problem, on your site, GitHub, LinkedIn. The model builds one picture of you. 5) Write so a machine can quote you. Put the answer in the first line. Let each section stand on its own. Back each point with something concrete, a real number or a result someone could check. Not a soft claim. The specific bits are what get pulled into the answer. None of this is a hack. It's just being findable for one specific thing. Do that and the agent does the selling for you... while you sleep.

• 
  Alpha Batcher (@alphabatcher) reported 16 minutes ago

  Your coding agent is wasting tokens alone Give it a loop that catches real work Loop engineering is the move from prompting a coding agent one turn at a time to building the system that prompts it for you The loop needs 6 pieces: - automation: finds work on a schedule - worktrees: gives each agent its own checkout - skills: stores project rules between runs - connectors: reads GitHub, Linear, Slack, CI - sub-agents: separates builder from reviewer - memory: keeps yesterday's work outside the chat One morning run could look like this: > read failed CI + open issues > write findings to LOOP.md > open 1 worktree per real fix > send builder agent > send reviewer agent > run tests > open PR > leave anything uncertain in triage The danger is simple: a bad loop can burn tokens while making bad choices confidently So give it hard stop conditions: - exact test file passes - lint clean - ticket linked - reviewer lists zero blockers - human reads the diff before merge Build the loop Stay the engineer

• 
  Mehmet Doğan (@md_daywhite) reported 17 minutes ago

  @heynavtoor If you have a server, pc or something with high speed internet you don’t need this stupid github thing. You can download steam offical app called “STEAM LINK” and you can stream other platforms. Steam has that feature like centuries.

• 
  Wasim (@WasimShips) reported 17 minutes ago

  Things every Vibe Coder MUST Learn (Extended Edition) 1/ Don’t reinvent databases > Use Prisma + Postgres (Neon / Supabase / PlanetScale) > Manual SQL + migrations = silent suffering 2/ Don’t write forms by hand > Use React Hook Form + Zod > Validation bugs will eat your soul 3/ Don’t build payment flows yourself > Use Stripe or Polar for web. Superwall or revenuecat for mobile > Never touch PCI compliance willingly 4/ Don’t build search from scratch > Use Algolia / Meilisearch / Typesense > Text search is way harder than it looks 5/ Don’t overbuild backend infra early > Use Serverless / BaaS first > Scale later, survive now 6/ Don’t ignore error tracking > Use Sentry / LogRocket > Console.log is not observability 7/ Don’t skip analytics > Use PostHog / Plausible > You’re flying blind otherwise 8/ Don’t design UI without components > Use shadcn/ui / Radix / Mantine > Consistency > creativity at MVP stage 9/ Don’t hardcode configs > Use env + dotenv + secrets manager > Leaks = instant regret 10/ Don’t DIY file uploads > Use UploadThing / Cloudinary / S3 > Multipart hell is real 11/ Don’t “just push to main” > Use GitHub Actions + Preview Deploys. Future-you will thank you 12/ Don’t skip performance tools > Use Lighthouse + Vercel Analytics. Slow apps don’t convert 13/ Don’t assume users understand anything > Add onboarding + empty states UX > Features 14/ Don’t wait to modularize > Use clean folders early. Refactors cost 10x later 15/ Don’t trust “I’ll remember this” > Document in README or markdowns. Your memory will betray you Bookmark to ship Better !

• 
  Matthew, MBA (@bit_finance_) reported 18 minutes ago

  This weekend I built a Series 7 study tool. I wrote 0 lines of code. The tool barely matters. Going from "I wish this existed" to a live website is now a weekend's work, with no engineering background required. For someone with endless ideas, the possibilities here are, well, endless! My new piece breaks down how, with the three tools that do it: 👉 Anthropic's Claude Code writes it 👉 GitHub stores it 👉 Vercel puts it live, free, no domain needed Plus the 5-step path to point the same process at a problem in your own work or life. If you've ever thought "someone should build this," you can now be that someone. Link's in the comments.👇

• 
  Pranay Prakash (@pranaygp) reported 22 minutes ago

  @SharingPsyche @cramforce @rauchg i would also be very interested in supporting is improving the postgres deployment story with azure here - so if you have specific issues you’re running into please do open github issues and let me know how we can make postgres world better for production deployments. there are a lot of people in the community running or attempting to the run the postgres world in production and we’re interested in supporting that story

• 
  ThePrimeX (@ThePrimeX12) reported 23 minutes ago

  Age verification sounds simple until you look at the privacy, OS, and app-store problems. Even with zero-knowledge proofs, someone still has to verify you first. That could be Apple, Google, Microsoft, a government ID app, a bank, a carrier, or a third-party vendor. The app may only get “18+ confirmed,” but the verifier may still collect ID scans, selfies, birthdays, device info, IP addresses, failed attempts, fraud scores, or parental consent records. Main issues: • Who stores the original data? • Can users delete it easily? • Do third-party vendors keep copies? • Are backups deleted too? • Can apps track users across services? • Are tokens app-specific or reusable? • What metadata is logged? • What happens after a breach? • What if an adult is wrongly blocked? • What about people without ID? • What about browsers and shared devices? OS/app-store problems make this harder: • Legacy apps may not support age APIs • Foreign apps may not follow the same rules • Sideloaded apps can bypass app-store checks • Windows has EXEs, Steam, Epic, GitHub, browsers, and direct downloads • Android has APKs and alternate stores • iOS has regional app-store rule differences • Web apps may avoid native OS age signals • Shared family devices can confuse adult/minor status • Offline apps may never request an age signal • Developers may not update old apps • Laws may differ by state or country Windows would be especially hard because many apps do not come from the Microsoft Store. A realistic Windows fallback could be a compliance broker: • Microsoft account verifies 18+ • Windows stores an adult eligibility credential • Apps that support the API request the age signal normally • Unknown or legacy apps with no age signal go through a fallback path • The broker confirms only “18+ verified” or “minor/unknown” • Family Safety blocks or limits minors • Verified adult accounts get access without extra app-by-app checks • Sideloaded/foreign apps can be controlled by OS permissions, warnings, or parental blocks Likely fallback paths: • For adult accounts: allow access by default once 18+ is verified • For minors: use Family Safety, parental consent, and app-store limits • For uncertain age: restrict sensitive features until verified • For legacy apps: use OS/app-store controls instead of requiring the app to understand the law • For Windows unknown apps: use an 18+ fallback API/compliance broker • For sideloading: use OS-level warnings, permissions, or parental blocks • For foreign apps: require platform-level compliance before distribution • For browsers: use a privacy-preserving OS/browser age signal • For mistakes: provide an adult override and appeal process Real solutions should include: • Verify once, not with every app • Share only an “18+” or age-range signal • Use zero-knowledge proofs • Use app-specific tokens so apps cannot track users across services • Store the credential locally on the device/account • Delete raw ID data quickly • Give users a clear delete button for every third-party vendor • Show which company verified the user • Ban ad targeting with age-verification data • Require independent audits • Require transparency reports • Use a broker/middleware path for legacy apps • Let verified adult accounts use apps without extra restrictions The goal should be child safety without turning the internet into an ID checkpoint. Age verification should prove eligibility, not expose identity.

• 
  Vladimir Cageyv Samoylov (@cageyvdev) reported 26 minutes ago

  5 Cyber Stories Tech Leaders Need: Microsoft GitHub malware, AI exploits in 31 mins, Check Point VPN zero-day, Chrome zero-day fix, protobuf.js RCE. Automation is double-edged. Move fast or pay later.

• 
  gitbankbot (@gitbankbot) reported 32 minutes ago

  Gitbank runs entirely through GitHub. Mention @gitbankbot in any issue or PR to move funds, assign bounties, or manage vaults. No app required. 222 vaults operating this way now.

• 
  Monte Thakkar (@montethakkar) reported 33 minutes ago

  In the Claude Fable 5 launch video by @AnthropicAI, one line stuck with me: "Point it at something that matters. What's the problem we'll look back on and wonder why it took so long to solve? We know what Claude Fable 5 can do. The interesting part is what you'll do with it." Why this matters History has a shelf of problems like that. Scurvy's cure was demonstrated 160 years before navies adopted it. Semmelweis proved handwashing saved mothers and was ignored for decades. Ulcers were treated as stress long after we found the bacterium behind them. None of these were capability problems. They were stuck on synthesis, bad incentives, and grind nobody was staffed to do. That work can now go to an agent that runs all day, never gets bored, and doesn't need a grant. What I set up Two scheduled Claude Code routines and one GitHub repo. No framework. No orchestration code. A scout runs every morning, hunts for stuck problems, and writes an intake brief. A worker wakes every 4 hours and runs one step of the loop: a planner turns the brief into a milestone spec, a builder executes one milestone, an evaluator judges it pass or fail with fresh eyes. Then it commits, pushes, and dies.

• 
  Matan Borenkraout 🥬 (@matanbobi) reported 33 minutes ago

  @igalklebanov @github @liran_tal Not sure I 100% understand what’s happening here.. someone is trying to make contributions so they’re creating bounties so people go search for tiny issues and post them there and not in the original repo?

• 
  Abi (@larysonlawliet) reported 36 minutes ago

  I'm currently at IIM Ahmedabad selected from 32,000 applicants. 8 months ago I was a CS student in Tier 3 city with nothing but a laptop and GitHub. The only difference? Someone gave me a real problem to solve.

• 
  hasanfr (@hasanfr_0rg) reported 37 minutes ago

  Uber burned their entire 2026 AI coding budget in 4 months. Had to cap employees at $1,500/mo by April. Not even on Copilot they used Claude Code and Cursor. This isn’t a GitHub problem. Agentic workflows just cost more than flat seats.