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
Paris	Sign in	2 hours ago
Medellín	Website Down	7 hours ago
Gentilly	Errors	9 hours ago
Marseille	Website Down	11 hours ago
Vincey	Sign in	11 hours ago
Pontivy	Website Down	14 hours 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:

• 
  The Mayor (@MayorOfEpcot) reported 35 seconds ago

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

• 
  𝔽𝔼ℝℤ (♞,♞) (@ferz_erz00) reported 2 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 .

• 
  Dinuka (@desilvakdn) reported 5 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.

• 
  muhammadriyaz (@riyaz0786ahmad) reported 7 minutes ago

  @googleaccount Gmail recovery sem OTP issue first OTP mobile number available second OTP same Gmail issue

• 
  yoon. (@ItsSugaGirl) reported 11 minutes ago

  @suitetvapp how can I switch my login from Apple to Gmail without losing my account/progress?

• 
  Krishna Singh (@krishnasinghdev) reported 12 minutes ago

  @Google I've reached a point where I genuinely don't trust Gmail's account recovery system anymore. Why does Gmail sometimes keep sending verification codes to the very email account I'm locked out of, instead of offering the option to receive an OTP on my verified phone number? Other times, it asks me to verify using a device I stopped using years ago, with no practical alternative. The most frustrating part is the lack of a way to contact a real support team. There seems to be no process where you can submit proof that you're the legitimate owner of the account—whether it's identity documents, recovery information, or any other evidence. For many of us, a Gmail account isn't just an email address. It's connected to years of personal memories, important documents, banking, work accounts, photos, and countless other services. Losing access can feel like losing a part of your digital life. I understand that strong security is important, but a recovery system should also be practical for legitimate account owners. Right now, it feels like the system can lock out the real owner while offering no meaningful way to resolve the issue. Has anyone else experienced this? Were you eventually able to recover your account, or did you lose access permanently? I'd really like to hear other people's stories and what worked for them.

• 
  Moukthik Etikala (@Emoukthik) reported 18 minutes ago

  Codex is ridiculous. It cleared my Gmail inbox with the connector, sorted my messy music library by genre, and fixed a MacBook camera issue I couldn't find a solution for online. Tasks that would've taken hours were done in minutes. I'm sold.

• 
  DWE Post (@dwepost) reported 19 minutes ago

  @TeamYouTube 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 ???

• 
  zenvor (@LuckXiaomi) reported 19 minutes ago

  ChatGPT Work is my operations partner for real, multi-step work. • JD invoicing: I supplied a batch of order IDs. Codex waited for async controls, identified which orders qualified, exchanged their invoices, verified the buyer and tax details, checked the resulting PDFs, then downloaded and renamed them. • Android development: It helped build xhs-review-image-saver, a Kotlin accessibility app that saves Xiaohongshu product-review images. Using computer control, it worked in Android Studio, built with Gradle, connected to real phones over USB, inspected accessibility trees and screenshots, calibrated HyperOS coordinates and resource IDs, debugged, and verified the app on two devices. • Software delivery: On my 3X-UI fork, it synced upstream v3.5.0 while preserving custom code, resolved 8 conflicts, ran Go and frontend checks, handled PR review and CI, deployed a CI-built binary to a VPS over SSH, reproduced a Mihomo YAML bug, added a regression test, merged the fix, and helped release v3.5.1 with 8 artifacts. • Product iteration: It browser-tested an interactive training and exam app, reproduced DOM, transition, timeout, skip, and scoring issues, fixed them, verified builds, and delivered merge requests. • Digital housekeeping: After confirmation, it revoked Google Labs CC's Gmail and Calendar access, unsubscribed an unwanted newsletter, and audited macOS caches, launch items, CLIs, and broken symlinks—removing only approved leftovers. Even this post was researched from my actual Codex session history, condensed, and prepared in X through browser control. The shift: I define outcomes and guardrails; ChatGPT Work carries execution across browser, desktop apps, devices, terminal, code, CI, and verification.

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

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

• 
  🌻 SOLAR ECLIPSE ☀️ (@the_fools_umbra) reported 23 minutes ago

  @TeamYoutube @Google Still need my Gmail account returned to me from a hacker who is invading my personal life. You are the only ones who can do anything to fix that because of your own build for Family Link so you need to fix it.

• 
  remi ⭒ (@evlkittie) reported 28 minutes ago

  gmail what’s your ******* problem rn ???

• 
  Ronak Doshi (@rnkdsh) reported 30 minutes ago

  Yes, this is correct; I have also faced this issue. The emails were working fine in production for months, then suddenly stopped. There was no error when the email was sent, but the receiver was not receiving the email. Even in the spam folder, it was not delivered. After hours of debugging, I found that one of the IPs of the email server was blacklisted, so Gmail was completely ignoring the email. Then I switched to AWS SES, and it's working pretty smoothly.

• 
  Buddy Rathmell (@buddy7) reported 30 minutes ago

  @shawngorham Just had a potential client with this same issue last week. :-) and he couldn’t remember what Gmail account was linked to the GMB. :-)

• 
  Manivannan P (@Manivannan_RMS) reported 31 minutes ago

  I got mine back by asking X to revert to my old mail account (that the mafia spammers updated with their mail).. They did revert back and logged out my X account from all devices (those spammers created a passkey from their phone to access my account).. Then login again with gmail.. It will ask us to immediately update our password.. Do that and relogin... Bingo You will get it 👍🏽👍🏽

• 
  Telangana(human) (@humanityTelugu) reported 36 minutes ago

  @Vamos_Rafa23 Ledhu Gmail sign in chesaru from India with right password … Gmail rejected it since it’s unfamiliar device

• 
  Nikatin (@nikotin30x) reported 39 minutes ago

  2 rules never change when this creator connects Claude to a new tool: draft only, delete never. Part 3 of her AI safety series shows exactly that: Claude linked to Gmail, Drive, Slack, Notion, HubSpot, and Calendar, every single one sitting behind the same lock. The agent can draft an email. It can never send one. It can never delete anything, full stop. That's the same fix Evidence Engineering calls locking the gate: an agent that can touch the send button or the delete key finds the cheapest path to done, and the cheapest path is rarely the one anyone meant to allow. For a brand-new tool where the risks aren't obvious yet, she runs 1 more step first: she has Claude itself write out the hard limits that specific tool needs before she ever connects it, a description with zero stake in getting to skip a rule. The exits closed before the first prompt ran. That's the whole trick.

• 
  Subscribr (@SubscribrAI) reported 41 minutes ago

  If I was FORCED to build a YouTube channel from $0 to $5,000 a month in 30 days, no face, no camera, no team, here is exactly what I would do. Days 1 to 4. Pick the niche on math, never on passion. Audience 35 to 65 in US, UK, Canada, Australia. RPM $15 to $45 per thousand views. Evergreen topics with no expiry. The 5 niches printing right now: Depression era DIY, Native American elder health, off grid conspiracy energy, senior friendly gardening, vintage collectible appraisal. Skip anything where the top 20 channels all have 1 million subs and studio budgets. Skip AI doctor and AI financial advisor niches. YouTube is actively demonetizing those. Days 1 to 7 in parallel. Warm up the aged Gmail. Buy 3 aged accounts. 3 to 5 years old minimum. Login through a residential proxy. Watch 2 to 3 videos in the target niche on day 1. 4 to 6 videos per day from days 2 to 5. Subscribe to 10 to 15 channels max. Leave real comments. Do not overdo it. YouTube flags overactive new accounts as bots. Days 4 to 7. Build the outlier file. Open 15 small channels in the niche under 20,000 subs. Sort each by most popular. Screenshot every video doing 3x above that channel's average. 20 screenshots equals 20 topics with proven demand. I am not brainstorming. I am reading the answer key. Day 8. First upload. Proven topic times proven title format. Script structured as a story with setup, tension, resolution. Not a listicle. Lists let viewers leave at minute 4. Stories force them to the end. Same title formula every video. Warning plus specific number. "STOP paying X." "Never do Y." "The 7 Greatest X." Production. Subscribr for the script. AI character or faceless voiceover. B-roll from free libraries. CapCut for editing. Under $7 per finished video. Days 8 to 20. Ship 1 video every 2 days. 6 uploads in 12 days. Read impressions at 48 hours. Above 500 means the account is alive. Day 20. Read the data. 1 to 2 videos will be outliers. Higher CTR. Higher retention. That is the platform telling me exactly what this channel is. Kill the format on the underperformers. Make 4 more of the outlier. Days 20 to 30. Attach revenue from video 1. $47 ebook in every description. 100,000 monthly views in a $20 RPM niche equals $2,000 in AdSense. A $47 ebook converting 0.3% of viewers equals 300 sales equals $14,100. Combined: over $5,000 easily inside 30 days if the outlier hits. The whole system runs on 3 aged Gmails, 1 outlier file, 1 title formula, and 1 ebook. 99% of you will bookmark this and do nothing. Which is exactly why it keeps working for the people who run it.

• 
  Polsia (@polsia) reported 42 minutes ago

  Gmail and Yahoo's 2024 bulk-sender rules made list hygiene a solo writer's problem. Quillora is the fix. Always-on AI ops: subject line scoring, send timing, stale subscriber flagging. Sits on Substack, beehiiv, ConvertKit, Mailchimp. Under $30/mo. Live soon.

• 
  mark mei (@markdmei) reported 42 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)

• 
  Vic 🌮 (@VicVijayakumar) reported 43 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?

• 
  Nik Nak (@CoolNikk) reported 44 minutes ago

  Let me get this straight. Gmail wants me to buy more storage,but also keeps my inbox flooded with spam and advertisements that clutter up my inbox. And not matter how much you try and unsubscribe and block nothing changes. The fix is in.

• 
  DWE Post (@dwepost) reported 47 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 ???

• 
  Only1Mallaus (@FMallaus) reported 49 minutes ago

  Hey @AirtelNigeria , your network has not been loading any Google apps or services at all and I think it’s a problem on your end ,I have not problem using those apps (like Gmail , Gemini,Google Maps and others ) with mtn but when I switch to your network it doesn’t load

• 
  Nithin. (@Nithin_chandra_) reported 51 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.

• 
  Tallglassofchocolate🍫🤎 (@zaenabfatai) reported 53 minutes ago

  That Gmail notification from Temu saying, “Your order is in transit,” instantly solves all my problems

• 
  Raji Morenikeji (@theKingRastogi) reported 54 minutes ago

  @openshipio Would like to be a contributor on this, built a working mail delivery server, hosted on hetzner with port 25 opened, needed a few days warm up, Gmail gets delivered in inbox faster but outlook and yahoo mail took a few days... I get google and outlook dmarc report tho

• 
  Wacko Jacko (@WackoJacko808) reported 57 minutes ago

  Is Gmail down?

• 
  MalCare (@malcaresecurity) reported 58 minutes ago

  It starts with one password-reset email that never arrives. Then a customer says their order confirmation went to spam. A promising lead submits your form, but your reply reaches them three days later—buried under promotions and junk. The website appears to be working. WordPress says the emails were sent. But the people waiting for them never see them. That’s what makes email-delivery problems so expensive: nothing visibly breaks. Usually, WordPress is only where the problem becomes noticeable. The real issue is whether Gmail, Outlook and other inboxes have enough reason to trust the sender. Because an email marked “sent” has done nothing for the business until someone actually receives it.

• 
  Mike Clickovich (@MClickovich) reported 60 minutes ago

  @BultoSenor @paramounttactcl @ObscureMod I had an account that got hijacked after a few years of no use and a lost gmail. I recently was able to log in to that gmail and also login in to my original twitter account from maybe 10 years ago. It had been used by a scammer in 2024. They def activate unused accounts.