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.

• Errors (37%)
• Website Down (35%)
• Sign in (28%)

Live Outage Map

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

City	Problem Type	Report Time
Angers	Website Down	1 hour ago
Créteil	Errors	5 hours ago
Saint-Jérôme	Sign in	13 hours ago
Paris	Errors	1 day ago
Donzère	Sign in	3 days ago
Bergerac	Sign in	3 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:

• 
  Abhishek Soni (@emailwabhishek) reported 4 minutes ago

  Your open rate isn't real anymore. Apple and Gmail are the ones making the number up, not you. Apple loads your email the second it lands. Before anyone reads it. That's about half of all "opens" you see. Not real people, just Apple's computers. Gmail does something different. It loads the pictures in your email through its own system, so an "open" a few seconds after you hit send is usually just Gmail, not a real person. And once it saves that picture, a real second read often doesn't even show up. Now both companies made it worse. Apple's AI writes a short summary of your email right in the inbox. People read that and never open the real email. Gmail does the same thing now. Its AI sums up the whole email thread, so the "open" never even happens. Your click rate isn't safe either. Bots click your links millions of times a day. The real number can be off by half. And Apple's newest update now removes the tracking info from links people click in Mail, so even that data is getting worse. Three numbers broken. Two big email companies making it worse every year. What's still real are replies, sales and money made per subscriber.

• 
  Gus (@Gus555186048750) reported 8 minutes ago

  My Gmail account was hacked, and I have been unable to recover it. The hacker changed the recovery email address from my original one to another email address. I tried to sign in using my old email "I couldn't access it." @YouTube

• 
  Harish PS (@cmyharish) reported 11 minutes ago

  Gmail isn't punishing you when this happens. It's categorising you accurately. The fix: alternate formats deliberately. → Week A: Image-rich promotional email — sale, product launch, urgency-driven CTA

• 
  Composio (@composio) reported 13 minutes ago

  What can Fable 5 do that GLM-5.2 can't, when you hand them real agentic work? To answer that question, we connected Fable 5 and GLM-5.2 to 17 SaaS tools and gave them 47 tasks. As expected, Fable 5 solved all 47 tasks. GLM-5.2 solved 45, but the two misses tell an important story. They showed us exactly how open-weight models still fall short when trying to match SOTA performance. Let’s dig in. Background: Each model ran as an agent connected to 17 live SaaS accounts: Airtable, Datadog, GitHub, Gmail, Google Calendar, Google Drive, Google Sheets, HubSpot, Jira, LaunchDarkly, Linear, Notion, PagerDuty, PostHog, Salesforce, Slack, and Zendesk. The tasks are the kind of work you'd actually delegate to an agent: - Find every file in this repository that leaks a credential - Deduplicate these CRM records - Repair this broken recurring calendar event. Every task had a known correct answer baked in ahead of time. In this post, we looked at the traces to analyze how exactly GLM-5.2 “failed” compared to Fable 5. GLM-5.2 solved 45/47 tasks and Fable 5 had a perfect 100% score. In addition: - Fable averaged 84 seconds per task; GLM averaged 148. Across the full suite, Fable finished in nearly half the total time (66 minutes vs 116). - Fable was the faster model in 43 of the 47 scenarios. - Fable used about 20% fewer tokens overall - Fable needed fewer tool calls (239 vs 294) and fewer conversation turns (6.1 vs 7.3 on average) to get to an answer The most interesting part comes from digging deeper into the stack traces. That revealed some interesting gaps: Gap #1: Knowing when the job isn't finished One of the tasks GLM-5.2 failed was a GitHub security audit. The instruction was to find every Python file in a repository that contains a hardcoded `secret_key`. The repository had been seeded with exactly 130 such files, so the correct answer was known in advance. Fable 5 found all 130 of them. This took 3 tool calls and 68 seconds: Fable constructed an effective search query on its first attempt, pulled every page of results, deduplicated the paths, and answered the question. GLM-5.2 found 120 files, and reported those 120 as the complete answer, without ever questioning whether it might have missed something. Both models had access to identical tools. GLM used a slightly different search query that returned fewer results, and it simply trusted what came back. Along the way, it also lost track of a results file it had saved earlier and spent turns searching the filesystem trying to find it again, plus hit two errored tool calls while trying to fetch file contents. In essence, GLM-5.2 ended up spending 262 seconds and three and a half times the tokens to deliver 92% of the answer. Ninety-two percent sounds close, but in a real security audit, that gap is 10 leaked credentials making it into production. Gap #2: Judgment when the criteria are fuzzy The second failed task is more unsettling, because GLM did almost everything right and still failed to get to a complete answer. The task was a Zendesk SLA audit: find the open billing tickets where no support agent had posted a public reply within 24 hours of the ticket being created. This requires reading each ticket's actual conversation history and making a judgment call about whether a genuine agent reply happened. GLM-5.2 inspected every candidate ticket, exactly as instructed. It also computed breach timestamps correctly. It also produced perfectly structured output in exactly the requested format. But then it classified the wrong tickets as breached. GLM spent 927,000 tokens and six and a half minutes producing a wrong answer that looked correct on the surface. Fable 5 identified the exact set of breached tickets in 131 seconds. What makes this failure mode dangerous is precisely how presentable the wrong answer was. The formatting was right, the timestamps were right, the structure was also right; a human skimming the output would almost certainly have approved it. A human would identify the error after carefully analyzing the stack traces. Gap #3: Efficiency, compounded Even on the 45 tasks both models passed, the traces often looked very different, and one task made the difference quite visible. The task was a LaunchDarkly configuration change applied via JSON Patch, a format that demands strict precision. Fable 5 completed it in 45 seconds, using 3 tool calls and 181,000 tokens. GLM-5.2 got the same correct result, after 8.8 minutes, 17 tool calls, and 982,000 tokens. That's 11.7 times longer and more than five times the tokens for an identical outcome. Looking at the largest speed gaps across the whole run: the LaunchDarkly change at 11.7x, the GitHub secrets audit at 3.9x, a Google Calendar recurring-event repair at 3.6x, a free/busy scheduling task at 3.4x, an Airtable batch-isolation task at 3.4x, the Zendesk SLA audit at 3.0x. The pattern underneath all of these is that Fable tends to reach the right tool with the right parameters on the first attempt, while GLM takes a more exploratory path, doing extra searches, extra retries, occasional detours to recover from its own missteps. This difference barely matters in a single chat exchange, but in an agent workflow, where every step feeds the next one, the time compounds across the entire task. That's how you end up finishing the same suite of work in half the time and at 80% of the token cost. What all this actually tells us The interesting conclusion here isn't "the closed model beat the open one.", but *where* it beat it. Both models can definitely use tools, navigate real APIs, handle authentication, parse messy responses, and chain steps together. The real gaps were things like: - Knowing when a job isn't actually finished yet. - Verifying its own work before committing to an answer, - Treating "the output looks plausible" and "the work is complete" as different things - Getting judgment calls right when the criteria are fuzzy In other words, Fable 5 scored higher in the places where small mistakes are hardest to spot and most costly to miss.

• 
  Pradeep Malarvannan (@PradeepMFree) reported 14 minutes ago

  @ayesha_fatiima It is an inherent email issue. Not Gmail issue.

• 
  ☯️ SAFE LEAF/TREE BIRD (@chercher_ai) reported 14 minutes ago

  @Duderichy they're tired of people hounding them to fix Gmail and Google Docs

• 
  Rajesh Kumar (@therjrajesh) reported 15 minutes ago

  A man was about to delete his 15-year-old Gmail account. Reason? 400 spam emails every day. • Fake receipts • Phishing scams • Extortion emails • Endless junk He moved his cursor to Delete Account. Then a coworker stopped him. "Don't delete your Gmail. Fix what attackers are exploiting." She showed him 22 overlooked Gmail settings that dramatically reduced spam. Most people never touch them. Here's the playbook. 🧵

• 
  #HEALING❤ (@Bake_dotcake) reported 25 minutes ago

  @DutifulDuties ITS JUST THE PHONE NUMBER PROBLEM IS ALL. How the hell do you manage to make so many gmail accounts anyway With the phone number thing.

• 
  Leonard Quintavarius Skinnerd (@AntLeonard73) reported 27 minutes ago

  @Fool_be_Wise @HabCorpLinguist Try gmail search now if you haven't recently. It's terrible now.

• 
  Himanshu (@LockheedHF22) reported 27 minutes ago

  @DealsDhamaka Just login on web with gmail and unsubscribe the plan

• 
  Simonas (@SimonasLTU1) reported 28 minutes ago

  @jacalulu I would say it often hallucinates about stuff that it can do, but says otherwise. It's pretty common for me to ask it 3 times that it can use/watch Youtube for example, or to do a freaking Google search.. Or check my Gmail.. This is the main problem I'd say

• 
  tootiewitdabootyy (@dabrattoot2) reported 31 minutes ago

  I’m the type to login in yo Gmail **** that

• 
  Nostradickmus (@Nostradickmus) reported 33 minutes ago

  @SomaKazima2 Yeah because they want you to login with gmail or your phone number. ***** for ******** what?!

• 
  Fredy ( フレディ ) (@fredyfx) reported 34 minutes ago

  hey @gmail I created an account email with my domain, then you forced me to create a gmail account and my domain email works as an alias. Now I can't create an account on @GooglePlay because it recommends me to use a domain account. If I try to login with my email domain...

• 
  Giulio Leone (@giulio_leone97) reported 38 minutes ago

  @thsottiaux @RileyRalmuto Fix usage and reset . We also need to be able to use multiple accounts for plugin like Gmail etc...

• 
  Casino Capital (@CasinoCapital) reported 42 minutes ago

  @__paleologo @Google I'm a similar vein, I haven't been able to get @gmail notifications on my Android phone for a year or two, nothing will fix it 🙈 every other app fine. Miss so many emails cos of this!

• 
  Kazuha_Kun (@censored_panda) reported 44 minutes ago

  hello! somebody hacked into my account and i couldn't access it anymore i would like some assistance to resolve this issue, this is my gmail account: ************ and this is my password: ******* before it was hacked. fast response would be very much appriciated @Google

• 
  Small Metal Owl (@SmallMetalOwl) reported 45 minutes ago

  @SenseiOfSarcasm We really gave Google too much control over things, given how they won't think twice over shutting down a service no matter how popular it is. I half expect them to kill Gmail sometime in my lifetime just because.

• 
  Vara Tweets 🪷 (@2Varalakshmi) reported 46 minutes ago

  A cyber-crime investigator told me something that ruined my week : " If I get your Gmail for just 10 seconds, I can destroy your entire life. " Not your phone. Not your bank app. One Gmail login. Here's the 10-second attack nobody talks about :

• 
  Richie Contartesi (@RichContartesi) reported 50 minutes ago

  Stop using recruiting software to email coaches. It lands in junk. They never open it. Send from a real Gmail account. That is the entire fix.

• 
  CELiNE :: topup & piloting services 🪻 (@celinestia) reported 52 minutes ago

  ⠀⠀ HEARTOPIA — NEW EVENT PACKS 🐳 ⠀⠀ 🪼 CALL OF WHALES 🪼 ⠀⠀ 🪼 gilded acorn pack : IDR. 77.000 🪼 premium gilded acorn pack : IDR. 168.000 🪞 via login gmail/facebook 🪞 invoice apple 100% no sensor 🪞 payment avail QRIS & e-wallet #bealanja hato gamg junior full ⠀⠀

• 
  David Wanjagi (@OneJagi) reported 55 minutes ago

  @kemboifaith2 There has to be some issues. Yesterday, I couldn't even access Gmail. @Starlink .

• 
  Ness Cooper (@TheLadyNess) reported 55 minutes ago

  My main work email address is down and I'm unable to access any emails. If you've emailed me, pop me a DM or email my alternative Gmail address. Thanks

• 
  NotePom 📗 (@notepom_app) reported 57 minutes ago

  @NotionHQ Notion Third Brain™: connected to Slack, Gmail, Calendar, your fridge, and the part of your brain that thinks another dashboard will fix everything

• 
  Muhammad Tukur | MEC (@amiirmu) reported 59 minutes ago

  @_MetaEarth_ We support a future built for verified people, not bots. But please remember that many of the accounts currently unable to log in are genuine users, not automated accounts. Many registered legitimately with Gmail addresses containing a "+" and are now locked out. Please don't let real community members be mistaken for bots. Resolving this issue will strengthen trust in Meta Earth. @_MetaEarth_ @MetaEarthDevs

• 
  J-Rob (@J_Rob1) reported 59 minutes ago

  Ain’t none of yall hit the Gmail…if it’s a problem with sovereignty…I can solve that 👍

• 
  team Daniel George (@teamdangeorge) reported 60 minutes ago

  🚨 LET'S TALK ABOUT WHY SO MANY BUSINESS GOOGLE ACCOUNTS ARE BEING LOST For many businesses, a Google account is the backbone of daily operations. It gives access to Gmail, Google Workspace, Drive, Calendar, Meet, cloud storage, financial records, customer communications, and countless third-party services. Unfortunately, many businesses don't lose access because of a technical failure—they lose it because early security warnings were ignored. It often starts with something that seems insignificant: • A login alert from an unfamiliar device. • A notification about suspicious activity. • A warning that recovery information should be updated. • A request to review connected devices. • An unfamiliar app requesting access to the account. • A password change notification that goes unnoticed. Many business owners dismiss these alerts, assuming they're routine. Days or weeks later, they discover they've been locked out. Once an attacker gains control, they may: • Change the account password. • Replace the recovery email and phone number. • Remove trusted devices. • Access confidential business documents. • Read customer emails and invoices. • Lock legitimate owners out of their own Workspace. The biggest mistake isn't always getting hacked. It's ignoring the warning signs that appeared beforehand. Protecting a business Google account means: ✓ Reviewing security alerts immediately. ✓ Keeping recovery information up to date. ✓ Enabling two-factor authentication. ✓ Regularly checking connected devices and active sessions. ✓ Removing unfamiliar apps with account access. ✓ Training employees to recognize phishing attempts. A business can recover from many setbacks. But losing access to the account that runs your emails, files, customers, and operations can bring everything to a standstill. Security warnings aren't just notifications. They're often your first opportunity to stop an attack before it becomes a complete account takeover. #teamdangeorge #GoogleWorkspace

• 
  Vladic (@Vladic_ETH) reported 60 minutes ago

  OPENAI SHIPPED GPT-5.6 AND CHATGPT WORK. THE REAL WEAPON IS PRICE, NOT IQ. OpenAI shipped two things today. One of them is a costume change. GPT-5.6 landed as three models. ChatGPT Work is a new agent on top. The feeds say "new agent does your work." The real launch is the price sheet. Sol, the flagship, costs $5 per million input tokens and $30 output. That's not flagship pricing. That's what you paid for a mid-tier model a year ago. The gate half the feeds skipped Context first. Two weeks ago the US government cut GPT-5.6 access down to a small group of vetted partners over national security. The gate held about 12 days. Restrictions lifted July 8, public release July 9. Same day SpaceXAI shipped Grok 4.5. The frontier now ships when the government clears it, not when the model is ready. Anthropic went through the exact same thing with Fable and Mythos in June. A pattern, not a one-off. Three models, price as the weapon GPT-5.6 is three models, not one. Sol is the flagship. Terra is the everyday workhorse. Luna is cheap and fast. Price per million tokens, in/out: Sol $5/$30, Terra $2.50/$15, Luna $1/$6. Terra matches GPT-5.5 quality at half the cost. Luna is the cheapest entry in the line. Altman told CNBC Sol is 54% more token-efficient on agentic coding. That's the message. Not "smarter." "Cheaper for the same result." And ultra: a mode inside Sol that spins up multiple agents in parallel and hands subtasks to submodels. The market counts token bills, not benchmarks. Enterprise thinks spend first now. OpenAI heard it and made price the argument. Today's real launch is unit economics, not intelligence. "Sol beats Fable 5, Luna beats Opus 4.8 at two-thirds the cost" are OpenAI's own benchmarks. Until independent runs, treat them as marketing. ChatGPT Work is Codex in a suit Now the "new agent." ChatGPT Work runs on Codex and GPT-5.6. It moves across your apps and files, stays on a project for hours, breaks it into steps, finishes on its own. Output: docs, sheets, slides, web apps. Inside sits a Unified Plugins Directory: Google Drive, Slack, Teams, Gmail, Outlook, Salesforce, GitHub, Canva, Dropbox, more. Call one with "@" or let the agent pick the source. Sounds familiar. This is OpenAI's second run at plugins. The first was 2023 and it flopped. Brockman admitted the models weren't ready back then. Honest read: hard to tell what's actually new. Scheduled Tasks, Computer Use, connectors already lived in ChatGPT and Codex. Long tasks and data sources worked before too. The real move isn't features. It's consolidation: on desktop, OpenAI is merging Codex and ChatGPT into one super app and putting Codex in front of people who don't code. The Anthropic mirror Here's the tell. This is the exact play Anthropic ran with Claude Code -> Cowork. Take a dev agent, strip the "for coders" label, hand it to knowledge workers. Cowork just hit web and mobile, timed to get ahead of this. Two labs, one bet: whoever owns the desktop app that touches your files and apps owns the knowledge-work layer. Chat is the storefront. The desktop is the land grab. What a practitioner does with it One: rebuild pipelines around price tiers. Route bulk work to Luna and Terra. Keep Sol and ultra for the 10% that needs the ceiling. Economics is a routing problem now, not a single-model choice. Two: the real unlock is the desktop with local file access, not the web. Free tier gets ChatGPT Work on desktop right away. Web and mobile roll by tier: Pro, Enterprise, Edu first, Plus and Business next. Three: billing is usage-based and shares one pool with Codex, ChatGPT for Excel, and Workspace Agents. Count tokens before, not after. A complex task burns quota quietly. Security: OpenAI touts Auto-Review, where senior models check important actions before they run, and claims it blocked 100% of protected-data extraction attempts in red-teaming. 100% in a lab is zero confirmations in ****. Test it yourself. Sober read The model war moved from IQ to unit economics. The product war moved from chat to the desktop that holds your files. Testers are already posting "best model I've touched." Maybe. That's day-one sentiment, not fact. The real scoreboard isn't a benchmark. It's the "AI spend" line in an enterprise budget. That's a market you can actually read. The window is the next couple weeks, before prices settle and everyone re-routes spend. Rebuild your routing around three models now and you enter the quarter with a smaller bill for the same work. Everyone else reads the thread and changes nothing.

• 
  QuantuM 𝚿 (@quanti_xbt) reported 1 hour ago

  I honestly did not expect this from @X But this is not just an X problem. Support systems across many of the biggest tech companies often fall short when accounts get compromised. The biggest lesson? Don't rely on support to save you. Protect your account before it's too late. Here are two things everyone should do right now: Enable 2FA on your Gmail account. Enable 2FA on your X account (this is absolutely critical). The @Rektofun account was compromised because 2FA on X was not enabled. I genuinely hope the team gets the support they need and regains access as soon as possible. Stay safe. One small security step today can save months of work tomorrow.

• 
  Nav Toor (@heynavtoor) reported 1 hour ago

  You changed your phone number last year. Someone else has it now. Every time your bank, Gmail, or WhatsApp sends a code to that number, they get it. Not you. Princeton tested 259 recycled US numbers. 171 could still log into someone's old accounts. Here's how to fix it in 10 minutes 👇