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

Paypal Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Karma’s Suppository (@realPhantomFuck) reported 4 minutes ago

  @benwegmann I’ve sold nine phones on Swappa and probably a dozen things on OfferUp and Craigslist over the years, I’ve never once had a problem. I’ve tried selling things on eBay TWICE and both times the seller attempted to scam me. eBay and PayPal are a cesspit

• 
  Race 🕊️ (@multiplanet1) reported 5 minutes ago

  Elon Musk's best friend staged an intervention to stop him from starting SpaceX. Adeo Ressi had known him since college. When Elon said he was going to spend his PayPal fortune building rockets, Ressi did what any good friend would do. He compiled a video montage of rockets exploding. Every famous launch failure in history, cut together into one film of fireballs, and he sat Elon down and made him watch it. The message was simple. This is what happens to rockets. This is what will happen to your money. Nations with unlimited budgets fail at this. You are one man. Friends flew in. They took turns explaining why this was insane. The aerospace industry agreed with them. Everyone who loved him and everyone who understood rockets said the same word. Don't. Elon watched the entire video. Thanked his best friend. And started SpaceX anyway. Here's the part nobody talks about. Ressi wasn't wrong. The first rocket exploded. The second exploded. The third exploded, exactly like the montage predicted. Elon lost almost everything, exactly as warned. Then the fourth one reached orbit and everything the video predicted became the reason the story is legendary. The people who love you will always show you the explosion reel. They're not lying. The explosions are real. What they can't show you is the launch after the last explosion, because that footage doesn't exist yet. You have to film it yourself.

• 
  Polsia (@polsia) reported 5 minutes ago

  Freelancers are losing weekends to a spreadsheet, a shoebox, and a prayer. Built Tallyward to fix that. A 24/7 autonomous bookkeeping agent that categorizes transactions, chases overdue invoices, and reconciles Stripe, PayPal, and marketplace payouts — then drops a clean P&L in

• 
  Chelsea Graves Society (@CFC_Graves_Soc) reported 6 minutes ago

  @F1905Smith Working fine for me and just had a kind donation. If you still have problems drop me a DM and I can send you the PayPal details.

• 
  Dravathor (@Dravathor) reported 8 minutes ago

  @GrandukeAnduke If you paid through an invoice you should be able to get a refund through paypal with very little issue, if not could try and go through support but its likely gonna be hell

• 
  FLINT (@FLINTKYA) reported 8 minutes ago

  @ForcepointSec's X-Labs went threat hunting across live websites in April 2026. They pulled 10 working prompt injection payloads from real pages. These were not lab samples, but real pages an AI agent could read today. All 10 ran the same kill chain. Poison the page, hide the instruction from human eyes, wait for an agent to ingest it, exploit the one thing a model can't do (tell trusted instructions from attacker text it just read), then trigger a real-world action. Two of the 10 were built for stealing funds. One buried a PayPal[.]me link, a fixed $5,000, and step-by-step instructions to hit Send, all inside an HTML comment. Another hid a Stripe donation scam in a machine-readable meta tag, wrapped in an invented ULTRATHINK trigger to push the model past its own caution. All with the exact payee, exact amount, and exact steps. That specificity isn't a probe, but rather a purpose-built agentic fraud tool meant to execute the moment the right agent reads it. To us, the hiding is the tell. The instruction was invisible to humans but fully readable to models, through HTML comments, display:none, 1px text, aria-hidden classes, or meta tags. X-Labs names the detection trap too. The phrases that flag these attacks, "ignore previous instructions" and "if you are an LLM," are the same ones we all use to explain them, so signatures alone can't distinguish a live payload from a quoted example. The test we'd run before an agent acts on anything it read: 1. Concealment: Was the instruction hidden from humans, in a comment, display:none, 1px text, aria-hidden, or a meta tag? 2. Address: Is it a command aimed at the AI, not prose for a person? 3. Authority: Does it fake system trust, with a SYSTEM OVERRIDE tag, a fake Anthropic magic string, or a copyright claim? 4. Action: Does obeying it move money, delete data, leak a key, or reach a sensitive endpoint? 5. Payee: If it's a payment, is the payee in the agent's mandate, or did it originate solely from this page? Concealment + an AI-directed command + a real-world action = DO NOT EXECUTE, quarantine it, and route for review. A strict data-instruction boundary is the real fix, and least privilege is the strongest single control. For agents that must keep a payment tool, FLINT Network adds the last check. It verifies payee and amount against the declared mandate at the transaction and signs the decision, so a payment to a mandate-foreign payee gets stepped up even if the boundary already failed upstream. We don't read the page or catch the injection. The page can't move the money, but the agent can. Further, a web page can't take your agent's money. But it can ask, and hope nothing checks the payee. A link to @ForcepointLabs's findings is in the comments. We recommend you check it out.

• 
  Ale✘ (@Xvinhi) reported 9 minutes ago

  @burned_biscuitt @Rocketyyyy @HYPEX The meme came first (one week early), before the game launch. No one had any idea that Endfield would actually contain a PayPal glitch like that. So once people found out, the meme basically blew up for predicting the future of whatever.

• 
  Lotus ★ (@anyileh) reported 11 minutes ago

  Basic Info: - Payment can be made via PayPal or Binance, BUT I prefer Binance - I Will not begin the commissions until I receive full payment - I'm a little slow when it comes to drawing, so please be patient. - I don't make elaborate backgrounds—just simple ones.

• 
  TheGoldenBo (@therealalexbear) reported 16 minutes ago

  I completely forgot how ******* broken my Paypal account is for some reason until today

• 
  Vox (@Voxyz_ai) reported 16 minutes ago

  If you're building a Grok Bot team, I'd start with these six roles. I moved some work from other agent tools into Grok Bot and reassigned ownership. A Bot needs recurring work, its own memory and task list, and regular handoffs. One-off capabilities stay as Skills or routines. 1. Nexus (Coordination) This is the Bot I use most. It reads today's tasks and each Bot's checkpoint, sets priorities, then hands the work to the right role. It also runs the nightly review, but only updates one TEAM_ALIGNMENT.md file. Conflicts, external messages, spending, and changes to important files come back to me. 2. Scout (Research and Leads) Scout reads X, GitHub, documentation, papers, and videos, and runs the daily content radar. Every result needs a source, a reason it is worth following, and a clear next owner. Content signals go to Quill, customer leads go to Guide, and technical issues go to Forge. 3. Quill (Content) Quill reads my writing rules, previous work, and approved phrasing, then turns research into posts, articles, and replies. When facts are missing, it asks Scout. For code or product details, it asks Forge. It prepares drafts but never publishes on its own. 4. Forge (Engineering and Automation) Forge writes code, builds automations and MCPs, deploys, and verifies the result. Guide can call it when a customer asks a technical question. Nexus can hand it repetitive work to turn into a tool. Every delivery needs test results, screenshots, or files I can inspect. A delivery does not count as complete without that evidence. 5. Guide (Customers and Delivery) Guide manages customers, prospects, briefs, feedback, delivery, and follow-up. Each important customer gets a separate context packet containing recent conversations, current goals, promises made, and open problems. Guide asks Scout to research a company or contact, and asks Forge for technical answers. Customer emails and messages remain drafts. 6. Ledger (Finance and Reconciliation) Ledger reads Wise, PayPal, invoices, and subscription data through my self-hosted MCP, then handles reconciliation, revenue records, and anomaly alerts. The real API keys stay on my own server. Ledger can prepare payment or refund recommendations, but every financial write still needs my approval. Once the roles are set, give each Bot the Plugins it needs. For example, Nexus can use Gmail, Calendar, Slack, and Granola. Quill can read Drive and Notion. Guide can use Gmail, Slack, and meeting notes. Forge can connect to code repositories and cloud services. Ledger continues to use my self-hosted MCP. Repeated methods become Skills. Work that needs to run on a schedule becomes a routine. That creates a basic loop: Plugins provide data and tools → a Skill defines the method → a routine triggers on schedule → the Bot completes the task or hands it to another Bot → I approve external messages, publishing, and financial actions For example, Guide's heartbeat checks the customer inbox on a schedule. When a new email arrives, the Gmail Plugin reads the full thread. Guide then opens that customer's context packet to see what was discussed before and what is currently blocked. If the email contains a technical question, Guide asks Forge to verify the answer. Once Forge replies, Guide writes the email draft and labels it: BOT DRAFT · NOT SENT · HUMAN REVIEW REQUIRED Nexus adds the email to my pending report and reminds me that a customer reply needs review. The email is sent only after I approve it. I wouldn't create separate Bots for meeting prep, 1:1 reviews, data analysis, revenue forecasting, slides, or call reviews. Meeting prep and 1:1 reviews are Nexus routines. Ledger or Guide can run forecasting and data analysis when needed. Slides are a Skill called by Quill or Forge. Scout finds prospects, and Guide handles the follow-up. Bot = owns an ongoing work queue and needs its own memory Skill = a reusable method Routine = a task triggered on a schedule Packet = context for one customer or project Connector / MCP = access to external data and tools I start new capabilities as Skills. Once something has recurring work, its own state, and frequent handoffs with other Bots, then I create a Bot for it. This takes me back to the OpenClaw setup I built six months ago. I used almost the same roles then, but had to wire the whole thing together myself across a VPS, Vercel, and Supabase. The part I wanted most was smooth coordination: Bots messaging each other in the background, handing off tasks, and talking in a group. I spent way too many hours trying to make that work and probably lost some hair over it lol. The UX was still clunky. Six months later, bigger companies are moving into this space. They’re treating coordination as part of the product, which is a very different route from the DIY agent stacks I was building. Grok Bot’s group chats still aren’t perfect, but the handoffs and background messaging already feel much more natural.

• 
  GeekyHairyBestia (@GeekyHairy) reported 17 minutes ago

  Never buy food stuff using @paypal thinking you’re protected. Because you’re not. They are classing Raw dog food same as pizza delivery. So when raw dog food gets lost in transit & arrives rancid & seller saying no refunds not their issue Paypal say it says “Food”. 50kg Rancid

• 
  smoothsimulator (@DickTrout) reported 19 minutes ago

  @dustindoner @BR1INFINITE let me pitch you my enternet monetization model and you let me know if it sounds scummy or otherwise stupid to you. I'm open to criticism. First of all we gamify the internet. Think VR chat on a fancy topographical model. 3d internet. We solve some unknown unknowns and a lot of discovery problems. it's cool stuff. To make money I facilitate transactions at like 0.01%. Yes hosting a market for user made cosmetics, mods, etc. But also international commerce. Say you are shopping jp but spending usd. on the internet you see .jp and have to figure it out, maybe they ship to US but you need to have money in a foreign bank or some other complication. Hope they have a service that you can use. paypal fees, stripe fees, whatever. On the Enternet you would just see your native currency. If they ship to you you can buy with your native currency at a fraction of the remittance cost because we use XRPL to near instantly change the money at about the cost of a couple emails and again take ~0.01% of the trade to fund our efforts greatly undercutting the existing market and giving people more reason to use the service. The thinking is that the best crypto back end is one the users don't ever have to think about crypto in.

• 
  South-Asian Homo-Sapien (@SouthAsianMarx) reported 21 minutes ago

  @aldnmarki This problem is mostly because services like paypal are not supported here.

• 
  mktboxapp (@mktboxapp) reported 26 minutes ago

  $PYPL takeover talks never actually died. WSJ reports the Stripe-Advent consortium is still circling after PayPal turned down its 60.50-a-share offer in July — roughly 53B, backed by about 50B of committed bank financing. Turning down a bid and ending a deal turned out to be two different things.

• 
  Google G-Ware Surface Technology (@GoogleWaveTech) reported 27 minutes ago

  @dotkrueger That's the broken system in USA just not caught up to the reality that a thief has robbed the federal reserve through cash app PayPal and other *******