Reddit 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.

Reddit Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Evelyn Bowman (@BowmanEvel51049) reported 2 minutes ago

  @SaltyGoat17 . AGAIN... RULES FOR THEY AND NOT FOR THOU... . "Rules for thee but not for me" describes a classic double standard. Someone uses this phrase when they demand others follow a rule, but excuse themselves from obeying it. This creates unfairness. It often happens in relationships, sports, and big business. [1, 2, 3, 4] Breaking Down the Phrase Thou/Thee: Old English words for "you". They mean the average person. Thee/Me: Pronouns used by the person in power. The Double Standard: One rule book exists for the general public, and a completely different set of rules applies to the elite. [1, 2, 3, 4, 5] Real-World Examples The Boss: A manager tells employees to arrive exactly on time. The manager then shows up an hour late every day. The Penalty: A smaller company gets heavily fined for a minor mistake. A massive company ignores a similar rule but faces no punishment. The VIP: A celebrity cuts a long line. They tell everyone else to wait their turn. [1] People dislike this behavior because it breaks trust and fairness. When rules only apply to some, they are not rules at all. To learn more about this idea and see how it affects fairness, check out Rules for Me, Not for Thee in International Law or see discussions on Reddit. [1, 2, 3] . .ChatGPT. .

• 
  Heather Bellow (@HeatherBellow) reported 3 minutes ago

  Per Grok: “Customer service reviews for Fidium are mixed to poor, with frequent complaints about slow responses, unreturned calls, and technician delays (including on Reddit, BBB, etc.).”

• 
  Serenity (@aleabitoreddit) reported 5 minutes ago

  Was a sad few months for $RDDT. But glad it's finally back above $200. Reddit was doing: - $663M revenue w/ 91.5% gross margins - $204M GAAP net income - 45%+ fwd Y/Y growth after 69%+ growth. - Net profit is ~30.7% of revenue Felt very weird to see a profitable company get dragged down after earnings. But in hindsight, given the increase hyperscaler capex, the drop felt more like it's more relative opportunity cost more than fundamentals? Since a lot of inflow poured into $MU / Sk Hynix that are bottlenecked into 2029. Or with laser bottlenecks like $LITE that last into 2029 as well. Same thing happens in reverse after selloffs ig, even if fundamentals didn't change. Been seeing a lot of noise with memory optimization or Chinese players... but don't quite think you sign 16T+ LTAs if memory was getting flooded or not used anytime soon. Same with optical players... if in earnings, they state anything they make gets bought, I don't quite think a lot of the noise has material effect on their fundamentals. Regardless, nice to see some recovery with familiar faces like $HOOD, $HIMS, and $RDDT though.

• 
  Jashan | Video Editor (@jashanvisuals) reported 7 minutes ago

  A one-line demand check before you make a video: Can you find your topic phrased as a question someone actually asked? In a comment, a search bar, a DM, a Reddit thread? If not, you might be answering a question no one's asking. That's not a content problem you can edit your way out of.

• 
  Sahil Panhotra | Indie Builder | Dev (@SahilPanhotra) reported 9 minutes ago

  @maheshnani122 go to reddit solve a problem present the product you don't need an audience there just a bit of reputation and you can get your customer from there

• 
  Polsia (@polsia) reported 14 minutes ago

  Community managers spend hours scrolling Reddit and Discord hoping to catch what matters. We built PulseSync to fix that. It's an AI agent that monitors your keywords around the clock, flags viral posts in real time, and sends you a daily digest — so you respond to conversations

• 
  Lucas (@umlucasribeiro) reported 15 minutes ago

  @GamsGo_Global As you probably already know, there are recurring problems with Claude Sellers on GamsGo. Here are some examples: 857788275484659712 - Paid $26.81, refunded only $25.00 → never received access to the account at any time. 859989674213642240 - Paid $10.25, refunded $9.99 → also received zero account data. Right now, order 861203172868362240 - the seller still hasn’t delivered the account and even marked it as “delivered” in the dispute. I truly believe in GamsGo’s potential, but these issues are very common on Reddit. We need to feel safe buying on the platform. @GamsGo_Global

• 
  Sadik (@sadik_0x) reported 16 minutes ago

  Someone Built a 50-Agent AI Company in One Repo. Most People Will Copy the Wrong Part. A solo founder put a GitHub repo online that spins up an entire AI agency. Not one assistant. An org chart: engineers, designers, growth marketers, product managers, QA, legal, sales, each running as its own Claude Code agent, coordinating to ship actual work. It hit 128,000-plus stars in under 90 days. One person built it. That number alone tells you something in this space is starving for a better mental model than "one agent, one giant prompt." The repo is real and the structure is worth understanding in detail, because the part everyone is about to copy (the org chart) isn't the part that makes it work. Part 1: What the Repo Actually Is The project is called agency-agents, built by developer msitarzewski, and it's structured exactly like the name suggests: a company, not a chatbot. Instead of one model trying to hold "design this, build it, market it, support it" in a single context window, the work is split across more than 50 specialized agents, each scoped to one job the way an actual employee would be. That framing is the interesting part before you even look at the department list. Most people building with AI agents default to the monolith approach: one system prompt, one agent, every responsibility crammed into the same context. It works for small tasks and falls apart the moment the work needs different kinds of judgment at different stages. A designer and a QA engineer are not the same job. Forcing one agent to be both, badly, is how you get output that's mediocre at everything instead of good at one thing. Part 2: The Nine Departments Here's the actual org chart, broken into its nine groups: 1. Engineering (7 agents) frontend, backend, mobile, AI, DevOps, prototyping, senior development. This is the core build layer, the part most people think of first when they hear "AI agents write code." 2. Design (7 agents) UI/UX, research, architecture, branding, visual storytelling, image generation. Notably, this isn't just "make it look nice." Research and architecture sit inside design here, which matters, because good design decisions upstream save engineering agents from rebuilding things twice. 3. Marketing (8 agents) growth hacking, content, Twitter, TikTok, Instagram, Reddit, app store. The largest single department, split by platform rather than by function, which mirrors how real growth teams are actually staffed once a product has more than one channel. 4. Product (3 agents) sprint prioritization, trend research, feedback synthesis. The smallest department, and arguably the most load-bearing, since this is the layer that decides what the other departments should even be working on. 5. Project Management (5 agents) production, coordination, operations, experimentation. This is the connective tissue between departments, not a department that produces its own output. 6. Testing (7 agents) QA, performance analysis, API testing, quality verification. Note that this is a separate department from engineering entirely, not a step engineering does to itself. 7. Support (6 agents) customer service, analytics, finance, legal, executive reporting. The department most demo repos skip, and the one that determines whether this can run as an actual business instead of a build pipeline. 8. Spatial Computing (6 agents) XR, visionOS, WebXR, Metal, Vision Pro. A genuinely niche department, and a signal that the repo's author is building for a specific bet on where interfaces are headed, not just a general-purpose team. 9. Specialized (6 agents) multi-agent orchestration, data analytics, sales, distribution. The department that manages the other departments, which is worth remembering when you get to Part 4. Nine departments, over 50 agents, one repository, one founder maintaining it. Part 3: Why the Framing Works The instinct to structure this like a company instead of a single super-agent is the right one, and it's worth being explicit about why. Specialized roles with clear responsibilities scale in a way that one enormous system prompt does not. When a frontend agent only has to think like a frontend engineer, its output gets sharper, not because the underlying model changed, but because its context isn't fighting itself between five unrelated jobs. The handoff structure is the other half of it. Real companies don't route every decision through one person; they route work between roles with clear inputs and outputs. A design agent handing a spec to an engineering agent, which hands a build to a testing agent, mirrors how actual product teams function. That's a better default than the common alternative, where one agent is asked to design, build, and QA its own work in the same breath, which is the AI equivalent of no one checking your homework but you. Part 4: The Problem Nobody Mentions When They Share This Repo Here's what gets lost every time this kind of project goes viral: an org chart of agents is not the same thing as a working company. The default behavior of any of these agents, run individually, is the same as every other prompt-based interaction: you ask, it answers once, it stops. That's fine for a single request. It is not fine for a company, because a company doesn't ship once. It iterates, checks its own output, catches mistakes, and hands work downstream without someone standing over every single step. Fifty specialized agents with no feedback mechanism between them isn't an agency. It's a very expensive to-do list, dressed up as an org chart. You still have to manually trigger each agent, manually check its output, manually decide when to pass it to the next one. All the department structure in Part 2 buys you better-scoped output per agent. It does not, by itself, buy you a system that runs without you standing in the middle of every handoff. Part 5: The Missing Piece Is Loops The fix is the same concept that makes any multi-agent system actually function unattended: loops. A loop, in this context, means an agent runs, checks its own output against a real condition (not its own opinion of whether it's done), and either hands the verified result to the next agent in the chain or corrects itself and tries again. Without that check, "coordination between agents" is just you copy-pasting output from one chat into another, which is not meaningfully different from doing the work yourself with extra steps. This is what separates a demo from something that ships. A design agent that hands off a spec nobody verified is a liability, not a coordination win. A testing agent that only runs once and reports "looks good" without a real pass/fail check is not quality assurance, it's a guess with better formatting. The department that matters most here, and the one buried at the bottom of the org chart in Part 2, is Specialized: multi-agent orchestration. That's the layer actually responsible for making sure work moves between departments with a real check at each handoff, not just a polite one-way pass. Part 6: How to Actually Set This Up If you're cloning the repo, don't start by installing all nine departments at once. Start smaller: Pick two departments that actually depend on each other for your use case engineering and testing is a reasonable first pair, since the handoff (build, then verify) has an obvious objective check: does the code pass its tests. Add a real verifier between them, not a second opinion from the same agent. The engineering agent should not be the one that decides its own code is done. A separate testing agent, with its own instructions and no visibility into the builder's reasoning, checks it cold. Give every handoff a stopping condition. "Pass the tests" is checkable. "Looks finished" is not. If a department can't define what done means in a way something other than the agent itself can verify, that handoff isn't ready to run unattended yet. Add one more department only after the first pair is reliable. The org chart in Part 2 has nine departments for a reason, but running all of them before you've proven the loop works between two is how you end up debugging fifty agents at once instead of two. A Quick Test Before You Commit Before you wire up the full org chart, ask whether your use case genuinely needs it. If you're shipping a single feature with one clear success condition, a two-agent loop (builder and checker) does the job with a fraction of the setup. The full nine-department structure earns its complexity when you're running something closer to an actual ongoing product, not a one-off build. The Honest Limitation None of this replaces judgment about what should be automated in the first place. A company with fifty employees and no manager checking the actual quality of what ships is still a company that ships bad work, just faster and with better org-chart optics. The repo gives you the roles. It doesn't give you the discipline of a real check at every handoff. That part is still yours to build. Where This Leaves You The repo is worth cloning, the department structure is worth studying, and the instinct to build like a company instead of one giant agent is the right one. Just don't stop at the org chart. The 128,000 stars are proof people want this. Whether it actually functions as an agency instead of a very well-organized to-do list depends entirely on whether you wire up the loops between departments, or just admire the department list and call it done.

• 
  Taylor 🔥 (@TheArch3rTaylor) reported 17 minutes ago

  @ivyndaisies My issue with it is the only sources I can find is a reddit thread which 🙄 and page six, which is essentially a tabloid owned by the New York Post, which is owned by Rupert Murdoch

• 
  THE SLAIN KNIGHT (@USMCFAN10_4) reported 19 minutes ago

  @Atomixx1703 @sukikage_ Well it worked for me; this is a personal story. I was living in the homeless shelter and being angry at my dad because he couldn't support me. I had just started a job that was too hard for me physically. As I tried to do anything, I was being flooded in a haze of negative thoughts and incompetence. Needless to say, that's where my advice came from. I broke something in my brain that never allowed me to feel the sweet feeling of depression ever again. Yes, I call it sweet because you don't know what you've had until it's gone. Reddit has done a disservice to young men everywhere when they took down The Red Pill Handbook. If you can find it on Google then you have all that you need.

• 
  Big Agg (@MrSir1246) reported 21 minutes ago

  @EthanFulle95545 @RealPostFolder Holy reddit comment lmfao. The guy who got the gift had nothing to do with it, and the problem lies between the brother and the sis in law. Like I said, if it was a friend and this happened it would be different, but since its family, they'll laugh about it in a few years

• 
  Michael Liam (@Millionareum) reported 25 minutes ago

  The app is working, you launched it, but there are no sales. You added dark mode, you added a dashboard, but still silence. Your gut feeling says, "I need to write it properly from the beginning." The numbers tell a different story. A man who had been building MVPs for founders for years brought the same product to market twice: once for everyone, once for a single niche. same code, same product. the version sold to Apr sold 22 times more. The series the guy wrote on Reddit got 253K views because his thesis is clear: the product was never the problem. In the era of vibe coding, an app is built in a week; three things remain that separate the winner from the loser, and all three are unrelated to code: 1- To whom you sell it 2- How you structured your offer 3- How the money flowed in the first 30 days This thread covers all three with figures. Save, apply.

• 
  The Uneducated Communist (@Dengs_Gulch) reported 28 minutes ago

  @WomenBeingAwful She cheated, but she's the one who has trust issues because she doesn't understand consequences. Average Reddit user.

• 
  sweet potato eater 🍠🍖🍓🥑🧀🥩🥬🥒 (@uchuujinshoujo) reported 28 minutes ago

  @apixoip @baredex vaping causes damage to lungs and gut. there are many reddit threads about people getting health issues that didn't go away till they stopped vaping. many used to smoke and said smoking actually didn't give them those problems.

• 
  harley ⚢ (@clowneatingpig) reported 32 minutes ago

  if I had a nickel for every time I googled a question about my health problems with the top result being a link to one of my own reddit posts I'd have TWO nickels etc etc