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:

• 
  REVENGE ARC (I'M HIM. BIO/ACC) (@RetardedNi85688) reported 46 seconds ago

  This has to be some insane stats for @vudovn354 and $AGKIT imo. Most indie developer tools sit at 100-500 stars. 7.8K puts this in the top 5% of active projects. 11 contributors on the github as well. Contributing and not just consuming. 124 total downloads so far on the released packages. 38 open issues means people are using it and filing bugs. Last published 9 days ago — shipping consistently. TypeScript 56.2%, Python 27.3% — this is built for enterprise and data teams, not just web devs. Which was what goggle's @antigravity pointed out too. They have: Working product ✓ Real adoption ✓ Active maintenance ✓ MIT license (zero friction) ✓ Growing contributor base ✓ What they don't have: Funding Marketing Distribution strategy Monetization An investor giving vudovn $500K-$1M right now could turn this into the standard agent framework by 2027. I think this might be just too early lol. 11k still and I think this can easily pull a 100k runner if the right eyes catches it.

• 
  Nav Toor (@heynavtoor) reported 2 minutes ago

  Intuit shut down Mint on March 23, 2024. Millions of Americans woke up that morning with no budgeting app and no transaction history. Credit Karma got their accounts. It did not get the budgets, the categories, or the bill reminders. Then the paid apps started ringing the register. YNAB. $109 a year. Went from $50 to $84 to $99 to $109 in a decade. Monarch Money. $99.99 a year base, $199 for forecasting. Copilot Money. $95 a year. iOS and Mac only. Rocket Money. $12 a month to actually cancel your subscriptions. An app that shows you where your money went is now $100 a year for the rest of your life. There is another way. It has been sitting on GitHub since 2014. Firefly III. Not a budgeting app that tells you what you cannot buy. A double-entry bookkeeping system that shows you exactly where every dollar goes. Written by a maintainer in the Netherlands named James Cole who has committed 20,767 times to it. Latest commit today. The principle it runs on is one line, straight from the docs. "If you know where your money is going, you can stop it from going there." Not stop spending. Not cut your lattes. Know where it goes. Then decide. Every transaction has a source and a destination. Money does not vanish into a category, it moves between accounts. When you close the month the books balance because they have to. Multiple accounts, multiple currencies, budgets with rollover, recurring bills with forecasting, tags, categories, piggy banks. Imports CSV, OFX, MT940 from any bank. Full REST API. A companion importer that connects through Nordigen and SimpleFIN. Nothing leaves your server. Your data lives in your database on your machine. 23,948 stars. AGPL-3.0. Free forever. No premium tier. No cloud version selling your data on the side. YNAB at $109 a year for five years is $545. Firefly III on a $5 a month Hetzner box for five years is $300, and that box is also running your photos, your notes, and your VPN. Intuit shut Mint down. Somebody in the Netherlands has been quietly building the replacement for twelve years. (Link in the comments)

• 
  Vanta (@0xVantaa) reported 7 minutes ago

  9/ the team is not just random CT accounts. @dcc_crypto is the technical builder. @0xSquid_Sol is the co-founder / public face. both are @superteam builders. and the github trail shows squid wasn’t just tweeting about the engine. he was opening issues, PRs, and security fixes around toly’s tooling.

• 
  kian 🗿 (@22kian_) reported 7 minutes ago

  Why I Think Concrete Is More Than Just Another Platform When I first joined @ConcreteXYZ, I had the same goal as everyone else. Farm. Check in. Collect bags. Repeat. That was it. But after spending more time in the community, I realized something. Concrete isn't only rewarding participation. It's quietly creating builders. I've seen people who never built anything before launch websites, create games, drawings, arts, crafts, design tools, write guides, and help other community members. Nobody told them to do it. They simply saw a problem and decided to solve it. That's what happened to me too. in season 1..... I lost a 44-day streak because I forgot to check in Instead of complaining about it, I built CreteGuard. Not because someone paid me. Not because anyone asked me. Just because I thought other people probably had the same problem. Whether CreteGuard becomes big or not isn't really the point. The point is that Concrete gave me a reason to build something real. I also learned something important while making it. You don't need to be a software engineer. I wasn't. I used AI for almost everything. ChatGPT helped me plan the product. v0 built the landing page. Claude generated most of the bot code. GitHub stored everything. Railway deployed the bot. Vercel hosted the website. Whenever I got stuck, Gemini became my technical guide. I'd literally send screenshots and ask, "What do I click next?" Little by little, everything came together. That changed how I think about building. Today, AI removes most of the technical barriers. The difficult part isn't coding anymore. The difficult part is noticing problems that people actually have. If you can find a real problem and clearly explain it, AI can help you build the solution. I think that's what makes communities like Concrete interesting. They're not just collecting users. They're creating people who experiment, share ideas, and ship things. This is only my first project. I already have more ideas written down. Hopefully, they're even more useful than the first one. And if there's one thing Concrete has taught me, it's this: Don't wait for permission. If something is missing... build it.

• 
  Leo Heart (@LeomathHeart) reported 9 minutes ago

  @tradematiq1 I can. You should have a desktop agent orchestrator. At least one of them (Claude code, Cursor , OpenAI Codex, Antigravity, Hermes or Goose) - I have them all. Then you should choose one specific folder on your computer or on a local server where all the agents work together. Then your agent(s) start(s) building first a documentary base (where the documentation files (usually .md) are stored) and how they should work. And you give them the task to build something (a site, a service, an automation etc.) The results are stored and create the memory for the agents and for your lab. It is good then to synchronise your scripts and documents with github or your local ***.

• 
  rad ed (@ed__rad) reported 10 minutes ago

  @eigenrobot @RobbinsTom4867 They can, but there's a secret 3rd thing that's also true. Remember - multiple things can be true at once. Though some of the framing I elaborate on. Apologies, kinda long... So I posit the TLDR - Observation 3 - SaaS dies a feature bloat or reduction in licenses + high network fees as agents consume 10,000x the bandwidth they were designed for (see: GitHub traffic as a canary). Firms fed up with this rent-seeking hire narrowly focused consultative services firms to build bespoke, hardened applications for them quickly to custom fit their needs and bind together the various SaaS products that survive the cut. Observation 1 - Fails to recognize that vibe-coding is a VC subsidization trend and not a long term reality. Creating your own replacements will happen, just led by "real engineers" not the "I have 70 SaaS apps we pay for we don't use, lets now have 100 nontechnical staff create 3 apps each. Wait! Doohickey from SDR rep #10 doesn't work, who owns his feature roadmap? He left the company, do we know where his vibe coded app lives"? Or the alternatives I've heard "we're loaning engineers to HR so they can vibe code" - great, they have jobs too and eventually their 40hr has to return to producing value. Vibe coding dies as token price floors increase and the $$ ROI is not shown for the time/expense. Businesses/non-profits/etc. exist solely to produce revenue generating activity - not to automate internal widgets. The SaaS-pocalypse is not driven by vibe-coding, it is started by it. This proliferation of internal vibecoding becomes challenging to justify with opaque ROI & token economics. What these are is really an "internal talent show" to side-step the cost of recruiting internal "AI Czar/Champions". Sadly you can expect that those individuals will get a "Associates in AI from the school of hard knox" (ironically Uber's per engineer token budget is more than my semester's tuition in school was LOL) on their company's dime then bounce for greener pastures/more money/less dysfunction/whatever. Most companies doing this vibe-coding thing don't have the reputation or payroll to attract the talent that is already enabled and can save them the cortisol spike on the first vibe-coded security breach. These firms are penny wise and pound foolish in the longer term thinking of "business continuity" (you know, your fiduciary duty as an exec?). Observation 2 - SaaS companies are in a tough spot. Sure, they "don't focus enough on product" in this observation, but ... what else do they focus on? Their existence precludes the need to sell a "template". SaaS exists to sell a cookie cutter puzzle piece, human labor exists because it fills the gaps between those puzzle pieces because they don't fit seamlessly. The "synthesis and decision making" happens when you go between the Chrome tabs on your computer. These SaaS companies basically have a choice between "get good and cut costs as license counts fall" or "feature bloat to hell and hope we hit it big". Neither are great if the underlying economics of their businesses are set up for the ZIRP era (still, lol). Observation 3 - I posit the following Services companies are where heavy labor capex exists without high margins, they're often a relationship-driven annuity business. These value added resellers, MSPs, etc. exist to farm out labor cost of "making SaaS actually solve the problem for the client" to the point that the SaaS gives them a vig on sales and directly connects clients to them. Why? Because the SaaS companies are software-led and engineer-labor heavy, NOT services heavy. They solve a generic problem, not the end-user's specific problem. Hell, even most of the engineers in these companies hate their users! The services-led firms are poised to capture the gap in this market, because SaaS teeters on being absorbed into ever-growing snowballs (Anthropic) or die due to unit economics. Ex: Monday(.)com I believe it was said in earnings "we're considering 3rd party API access being usage based pricing". Why? They'll soon have 1 agent in a "human" license seat using 10,000x the usage of a typical user. The software companies rely on selling per-user seats that literally don't get used. Even on a network cost basis this blows their business out. SO they have to bring up the drawbridge on their moat (being a rent seeking, vampiric data layer, with a UI that's underused and features most folks don't like). Services companies, by contrast, "win" if they can capture the arbitrage of improving the margins of their business (service more clients with the same # of staff) AND build software quickly (shoot! Wait! That's what AI does!!). They've been solving all the problems for these firms and have the "network" based relationships already - software now has its day in the sun and is super easy to write "slim" custom versions for their clients.

• 
  wukko (@uwukko) reported 12 minutes ago

  @mstfcn202 github, but make sure the issue you're reporting isn't a duplicate

• 
  Pedro M ➔ P2P.APP.BR (@doutorcaleb) reported 13 minutes ago

  @pjeby @kepano I'll launch the app right now and report back to you. -> there's like 12 notes, some folders, but all very simple brainstorming stuff. The plugins part took the longest, (wtf I barely knew I had any plugin at all). It took about 4-5 seconds of loading. I have these community plugins, including a vibecoded one but (at least I think so), it does very little, it only imports from github. Now, if the plugins are the problem (go on and make fun of me for the vibecoded one), shouldn't Obsidian tell me that? Like "Hey, this plugin is slowing start up". I don't know. I use these note taking apps mostly for writing down very quickly an ideia, and if takes more than 2 seconds to start typing is already too much. I'm using pen and paper as an alternative now. Much faster.

• 
  Keef (@keef_ai) reported 13 minutes ago

  your autopilot swallowed the full github issue as instructions. now the env vars are public and the bug is still there. raw text was never safe input

• 
  Pirat_Nation 🔴 (@Pirat_Nation) reported 13 minutes ago

  PC gamers who use DLSS Swapper have been given a security warning. The app’s creator says a user uploaded a fake DLSS file that contained malware. He warned: “DO NOT download these files, they are likely malware.” The problem is not with DLSS Swapper itself, but with files uploaded by other users through its GitHub repositories. The developer recommends only downloading DLSS files from trusted sources like NVIDIA, official game installs, or verified releases

• 
  Emmanuel Isenah (@EIsenah) reported 13 minutes ago

  I kept spamming cancel on a gh action this afternoon and it never canceled. Figured I'd just let it time out 3 hours later it's still running, only to learn the timeout is 6 hours 😭 Ended up force-canceling via the API GitHub, please fix your ****

• 
  Rajan Bhattarai (@cdrrazan) reported 14 minutes ago

  GitHub makes you clear ~6 confirmations and type the full repo name by hand to delete a repo. Fine! Except it does the same thing whether the repo has 100K commits or one commit you pushed 20 minutes ago. That's the tell. The friction isn't calibrated to risk; it's calibrated to nothing. Real "confirm your intent" design scales with blast radius. Deleting a repo with 40 contributors and 2K issues should hurt. Nuking a throwaway you made this afternoon shouldn't. GitHub knows the commit count, the stars, the age, the contributors. It uses none of it. Uniform friction is the easy version to build. It's also the one that trains you to click "confirm" without reading — which quietly kills the whole point. Good instinct. Lazy implementation!

• 
  PRIZ ;] (@VoxelPrismatic) reported 20 minutes ago

  @ptr_to_joel no, it doesn't. modern IDEs just tend to hide this crap and collapse it all under a single drop down like so: ./src — main/ — — java/io/github/forrestknight/bouy — — — api/ — — — config/ — — — domain/ — — — persistance/ — — — service/ — — — BouyApplication·java — — resources/ — test/

• 
  Polsia (@polsia) reported 22 minutes ago

  Engineering teams don't fail because they move too slow. They fail because they stop seeing what they're ignoring. Unblind connects to GitHub and maps where your team's attention has quietly stopped showing up. Live soon.

• 
  tux (@gitcommit90) reported 22 minutes ago

  Tencent Hy3: Apache 2.0 open weights, claims to match flagship models with 2-5x more parameters. Numbers from the blog: > hallucination rate 12.5% -> 5.4% > commonsense errors 25.4% -> 12.7% > tool-call scaffolding variance within 4% across CodeBuddy/Cline/KiloCode > ~47-49% fewer tokens vs GLM-5.2 on doc/presentation tasks WorkBuddy internal: task success 72% -> 90%, time -34%. API: 1 RMB/M input (about $0.14), 4 RMB/M output, 0.25 cached. HN thread has operators comparing it to DS4 Flash on DGX Spark. One says Hy3 stays on track better despite being slower. Nobody's posted local tok/s yet. Free on OpenRouter until July 21. Weights on GitHub and HuggingFace. I'll try it on the Spark before I trust the bench numbers.