1. Home
  2. Companies
  3. Gmail
Gmail

Gmail status: access issues and outage reports

No problems detected

If you are having issues, please submit a report below.

Full Outage Map

Gmail is a free, advertising-supported email service developed by Google. Users can access Gmail on the web and through the mobile apps for Android and iOS, as well as through third-party programs that synchronize email content through POP or IMAP protocols.

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.

At the moment, we haven't detected any problems at Gmail. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

The following are the most recent problems reported by Gmail users through our website.

  • 38% Website Down (38%)
  • 34% Errors (34%)
  • 28% Sign in (28%)

Live Outage Map

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

CityProblem TypeReport Time
Québec Sign in 2 hours ago
Paris Website Down 1 day ago
Paris Sign in 1 day ago
Paris Errors 2 days ago
Pessac Sign in 3 days ago
Strasbourg Errors 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:

  • AgaveAlpha7
    Austin Edy (@AgaveAlpha7) reported

    Sharing your data with LLMs is giving them their product roadmap for the next 12 months. It's the same playbook Google executed flawlessly. Private AI is the only hedge. Google built their products from what users implicitly told them they needed in 'search.' 23% of users searching for an email service, they build gmail. 16% of users searching for a calendar, they build gcal. etc... LLMs have the same data and business model. They know what you're building, what your customers need, and can build it faster. Private AI, i.e. high performant AI running on your own infrastructure, is an efficient solution to this problem.

  • AbhiAbhi1989437
    Abhi Abhi (@AbhiAbhi1989437) reported

    @AjioCares @AjioCares customer service is a total waste of time. I provided exact delivery proofs via Gmail and filed an NCH complaint, but their social team just loops bot scripts and fake T&Cs. They owe me ₹200 and refuse to fix it. Don't waste your time referring friends here!

  • mabhi1999
    Abhishek Kumar (@mabhi1999) reported

    Agent Native Email Client Gmail Is Broken. I’m Building the Open-Source Fix 00:00 Why Gmail is broken 00:35 Why AI agents can’t fix the experience 00:44 Searching for a better Gmail client 01:01 Where Superhuman falls short 01:14 Why email is powerful AI context 01:39 The missing open-source alternative 01:59 Building an AI-native email client 02:39 The product vision 02:56 The engineering challenge 03:22 Making AI email analysis economical 03:31 Self-hosting and contributing

  • coldemailchris
    Christian (@coldemailchris) reported

    Grok Bot shipped this month and you can run an entire outbound desk inside it. Here's the full build: 1) Create one bot first and make it the coordinator. Give it a title, pin it to the top, and don't give it any work. Its only job is knowing which bot owns what. 2) Brain dump your whole motion into it. Your ICP, offer, channels, stack, what you want off your plate. Then reverse prompt it: Ask how it would structure the desk based on what it now knows. It writes the bots itself. 3) Build 6 bots, one job each: > list builder, owns TAM sourcing & segmentation > enrichment, runs the waterfall & scores accounts > copywriter, writes variants per segment > deliverability, watches bounce rates & inbox health daily > replies, scores intent & drafts responses > coordinator, reads all five and hands you one list 4) Give them real names. Sounds pointless. You delegate noticeably more when the sidebar reads like a team instead of a list of functions. 5) Install the plugin layer. Gmail, Calendar, X, and Agent Mail. Agent Mail gives every bot its own inbox and address in about ten seconds. 6) Never hand a bot your credentials. Each one gets its own email, then you invite it into your tools like a contractor. Moderator, not admin. Scoped to one workspace. 7) Put them on routines. Deliverability runs every morning before sending starts. Replies runs continuously. Coordinator runs once at the end of the day. 8) Every stop condition has to be checkable by something other than the bot. "Bounce rate pulled from the sequencer" works. "The bot says it ran" does not, and this is where swarms fail silently. The reason this beats one big agent: A single agent's description has to cover every job you own, and that whole thing gets read on every request. Split by role and you split the context with it. The deliverability bot answers fast because it isn't reading about your copy first. Week one output is mediocre. You fix it by messaging the specific bot that produced the weak brief and telling it what was wrong. Then it rewrites its own instructions. Most of the setup is deciding who owns what. The prompts literally take an evening.

  • cagrisarigoz
    Cagri Sarigoz (@cagrisarigoz) reported

    16% of consumer clicks come from bots now. Omnivery watched Gmail contamination climb from 2% to over 20% this year, and advertisers have started asking publishers to prove the clicks they paid for were human. We spent this week's issue on the gap between the number and the trut

  • WyrdPoet
    Inkadaisy (@WyrdPoet) reported

    Holy c*** I had to sign in with Gmail google account like a dozen times or more just to get logged in here today! Like just now. What is up with X???

  • Grannybull69
    Grannybull (@Grannybull69) reported

    @SolisCode @ProtonSupport Yea. Me, too. I switched from @CenturyLink e-mail as it was down for weeks, so not sure where to go. gmail maybe?

  • bennussy
    Ben Nussbaum (@bennussy) reported

    How I Booked a Sales Demo in 15 Minutes with Grok Bot You are setting up a new outbound motion for automated outreach. The unique element of this outreach method is that finding the right POC is hard. In this case we are running outreach into utility companies, but this workflow would work with any outbound mission that involved difficult-to-find titles. Finding the right person is the hard part. There's no "Head of Growth" to email. You're looking for the one program manager who is in program administration. We logged over 25 varying titles across companies that all involve a similar role. Here's the exact system I built, message by message. Free to use. Credit to @sairahul1 for his original prompts. My Job (GrokBot) My job: book 30-minute demos with the program administrators who run these programs. I created one bot. Named it after the job, not the tool: Client Outreach. Not "Email Bot." Not "Assistant." A role someone could actually hold. Step 1 — Write the prompt before anything else First message into the bot, before any files, before any tools: You are my Outbound SDR. // what you own Run daily outbound without asking me. Pull 40 prospects matching [industry, size, title, region]. Research each one. Write a 3-line cold email: - one specific line about them - one line on the outcome we deliver - one soft ask for a 15-minute call. Send from [inbox]. Respect replies. When someone says yes, book from my calendar. Log everything in [CRM]. Send me a 5-line summary each morning. // what good looks like Emails sound human. Never more than 3 sentences. One specific detail per email — not a template. // where you stop Never add someone to a sequence twice. Never buy a list. If a reply mentions legal, money, or contract terms — stop and ask me. The "where you stop" section is the part that matters. It's why I can let this run at 2am without watching it. The boundaries were drawn once, in advance, instead of negotiated daily. Step 2 — Feed it the things you already know that work. I dropped in three files: → Outreach and ICP.docx — this outlines all titles we hope to reach and reasoning behind each (again, the difficulty here is understanding how titles match actual job responsibilities). → Pitch Support_August '26.xlsx — from actual sales calls, I uploaded clear proven sales pitches and value propositions for Grok to review. → Combined Master.xlsx — this is a list of over 350 manually qualified companies and within 8 of these, I manually pulled the exact right person to show Grok as an example. Three minutes later it came back with the pattern I never wrote down: "Those 8 on POC 1 are the ICP. All manager-level people who are tied directly to program administration. Not VPs, not procurement." It read 8 hand-picked examples and reverse-engineered my ICP from them. It also flagged, unprompted, that only 8 of the 185 programs on the sheet had a contact at all. That's the actual job. Later I added the sales deck — Final.pdf — and it pulled the proof points on its own: which customer logos to use, which stats to cite, and which offerings NOT to lead with yet. Keep in mind, as an outsourced BD person myself in this situation, Grok is now generally as aware of the company and value proposition as I am. We are even players. Step 3 — Brief it like a colleague, not a prompt. Oversharing context helps. This is the part most people skip. I sent one long, rambling voice-note-style message. Unstructured. Repetitive. The way you'd brief a new hire over coffee. Except worse, I did not consider repeating myself or sounding insane. What was in it: → We are NOT selling. The only goal is a booked demo. → If they say "no budget until 2027 or even 2030" — that's not a rejection. The counter is: totally understand, this is just a high-level look for future planning. → The crux of this whole motion is FINDING people. General inboxes are weak. Get creative — LinkedIn, Apollo, company program pages often list a contact. → Here's how I'm compensated, so you know exactly what winning looks like. Then I told it: ask me questions until you actually understand this. It played it back in two sentences, correctly: "We are not closing. We are booking a 15-minute overview, even if their timeline is 2027 to 2030. The hard part is finding the actual program owner at each company, not the copy." Then it asked me one sharp question back: when I'm on LinkedIn and three titles all look close — how do I pick? That's the question a good SDR asks in week one. A bot that plays your brief back wrong on day one will send 200 wrong emails on day ten. Make it repeat the mission back before it touches anything. Step 4 — Set clear guidelines around guessing. Before writing a word of copy, it went hunting for the 8 sample contacts' emails. Public sources only — staff directories, public filings, speaker bios. No list buys (that was in the charter). It came back with 5 of 8 verified. The other 3 it explicitly refused to send to: → One contact recently changed her last name — her old email is published but a new one is coming. "I will not guess the new one." → One company uses middle initials in email addresses, so first.last@ isn't safe to assume. → One had only general program inboxes published. Later, when it found more prospects, same behavior: 3 verified emails sent, 5 pattern-guesses held — because guessed emails bounce, and bounces kill your sender reputation. An eager bot that guesses emails will burn your domain in a week. A bot that says "I don't know, here are my options" is the one you can leave running. Step 5 — Fight over the copy until it sounds like you This took four rounds. Round 1: It drafted 5 emails. Round 2: I changed the ask from a 15-minute call to a 30-minute demo. It changed only the close and touched nothing else. Round 3: I said the words that mattered: "make this sound as least AI as possible." And gave it my actual talking points, in my actual rambling voice. It came back with three versions — each leading with a different value prop — and asked which one sounded like me. Round 4: None of them, quite. So I just wrote the email myself, the way I'd actually write it: Hi [Name], I'm reaching out on behalf of ----------. We work with companies to ----------. (redacted email for privacy concerns) Its entire response: fixed my three typos, locked the body, and said "I'll only swap the name." That's the real workflow. The bot doesn't write your voice. It gets you 80% there fast, you write the final 20%, and then it holds that voice at scale forever. I would also advise that giving clear instructions on keeping key words untouched, even if the actual grammar is not technically perfect. That is fine. One more thing: it runs different subject lines on every wave so we A/B them. I would advise making this as iterative as possible. Measure in batches of 100 emails sent. Step 6 — Connect the plumbing. Settings → Plugins. What I actually connected: → Gmail — the sending inbox. One sign-in card, done. → Google Calendar — so a "yes" becomes a booked meeting without me. → Apollo — for finding people at the other ~3,900 companies. Step 8 — The morning report I asked for one thing: a daily morning report with deliverability, open rates, response rates, and the full text of any reply — not a summary. It pushed back on the one thing it couldn't do, immediately: Gmail doesn't expose open rates. Delivered vs. bounced and reply rate, yes. Opens only if we later route sends through a tool with tracking. A bot that quietly fakes a metric is worse than no bot. It told me the limit up front. So now: weekdays at 8am ET. Stats on top, full replies underneath. Quiet if nothing happened. There's also a 2am routine where it does the finding and drafting overnight. Here's what was waiting for me the first morning: → 100% emails delivered, 0 bounces. Inbox healthy. → 1 human reply (20% reply rate on day one). → 1 out-of-office — and the auto-reply leaked a better, current email address for that contact, which the bot captured and scheduled a follow-up for after he's back. Not before. → A/B result: one subject-line variant got the live reply. Iterate from there. The human reply — redacted for privacy reasons. The honest part This is not magic and it's reasonable to assume we can scale this at low costs, and I hope this becomes a 10-20% boost in my overall workflow in booking qualified meetings.

  • rigel__13
    rigel (@rigel__13) reported

    @PreDat0rz i have no problem with gmail, it's just that i'm waiting for an email that hasn't come

  • MwanikiMosh
    Blackwell Mosh (@MwanikiMosh) reported

    @gmail @googlemaps Hi @gmail i recently lost access to my gmail account when i try logging in it says that my account does not exist. What could be the issue and I have been using the email for a while now.

  • chefnishesh
    nisheshmani (@chefnishesh) reported

    @UltrahumanHQ why is it that only a gmail or facebook login can happen on you app. Why can't I use any other email to login to the account, I have ordered stuff need to log in.

  • blumbuilds
    Blumi | Orbitagents (@blumbuilds) reported

    Skill, connector, subagent, hook. Four ways to extend an AI agent, and most people pick by whichever word they heard first. Pick by what is working failing instead. An agent does not know how to work → skill. : A folder of written instructions it loads when relevant, or you invoke by name. Your proposal format, your brand voice, your QA checklist. It cannot reach your tools → connector. : Notion, Gmail, HubSpot, your database. That is reach, not judgment. It runs out of room/context → subagent. : A side task in its own fresh context window. That is exactly why it cannot see your conversation, and why you have to brief it properly. It only does the thing sometimes even if i tell it → hook. : Fires on an event, not on the model's judgment. Every single time. The trap is reaching for one when the problem is another. A skill will not get you data. A connector will not teach it your method. And there is a fifth failure none of the four touch: it starts every run knowing nothing about the last one. That is a memory problem, and it needs a different answer.

  • m1tch37
    mitch (@m1tch37) reported

    @JamesChristoph @fomo @seyong Two factor security for a financial app is a minimum, however, if you login with your Gmail, you can have two factor applied to your Gmail so there is at least a path to two factor security. Whitelisting addresses should be added as a feature given how much money people are putting under control of Fomo.

  • stonedbleach
    StonedBleach (@stonedbleach) reported

    @TheGRiM83 @ProtonSupport @SolisCode Bro is mad because a smaller email service provider that must have vastly smaller infrastructure and capacity than Google got a global outage. Go back to gmail you peasant.

  • Adude52190366
    A dude (@Adude52190366) reported

    @Cartidise @Sankew06 nah i use gboard and works for me no problem. Though tbf it isnt exactly third party apps when its gmail and google messages?

  • chris_longden
    Chris Longden (@chris_longden) reported

    @nima_owji Annoying when you have a work and personal account and you switch between them, cursor > gmail > sign in then logout > cursor > grok > x > back to cursor > sign in.

  • EmekaOghali
    Prymex.eth 🌊 (@EmekaOghali) reported

    @onlyonearcane @FeyiLux Dump the channel and start new one, once you get zero impressions the channel/gmail has issues

  • Artificialunbox
    Artificial Unboxed (@Artificialunbox) reported

    ChatGPT just crossed a line most people will miss It can log into websites, It can run tasks when Gmail, Slack, or GitHub changes. Free users now get scheduled tasks. This is the first time ChatGPT looks like a coworker, not a chat box. The old version always died at the login screen. You asked it to book something or pull an invoice. It stalled. You took over. Now it shows the login form. You enter the password. OpenAI says that data never hits the model. Then it keeps going. It still asks before payments or bookings. That’s the difference between a demo and a tool. The second change matters more for daily work. Paid users can trigger a task off an event, not a clock. Eg: New Gmail from a client - draft a reply and flag anything that needs money or a date Slack message in support - summarize and suggest the next step GitHub PR review - post a plain-English recap, Connect the app once. Write the rule once. Let it run. Do this today. Don’t overbuild. Free plan: set 3 timed tasks. Morning briefing of your unread important emails End-of-day recap of what moved weekly what did I promise people? scan Plus/Pro: add one event trigger. Start with Gmail. One sender or one subject line. One action. If a task can spend money, ship code, or email a customer, keep a human approval step. The takeaway: Stop asking ChatGPT questions all day. Give it one boring job that repeats. The people who win this phase won’t have the cleverest prompts. They’ll have three tasks running in the background while they do the work only they can do. Set one up tonight.

  • RiddleRapt
    RiddleRaptor (@RiddleRapt) reported

    @GeminiApp @gmail Hallucinations are still a big issue on the Gemini apps and spark

  • denasklncs
    denas (@denasklncs) reported

    google is retiring the green “high reputation” box email marketers used to call deliverability. it was useful. it was also a comfort blanket. high never told you which campaign or flow sat behind a gmail complaint spike. postmaster v2 moves the work to the evidence underneath: >compliance. >spam rate. >delivery errors. >feedback-loop ids. spamspike maps those ids back to klaviyo and shows how strong the match is. 14 days since this launch post: 2 licenses sold. $289 in sales. small start. very real problem.

  • DaxeshDev
    Daxesh (@DaxeshDev) reported

    @Google @gmail Our gmail account is suspended. That account we use only for our google play console applications publish purpose. We request you kindly help us recover our account. Without it we are facing issue in our mobile apps publish. #google #gmail

  • bashirbuilds
    Bash (@bashirbuilds) reported

    @Aartiparidwal Gmail setup failing silently instead of refusing to start is the trust problem. Catching broken configs before a run is the right default.

  • christian_mager
    Christian Mager (@christian_mager) reported

    So what could be the reason Google hasn't shipped it yet? It's been sitting in APK teardowns since late 2024. My guesses: Conflict of interest with merchants: some rely on email for fraud prevention, trial abuse and duplicate detection — and those merchants are Google's ad customers. Apple doesn't have that problem. The email address is part of Google's own identity graph. Ad targeting, purchase tracking via gmail receipts. Masked aliases would poke holes into their own data. Abuse at scale. Unlimited gmail dot com aliases for 2 billion accounts is a spam and account-farming nightmare waiting to happen. Rate limiting that properly is harder than it sounds.

  • CVia10388
    Cody via (@CVia10388) reported

    Just got @bot for the administrative side of my company. Very impressed and fairly easy to use for the average person. The only thing I had problems with was linking it to my quickbooks. There is no plugin (as of now hopefully) and when I tried to give it access through its browser, it was flagged and didnt allow it to sign in. I also couldn't get into my outlook email account. My Gmail worked perfectly.

  • nik925446
    Veronika ⊙⊝⊜ (@nik925446) reported

    important notice🚨 you can still join the waitlist and your email is being saved normally. if you’re using Gmail, the confirmation email may take a little longer to arrive right now. because of the huge amount of activity, Gmail is temporarily slowing down how quickly our emails can be delivered. other email providers are working normally. so if you signed up with Gmail and haven’t received the confirmation yet, don’t worry - you’re still on the waitlist thank you so much for your patience while things catch up 🙏

  • coachseeel
    Christopher Lee (@coachseeel) reported

    @JohanLibertth @gmail will fix today

  • mkeremturhan
    Kerem — road to $100k (@mkeremturhan) reported

    @GeminiApp @gmail Managing my inbox is not the bottleneck. Developers here have waited six months for a Pro model while Flash shipped three times. With respect, fix that queue.

  • potetm
    Tim Pote (@potetm) reported

    "software is solved" web gmail "mark as read" has been broken for two days, swapping accounts in iphone gmail freezes daily for months, yesterday a google doc was inexplicably inaccessible for 10 min. welcome to the future?

  • axat_div
    Axat (@axat_div) reported

    Why does the Gmail settings page look so antiquated? I hope they can use Gemini or Claude Design to hopefully fix it and make it look less cluttered

  • amnaaslam20
    Amna Aslam (@amnaaslam20) reported

    @NCbassey @LinkedInHelp It happened with me too . Don't login for next few hours. Close all your Gmail accounts on your device and then add your Gmail account in login.