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:

• 
  Dave Rapoza (@DaveRapoza) reported 6 minutes ago

  anybody else have issues with gmail just not showing relevant emails to you in 'important' or in search? is this a new thing? I seem to miss all sorts of stuff

• 
  RAK (@rk9712246) reported 7 minutes ago

  @TutaPrivacy @PeteMundo, Happy Tuesday. Based on your gmail rant yesterday I wonder if it might have been a google AI glitch vs a hacker.

• 
  The Valehart Project (@ValehartProject) reported 7 minutes ago

  @nicdunz It's cool. You can just utilise the bug in their billing to get access to other accounts that they won't fix despite it being on the dev forums. I used this on a Gmail account to "breach" my own business account for a proof of concept to get them to fix it. Didn't need to provide consent or anything. Just sitting there draining my own business account via a gmail.

• 
  Rabiisu (@Taimoor_khan01) reported 8 minutes ago

  @HeyGen Important Note: Hi Heygen Support Team! I subscribe Heygen Pro Since May 2019. 1 week ago the gmail i used to signup Heygen Subscription was compromised and i talk to Mail Team to immediately shut down my email so the hacker canton access my important account’s.

• 
  mayrachm (@mayrachm) reported 12 minutes ago

  @egavrilenko11 @bot 2/3 GitHub didn't work either. I even tried creating a Cursor account, and it was the same. It only worked when I used the Gmail login option. I used another personal account and then linked it to my Supergrok account. I'm logged in that way, but when I connected the X plugin...

• 
  anshuman (@athletic_coder) reported 12 minutes ago

  okay, so i was diving into the rollouts generated by qwen3.5 4B, here are some findings (given model has access to only api_search and api_fetch tool at any given point of time) > model is looking to gather information it needs to address query but ends up burning tokens and exhausts upper cap of 50 turns in getting a query that actually returns functions that can help model clear ambiguity. > in the partially succeeded rollout (score this way was 17), where the model did discover the correct tool, it would eventually fail to solve that particular task, eg. - (sales subset) example id 504: Qwen found and used the correct Salesforce update endpoint. It updated the wrong Marcus Wong. - (sales subset) example id 503: Qwen found and used the CampaignMember endpoint. It enrolled prohibited people because it skipped the policy. - (sales subset) example id 1204: even knowing the Facebook photo endpoint does not tell it which image is eligible; it must retrieve Gmail policy + Sheet rows first. so my takeaway is that entire problem breaks down to two subproblems: 1. tool discovery (has to be token efficient) 2. the core policy i.e. Prompt > infer what information is missing > search for a capability to retrieve it (basically 1st subproblem) > call that capability > interpret returned observation > identify what remains uncertain > retrieve more evidence > choose target(s) > execute minimal writes > verify end state > finish the moment we break the problem, it is clear that it is a variant of computer use problem. the model needs to learn the ReACT loop. that's it. that's the optimization objective.

• 
  Fatih Arslan (@fatih) reported 14 minutes ago

  I sent my Grok @Bot to hunt down an out-of-stock book! It couldn't find any in stock, and the only copy left was way too expensive. But since it has access to my Gmail, it just started emailing publishers and bookstores itself. They're all Turkish, so it wrote the emails in Turkish. I would spent hours on this previously, now it's minutes. Let's see how it ends up :)

• 
  Tony Tong | Founder | Ancient Systems x AI (@tonytonggg) reported 15 minutes ago

  @_avichawla Cutting the redundant layer out of a pipeline is the same instinct I applied to my own inbox. I set up Opencode with a Gmail MCP server to triage which emails actually deserve a reply and read the warmth behind them, authenticated through the gmail-mcp auth step.

• 
  Boomer (@accesscode305) reported 16 minutes ago

  Firstly financial institutions have to inform both regulators and customers about any maintenance. If they don't inform, they could have fines or get sued. 8 hour maintenance doesn't mean 8 hour downtime. All other tech services including AWS, Gmail, etc can have downtimes and not answerable to anyone. No AWS customer ever got any compensation when it went down. Next is most critical financial transactions work through the maintenance (most monetary txns). Even most web or mobile applications work too with concurrency and parallel leg deployment. Lastly, FI have a balance between cost and modernity. They don't need to have every shiny new toy in the market. 50 year old mainframes work perfectly well with just peripheral API stack instead of wholesale cloud migration.

• 
  Kay Dray 💎 | (@Richhard430) reported 18 minutes ago

  @Ask_ORO I can't even login into my account I used my Gmail and X buh can't connect

• 
  Bhargavme (@bhrgvtlkdr7) reported 19 minutes ago

  @enough_yt hey, should i sign in my gmail with it or not? coz of security reasons

• 
  JovanHuttonPulitzer™ אני לא סובל טיפשים! (@JovanHPulitzer) reported 19 minutes ago

  @stelzner_n1150 This has to be the stupidest comment ever sorry. 100% of cell phones, smart phones, cable boxes, electric meters, computer usage and email GOES THROUGH DATA centers and always has! Here are the facts: That claim is backwards. The internet and smartphones have always run on data centers (or the same thing under older names: server rooms, colo, hosting farms). What changed is the size, location, and branding — not whether the machines exist. The internet never ran without servers Commercial internet use took off in the early 1990s. From day one it needed: ISP modem banks and backbone routers Web/email/DNS servers Co-location and hosting facilities Those are data centers. Exodus, AboveNet, Equinix, and telco “carrier hotels” were already packing raised-floor rooms with racks in the mid-to-late 1990s. Google’s first big custom plants and Amazon’s early AWS rooms were 2000s expansions of that model, not a new species of building. You could run a static homepage off a PC in a closet. You could not run search, streaming, maps, payments, or “the internet” as people actually used it. Smartphones made the dependence worse, not optional The iPhone shipped in 2007. A phone is a thin client. Almost everything people treat as “the phone” lives off-device: iCloud / Google account sync Maps and traffic App Store / Play Store Gmail, Photos, Drive Instagram, TikTok, YouTube, Spotify Siri / Assistant Banking and payments That traffic hits someone’s data center. If those rooms went dark, the glass slab in your pocket would still make calls on a good day and not much else. Twenty years of smartphones is twenty years of more backend compute, not twenty years without it.

• 
  Kakwenza Rukirabashaija (@KakwenzaRukira) reported 26 minutes ago

  These capitalistic tech giants astonish me. They handed me a shiny free Gmail service, stealthily vacuum up my life, then either feed the data into their own next product or sell it to whoever pays. They want a front-row seat to almost everything I do—and then they have the nerve to charge me a subscription for the privilege. Classic move: invent the problem, monetize the “solution.” The whole racket of capitalists is so brazen it almost deserves a ceremonial send-off: wrap the lot of them in their own terms of service and drop them into the deepest trench the ocean has. Anyway. Time to say goodbye to Gmail.

• 
  R Dilip Kumar (@dkspeaks) reported 27 minutes ago

  An imported automation will not just run, and that is not a broken template. Every one of them needs your own accounts connected before it does anything. Your Gmail, your Notion, your Drive. The workflow is the wiring. It is not the electricity. Most people import one, hit the first credential error, decide the tool is broken, and never open it again. That error is the normal first step. It is the workflow telling you exactly which account it wants.

• 
  Cody Schneider (@codyschneider) reported 28 minutes ago

  cold email explained Low IQ: Get a list of people with the problem. Send them four sentences about the problem and one specific offer. Send a lot of them. Midwit: 40 domains, 120 mailboxes, a rotation schedule, and a spreadsheet tracking mailbox health Warmup tools running permanently at 30 emails/day forever Spintax on every sentence, {{first_name|there}} fallbacks nested three deep "Spam word" avoidance — rewriting "free" and "guarantee" out of copy like it's 2011 Gmail Open tracking on, via a custom tracking domain (open tracking is itself a deliverability liability) AI personalization on the wrong variable: "Noticed you studied at Michigan State — go Spartans!" 9-step sequences ending in "bumping this up," "did this get buried?", and the breakup email 14 micro-ICP segments with bespoke copy for each A/B testing subject lines on 200 sends and declaring a winner Reporting reply rate as the KPI When it doesn't work: buy more data, add more mailboxes High IQ: Precise list, short email, one specific offer, high volume, hygiene done once. Measure meetings held and pipeline, nothing above it.