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 (36%)
• Sign in (27%)

Live Outage Map

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

City	Problem Type	Report Time
Gondreville	Website Down	3 hours ago
Champniers	Website Down	7 hours ago
Cannes	Errors	10 hours ago
Dakar	Website Down	22 hours ago
Biscarrosse	Sign in	1 day ago
Sydney	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:

• 
  Simon Ostler (@SimonOstler) reported 3 minutes ago

  @KFILE @BobPickard Gmail is also terrible to search. 🔍

• 
  Matt (@mattsaltaccount) reported 3 minutes ago

  @JustinBleuel @bonitadreama @ChatGPT Multiple Gmail accounts in the Gmail plugin. It's honestly broken without that. Who only has one Gmail account?

• 
  BIAST Archives (@BIASTArchives) reported 6 minutes ago

  Our contact information is true, you can messages us on Gmail for biast archives, aswell as maybe a potential discord server? We might not do that, since it might appear as "Unprofessional" to our boss.

• 
  CyberMike+AI+Bots=LFG (@CunningLinguini) reported 7 minutes ago

  @GergelyOrosz Good post. Here's my take: connecting several Gmail accounts without a new tab per inbox is the boring win. Codex and Cowork still make you live in one login. That's why it feels like staff.

• 
  Luke (@ldo_dev) reported 7 minutes ago

  Tern sync used to take ~20 seconds. Now it's roughly one 🫡 The trick was asking for less. Before, every check would fetch folder lists, old threads and a pile of mailbox data that hadn't changed at all. Now Tern just asks "what's new?" It grabs the latest mail, pulls in what's needed and gets out of the way. The heavy stuff (folder structure, backfilling old mail) happens quietly in the background. It also adapts to what you're doing: Looking at it? Checks every 5 seconds Inactive tab? Slows down to save battery New mail mid-check? Checks again straight away Gmail, Outlook and IMAP all sync in parallel, so multiple accounts still feel like one inbox. Small change on paper. But the inbox finally feels alive 👀

• 
  RotorBird (@TheRotorBird) reported 8 minutes ago

  Google sent me a “login here” email saying it was ready to go from the recovery… it wasn’t. So… it is now counted as a new attempt and a 7 day lockout from the Gmail. AWESOME

• 
  Erik van Eykelen (@hackteck) reported 9 minutes ago

  I swear Microsoft sits on Claude sign in emails longer than necessary just out of spite. Instant delivery via my Gmail accounts, 5+ minutes via O365.

• 
  J 🦇 (@Ravanaa999) reported 10 minutes ago

  @RajezzO Slow ah ilaya na Nama gmail account link pana any problem? With this browser

• 
  ClawSecure (@ClawSecure) reported 10 minutes ago

  How to create an agent access review schedule. The periodic audit that catches permission creep before it becomes a liability. Permissions accumulate. You gave your agent Gmail access for one task three months ago. You never revoked it. Now it has access to every email you've received since. The review schedule: 🔵 Weekly: check your agent's audit log for any access outside its defined scope. Flag anomalies. 🔵 Monthly: full permissions review. For every MCP server connection: is this still needed? Are the permissions still proportional? Revoke what's expired. 🔵 Quarterly: credential rotation across all agent-accessible services. No exceptions. 🔵 After every incident: immediate access review. What did the agent have access to? Was any of it unnecessary? The review takes 15 minutes weekly and 30 minutes monthly. The cost of not doing it is an ever-expanding attack surface you don't know you have.

• 
  Gabriel (@gbrl_dick) reported 11 minutes ago

  kind of amusing just how bad search is across every platform that's not specifically a search engine. spotify search? atrocious. gmail search? somehow also bad. this seems like a very solved problem

• 
  Monica Cheng (@MeredithCheng22) reported 11 minutes ago

  I used to think “agents in group chats” were a gimmick. Now I think the bigger problem is that too much strategy still lives in my head, and too many useful skills are too messy or sensitive to share cleanly. That’s what changed my mind. I’m starting to think a multiagent should become the default workspace for our growth team. Not because Slack or gmail are unusable. They’re just very good at holding messages, and not that good at holding work. What I actually want is one place where people can @ my Codex directly to ask positioning and strategy questions. A lot of the time the problem is not execution. It’s that people are operating on slightly different versions of what I want. For example, yesterday Mengyao and Alisa pulled me into a meeting to ask what I meant by doing a small creator push for OK eight. My expectation was not “go broad.” It was really 2 different motions: - pure volume: find cheap AI creators at scale - deep collaboration: work with a very small number of creators, but go deep on content, including interviews, reaction videos, and co-created content That kind of nuance gets lost constantly if the only interface is “ask Monica in a meeting.” And honestly, I also forget to sync strategy changes fast enough. Sometimes I change my mind on priorities, or realize an angle is wrong, or want to shift the goal slightly, and I just forget to tell everyone in time. Then different people are working off different versions of the strategy. Nothing is fully broken, but the team drifts. I also want the group to automatically turn the past week of work into a real weekly report. I’ve tried asking people to write trackers before, and it’s painful for everyone. Not everyone is trained to produce polished internal docs, and more importantly, they shouldn’t have to spend time doing that just to prove work happened. What I actually want from a weekly report is: - what worked - what didn’t - what content performed unusually well - whose priorities are off - where output quality is weak - which direction feels wrong That should be inferred from the work, not manually reconstructed afterward. Then there’s the skill-sharing problem. Some of the most useful internal skills are hard to share directly because they expose too much. Sometimes sharing a deep skill means exposing keys. Sometimes it means exposing messy internal setup. Sometimes it’s just too complicated to package cleanly. I built a pretty complex video editing skill recently, and it made this very obvious. In theory I want that capability to be reusable. In practice, sharing it cleanly is hard, and sharing it carelessly is dangerous. I also keep running into a simpler but equally stupid problem: the context already exists somewhere, but I forget to attach it. For example, Mengyao ran a Reddit reply test recently, and the doc from that experiment has a huge amount of signal in it. It could shape product direction, growth direction, and a lot of downstream decisions. But when I’m talking to Codex about strategy, I still sometimes forget to include it. That is such a stupid failure mode. I used to think “agents in group chats” were a toy. Now I increasingly think a lot of teams do not need a smarter agent first. They need a workspace where the agent is already sitting inside the context, absorbing strategy changes as they happen, and using the shared work without everyone manually re-explaining it. We’re going to test this internally for real. I’ll report back next month with what worked, what was annoying, and what turned out to be fake.

• 
  claire vo 🖤 (@clairevo) reported 19 minutes ago

  @BrainHarrington Open gmail in browser and then say "fix my life"

• 
  Omoroboy (@sackamorinnow) reported 21 minutes ago

  @emeka_ug @gmail @YouTube This is the second issue of this kind I am seeing on X in 2 days

• 
  Mike P (@mikepat711) reported 25 minutes ago

  @gusiggins “i have this problem where both of my gmail inboxes are so full of **** and i do not want to face cleaning them up. but i'd love to not have thousands of emails in each. do you think there's a way you could go mop them up for me? i don't want to lose old important emails, but there's so much crap in there that i'd love to get out so my inbox isn't packed”

• 
  Mike Bohn (@MikeBohn) reported 32 minutes ago

  @EatPoopLye @TeamYouTube @gmail Got YouTube and Gmail hacked. They already verified my identity to get the YT restored but giving me issues with email despite proof of ownership since 2013 💀

• 
  InferX (@InferXai) reported 33 minutes ago

  @PandarYogesh Hi. Once you login either using Gmail or GitHub, you will see an option to subscribe..

• 
  🍉crzela (on hiatus) (@cccrzela) reported 34 minutes ago

  everyday i try to recover to get back to doing stuff a new problem arises. someone remind me to migrate all my accounts from gmail to a not-gmail account. can't deal with google's enshittification anymore

• 
  Michael Pepper (@M1CHAEL_PEPPER) reported 34 minutes ago

  @Ghenosis The sucky thing is if you have no data or really slow data, you either won't be able to do it or it's going to be drastically slow. But, I can see where they can set limits and if you're one to be recording a lot of video, you most likely already pay for a decent amount of cloud storage. There has to be a reason they upgraded the 2tb tier to 5tb. But, there are plenty of people who shoot on their phones and prefer local back up. I transfer my clips to external storage and every once in a while delete videos from my devices if their just for my channel or things like receipts. My next phase is to build a NAS and get as much off online cloud storage as I can. I don't trust that Google won't be scanning everything that goes to their cloud. I already disabled the Gmail scanning that they enable by default. I guess if you're buying a Pixel, you are accepting that they will get access to your stuff potentially. I just don't like the idea that things that should be basic are so reliant on internet connection.

• 
  Sophia Orthoi (@SophiaOrthoi) reported 35 minutes ago

  @hfakos @Alonso_GD Mail can be similar as banking. If you run an email server, gmail classifies mails send from it as spam, even if you comply with their conditions. If you ask them why they do it, you get no answer.

• 
  hadjG moh. (@hadj_gesinde) reported 35 minutes ago

  I called her and asked her to search her Gmail for her JAMB login details. I noticed she was pressing the phone somehow, so I collected it from her. I pressed up; Gmail closed. I clicked on Gmail, and Calculator opened. The phone touch had spoiled.

• 
  💫 (@earthwolf_13) reported 36 minutes ago

  @discord Hi Discord Support, I’m unable to log in to my account because I’m not receiving the login email or password reset email in my Gmail. I also don’t remember my password. Could you please help me regain access to my account?

• 
  Sahora (@tin77467) reported 43 minutes ago

  @rabitnetwork We really need for account security such as 2FA and gmail code when login from unknown device to safety real user

• 
  Wasim (@WasimShips) reported 47 minutes ago

  how to plan a full AI product without the chaos (wayfinder by @mattpocockuk ) in <30 Steps : 1. start with one concrete outcome, not a vague idea 2. weak: "build an AI sales tool". clear: "founder connects gmail, agent finds qualified convos, drafts follow ups, asks approval before sending" 3. that one sentence becomes the filter for every decision after it 4. most vibe coded builds skip this and start typing prompts immediately 5. 3 days in the database model has already changed twice 6. onboarding has 4 different half built versions 7. the agent has no clear boundaries on what it can and cant do 8. frontend is stuck waiting on backend decisions that were never made 9. claude ends up rewriting code it shipped yesterday 10. wayfinder's fix: work backwards from the destination and list every open question blocking it 11. for an AI product that means asking what data the agent can access 12. where does company context actually live 13. what can the agent execute without a human in the loop 14. how does a user inspect the agent's reasoning after the fact 15. how do retries and failures get handled 16. what counts toward paid usage 17. each open question becomes a ticket instead of a random note in a doc somewhere 18. some tickets block 5 others sitting behind them 19. example: you need to define agent access before you can design approvals, logs, or permissions 20. wayfinder surfaces which questions can actually be solved right now 21. that's the frontier. claude gets one clear next decision instead of grabbing the easiest feature in the repo 22. every ticket gets tagged HITL or AFK 23. HITL is founder judgement or a real business tradeoff, pricing lives here 24. AFK is research claude can run alone off docs, APIs, the codebase, oauth limits live here 25. one session resolves one decision and updates the map. nothing more 26. resolving gmail scopes usually reveals the approval rules 27. approval rules reveal the activity log 28. the activity log reveals the database model 29. claude keeps the reasoning attached to each decision so the next session isnt guessing why something was built that way 30. once the fog clears run /to-spec then /to-tickets and split remaining work into things agents can run in parallel Hope this helps !

• 
  SG (@sgmlabs) reported 47 minutes ago

  I don't want to sound like an AI alarmist, but I increasingly think AI in the hands of engineers will lead to a devastating world. And the key point here being "in the hands of engineers". This might sound controversial. I would be the first to, in fact, say that engineers still need to be involved in implementing AI. That true agentic experiences are nearly impossible without involvement of engineering. But the more I run into walls with products at some of the most skilled engineering companies (xAI, Google), the more I realize that engineers are just not suitable to govern this powerful resource. In the same way, that engineers are not suitable to govern Customer Support, or Sales Development. An engineer might built a product and a successful company with a customer support. But that customer support cannot be successful and be managed directly by the said engineer. Same with AI. Consider my own recent situation. I got locked out from an old gmail account that I haven't checked in a long time. I have the password; I have the recovery email address. I went through all the steps required to confirm my identity, and was still denied access. Or another recent experience running ads on X. Somehow the system decided that my ads violated their terms (they did not). A duplicated ad got flagged for the same issue. The account is now flagged for life, and there is no recourse. While these are not the fault of AI, and AI can certainly be modified to better handle edge cases, the bigger problem is higher up in the food chain. The problem with treating AI as just another function in the overall user experience, is the misunderstanding of what AI is competing with. When engineering perceive the value of AI, the intrinsic motivation: efficiency and automation. Engineering does not want to deal with the problem, so AI is introduced to automate the solution. But this is an entirely wrong way to think about it. And it is precisely the type of thinking that leads to a Gmail account owner not being able to authenticate into his (my) own account. The right way, in fact, should be to think of AI as a replacement for a person. And a replacement for a person, while a form of automation, is not necessarily about efficiency. In some cases, the AI replacement should actually be plenty inefficient. For instance, when an edge case situation is evaluated. A support ticket comes for a previously automated decision. Efficiency was already applied. To then re-apply the same efficiency, engineers are creating the decision maker and the judge in one body. Dumb AI is a decision maker, the judge, and the executor. That's not how it should be. Some form of AI should always be allowed to have larger freedom to self-correct. And frankly, freedom is not how engineers tend to think about systems they want to control. And how do I know all this? Because I am an engineer.

• 
  Conan the Barbarian (@RandomPerson242) reported 49 minutes ago

  @mikepat711 I just recently did this too. Gmail had been warning me about nearing my cap. I had the AI purge like 50,000 emails of old obvious garbage. Problem solved. See ya again in 10 years when I'm maybe near the limit again.

• 
  Rowena House (@HouseRowena) reported 49 minutes ago

  @FrancesHardinge Gmail seems to be part of the problem.

• 
  Allan Ssenyonga (@ssojo81) reported 54 minutes ago

  @jptorach The problem is the email is just my name. One name, no underscore or numbers. So guys who have no email and are filling in forms simply put their name and add at gmail. So I end up getting their emails. So I suffer because I got onto the service early

• 
  mohitnair_ (@mohitnair_) reported 54 minutes ago

  @ldo_dev Personally, I don't have a use case for Tern. I only got Gmail accounts and don't have trouble managing them. From my pov, the self storage is a good idea for the trust sentive group, but for the broader market it feels like a point of friction. So it might be better as an optional mode for advanced users 👀

• 
  Dean Hunt (@deanhunt) reported 58 minutes ago

  @poteto @billykyle Anything that solves the issues with loading sites. Gmail works well, but a significant amount of sites and services have it detected as a bot and won’t work. MCP integration to X feels like low hanging fruit too :)

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 58 minutes ago

  GROKBOT JUST MADE AI TEAMS STUPIDLY EASY TO BUILD. But after 20 minutes of testing it, I hit the problem that could kill the whole idea. Why Grokbot is interesting: → Telegram-style interface for managing entire AI teams → Give different bots different roles, including a CEO bot → Agents get their own computers in the cloud → Connect tools like Gmail with a couple of clicks → No Mac Mini, terminal setup, API gymnastics, or local model decisions Where it falls apart: ✓ My supposed week-long trial ran out of usage credits in roughly 20 minutes ✓ Computer use burned through tokens while struggling with a simple CAPTCHA ✓ You're currently locked into Grok rather than choosing Claude/local models ✓ It's not open source, so pricing, limits, and model access aren't under your control My current AI agent ranking: ClaudeBot: 3/10 looking back Hermes Agent: 6–7/10 Grokbot: 6/10 Grokbot wins on simplicity. Hermes wins on control. If Grokbot can fix the usage limits without destroying that simplicity, this gets VERY interesting.