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

Gmail Issues Reports

Latest outage, problems and issue reports in social media:

• 
  chiingx 🍉🔻 (@sope_on_top) reported 6 minutes ago

  @TeamThe8_ @pledis_17 i first loged in with my gmail account, and then on the same device i tried to log in with apple account to vote but then it said the vote violated the guidelines or something. do you know how to fix this?

• 
  iamjepuhseun.Base Ⓜ️ (@iamjepuhseun) reported 7 minutes ago

  @chokmahxbt I used the real gmail to access my account and the wallet that eligible for the airdrop is also connected there. But when i tried to connect my wallet the error says that this wallet is connected to other account. This is weird cause im already logining the correct account.

• 
  Saad 📱 (@saadbelfqih) reported 8 minutes ago

  Most people judge Apple Ads way too early.. and I did too! They look at taps, installs, CPI… then pause the wrong keywords.. The real game is: keyword → install → trial → paid → revenue → ROAS. If you're not tracking that, you're guessing.. and with a small budget here's what I would do: 1 - Use Apple Ads Advanced. not basic.. please! Basic is easier, but you lose control over keywords, bids, countries, match types, and search terms. With a small budget, control matters! 2 - Start with Search Results only. that's where intent is. someone literally searched for the thing your app solves.. 3 - Don't start with "I want to scale." Start with: I want to learn what converts. .. which country, keyword, intent, product page or paywall. Scaling comes later. 4 - Don't mix too many countries in one campaign. One country per campaign is cleaner.. If one market works and another doesn't, you want to know that.. 5 - Don't sleep on smaller / cheaper / overlooked markets. I've found good pockets in places like Germany and Switzerland, and some tier-3 spots like Indonesia, Mexico, Philippines have honestly surprised me. Test around, your niche might live somewhere you didn't expect.. 6 - Start with exact match. Not broad. At the beginning, you want to know exactly what keyword triggered the tap. Broad / discovery can come later... I personally avoid it but you can always try at a later stage! 7 - Keyword buckets I'd test: competitor names, common typos, long-tail generic keywords, problem-aware keywords. Examples: transkribe, budget planner for couples, ai keyboard for iphone, Video to text etc.. 8 - Long-tail keywords are underrated. don't only bid on: scanner, keyboard, pdf, identifier. try the searches that sound closer to real intent. Less volume, but usually cleaner.. 9 - Competitor keywords can work (yes) but only if your app is a real alternative.. same niche, clear value & strong screenshots but not a random clone. 10 - Search Match OFF at the start. I know Apple suggests it. When you're learning, you don't want Apple picking random search terms for you. You want to know exactly what you paid for.. and I'm sure you don't want to be paying for Facebook, Gmail keywords at the start.. 11 - Start bids lower than Apple suggests. then increase slowly. also apple ads has lag, so don't change bids every hour.. 12 - Your product page does the selling before your ad ever does. People see: icon, name, subtitle, ratings, first screenshots. so if these (esp the screenshot) don't sell the outcome fast, the right keywords won't help you much 13 - Before spending, check competitors. not to copy of course, but to understand the pattern: what do they lead with? what outcome do they sell? how much text do they use? what pain do they show first? big apps already paid for some of that research 14 - Set up tracking before judging anything. Use RevenueCat, Superwall, an MMP, .. whatever, just track it! you want to monitor: country, campaign, ad group, keyword, spend, installs, trials, paid users, revenue, ROAS 15 - CPI can lie! a $0.40 install can be trash but a $2 install can be profitable.. The only question is: did this keyword bring paying users? 16 - Read the funnel properly: spend + no impressions = bid too low / low relevance taps + no installs = product page problem installs + no trials = wrong intent / weak onboarding trials + no paid = paywall or product issue revenue > spend = increase slowly 17 - When you find a winner, move it out of the messy test campaign. Give proven keywords their own campaign and keep them away from your random experiments 18 - Discovery is fine later.. it can surface search terms you'd never think of. Once a term works, move it into exact match. and keep dumping the irrelevant stuff into your negative keywords list.. helps apple ads point you at better keywords over time.. as confirmed by an apple ads support staff I talked to 19 - A tailored product page is worth testing when the intent is different.. competitor keyword? show why you're the better pick. feature keyword? lead with that feature. Same with the paywall, if they searched something specific, don't drop them on a generic one.. 20 - My small-budget setup: Apple Ads Advanced, Search Results only, 1 country per campaign, exact match first, Search Match off, manual bids, $5-10/day cap, competitor + long-tail keywords, tracking from day 0 21 - Kill rules I'd start with: spend + 0 installs → lower bid or pause installs + 0 trials → fix page / intent trials + 0 paid → fix onboarding / paywall positive ROAS → raise slowly not enough data → don't overreact and keep experimenting ... also worth checking out @adapty report on apple ads for some markets stats and for a detailed apple ads playbook worth checking @ivesparrowai book

• 
  Defender (@Defender_RK) reported 10 minutes ago

  @Google @TeamYouTube I need help recovering my Gmail account. The verification OTP is being sent to both my registered phone number and the same Gmail account that I can't access, so I'm stuck and unable to sign in. Please help me recover my account. Thank you. #GoogleSupport

• 
  ⟭⟬ 𝒟𝐸𝐸 💛(◍•ᴗ•◍)⟭⟬ (@dee_devhs) reported 11 minutes ago

  @ibps_official Gmail verification of ibps PO form not working. Fix this soon.

• 
  Ravi Madabhushi (@ravibits) reported 12 minutes ago

  You connect Gmail to an agent and it quietly gets all ~30 tools that server exposes. Most agents need one or two. So it walks around holding access it never touches. Every unused tool is one more way to pick wrong, one more thing you trust on every run.

• 
  Jay Petty (@JPetty2498) reported 13 minutes ago

  @Heartofgold4422 Doing so. Problem I have is x is in a Gmail accountant for some reason I cannot get to it on the tablet. So I’m gonna change it when x will let me try and mess with the account again. I’m in a time penalty atm

• 
  Biks (@getbiks) reported 13 minutes ago

  @CleanShot I have already emailed you 3 days back with invoice and recording of the issue. Please check. its from my username @ gmail

• 
  chiingx 🍉🔻 (@sope_on_top) reported 17 minutes ago

  @CaratLandHQ i first loged in with my gmail account, and then on the same device i tried to log in with apple account to vote but then it said the vote violated the guidelines of the device or something. do you know how to fix this?

• 
  Anjula Dwivedi (@HeyAnjula) reported 19 minutes ago

  Claude, ChatGPT, Gemini, and Grok agree on almost nothing. They all quietly agreed on MCP. Here's the part nobody's telling you: there are 11,000+ MCP servers live right now, and fewer than 5% make a single dollar. The plumbing is built. The money isn't picked up yet. MCP is basically USB-C for AI. Before it, connecting an AI to your tools meant hand-wiring a custom integration every single time. Now you build one small server and every major AI can plug into it — Gmail, your database, Notion, any API. And you don't even need to be a real engineer anymore. You describe the tool, Claude or ChatGPT writes most of the server, you ship it in a weekend. The playbook is stupidly simple: → Find a boring workflow someone repeats every week → Build one sharp MCP server that kills it → Free tier for reach, paid tier for revenue → Charge per use, per seat, or per outcome Servers that actually solve something are pulling $500–3K/mo. Some hit $10K in six weeks. Built once, sold on repeat. The window where "understands MCP + ships one tool" is rare won't stay open long. The marketplace is empty. Be the one who fills it.

• 
  Kamil Hussen (@kamilhussen24) reported 25 minutes ago

  @joinpeanut @zzMaruf I also faced this issue when I was trying to create my account for the first time. Since I was in a hurry, my primary Gmail was selected, but the passkey was mistakenly created under my secondary Google account. The problem is that I don't use my secondary Gmail regularly. With most other exchanges and applications, users can easily add, remove, or update passkeys whenever needed. However, this system doesn't seem to offer that flexibility. So, what is the solution in this situation if passkeys cannot be managed or transferred?

• 
  Aryan Mahajan (@aryanXmahajan) reported 25 minutes ago

  Hiring a random AI dev to "transform" your business is the single most expensive mistake a founder can make right now. Not because it costs 10K. Because it costs you 2 months believing the problem is solved while it quietly isn't. I've watched this exact ending happen to enough founders this year that I could time it. You've been sold a lie dressed up as convenience. A $100/month Cowork subscription does not run a company. It runs a HOBBY. You could hand every founder the best model in the world tomorrow and this problem doesn't move an inch. What happens at 2am when something breaks and nobody's watching it? If you're clearing $500K a year off a Gmail inbox, a shared Google Sheet, and a Notion board, fine, plug in whatever you want. You never had problems deep enough to expose the gap. If you're running $2M through six people, three vendors, and a CRM nobody actually trusts, you already know exactly how deep this goes. Even "AI project management" for ten people is not wiring Fireflies into Claude into ClickUp and calling it done. A real project manager does not hand out tasks. He knows who's on the other end of every single one. The guy who's missed three of his last four deadlines and still swears he's on track. The one who goes quiet the moment he's stuck instead of raising his hand. The one who needs the deadline said twice, and the one who never forgives you for saying it twice. An AI reading a transcript knows none of that. It's a faster to-do list. It has never met your team. It never will. You already live this. You still carry 90% of the real weight whether you've hired three people or thirty. Every hard call still lands on your desk, every time. That is not a hiring problem. That is a system that was never taught who anyone actually is. Here's the fix, stripped to what it actually is: One file. Per person. Not a personality writeup. → What they're good at → Exactly how they fail, dated, specific, tracked over months → The rule that follows directly from the failure. Not policy. Consequence. This is the Operating Brain. Not a slide in a deck. A file that gets corrected. A competitor can steal the idea over a weekend. He cannot steal the file. The file only exists after the same mistake gets caught and corrected three separate times, months apart, on a real person. That's the moat nobody is pricing in. Not the model. Not the folder. Not the prompt. What's described and what's actually running are the same thing. Your job is building the business. The Brain's job is never forgetting who's actually in it. Centralize the data first. Build the brain before you build anything else. Everyone chasing the shiny dashboard is going to find this out the expensive way.

• 
  Jyoti (@virgojyoti02) reported 29 minutes ago

  Once your gmail decides that your storage is fix then there is no going back.

• 
  Matt Graham (@Matt_Graham_) reported 30 minutes ago

  Notifications are the smoking of our generation. Here's how I quit (as CEO of a 220-person company): I get pinged 183 times a day. And I'm a slow processor: I need to sit with a message, think, then respond. For a founder drowning in Slack and email, that's a problem. So I built a system. Not perfect, but it gave me my focus back. 1. Every notification needs a clear owner. If someone pings me, the system has failed. The default should be "go to this person", not "go to the founder." Took a year to build. Worth it. 2. Only a handful of people reach me directly. My executive team. That's basically it. For everyone else, we run a 15-minute daily sync: "I won't answer pings all day. But in these 15 minutes, ask me anything." 3. Delegate ruthlessly. Then trust the filter. Assistants manage my Slack, LinkedIn, and Gmail. I see maybe 3 emails a day - everything else isn't important enough. Now the honest part: this is expensive. And your team won't always do it as well as you would. Partnerships, sales, escalations - people want the founder. But I can't do it all. That's the price of scaling. So you let your team do their best. Keep raising the bar. And resist the urge to grab it all back. Not perfect. But I can finally breathe again.

• 
  Aakash Gupta (@aakashgupta) reported 34 minutes ago

  You click unsubscribe, the emails keep coming, and you assume the button is decoration. It's actually a hard 48-hour deadline, and the reason the emails keep coming anyway is dumber than you think. The button fires a real HTTP POST request at the sender's server the moment you click it. The request body is a single line: List-Unsubscribe=One-Click. Then Google gives the company 48 hours to comply. That window is why the button feels fake. The emails already queued in the company's send pipeline still land. You unsubscribe Monday, get hit Tuesday and Wednesday, and conclude nothing happened. The second reason: companies run separate lists. Unsubscribing from "Weekly Deals" leaves you enrolled in "Product Updates," "Partner Offers," and the four other streams they added you to at checkout. Each one needs its own click. Here's what actually makes senders comply. Since February 2024, anyone sending 5,000+ emails a day to Gmail must support one-click unsubscribe and keep spam complaints under 0.3%. Cross that line and Gmail can block the entire domain. In November 2025, Google started rejecting non-compliant senders outright. So run the math from the company's side. One unsubscribe costs them a subscriber. One spam report moves them toward the number that kills their whole email channel. Three complaints per thousand sends is the death zone. Google built the unsubscribe button as a pressure valve. Every click on it is a spam complaint that never got filed.