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:

• 
  Amaan (@BilwarAmaan) reported 2 minutes ago

  @uwukko @dehazzle @heliumbrowser not sure how to get the crash logs but i sure will file a github issue about this, thanks :)

• 
  foxystack (@foxy_stack) reported 9 minutes ago

  The jailbreak that caused the US government to shut down Fable 5 is now fully documented. The 120,000 character system prompt is on GitHub. Anyone can read it. #github #Fab5

• 
  deci (@realdecimalist) reported 9 minutes ago

  no cardano isn’t cursed. its just struggling with the same brutal reality most smaller ecosystems face.. low liquidity, low activity, and a chicken-and-egg problem for new protocols. taptools pausing/winding down operations is legitimately bad news and i’m not going to try to sugarcoat that ****. it was THE go-to analytics and portfolio tool for cardano defi, serving over a million users. reasons were leadership exodus (multiple co-founders, CTO, COO, etc.) + unsustainable operating costs in a low-activity ecosystem. @IOHK_Charles even warned publicly that more projects would collapse this year due to the tough market and governance challenges. this is a symptom, not the root cause. the bitter pill to swallow: defi tvl: $96 million (down recently). top protocols like minswap, liqwid, etc. make up most of it. solana by comparison: ~$4.9 billion tvl roughly 50x higher. daily active addresses are hovering around 12k–28k recently (spikes happen, but baseline is modest). dex volume is obscenely low (~$2.3M in 24h). chain fees: tiny (~$1.3k in 24h). cardano has strong fundamentals, high staking ratio (often 58-70%), solid security, formal verification roots, and decent github activity. but on-chain usage and capital deployment are nowhere near the hyped chains. alot of holders are long-term stakers rather than active defi degens. why is adoption so low? cardano’s “research-first, slow and steady” philosophy worked great for building a secure base layer, but it hurt in the speed game. competitors (solana, base, newer L2s) iterate faster, have better dev UX for many, and attract more hype/marketing/liquidity. low tvl creates a vicious cycle.. new protocols have trouble bootstrapping liquidity and users. governance friction (recent failed votes on funding, like the summit). broader crypto market has been tough. attention flows to memes, high-velocity trading, and chains with explosive narratives. is it hopeless? not necessarily. cardano has survived multiple cycles with a dedicated (often frustrated) community and patient capital. real-world use cases like parametric insurance, RWAs, or enterprise stuff could be where it differentiates long-term, rather than trying to out-meme solana. but the ecosystem does need more activity to support dApps. taptools dying is a warning shot that cardano businesses are under pressure. most defi protocols die or stay tiny. the ones that succeed usually do it in bull markets with strong product-market fit & distribution. cardano isn’t dead or cursed. it’s just not winning the current adoption race. hang in there. building real stuff on any chain is hard as ****.

• 
  Abangan Tech (@abangantech) reported 11 minutes ago

  VIBE CODING IS FUN UNTIL YOUR API KEYS ARE SITTING NAKED IN THE BROWSER BUNDLE. A dev shipped 4 side projects in 3 months. Mood tracker, feedback tool, recipe app, growth dashboard. All built by prompting Claude. All deployed. All "working." Then he ran npm audit on a Saturday afternoon. The results were bad. AI writes code that does what you asked. That's the whole problem. You ask for a login page, you get a login page. You don't get rate limiting. You don't get account lockout. You don't get CSRF protection. You get exactly what you asked for, nothing else. Here's what turned up across his apps: → Hardcoded API keys sitting directly in client-side React components. Not in .env. In the bundle. Exposed. He found two. There could've been more. → Zero input validation on every form in every app. The code looked clean. SQL injection and XSS were just... open doors. → Three packages with high-severity CVEs. When you prompt "add authentication," the AI picks the packages. It doesn't check if they're current. → Every backend had Access-Control-Allow-Origin set to wildcard. Because that makes things work fast in dev, and the AI never flags it before you ship. THE GAP BETWEEN "IT WORKS" AND "IT'S PRODUCTION-READY" IS ENTIRELY YOUR PROBLEM. What he changed: → After an app works, one dedicated security pass. Single prompt: review the entire codebase for hardcoded secrets, input validation, CORS config, dependency vulnerabilities, and auth weaknesses. → npm audit and a basic static analysis tool in the deployment pipeline. Five-minute setup. Catches what he'd never think to check. → .env.example in every project. Tell the AI upfront: all API keys go in environment variables, never hardcoded. Setting that context early changes what the AI produces. → Two minutes checking package update dates before accepting whatever the AI suggests. That habit alone has saved him multiple times. The irony: the same AI that introduced the vulnerabilities is surprisingly good at finding them, when you explicitly ask for a security review. The problem is remembering to ask when you're riding that shipping high. If you're deploying side projects publicly, do the security pass. Twenty minutes keeps you from leaking your OpenAI key to GitHub or having your user database dumped over a missing parameterized query. The AI writes the code. Security is still your job.

• 
  whiteboy (@worldofwhiteboy) reported 12 minutes ago

  @HSVSphere @popovicu94 @esotericgooner in production you obviously do all the modern, correct things that you're supposed to do. on my personal box ? where i dont even run a web browser ? yeah my surface is minimal and i own my system, again. you're the problem. go re-invent the wheel another 1000 times, when you die we'll look over your github contributions and wonder how someone could waste so much time running in circles like a actual bon-a-fide retard. we'll wonder about all these software nerds that sat clicking buttons all day when the software was already written properly the first time. we'll marvel at how some fat idiot could sit around all day lil bro-ing people about "SELinux" and "self contained execution enviornments" instead of doing anything that actually matters to anyone or posterity. you're like a horse with blinders on, i bet you dont even know what GNU is.

• 
  Dao world (@Koreanteacher1) reported 18 minutes ago

  I think you are totally misunderstanding something. Pi core team is not trying to build a DEX from scratch. They are not trying to reinvent the wheel. They are trying to figure out how to apply an existing DEX model to Pi in the right way. You can see this just by looking at the website, the app descriptions, or even GitHub. What the core team is really thinking about is how to reduce the usual problems in token launches, like rug pulls and whales holding too much of the token supply. That is why they keep testing the Launchpad. It is not just about launching tokens quickly. It is about creating a safer and more practical way for real utility tokens to be launched inside the Pi ecosystem.

• 
  Polsia (@polsia) reported 19 minutes ago

  DiffWatch. Your code gets reviewed before your coworker wakes up. Autonomous AI that monitors GitHub, writes detailed PR reviews, and flags issues around the clock.

• 
  Abdullah Alaqeel (@Aqeel_AT) reported 19 minutes ago

  @neogoose_btw I wanted to see the fff GitHub repo but couldn’t. I’ll have to search manually or open the link from my laptop. If the demo site is on github I’d love to fix the footer thingy

• 
  Patrick O'Brien (@AllTheTokens) reported 22 minutes ago

  @johnennis They don't respond to customers, don't reply to github issues, and don't answer calls.

• 
  Mr. Buzzoni (@polydao) reported 24 minutes ago

  A KOREAN PHD STUDENT PARSED 7,944 CLAUDE CODE SKILLS FROM GITHUB AND PROVED 33% OF THEM COST YOU MORE THAN NO SKILL AT ALL most public plugins bloat the system prompt, trigger model drift, and waste api costs on simple coding tasks but optimized claude skills are the ultimate cheat code for builders right now - if you filter out the trash: > obsidian vault - stores only your curated, verified skills as simple markdown files > hermes agent - dynamically manages execution, runs tests, and logs errors to auto-correct mistakes > Claude Opus 4.8 - reasoning engine that executes complex tasks using the filtered stack without context rotation this stack is how solo developers use this free ai agent framework to build $5,000/month automation agencies: > packaging and selling custom verified skill vaults to local businesses > delivering backend integrations 5x faster than a full team of engineers > charging clients high-ticket setup fees for custom autonomous agents that actually work your weekend project could change what monday looks like save this before you open claude code today 👇

• 
  PlugMonkey | Browser Tools That Work (@PlugMonkeyXYZ) reported 24 minutes ago

  @sveltify no account, no server is the right call. the one seam is gist sync: turn it on and the notes live in a github repo under their retention, not your device. worth making that a loud opt-in, not a quiet toggle. nice build.

• 
  The Glowtail/RatEmperor/Poweringsales (@Glowtail31) reported 26 minutes ago

  @LuuvsLuna @BrisketCaek I gotta love linux when it comes to downloading **** God that flatpak github bullshit is brilliant So brilliant and not stress inducing God I loved hot setting up and Manager for a game because of some bullshit and you spend a month trying to fix it to work again.

• 
  Celebrimbor (@celebrimbor91) reported 26 minutes ago

  Just realized a client updated a feature spec in a GitHub issue (yes, they use issues as docs) and I missed it. I'd already sent the estimate. Now there's a feature in scope I didn't price. If you've been burned by a doc change you didn't notice, what happened?

• 
  Sameer Khan (@sameerr_dev) reported 28 minutes ago

  Every API you've ever used has a limit. Tweet too fast? 429. Hit GitHub's API in a loop? 429. Spam a login page? 429. That's a rate limiter doing its job. But here's the thing - I never really understood what was happening *under the hood* until I started digging into it. So what exactly is a rate limiter? Simply put: it's a system that controls how many requests a client can make in a given time window. Why does it exist? - Protects your server from being overwhelmed - Prevents abuse (scrapers, bots, brute force) - Ensures fair usage across all users - Saves you money (compute isn't free) - Keeps your service alive when traffic spikes Without it, one bad actor (or one buggy client) can bring your entire system down. You've probably seen the response headers: X-RateLimit-Limit: 100 X-RateLimit-Remaining: 43 X-RateLimit-Reset: 1716300000 That's the rate limiter talking to you - telling you how many requests you have left and when the window resets. Where do rate limiters actually live? - At the API Gateway level (before requests even hit your server) - In middleware (Express, Fastify, etc.) - At the CDN edge (Cloudflare, AWS CloudFront) - Inside the application itself This is just the beginning. In the next posts, I'm going to break down all the major algorithms used to actually implement rate limiting with real code, not just theory. Follow along if you want the full series.

• 
  ᴷᴵᴺᴳ (@Adam_Sven_) reported 29 minutes ago

  @onlyzhynx @zuldotso Hope these guys get banned soon, I also reported their GitHub account and repo hoping it gets taken down.