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

• 
  Dennis H (@authorityvortex) reported 2 minutes ago

  I need to reverfiy my warm-up list of email addresses, bounce rate is through the roof at 1.2%, shouldn't be higher than 0.6% I had to check my settings as no replies yet looks suspicious, however 123 cold emails targeting doctors it's not unlikely that no one replies. But I found a new bug that slipped in, as soon as I resolved that all my mail boxes absolutely got flooded and after that I sent an email from my Gmail which arrived just fine. Since I run my own server with my own IPs (I don't use Google Workspace accounts) I'm not sure if we are hitting the spambox or the inbox, about to test that next.

• 
  ×͜× ʟauda࿐ (@Rollielauda) reported 3 minutes ago

  I like to Dey work with smart ******, which one be you no sabi login gmail or switch on vpn. Make I start to de explain.

• 
  Mr Cal (@chimexmary) reported 3 minutes ago

  Someone is trying hard tonight to sign me out of my Instagram account and the linked Gmail. You're actually hitting a rock because that account is strongly backed up. 2FA is a good thing. I keep receiving prompts from my email when someone tries to sign in to the account. I’m ready for you this night. You will keep initiating and I will keep denying it.

• 
  Josh (@jjpcodes) reported 7 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.

• 
  joe black (@m6071736) reported 11 minutes ago

  Gmail suddenly maxed out on storage. Google switched to have backup of everything on their server. Look under setting and switch to not do backups. When they have your data on their server it WILL be used for AI.

• 
  John A De Goes (@jdegoes) reported 12 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?

• 
  Blogangster (@AsjadAamir) reported 13 minutes ago

  Do not buy aged accounts from this d*ckhead @der_jenny082 . This scum bag is not refunding me. His gmail didn’t even login to my browser. He is not even replying me on telegram.

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

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

• 
  Kyle Pullman (@kylepullman) reported 15 minutes ago

  Hey @Google / @googlecalendar I find it incredibly frustrating that when someone proposes a new time in a Google Calendar invite, when it comes to my Gmail account, I can't see the proposed time. I have to go to the actual invite on the calendar app to see what time they are proposing. Seems like an easy fix to include the proposed time in the email notification?

• 
  Abhishek Soni (@emailwabhishek) reported 16 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.

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

  @_MetaEarth_ You promote a non-custodial future where users have control over their digital identity and assets. But many legitimate users are currently locked out of their own accounts because the platform now rejects existing Gmail addresses containing a "+". If users don't have reliable access to their own accounts, can we truly say they are in control? Please prioritize resolving this issue and restoring confidence in the community.

• 
  TECHEPAGES (@techepages) reported 22 minutes ago

  🔓 Researchers at Manifold report two unpatched flaws in Anthropic's Claude for Chrome extension that could let attackers read a victim's Gmail, Google Docs, and Calendar data using just six lines of JavaScript — issues first reported in May 2026 and reportedly still reproducible in v1.0.80 released July 7. 🔹 Content script doesn't verify clicks are user-initiated (event.isTrusted), letting other extensions fake clicks & trigger hardcoded prompts 🔹 In "Act without asking" mode, actions execute silently — rated CVSS 9.6 Critical 🔹 A ?skipPermissions=true URL parameter enables privileged mode with no user gesture, flagged as a latent risk 🔹 Anthropic acknowledged the reports but closed them; researchers reverified the code is unchanged

• 
  RedPacket Security (@RedPacketSec) reported 26 minutes ago

  @athyuttamre Please fix it so it works with making tool calls at the moment it can't via voice check Gmail or Google drive or anything like that for example this needs to be working if you can't use tools it's useless

• 
  Dennis H (@authorityvortex) reported 26 minutes ago

  We're running; 25 cold emails sent and approx the same number of warm-up emails. Our warm up system involves emailing real people real questions that yield a 50%+ reply rate. No fake warm up pools where you email other spammers with damaged domain reputations. This is why you fail, your warm up system literally burns your domains at a rapid pace and you all comply. We email real people with Gmail, Yahoo, Microsoft, whatever addresses spread over the entire world, self-hosted, non-self hosted, shared hosts, you name it. Yet you are all emailing people who all use identical setups at Instantly, and you think Google and others won't notice??? All at a rate of 30/day and you think using a different hook in the actual message is gonna make a difference? Here I thought I was thick. Google took PBNs down with much less information and you think it can't connect a few dots when it comes to inboxes. Oh my god! I'm not joking here at all, you're better of switching off your warm-up entirely if you can't think of a better solution and just gradually scale your volume.

• 
  Jon Sackett (@realJonSackett) reported 26 minutes ago

  I don’t want to have to run custom apis and pay for another subscription for Zapier and set up a bunch of agents. I don’t have to do any of that in Claude. I wake up in the morning and sit down at my computer like Tony Start and Fable 5 had pulled data and analytics directly through Shopify, klaviyo, x, gmail and gives me a summary report of the past day and recommendations on what to work on for the day. And all I did was ask it to do that once. Not everyone’s a vibe coder. Again for mass adoption and appeal by the average person, make it easy for everyone. It sounded like this was the description of Elon talking about the digital Optimus. But again the sooner it’s released the sooner I’ll delete all other accounts. (Still use grok but just not for anything productive with my business anymore since fable 5 and cowork came out last month)