Gmail status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Gmail reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Gmail users through our website.

• Website Down (37%)
• Errors (34%)
• Sign in (30%)

Live Outage Map

The most recent Gmail outage reports came from the following cities:

City	Problem Type	Report Time
Pontivy	Website Down	11 minutes ago
Le Mans	Website Down	14 hours ago
Paris	Website Down	2 days ago
Clermont-Ferrand	Website Down	2 days ago
Paris	Sign in	2 days ago
Chartres	Sign in	2 days ago

Full 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:

• 
  DWE Post (@dwepost) reported 3 minutes ago

  Dear Google Team, I can’t access my Gmail account. I forgot my password, and the standard recovery options are not working for me. This is my primary account. Please help me recover it as soon as possible. Thank you. @TeamYouTube @nealmohan @sundarpichai ???

• 
  Monty (@mont_py) reported 5 minutes ago

  @krzyzanowskim @NathanBLawrence yep, they totally ****** up and centralized the email. it almost feels like 95% of the global is on the gmail and the rest of crumbles shared between outlook, proton, etc. such a shame, the times when we were able to run own email server...

• 
  mark mei (@markdmei) reported 6 minutes ago

  NEVER struggle with email deliverability again. I just fed Claude code our entire system for 98% deliverability rates. Because I see this with almost every brand we onboard... They were spending hours on copy or design... Then type a subject line in 5 seconds and hit send. - > Gmail flags the subject line for spam. - > Routes to promotions. - > Open rate tanks. And the brand sits there going "email doesn't work for us." Nah. Your emails work FINE... Your subject lines are just getting buried. We built this tool for our team to score every subject line before it goes out. Originally internal. Now it's yours. Inside the tool: • Instant deliverability + engagement score for any subject line • Pre-built templates by category (abandoned cart, welcome, sale, win-back, holiday) • Red flags so you catch problems before they cost you money • Formulas from campaigns that actually drive revenue for brands doing $100K+/month Want it? • Comment "SUBJECT" • Follow me (so I can DM you)

• 
  WiseStamp (@WiseStamp) reported 9 minutes ago

  You control everything. You choose what to hand off. 𝟯 𝗿𝗲𝗮𝘀𝗼𝗻𝘀 𝗪𝗶𝘀𝗲𝗦𝘁𝗮𝗺𝗽'𝘀 𝗘𝗺𝗽𝗹𝗼𝘆𝗲𝗲 𝗛𝘂𝗯 𝘄𝗶𝗻𝘀 𝘄𝗶𝘁𝗵 𝗲𝗻𝘁𝗲𝗿𝗽𝗿𝗶𝘀𝗲 𝘁𝗲𝗮𝗺𝘀: 𝟭. 𝗕𝗲𝘁𝘁𝗲𝗿 𝗲𝗺𝗽𝗹𝗼𝘆𝗲𝗲 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲. Let them adjust the small stuff themselves. No waiting on you for every tweak. 𝟮. 𝗙𝗲𝘄𝗲𝗿 𝗜𝗧 𝗿𝗲𝗾𝘂𝗲𝘀𝘁𝘀. Every change they can't make is a ticket. Free up the right elements, IT stops drowning. 𝟯. 𝗣𝗹𝗮𝘁𝗳𝗼𝗿𝗺 𝗳𝗹𝗲𝘅𝗶𝗯𝗶𝗹𝗶𝘁𝘆. Mac Mail, Gmail, Outlook, Android, doesn't matter. They keep their workflow. You keep the brand. Full control. Less involvement. Not a trade off. What do you think? Should email signatures should be under total lock down, completely open for employees to make changes, or somewhere in between? Let us know in the comments.

• 
  90S KID (@epochster) reported 10 minutes ago

  @svpino Nothing like handing your Gmail and Stripe credentials to an MCP server and calling it automation.

• 
  Vic 🌮 (@VicVijayakumar) reported 11 minutes ago

  Coding used to be the bottleneck and isn’t anymore so now there is a lot of brain power being spent at companies to play bottleneck whackamole while tokens are cheap. Problem: code review Multiple levels of automatic code review of AI written code doesn’t really increase trust, and AI code review still lacks the context behind WHY. So there’s all this effort to document everything by adding MCPs to every context store: jira, confluence, gmail, slack, zoom calls, google docs, whatever. The goal is to get to the first approve/reject recommendation before a human even looks at it. Problem: human time Human time is precious, your teams are overloaded, everyone is busy, and has their own brain split between 15 things, so let's intelligently @ people directly in public channels. Round robin it between reviewers, add leaderboards, daily reminders, and some public shaming. But wait. Someone says- can we just…skip human review? Problem: defect escape Whether or not we got a review from a human (rubberstamp or meticulous), we still need to prevent defect escape. Auto merge approved code to main which deploys to staging. Force it to bake on staging for X hours. Run every test suite against it (nothing new). Have adversarial agents use headless browsers to try and break your stuff. Should probably fix things too? Problem: blast radius This one isn’t new either. If you’re going to yeet out code that no human has looked at, you should probably reduce your blast radius with progressive deployments. Squeeze out a little bit, have an agent watch your error logs and dashboards, set a confidence threshold for rollback vs perseverance. Problem: incident triage If something breaks at 3am, unconnected to an ongoing deployment, you shouldn’t have to wait for a human. Have an agent triage the issue and link to relevant dashboards before the human can roll out of bed to get to their laptop. Problem: conflicts Your PR queue is a traffic jam. Agents will need to be constantly rebasing, resolving conflicts, and regenerating changes as main moves underneath them. Problem: trust boundaries How much rope can we give our agents? Under what conditions can we let yhem act without asking permission? Whose agent is going to be the first to screw up and leak PII? Gotta wrap it up, my toddler is waking up. What did I miss?

• 
  ✿ 𝑷𝒐𝒐𝒕𝒊𝒆 ✿ 💫🍃🔮💨 (@Platapootie) reported 11 minutes ago

  @Angela_Blight **** I’m so sorry if you haven’t already turn off the WiFi to ur pc and change ur gmail and discord passwords if you can still get in with just ur email ): I’m so so sorry I feel terrible

• 
  Verdha | DTC Email Marketer (@cleaacreative) reported 20 minutes ago

  Most DTC brands send every campaign to their entire list. Then they wonder why open rates are dropping, unsubscribes are climbing, and Gmail is pushing them to promotions tab. Here’s the sending strategy I use for every brand I work with and it consistently keeps open rates above 50%. It’s called graduated sending. Here’s how it works: Step 1: Segment your list into three buckets. → 30-day engaged (opened or clicked in the last 30 days) → 60-day engaged (opened or clicked in the last 60 days) → 90-day engaged (opened or clicked in the last 90 days) Step 2: Send your campaign to the 30-day segment first. This is your warmest audience. They open. They click. Gmail sees strong engagement signals from the jump. Step 3: Wait 30-60 minutes. Check performance. If open rates are healthy (40%+), expand to your 60-day segment. Step 4: If still performing, expand to 90-day. What you’ve done is built a positive engagement signal before your email reaches colder contacts. Gmail saw hundreds of opens before a single unengaged subscriber got the email. This one shift protects your sender reputation, improves inbox placement, and gives you real performance data on every send. Most brands blast everyone at once and hope for the best. Hope is not a deliverability strategy. I set this up for every DTC brand I work with. If your campaigns are going to the full list every time, DM me this is the first thing I’d fix.

• 
  Tom Czerniawski (@BlackTomThePyr8) reported 20 minutes ago

  @sama4rtyu7 @ProtocolWidow Johnson did issue that call, but not sure if that gmail address is legit.

• 
  Dinuka (@desilvakdn) reported 23 minutes ago

  i'm bit late. but need to say this. you guys doing a great job. appreciate, but free hosting doesn't mean free emails. here's why. • most vps ips already have a bad reputation. before you even start, check it on spamhaus. there's a good chance someone else already used it for spam. • a lot of vps providers block port 25 by default. some will unblock it if you ask. some won't. • if you don't have a proper ptr record, gmail is going to be suspicious. some providers don't even let you configure one. • your ip isn't judged on its own. if other ips nearby are sending spam, that can hurt you too. • without google postmaster or snds, you're guessing. you might think everything is fine while your emails are quietly landing in spam. • you can't send 80k emails on a brand new ip. you have to build trust over time. if you go all in on day one, you've probably burned that ip. • you also have to deal with bounces and complaints yourself. keep sending to bad addresses and your reputation drops fast. my setup is pretty simple: • hostinger for inboxes, about $1/month • aws ses for sending. around $0.10 per 1,000 emails, so 80k emails costs about $8. ses takes a bit of work to set up. you need spf, dkim, dmarc, production access, and maybe a dedicated ip if you're sending a lot. but the hard part isn't the server. it's building and keeping a good sender reputation. self-hosting is great if you want full control of your inbox. sending large volumes of email is a completely different problem.

• 
  still mean 🍰 ไอริส (@ngong_z) reported 23 minutes ago

  @Matcha731136072 @aixstans if it's the general one, too many people are viewing it at the same time so need to wait it out. if it's the other playback error requiring login, just login on browser with your gmail then reload the page and it shall work.

• 
  Glenski 📷🇨🇦 (@glenegrant) reported 26 minutes ago

  MailMindz is live. I built it for one problem: email should tell you what matters before you waste time digging. It sorts your inbox by urgency, labels messages inside Gmail, flags what needs a reply, drafts in your voice, handles unsubscribe cleanup, and keeps the processing local. Gmail + SMTP - Windows + macOS. No market plan yet. No client attached. Just a real inbox problem turned into a working app. Boost your email intelligence.

• 
  Alex H (@alex_harl) reported 29 minutes ago

  @lydiahallie Improve the classifier. Mid work model switches lose in context knowledge, rely on perfect commits to not lose state, it’s tiresome having to keep mds of Fable hazards per repo (which part of codebase or tasks are not for Fable), handing off to Opus adds translation and reduces accuracy, compacts to return Fable are lossy. Classifier needs to infer from session context - long horizon potentially destructive actions are allowed for days then Fable switched on some keyword or even commits for work done by Opus*. Usage stats to show entire session not since last restart, nice to have would be /usage like codex - lifetime tokens, streaks. Don't enable by default all/never used MCPs in new CC sessions, not turn off all claude-ai MCPs but having to manually turn off individual ones like Gmail. Ability to send feedback without handing over the session - How is Claude doing do you want to share a session y/n freeform feedback no session grab. The new in-app permissions prompts are welcome and supersede a ~year of manual fudging to achieve the same, does this clone the repos to CC web, and can it be applied to older instances? We had /remote and that cloned, since last week permission prompts are in app but only new sessions. What is intended for older ones? Statusline to display what we are working on in already available text area but without us needing hooks + notes per session, you already have a recap which doesn't quite fit more work oriented (or as CC puts it a living work-coherence model). Ultraplan to not handoff to cloud repos that are not workable there, anything with secrets or session inheritance or specific permissions to systems not accessible from cloud. Native channels / messages between instances, not durable like custom MCPs (example agent mail). Cursor on Windows rendering is terrible if moved between different size screens, the entire session other than last page gets mangled as narrow text but codexes don't - sessions render properly. I don't use Cursor on Mac or move it about to test. *3 days Fable run to analyse my Databricks, ADO repos, my Az session inheritance, Databricks CLI, all pipelines, notebooks, jobs, warming up clusters and querying data - objectively a vast blast radius but that is my call. Classifier fires because some baby data engineer left a secret in a notebook 😭. How is that balanced? Equally ability to analyse own codebases for security should be a job for Fable.

• 
  Prajwal Tomar (@PrajwalTomar_) reported 31 minutes ago

  I built this in a single day. Gmail inbox triage. Auto-tagged leads. Kanban pipeline. Synced to a Google Sheets lead tracker. Two years ago agencies would have quoted 2 months and $15K for this. Lovable is not a UI builder anymore. You can build literally ANYTHING inside it. I've used it almost daily for over a year. Shipped 50+ MVPs with it. For clients. For myself. For the agency. I finally wrote down the whole system. Full breakdown in the article below.

• 
  Greg Cangialosi (@gregcangialosi) reported 35 minutes ago

  Bloated inboxes create anxiety for many folks. I know some people are type A with inbox zero, and others like myself just think of gmail as a big searchable database that can recall anything with search or labels. That said, I’m really grateful to have saved the amount of email I still have across all my various accounts. Especially the “I may need or want this one day” emails that I just left in the inbox. That day has arrived several times, and now I just launch my agent to pull any and all context on any subject from emails, attachments and drive files, and I get data and info that I’d otherwise hunt down in many different places, or never at all. Email alpha has finally arrived for those of us that appear to be email hoarders :-)

• 
  GROYP=3R (@EQUALS3GROYPER) reported 38 minutes ago

  @TobyTurner if youre actually having trouble registering ive found that they dont like non standard email domains. if u have a gmail account try using that

• 
  peetzweg/ (@peetzweg) reported 38 minutes ago

  @heyandras I assume it’s the receiving mail server classifying it as spam? Maybe even the client? Would be viable to use to send mails to yourself if you unmark it as spam. Horrible using Gmail programmatically as it requires reauth every week.

• 
  vlad jerkov (@vjerkov) reported 40 minutes ago

  @rahuprincess Use AI to pull down old emails and archive them yourself. I did this with my own mail servers. It can directly talk to gmail, should be easier.

• 
  Jordan Rey (@JordanRey98) reported 43 minutes ago

  @openshipio @liamgadams You guys are simply liars. I can bet $10000 right now that more than half of your emails went to spam, and 100% of them when sending to gmail and outlook went to spam. You try talking to people that have issues with emails, but they all know about the White listing mafia.

• 
  Just the Gems🔜PAX West (@_justthegems) reported 43 minutes ago

  @MGdoren @gmail I thought so too, but I get the same messages daily, so something must be broken

• 
  DWE Post (@dwepost) reported 43 minutes ago

  Dear Google Team, I can’t access my Gmail account. I forgot my password, and the standard recovery options are not working for me. This is my primary account. Please help me recover it as soon as possible. Thank you. @googlechrome @chromeunboxed @googleaccount help me please. ??

• 
  The Mayor (@MayorOfEpcot) reported 46 minutes ago

  @ChatGPTapp @OpenAI I keep getting "The Gmail tool has been disabled." Is this a known issue or is it just me?

• 
  . (@tsksssssss) reported 50 minutes ago

  @gmail can you guys shut down for like a week or two so I don’t have to work?

• 
  Nithin. (@Nithin_chandra_) reported 50 minutes ago

  Congratulations @Migma_AI 🥳 This is a real game changer Most email tools still break in the inbox. Migma with Zinn actually solves it — perfect rendering in Gmail, Apple Mail, dark mode, and even Outlook 2003. No more painful testing and broken emails.

• 
  𝔽𝔼ℝℤ (♞,♞) (@ferz_erz00) reported 51 minutes ago

  you might not have noticed this, but, every blockchain app today makes a silent choice that most developers don't think about until it's too late; and it's, you pick a chain, you deploy your contracts, you build your community, and in doing so, you've decided that every user on every other chain doesn't get to use what you built. that's not a technical limitation, it's just how the ecosystem is currently structured, and everyone has accepted it as normal. @PushChain is built on the premise that it doesn't have to be that way. it's a Layer 1 where developers deploy once and immediately become compatible with every supported chain; Ethereum, Solana, BNB Chain, Base, Arbitrum, and more. a user on Solana and a user on Ethereum can interact with the same app, the same smart contract, the same state, without either of them bridging or switching chains. the app never needs to know or care what chain the user came from. the three primitives that make this work are any-chain transactions, wallet abstraction, and universal fee abstraction. any-chain transactions means the routing between chains is handled at the protocol level, not the application level. wallet abstraction means users can connect with MetaMask, Phantom, Coinbase Wallet, or even a Gmail account, no new wallet, no seed phrase. fee abstraction means the "you need ETH for gas" problem is gone; users pay in whatever token they already hold on whatever chain they're already on. the practical implication is that the addressable user base for any app built on Push Chain isn't one chain's community. it's every wallet across every supported chain simultaneously. that's not a marketing claim, it's what the architecture actually enables. built an interactive product experience with a live universal app simulator showing exactly how a user from any chain onboards to a Push Chain app, without bridging, without friction. powered by @goldrushdev .

• 
  Wwrd.app: What Would Robinhood Do? (@STACCoverflow) reported 52 minutes ago

  The rate at which nefarious login attempts on my devices and accounts have been occurring has been skyrocketing Someone in Philadelphia just tried logging my Gmail Sigh

• 
  Iremide Vado (@IremideVado) reported 53 minutes ago

  yeah, I just noticed some unusual stuff Google is doing. When you login your Gmail on someone else’s phone, they just automatically link the person phone number to your Gmail account without the person even verifying their phone number or try linking their phone number on your Gmail account……That’s BS Check your Gmail account and check if Google didn’t link someone else’s phone number to your Gmail account.

• 
  TrueAI | Trading Co-pilot (@truetradingai) reported 55 minutes ago

  Update Notice: Phantom is incorrectly flagging our app due to high traffic. We are working on a fix 🔧 Swaps via True-related wallets (Email, Gmail, Telegram, X, Apple) are working fine. If Phantom shows a warning, please tap "Proceed anyway (unsafe)", it is a false error.b

• 
  iamkenny (@iamkenny5084) reported 55 minutes ago

  @Caleb_dharmie Have you reach out to their customer support. The only time I experienced this is when I changed old email on the account to a new and I was trying to login (with Google ) the next day with the old Gmail

• 
  enes (@eneszyyl) reported 59 minutes ago

  @TeamYouTube My previous phone was completely destroyed. Even though I successfully enter the 2FA SMS code, Google says "Could not verify that you own this account". The system is totally broken since May 1st. Please help me recover my Gmail and channel (@enes3292).