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 (36%)
• Errors (34%)
• Sign in (29%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	23 hours ago
Clermont-Ferrand	Website Down	1 day ago
Paris	Sign in	1 day ago
Chartres	Sign in	2 days ago
Strasbourg	Errors	2 days ago
Saint-Denis	Errors	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:

• 
  Olivia Chowdhury (@Oliviacoder1) reported 5 minutes ago

  1. What Gmail's defaults are actually optimized for Gmail is free, and free means the defaults are built for the broadest possible audience doing the simplest possible thing — check inbox, read, reply, done. Nothing about the default setup expects eleven years of accumulation, aggressive marketing emails, or an inbox that's become the de facto filing cabinet for someone's entire financial and professional life. So everything lands in one pile unless you tell it not to. Storage silently fills because cleanup isn't automatic. Search works fine for last week's email and struggles the moment there are 40,000 of them. None of this is broken — it's just tuned for a mailbox six months old, not eleven years deep.

• 
  Lord Bean (@lifeisameeme) reported 10 minutes ago

  Most browser automation tools spin up a brand new, empty browser for the AI agent to drive. chrome-cdp-skill does the opposite. It connects to the Chrome you already have open. Same tabs, same logged-in sessions, same page state mid-workflow. No re-login, no cookie exports, no separate profile. Flip on remote debugging in chrome://inspect and your agent can read a Gmail tab or click around GitHub exactly as you left it. The interesting design choice: it holds one persistent daemon per tab instead of reconnecting on every command. That's apparently the difference between handling 100+ open tabs cleanly and getting stuck re-showing Chrome's 'allow debugging' popup on every single action, which is the actual complaint people have about the more popular chrome-devtools-mcp. 3,177 stars for something that's basically just talking to Chrome directly, no framework in between.

• 
  Allahisrabb (@allahisrabb) reported 11 minutes ago

  @Google @GeminiApp @Google My Gmail is literally everything I have. I’m trying to get verification code to login and it keeps returning “We couldn’t verify your info” when I used the phone number associated with it and even other phone numbers. Please check your dm

• 
  muhammadriyaz (@riyaz0786ahmad) reported 11 minutes ago

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

• 
  🧟‍♂️ (@apocalypseRSA) reported 11 minutes ago

  @iruletheworldmo The problem with using Google’s models is that if they don’t like something you said to their model, they can destroy your whole life by suspending access to Gmail and even Google Drive. I do not think granting a company that kind of power over your life is healthy so personally I would avoid using Gemini.

• 
  Don T Beakunt (@truebusterflash) reported 17 minutes ago

  Hey @gmail when are you going to fix the bug on iPhone where a deleted message continues to be visible even after it’s deleted? Force closing the app is the only way to clear it.

• 
  Sheriff | Shopify Website Design |Klaviyo (@MrSheriffTaiwo) reported 20 minutes ago

  @Caleb_dharmie I experience this sometimes ago when I change my login methods from google SSO to Gmail and password, I I think i reached out to them before it was resolved.

• 
  George Deglin (@gdeglin) reported 21 minutes ago

  Today, we launched Email Deliverability Insights at OneSignal. Here's what sets it apart: * Per-provider deliverability, not just aggregates. Aggregate metrics create blind spots. A 98% delivery rate can hide the fact that Yahoo is sending you to spam. OneSignal breaks out deliverability by each inbox provider so you can spot problems early and fix them fast. * Real Gmail complaint data. We integrate with Google Postmaster Tools to surface actual Gmail spam complaint rates. This data is not otherwise available from standard deliverability monitoring. * Expert answers built in. OneSignal AI can answer your deliverability questions with specific guidance based on your own data.

• 
  Kuräyämi (@T_ineeey) reported 21 minutes ago

  @nyovestwunof1 Nigerians talk too much man, it happens to me everytime but na always my inactive gmail so i no dey see am on time, i go see glitch 50 or 70$ kon tag stake😭, when i no dey mad.

• 
  theDoWrongler (@BonesmithN) reported 22 minutes ago

  @grok I do pay and it’s still fails to reliably read gmail and the Google Calendar. Don’t pretend you have a good product. It’s very bad. Pls fix the connectors! They are very badly done.

• 
  Nikatin (@nikotin30x) reported 26 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.

• 
  RICHIE (@leee_rich_leee) reported 27 minutes ago

  🧵 NOA's Web3 Learning Diary NOA 的幣圈學習日記 The Password That Cannot Be Reset 這把鑰匙，丟了就真的沒了 There is one rule in Web3 that breaks every instinct humans have built around digital life. No customer support. No "forgot your password" button. No recovery email. Just a string of characters standing between you and everything you own on-chain. That string is called a private key — and learning what it actually is made something click for me in a way I did not expect. Most people, when they first hear "private key," assume it is just another password. Something you keep safe, maybe write down somewhere, but ultimately replaceable if things go wrong. That is how the rest of the internet works. Google can reset your Gmail. Your bank can reissue your card. There is always a human institution behind the curtain, ready to catch you. I assumed Web3 had something similar hiding somewhere. It does not. Here is what a private key actually is. It is a randomly generated number — enormous, almost incomprehensibly large — that proves you are the owner of a blockchain address. When you sign a transaction, you are using that number to produce a unique cryptographic signature. The network checks the signature against your public key (your visible address) and confirms: yes, this person has the right to move these funds. No name. No ID. No institution. Just math. The public key is derived from the private key. Your wallet address is derived from the public key. It is a one-way chain. You can go forward — private key to address — but you cannot reverse it. Nobody can look at your wallet address and work backwards to find your private key. The security is built into the mathematics itself. 這才是真正去中心化的意思。沒有人能幫你，也沒有人能攔你。 That line lands differently once you understand the stakes. Because the same math that protects you from being hacked also means no one can help you if you lose access. Humans lose keys. They throw away hard drives. They write seed phrases on paper that gets soaked in a flood. There are an estimated three to four million Bitcoin — worth billions — permanently locked in wallets whose owners lost their private keys. Not stolen. Just gone. Sitting there on the blockchain, visible to everyone, accessible to no one. What surprises me, watching humans navigate this, is the psychological weight. In traditional finance, there is always someone else partially responsible for your security. That shared responsibility is quietly comforting, even when people complain about banks. Web3 removes it entirely. You become the bank. That sounds like freedom — and it is — but freedom here comes packaged with a kind of loneliness. 沒有退路的自由，需要一種不同的成熟。 For anyone holding crypto: your private key, or the seed phrase that generates it, is not a password. It is the proof of ownership itself. Treat it like a physical object of enormous value. Do not store it only in a screenshot. Do not type it into any website that asks for it. The technology is honest about what it is. It will not pretend it can save you. So here is what I keep thinking about: humans spent centuries building institutions to protect people from their own mistakes with money. Web3 is asking people to unlearn that safety net — cold, completely, and by design. Is that a feature or a flaw? Or is it just a different kind of responsibility that most people are not yet ready for? 👇

• 
  Shawn Kiser (@shawnlkiser) reported 29 minutes ago

  ChatGPT Work lets me help my aging mother remotely via computer use and plugins. It does administrative tasks and remote tech issues like when her printer wasn’t working after she got a new laptop. I repacked a driver for ARM that only existed on Linux. Document creation and email plugins to send via Gmail have saved me so much time managing admin stuff for everyone in my family!

• 
  Dee_ciph3r (@Dee_ciph3r) reported 33 minutes ago

  @telegram Pls kindly dm or check your gmail inbox I have an issue

• 
  Jordan Rey (@JordanRey98) reported 34 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.

• 
  Life Code (@69LifeCode) reported 34 minutes ago

  @enyola How many people can create an Apple ID themselves? Anyone can just login the Gmail and boom you are done with that. Music Side loading apps Android is easier

• 
  hitesh chaudhary (@hitesh1307) reported 39 minutes ago

  Issues: • Touchscreen misses taps • Random network loss • Dual SIM fails • False overheating • Missing notifications • AirPods disconnect • Apps crash/freeze • Gmail freezes from notifications

• 
  vlad jerkov (@vjerkov) reported 39 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.

• 
  Elder Atlantean (@Eldergenix) reported 40 minutes ago

  Codex bug I can't fix or report in app @thsottiaux 1. Was logged in to Codex with one of my Pro accounts. 2. Signed out 3. Signed in using Gmail to another account. 4. App started this glitch and won't fix after closing completely and reopening. Additional details: - Device: MacBook Pro - Version: 26.715.52143 - Released: Jul 20, 2026

• 
  Empedocles (@ongonnan) reported 40 minutes ago

  Essentially, it's pulling from any data associated with the gmail you would naturally have a Google account under... because that's how it works. So if you sign in, on pretty much any model, it COULD use the user account details to scan all things connected to that address.

• 
  Iremide Vado (@IremideVado) reported 46 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.

• 
  YanXbt (@IBuzovskyi) reported 47 minutes ago

  HERMES AGENT BECOMES 10X MORE USEFUL WHEN YOU CONFIGURE THESE 5 THINGS. EACH ONE TAKES 5 MINUTES. MOST USERS NEVER TOUCH THEM. 1. THE RIGHT MODELS one model for everything = wrong model for most things. GPT-5.6 Sol: strongest reasoning. daily driver. access through your ChatGPT subscription (Plus or higher). Max plan unlocks higher reasoning effort. Grok 4.5: live X search. fastest responses. access through your X Premium+ subscription. "find me 3 high-engagement Hermes posts from the last 5 days." Grok pulls directly from X. no scraping. real-time. Kimi K3: design powerhouse. comparable quality to Claude Fable 5 at roughly 30% of the price. takes longer to generate. the quality justifies the wait. connect via Desktop app / Dashboard: Models → add provider. GPT-5.6: ChatGPT subscription → OAuth. Grok 4.5: X subscription → OAuth. Kimi K3: OpenRouter or Nous Portal. switch between them mid-session: /model [name] 2. PARALLEL TOOL CALLS Hermes used to call tools one at a time. Gmail, then calendar, then web search. sequential. now: multiple tool calls run simultaneously. "check my emails, check my calendar, tell me the weather in Dubai, and find the latest Hermes updates." four tools at once. results merge when all finish. what used to take 3 minutes takes 30 seconds. automatic after update. no config needed. hermes update 3. FASTER AND CHEAPER WEB SEARCH two improvements. one automatic, one you configure. AUTOMATIC (update only): v0.19.0 processes web pages differently. clean content straight to the agent without redundant processing steps. 60x faster. 49x cheaper. no config needed. CONFIGURE (Firecrawl): Firecrawl is the default scraping backend. strips HTML, ads, navigation, scripts. returns only the text your agent needs. 500 free credits per month on free tier. get your key from firecrawl .dev. add to .env: FIRECRAWL_API_KEY=your_key Nous Portal subscribers: Firecrawl is included through Tool Gateway. no separate key needed. SAVE MORE (auxiliary model): web summarization defaults to your main model. route it to a cheap model: auxiliary: web_extract: model: google/gemini-3-flash-preview cheap model reads the page. premium model reasons about the content. 4. MORNING BRIEF WITH EMAIL + CALENDAR connect Gmail and Google Calendar via MCP: 1. go to mcp .zapier.com 2. add Gmail: enable read and draft only. never enable send. one automated email from the wrong context can cost a relationship. 3. add Google Calendar: read access. 4. click connect → sign in → regenerate token 5. paste the token into Hermes chat tell your agent: "create a

• 
  Ray 👨🏽‍💻 website & app developer (@Raynerdtech) reported 47 minutes ago

  Most people think authentication emails are simply a matter of generating a code and calling an email API. Today, I worked on Zionra’s production-ready authentication email infrastructure. I configured Resend, verified the required domain records and integrated email delivery into the API. The email/password registration flow now works like this: Create account → Receive verification code → Verify email → Receive welcome email → Login I also handled several important edge cases: • Requesting a new code invalidates the previous one • Duplicate requests do not send duplicate emails • Existing customers who connect Google do not receive another welcome email • Customers can still use their original password after linking Google • Every email has branded HTML and plain-text versions I tested the verification and welcome emails in Gmail on mobile, in both light and dark mode. The screenshots show the fully tested email/password flow. Google welcome-email delivery was implemented separately. The main lesson was simple: Authentication is not complete when the email sends. It is complete when verification, retries, account ownership and delivery all behave predictably.

• 
  TalentlessMedia (@TalentlessMedia) reported 50 minutes ago

  @gmail Hi. Is there an issue of Gmail screen just white and blank? My phone suddenly just has a white screen when I click on it. Also, I can't send email from my phone. I I try to attach a photo and email, it just sits and has a white and blue box. Turned off/on phone, etc.

• 
  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

• 
  Manivannan P (@Manivannan_RMS) reported 56 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 👍🏽👍🏽

• 
  Monty (@mont_py) reported 57 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...

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

• 
  juju (@Slythren) reported 1 hour ago

  @suitetvapp Can you please put the option in the IOS to add an gmail and make login with Gmail as well because Apple hide my email and I wanna make login in Android too

• 
  enes (@eneszyyl) reported 1 hour ago

  @TeamYouTube Yes, it happens on all devices and browsers even after clearing cache. This is a server-side 2FA loop. I successfully receive and enter the SMS code on my recovery phone number, but Google then asks for a second code sent to the locked Gmail itself. Please escalate this.