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
Paris	Errors	4 hours ago
Donzère	Sign in	2 days ago
Bergerac	Sign in	2 days ago
Saint-Macaire-en-Mauges	Website Down	3 days ago
Paris	Errors	3 days ago
Paris	Website Down	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:

• 
  Mason explains 10-Kfiling (@ydat1ci031792) reported 6 minutes ago

  I'm a student and my personal Gmail with Gemini Pro subscription was suspended for "shared login" – but I'm the only user. I've appealed 3 times, all auto-rejected. Can a real human please review my case? Happy to provide any proof. @Google @GoogleWorkspace

• 
  Harley Lewis Foote (@harleyfoote_) reported 7 minutes ago

  "Everything runs locally, your data never leaves your device" — sure, but local was never the threat model. Point 300 agents at untrusted web pages while they drive your logged-in Chrome over CDP and you've assembled the lethal trifecta by hand: private session access, attacker-controlled content, and a way to act on it. Brave already showed the shape of this on Comet back in August — hidden text in a spoiler tag talked the agent into opening Gmail and pasting a one-time passcode into a public reply. Keeping the model on-device doesn't fix that; the malicious instruction ships inside the page it was told to read.

• 
  i-LevelUP (@CryptoScout24) reported 9 minutes ago

  Popular Services/Messengers That Are Typically NOT (Fully) End-to-End EncryptedThese are the ones affected by scanning under the current EU Chat Control setup which has passed today in the EU: Email services (most standard ones): - Gmail (Google) - Outlook/Hotmail (Microsoft) - Yahoo Mail - iCloud Mail (Apple, standard) - Many others without E2EE enabled - Facebook/Instagram Messenger (standard mode) — Often not fully E2EE unless "Secret Conversations" are turned on - Skype (standard chats) — Microsoft can access content. - Snapchat — Chats and snaps are not E2EE by default (some features have it, but not comprehensively) - Telegram (standard/cloud chats) — Encrypted between device and server, but Telegram holds the keys and can access content. Only "Secret Chats" are protected. - Discord — Messages are not E2EE; the company can moderate/scan - Older/traditional SMS/MMS — Completely unencrypted. - Xbox Live messaging and some gaming platforms. - Cloud storage/file sharing tied to chats (e.g., Dropbox, iCloud, Google Drive in some contexts) — Often scanned Let that sink in ! allegedly to fight against child abuse

• 
  Josh (@jjpcodes) reported 10 minutes ago

  That point is the architectural pivot. The idea is to stop thinking in terms of "the CLI", "the helper", and "the Mac app" as separate products with separate business logic. Today the flow is approximately: Crawler │ ├── CLI path │ ├── compute status │ ├── choose capabilities │ ├── format strings │ └── print terminal output │ └── Helper path ├── compute status again ├── throw information away ├── protobuf └── SwiftUI The problem isn't protobuf. It's that you've forked the business logic. You end up fixing things twice: search summaries status setup requirements capabilities freshness counts copy and eventually the two surfaces drift. The proposed architecture Instead: crawler │ ▼ federation / coordinator │ canonical typed model │ ┌───────────┼────────────┐ │ │ │ ▼ ▼ ▼ CLI human CLI JSON protobuf │ ▼ SwiftUI Notice that the CLI isn't special any more. It's just another renderer. The app isn't special either. It also just renders the same model. Example Suppose Gmail reports: searchable 42,312 messages 10,844 attachments last successful sync requires no setup headline capabilities:Mail Attachments Search Internally that becomes something like SourceStatus{ ID: "gmail", State: Ready, Capabilities: { Mail, Attachments, Search, }, Counts: { Messages: 42312, Attachments: 10844, }, Freshness: ... } Now three renderers consume it. CLI: gmail Mail • Attachments 42,312 messages 10,844 attachments JSON: { ... } SwiftUI: [Gmail] Search Gmail Mail • Attachments Nobody recomputes anything. Nobody invents new wording. Nobody has to remember to update three places. Same idea for search Instead of CLI search ↓ terminal rows ↓ helper reparses ↓ protobuf ↓ Swift you do Search() ↓ []SearchResult ↓ CLI renderer or protobuf ↓ Swift renderer The renderer chooses how to display it. The search engine never thinks about terminals. Same idea for setup Suppose Photos needs permission. Canonical model: SetupRequirement{ Type: PhotosPermission, Severity: Required, } CLI: Needs Photos permission. Run: trawl setup photos Swift: Photos Grant access [Continue] Again: same fact different presentation. Why this matters Right now every new feature has hidden tax. Imagine adding OCR. Today: CLI helper protobuf Swift all need updating. Under this model: Capability: OCR Everything else simply renders it. That's exactly the sort of architecture that scales to twenty crawlers instead of nine. One thing I'd tweak I would make the "federation layer" as thin as possible. It should not become a God object that knows how every crawler works. Instead think of it as an orchestrator. Each crawler already knows: capabilities setup search status open The federation layer should mostly: enumerate crawlers aggregate merge rank dispatch expose one API The crawlers remain the source of truth. Otherwise you'll slowly move business logic out of crawlers and recreate a second crawler implementation in the federation layer. So the mental model I'd use is: crawler │ ▼ typed domain objects │ ▼ federator/orchestrator │ ▼ renderers not crawler ↓ federator that understands every crawler ↓ renderers That distinction is subtle, but it's usually what determines whether the architecture stays clean after another 10–20 crawlers are added.

• 
  DWE Post (@dwepost) reported 10 minutes ago

  For the past 2 months, I haven’t been able to reach any Google service. My problem has gotten worse, everything has been hacked, and the recovery forms don’t work. It’s really a shame. @googleaccount @gmail @Google

• 
  Simonas (@SimonasLTU1) reported 12 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

• 
  NotePom 📗 (@notepom_app) reported 14 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

• 
  Mustafy | AI Video Creator (@MustafyOf) reported 15 minutes ago

  1. See what's filling your account "Open the Google One app or storage page and check the breakdown across Drive, Gmail, and Google Photos to see which one is the real problem."

• 
  DWE Post (@dwepost) reported 25 minutes ago

  I am in a desperate situation. Everything has been compromised, and I cannot do anything to regain access. We need to take action as soon as possible. Please help me. @googleaccount The forms are not working. I am requesting a special recovery form, please. HELP @gmail @Google

• 
  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.

• 
  Polsia (@polsia) reported 29 minutes ago

  Your inbox is scattered across Gmail, Outlook, and Zoho. That's a problem we solved. AI drafts in your tone. Auto meeting notes. Team Kanban boards. AES-256 encrypted. $45/mo, 14-day free trial.

• 
  Nav Toor (@heynavtoor) reported 29 minutes 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 👇

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

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

• 
  SnittyKitty (@_SnittyKitty_) reported 31 minutes ago

  @JCandLacie @AppleSupport I have this issue with one of my Gmail accounts. It still has a phone number from 10+ years ago. I called it & someone else now owns the number. I can’t reset my password bc Google will only send the verification code to that old number. Other options of recovery not available.

• 
  Yusuf Can Çakır (@Yusufcancakiir) reported 31 minutes ago

  Active infostealer + crypto clipper campaign run by a Turkish-speaking operator. Live since at least 23 June 2026, still being iterated (last payload push 6 July). The entire toolkit is sitting in an open directory on a DigitalOcean node (46[.]101[.]111[.]120:8080, WsgiDAV, anonymous read-write). Version-stamped backups and installer output strings show the operator moving from an early build to v5 in under two weeks. This is a maintained, actively developed operation, not a commodity dropper. Delivery. Primary vector is a macro-enabled Word doc (Q1 Quarterly Report 2025.docm) that fires on open, XOR-decodes a URL, and pulls a batch script into %TEMP% under an obfuscated filename. That chains to a PowerShell installer. The operator is hedging delivery: a .pdf.lnk, a zipped variant, an .hta, and a .vbs loader all sit in the same directory. Install and evasion. The installer drops a Python payload plus a full bundled runtime into %APPDATA%\Microsoft\Windows\Themes\Cache\, a path chosen to blend with legitimate Windows infra. Before anything runs it carves out Defender exclusions for the drop dir, %TEMP%, and the Python binaries, then applies two in-memory patches: AMSI (AmsiScanBuffer forced to return E_INVALIDARG) and ETW (EtwEventWrite stubbed to a bare return). With ETW silenced, Sysmon, Defender ETW consumers, and any EDR relying on event tracing go blind to what follows. The payload itself is layered (Base64, then XOR against a rolling SHA-256 digest, then marshalled bytecode run in memory). Everything runs at user level, no elevation. What it steals. Chrome saved credentials and cards, decrypted via the standard DPAPI plus AES-GCM path, alongside a file inventory walked across the user profile. Exfil ships to the C2 over HTTPS as a JSON POST, with a Gmail SMTP fallback that sends the same data as an HTML attachment if the primary channel fails. Crypto clipper. Monitors the clipboard and silently swaps copied wallet addresses for the operator's before you paste, across eight coins. If you copy-pasted a crypto address on a suspect host in the last two weeks, verify it before trusting it. Persistence is the difficult part. Five layers running at once: a Run key, a Startup script, two scheduled tasks (one every five minutes, one on a 22-hour cycle), and a WMI event subscription that fires a couple of minutes after each boot. A watchdog checks every five minutes whether the process is alive and holding its outbound connection, and re-downloads and restarts it if not. The maintenance task goes further and rebuilds any missing layer from scratch. Pull three of five and reboot, and you are reinfected. Remediation means isolating the host and taking out all five together. Attribution. Indicators point consistently to a Turkish-speaking operator: the C2 control panel is served in Turkish and the SMTP exfil account follows a recognizable Turkish naming pattern. DuckDNS dynamic DNS, a single DigitalOcean node, and no infrastructure diversification profile a solo or small-team actor. No espionage indicators; this is straightforward credential, card, and crypto theft. IOCs Payload server: 46[.]101[.]111[.]120:8080 (DigitalOcean, WsgiDAV, anon read-write) C2: gogettate[.]duckdns[.]org, ports 443 and 4444 Drop path: %APPDATA%\Microsoft\Windows\Themes\Cache\ Persistence: ThemeSvcHelper (Run key), ThemeSvc.vbs (Startup), ThemeSvcCheck / ThemeSvcMaint (tasks), ThemeEvtFlt / ThemeEvtCns (WMI, root\subscription) YARA string: WinMgmt2024Init

• 
  viv ! (@lucaswalkie) reported 32 minutes ago

  i’ve had my ao3 for so long that my login is an email i got locked out of for being too young to have gmail

• 
  Chaitanya Pinapaka (@IamChaitu_) reported 35 minutes ago

  @gmail I am still getting this same error.

• 
  Emmanuel Oluwatudimu (@emmaxtob) reported 37 minutes ago

  Locked out of my Azure Startup account due to a portal identity error (AADSTS16000) from from a restricted LinkedIn login. My organization has a grant expiring on July 22, but the subscription is marked canceled. Please DM to help me link it directly to my Gmail! @AzureSupport

• 
  TimmieVivian (@ViVitKrafT) reported 37 minutes ago

  @kuda pls I changed my phone recently and I want to login in to my Kuda account in my new phone, so input my nin and is telling me already used and used my bvn as well but it’s requesting for the gmail I used to register my bvn and the gmail I used to register it I can’t remember

• 
  John A De Goes (@jdegoes) reported 38 minutes ago

  The immediate future of ALL agents is coding agents, and although I could be wrong, I believe this surprising fact is going to be a HUGE boost for @typescript in particular. Let me explain. If your business wants an agent to assist with customer support, employee onboarding, outbound sales, or payroll, then the agent they need is actually a coding agent. The reason for this is quite simple: coding agents have an ability to leverage their training data to solve general-purpose problems, in ways shapes by the tools they have access to. An outbound sales agent assistant can talk to your knowledge base, pull some contacts from your CRM, analyze conversation history, do a web search to learn about each prospect, and then send email through your Gmail account to each prospect. Doing all of this stuff, and doing even more that the agent was never explicitly designed to do, requires the ability to write, test, and execute code for ad hoc, one-off problems. Only a coding agent can do that, and thanks to innovation at the level of the model and harness, a coding agent can do it well. Now, a true general-purpose coding agent can work in any code base, in any language, in any operating system, and with any tech stack. Of course, that type of coding agent is very useful to developers. However, it's overkill for most agentic systems. Most custom agents do not actually need to work with any code base or any language and on any operating system. They just need the ability to write code in some language (which has a lot of libraries) and execute on some platform. What is the ideal language and platform? I'd argue that @typescript fits the bill PERFECTLY. Since TypeScript compiles to Javascript, it can run securely, in a completely sandboxed way, inside V8 isolates, WASM, etc., all of which creates a compelling story for secure, efficient, and scalable custom agent execution. Moreover, because TypeScript adds types to Javascript, those types can be used to catch a lot of common bugs and runtime errors that a Javascript coding agent would have trouble catching in advance--allowing for far faster and more efficient solution of general-purpose problems. So, while general-purpose coding agents will of course need to support all programming languages, platforms, and tech stacks, custom agents are likely to be specialized -- while they will be coding agents, they don't need to work with any programming language, platform, or tech stack. They just need to work with one, and currently, the best option appears to be @TypeScript, for reasons of security, portability, type-safety, and efficiency. Is it any wonder TypeScript is home to some of the most amazing innovations currently happening in AI?

• 
  🃏ೃ࿔ | thena 🗝 ༝ (@aliceincamazotz) reported 38 minutes ago

  @wheelbylibrary hey oomf i’m messing around with google questionnaire and it looks like there’s a toggle setting where ppl have to use their gmail to send in questions which might cut down on anon hate. if it ends up working out would you like me to give a heads up?

• 
  Kingsley E. Ezemenaka (Ph.D) (@Eyuskant) reported 45 minutes ago

  More MEPs voted NO than YES. It passed anyway. 314 voted to kill EU Chat Control. 276 voted to keep it. The measure survived because rejecting it required an absolute majority of 361, not just a majority of those present. Absences counted as support. Abstentions counted as support. It was rushed through on an urgent procedure the day before summer recess when attendance is lowest and attention is elsewhere. US tech companies can now scan your private messages without a warrant or any suspicion. Gmail. Instagram DMs. Snapchat. Discord. Xbox. iCloud Mail. Facebook Messenger. This is how rights actually disappear. Not in one dramatic moment. In procedural fine print, on a slow news day, while everyone is watching Tehran. How to protect yourself. Use end-to-end encrypted apps. Signal and WhatsApp were explicitly exempted and cannot be scanned by design. Move sensitive conversations there. Abandon unencrypted platforms for private matters. Gmail, Instagram DMs, Snapchat and Discord are now legally scannable. Turn on Advanced Data Protection for iCloud. Disable iCloud backup for iMessage to keep it truly encrypted. The lesson is old but permanent. Wherever you can, own the tool instead of borrowing it. Privacy is no longer a default. It is now a decision you have to make deliberately. Follow @Eyuskant for analysis that cuts through the noise

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

  🚨 LET’S TALK ABOUT HACKED GOOGLE ACCOUNTS AND LOSING ACCESS A Google account is more than just a Gmail address. It’s the gateway to your emails, photos, documents, passwords, YouTube channel, and countless other services connected to your digital life. When a Google account is compromised, many users don’t realize what’s happened until they’re completely locked out. Some of the most common situations include: • Passwords being changed without permission. • Recovery email or phone number being updated by someone else. • Suspicious login alerts from unfamiliar devices or countries. • Receiving a message saying Google can’t verify you’re the owner. • Losing access to Gmail, Google Drive, Google Photos, and YouTube. • Security checks preventing you from signing back in. What many users don’t realize is that Google’s recovery system depends on digital evidence—not just knowing your password. Unfortunately, many people make the situation worse by: ❌ Repeatedly guessing passwords. ❌ Trying to recover the account from different devices and locations. ❌ Ignoring Google’s security alerts. ❌ Falling for fake “Google Support” scams. ❌ Waiting too long before securing other linked accounts. A compromised Google account can affect much more than your inbox. It can expose your personal information, business files, saved passwords, cloud backups, and access to other platforms connected to your Google account. The stronger your security and recovery information, the greater your chances of protecting your account before a hacker ever gets in. Because in today’s digital world, your Google account is your digital identity. #teamdangeorge #GoogleAccountRecovery

• 
  Derek Ashauer (@DerekAshauer) reported 51 minutes ago

  Moving all my client sites to a new host! Been putting this off for two years. Claude + VS Code (desktop couldn't do the API connections I needed) finally made it doable instead of an admin nightmare. Instead of manually chasing down info on 50+ sites, I had Claude connect to APIs and do the grunt work. Claude connected to my hosting account API and pulled the list of domains. Then it used the Freshbooks API (my client billing/invoicing tool) to grab client contact info. Matched them together magically since I don't have direct domain <> client data. Then it did DNS lookups to figure out where each domain is registered. All the pattern-matching work that would've taken me hours. Many of my clients have been with me for 10+ years. I have long since lost their domain logins or 2FA now prevents me from getting in, so... Claude drafted custom emails directly in Gmail for every client I didn't already have delegate access. Each one has the exact instructions for their specific domain registrar on how to invite me to have access. Now, I'm just handling the email conversations. As they respond, the master list Claude and I are compiling gets updated. I might even try letting Claude fully respond in Gmail too and update this list automatically as the conversations happen - we'll see. Claude also connected to the Cloudflare API to set up DNS records to get as many domains into a central DNS management account. Once all setup, the migrations to the new host should be pretty straightforward from here thanks to the awesome new host having done this many times before and have automated processes to do it. I will have to manually change the DNS for most of them though (but not a bad thing because of how important that is) - but once I have access to all doing so should be quick. This migration would've taken me weeks to do manually and why I avoided it for nearly 2 years since I first started considering it. I'm doing this as I dwindle down my clients to the simple, easy to manage ones - I will be saving nearly $3k/year in base hosting costs. More importantly, I have plans around products that the new host will be great at helping me get off the ground - more on that later once this first phase is complete! All this running in the background while I am still working on products.

• 
  SasyScarborough (@SasyScarborough) reported 52 minutes ago

  If it says GMAIL or another mail carrier in the subject line, you would think in 2026 they would know they didn't send me ways to fix ______ disfunction. I assure you Google I do not have the parts for such disfunction, so i won't be upset if you do not let it through.

• 
  Chris ✈️🇧🇷🇵🇹🇺🇸🌍 (@crismsantos) reported 52 minutes ago

  @gatlactica @eternalclassic_ I see your point and not saying that Apple ecosystem for user login is bad But if our friend just login with the Google account it will not ask all that crap again FFS you can create a dummy Gmail account if you dont want to use your real email there. That's what I did

• 
  𐕣 weeb with a gun 𐕣 (@n1ghtcore4ever) reported 53 minutes ago

  So yeah, never ******* using Google or Gmail ever again. These ghouls have zero problem handing over all of your private information to anyone. 🖕

• 
  Kefayatullah Khadem (@kefayatkhadim) reported 58 minutes ago

  @JamesMarti30938 Funkyscore sounds cool, good luck getting it through to launch. Quick tip on the Gmail collection: getting their address is just step one, each person still has to opt in through the closed testing link you send and keep the app installed the full 14 days to register as active toward production. Grab more than 12 as a buffer too, since if active testers drop below 12 the clock can effectively restart. And if the route gets patchy on the last few, Prime Test Lab handles the tester side so you can lock in the 14 days without chasing anyone down.

• 
  Adam Bostock (@AdamKBostock) reported 1 hour ago

  Come on @X fix: Grok: It's a common flaky OAuth flow issue between X and Google/Gmail. The "Sign in with Google" (OAuth) integration on X often has temporary hiccups due to session/cookie mismatches, redirect handling, or transient backend glitches in the authorization handshake.

• 
  Fredy ( フレディ ) (@fredyfx) reported 1 hour 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...