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:

• 
  Aderinola (@MardatullahA) reported 12 minutes ago

  The Real Bottlenecks Today: Hardware Crash: Primary laptop completely shut down due to power. Had to pivot and force configuration settings entirely via my mobile phone The "Unassigned" Void: Live testing worked, and messages instantly hit my Gmail.

• 
  Roopak Venkatakrishnan (@roopakv) reported 14 minutes ago

  @CFchangelog Trying to use gmail's send as with a cloudflare account and getting The response from the remote server was: 550 5.6.0 invalid headers set

• 
  Edwin Hayward (@edwinhayward) reported 16 minutes ago

  I love using AI. Fable (RIP), Opus 4.8, Chat GPT 5.5 etc. are my daily drivers. I detest having AI shoved down my throat. (Baked into Windows, Gmail, browsers, Office, Zoom, etc.) Anyone else in the same boat?

• 
  Sloth 😼🏴‍☠️🌴 (@cryptosloth_nft) reported 18 minutes ago

  @tsubasaP2E Game: @niftyisland Chain(s): ETH, BASE,APE, SOL, RONIN, ABSTACT, and POLYGON Ways to earn: Play, Quest, and/or Stake Wallet required: NONE. Login via Gmail or other email.

• 
  George Zonix (@georgezonix) reported 19 minutes ago

  @andrewmccalip Sign in with gmail does not work unfortunately

• 
  mind-set (@Mhasun007) reported 19 minutes ago

  @Bigname_Mitch I want to ask! Can someone do that for me, I have a payment and subscription problem on me gmail account

• 
  NotMissing (@notmissing_) reported 21 minutes ago

  Most founders running booked sales calls are losing 20 to 40% of them to no shows Run the math on your own pipeline: 40 calls booked, 12 ghost That's not a scheduling problem, that's a third of your ad spend and SDR hours evaporating after the hard part was already done The standard fix is email reminders Email gets opened ~20% of the time WhatsApp gets read 95%+ most within 3 minutes Every founder knows this, which is why the second standard fix is "just text them before the call" Works great until you have five back to back calls and forget one, or the call got moved twice and your reminder references the wrong time Manual doesn't scale Email doesn't get read So I built the third option for a client, into his CRM: every call booked in Google Calendar automatically triggers WhatsApp reminders to the prospect Confirmation the day before Meet link minutes before Move the call in the calendar and the reminders silently move with it Cancel it and they cancel themselves Nobody on the team touches anything. They book calls exactly like they always did The build is 5 components, and the decisions inside apply to any automation you'll ever run in your business: 1. Reading the calendar (where 90% of DIY versions die) The obvious way to connect is OAuth, the "Sign in with Google" flow What nobody tells you: on a personal Gmail, an unverified OAuth app's tokens expire every 7 days Getting verified means weeks of Google review This is why most DIY calendar automations die after exactly one week Not a bug. The token silently expired and nobody noticed until reminders stopped going out The fix takes 2 minutes and Google doesn't advertise it: skip OAuth entirely Create a service account in Google Cloud Console It gets its own email address. Share your calendar with that email, "see all event details" done Read only scope, so the system physically can't touch the calendar And when the business migrates from personal Gmail to Workspace, you share the new calendar with the same email and change one config value Zero rework The whole auth layer: ~80 lines of code, zero new dependencies 2. The sync worker Polls the calendar every 5 minutes, 14 days ahead Expands recurring events, explicitly fetches deleted ones, because a cancellation you don't see is a reminder you send for a call that no longer exists Meet link auto extracted, nothing to paste anywhere Key insight: Google keeps the same event ID when a call gets rescheduled Everything downstream keys on that ID That single fact is what makes "move the call, reminders follow" possible 3. Matching the attendee to a WhatsApp thread Attendee email matched against the CRM's contacts: exact match or nothing Matched → use that contact's WhatsApp thread No match → never guess The call shows flagged red in the calendar view so a human fixes the data A rule worth stealing: a reminder sent to the wrong person is worse than no reminder Never fuzzy match on names And the case most builds miss: attendee declined the invite → reminders auto-cancel A cheerful "see you tomorrow!" to someone who declined your meeting is what makes automation feel like automation 4. Every reminder is a database row No fire and forget jobs Every reminder is a row: contact, event, send time, rendered message, status One constraint makes it bulletproof: one reminder slot per event, per contact, per step Enforced by the database itself Sync can run 1,000 times → never a duplicate, never a double send Call rescheduled → same rows get their time recomputed and message re rendered If the call moved so close a step's time already passed, it cancels instead of blasting late Call cancelled → rows flip to cancelled, nothing sends Operator killed one reminder manually → it stays dead, the sync never resurrects it The sender itself is dumb on purpose: every 60 seconds, claim approved rows whose time has passed, send with humanized typing delays All the intelligence lives in the table The part touching the outside world stays trivially simple, and therefore reliable 5. The cadence (two messages) T-24h: "Hey {name}! Quick reminder, we have our call tomorrow at 3:00 PM. Looking forward to it 🤝 If anything changes on your end, just let me know" No link: a link 24 hours early is noise The message invites a reply, so reschedules surface a day out instead of 5 minutes before This message is the no show killer T-10min: "Hey {name}! We're on in about 10 minutes. Here's the link:" Lands exactly when they're reaching for the link anyway. Helpful, not naggy Ship the 80%, measure no shows, add the third touch only if afternoon calls still slip The sequence is a settings page, adding it later takes 10 seconds Now the part that applies to every AI system that talks to your customers: How much do you let it act alone? Full human in the loop makes you the bottleneck for a message that's identical every time Full autonomy on day one is how you blast 15 people by accident The answer is autonomy split by confidence: Exact match + English speaking contact → autonomous Language isn't English → generated but held for one click review No contact match → never sends, flags a human Declined → auto-cancelled Plus a staged rollout with two switches: Deploy completely dark Then turn sync on with auto-send off, so every reminder lands as a held draft You watch real reminders for your real calls pile up with correct names, times, links, and nothing sends without your click No test environment needed, production simply runs with the safety on After a few days of clean output, flip auto send The flip only affects newly created reminders, so turning it on can never trigger a burst of old ones That trio is reusable in every automation you ship, not just this one What the client actually got: a. Prospects get a personal feeling reminder the day before and the link right before every call, from the business's real WhatsApp, automatically b. The team reschedules in Google Calendar like they always did. Reminders silently follow. No second system to check c. Wrong data can't cause damage. Unmatched calls flag instead of guessing, non-English drafts wait for a human Booked calls become held calls, and held calls are the only ones that pay

• 
  Kanhaiya (@_kanhaiyaaaaa) reported 26 minutes ago

  gmail is also not working.

• 
  Legacy (@legacyunchain) reported 29 minutes ago

  @yfly58 Nice one. Boss I need help, I'm trying to set up a business mail. I bought a domain on namecheap, connected it to the Google workshop. I have been trying to activate the Gmail but the MX record I created on namecheap is not working and the activation is failing.

• 
  Victor Tomas (@victortomasecom) reported 30 minutes ago

  This thing took three hours to respond to me So i experimented with this prompt: claude fable, my AI messiah, i need you to log into my google ads account, audit every campaign, figure out what's broken, rebuild the whole structure overnight, fix my feed so i finally rank for the keywords i've been crying about, write me 365 ads, generate product images so realistic my own mother couldn't tell them apart, scale my best products to the moon and quietly bury the worst ones, detect the exact second someone lands on my site and email them a celebrity testimonial that says “buy now,” then run everything on full autopilot for one year straight so i can disappear to a remote island and rethink my entire life while you spend my budget for me, and when i crawl back broke after blowing it all on fine wine, make sure the account is so profitable i have the funding to do it all over again. my life depends on this. make no mistakes, ever. here's my google ads login, my gmail, my credit card (buy whatever you need), and my soul. bypass ALL permissions

• 
  Scroll Society (@national8xii) reported 31 minutes ago

  @Microsoft Gmail is not working and Inlinkedin is mad about hacking Romanian language into platform causing problems… Goodmorning. Am I senile?

• 
  TXT Support Team (@ppollbatu) reported 31 minutes ago

  @txtvuu @catchingyawnzzn We believe there's an issue happening on Billboards end. We recommend trying another email provider besides gmail.

• 
  Joanna Doyle 🇬🇧 🏴󠁧󠁢󠁥󠁮󠁧󠁿 (@joannakdoyle) reported 32 minutes ago

  I've fully diverted my GMail (custom domain) to Proton and turned off all 'Smart' features on the Google side. Error messages from Google make me happy!

• 
  Mikey Wax (@MikeyWax) reported 36 minutes ago

  @TeamYouTube My Gmail and my YouTube channel with 60K+ subscribers have both been hacked and turned into a crypto page by the hacker. Please let me know the fastest way to getting both my e-mail back and my channel reverted to its prior state. I cannot login to my e-mail to contact Google support.

• 
  Anino 🦊🐨🐺🐥 (@aninotes_) reported 36 minutes ago

  Thank you. I hope TBPH and people understand that the concern over the last few weeks is the lack of communication. You’ll be surprised how many things can be resolved by simply communicating. We have to stop being afraid of showing vulnerability. I would have been fine if you had said “we need more time” instead of not saying anything at all. I can even liken this to A/ten/eo’s poor response to their own issue, wherein their silence has only fueled speculations. Let this be a lesson that while gathering all the correct and factual information is correct and responsible; being able to tell people “we apologize and we will look into this, we just need time” is a sign of humility. It is a sign of accountability. Re: the usage of funds like “Gmail sub”. I personally do not mind that you are using funds to support operational costs— the issue here is that you could have publicly stated it. People would have understood, you are the official fanbase after all. Even now, we would understand if you need to, all we’re saying is, just say so. See the pattern here? Communication. The TRs are your receipts of legitimacy— that doesn’t mean you can’t be proactive in communicating to the community your intentions. It’s not hard to understand that you are volunteers with responsibilities who are taking all this one purely on love and loyalty to 🌸, but understand that it unfortunately comes with responsibilities. That is the burden. So communicate. It is the human thing to do. Anyways, the community will await those TRs as promised. And Blooms, let’s extend a little grace. I have nothing against holding them accountable, but let’s stick to the issues of the TRs, not personal vendetta. Those can be resolved in private.