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:

• 
  Rohan Shrestha (@rohanshr_) reported 9 minutes ago

  First lie your dashboard tells you: "sent" doesn't mean "seen" Klaviyo said it hit 18,000 people. reality: – deliverability score sitting at 62 (anything under 70 is a fire) – dropped 4 more points in a month – DKIM broken, no DMARC at all gmail couldn't even verify it was them. straight to spam.

• 
  Ibrahim Mokdad (@ibmokdad) reported 9 minutes ago

  founder mornings are not slow because you lack a dashboard. they are slow because every app screams at the same volume. calendar: investor call slack: customer blocked gmail: numbers needed before noon github: checkout PR waiting linear: launch task overdue stripe: payment warning i made a @NousResearch Hermes morning control tower over sample signals. it turns the pile into: - do first - decide today - reply today - watch - ignore on purpose the important part is the last one.

• 
  Ayyaz Ali (@AyyazAliFurqan3) reported 10 minutes ago

  My A2P campaign keeps getting rejected for having a "public email" on the account. The thing is, I've already updated every email I can find. Notification email, profile email, all of it. All pointing to my brand domain now. The one I can't update is the authorized representative email on the approved business profile. That one still has my original Gmail from when I first created the account. And apparently that's what's triggering the rejection. Here's where it gets annoying: the @twilio API returns an error saying the field is in an "immutable state" once the brand is approved. So I literally cannot change it myself. I opened support tickets asking @twilio to update it on their end, and that was over two weeks ago. Complete silence. My use case passed. My CTA passed. The only issue is this one locked email field. So I'm reluctant to create a brand new business profile with the same details and resubmit everything from scratch, especially since any new A2P campaign would still have the same authorized rep Gmail unless Twilio manually changes it. Three rejections in now. A month into the process. the campaign rejects because of the Gmail, but I can't change the Gmail because the brand is already approved and locked. Can anyone please help me with this issue.

• 
  Irka IRON Pawłowski (@ironirka) reported 10 minutes ago

  The AI word of the week has been "loops" — adding yet another piece of jargon to the non-technical vocabulary. This is leaving a lot of people asking: what are they, how are they different from prompts? In a lot of non-technical circles the level of grey about what the parts of agentic AI actually are (and how to use them) can be overwhelming. What's more, they're not static — as things develop, so do their uses and how they work together. Loops themselves have evolved over the last few years. So, here's a little primer to make things easier: Prompt — we know this one. It's the instruction you write for the LLM. You send it, get your output, and any tweaking happens off the back of that output. Prompts are for one-off tasks. As you build reliable ones, you reuse them by pasting them into the terminal or chat. Agent — (this one we know too) the LLM running on its own, doing a series of steps without you watching each one. You give it a goal and walk away. Call — to invoke something by name so it runs. You "call" a skill (or a loop, a tool, an MCP) by typing its name and the LLM loads it and executes the setup. When you ask your LLM to use a skill, hook or loop you are calling it. Skill — a packaged set of instructions, files, and tools the LLM loads when you call it by name. A prompt is just one-off instructions; a skill brings the working setup with it — what to read, what rules to follow, what tools it can use, what to produce. You call it once and the whole setup runs. Some people stuff all this into their CLAUDE.md, but bloating CLAUDE.md causes context issues and the LLM starts ignoring your instructions. That's why skills are for specific contexts and tasks, not general ones. The rule of thumb is: when you have a task you do over and over, with rules → make it a skill. Call it by name instead of re-explaining the rules every time you want it done. Hook — a rule that says "when X happens, do Y." It executes automatically when triggered — a file is saved, a meeting ends, a session starts — and the hook runs the action you tied to it. These are basic automations. Use them when one task is dependent on a different event. Example: You save a new invoice PDF in your invoices folder → a hook automatically triggers your expense categorization skill and logs it in your accounting sheet. Loop — a small program you write that runs a prompt for you, over and over, and checks the work was done properly. It isn't the prompt itself — it's the thing that runs the prompt without you in the middle. Loops are more complicated than hooks and are not prompts. Where a hook does one thing from start to end when triggered, a loop initiates a process from start to end automatically at a time you define. Where a prompt is instructions, a loop is the directive to use those instructions. Use it for repeatable tasks where you're confident in the output and want them running without starting each one yourself. The loop runs the skill, checks the work, stops when the rules say so. Example: A daily "process inbox" loop that runs every morning at 9 a.m., summarizes new emails, extracts action items, self-verifies, and only pings you if something needs your attention. Loops only work if you set them up properly. A few things worth understanding before you do: - Self-verify — a step inside a loop where the LLM checks its own work against the rules before saving or moving on. Without it, the loop produces confident garbage. With it, the loop catches and fixes its own mistakes. - Simple loop vs supervisor loop — a simple loop is one LLM doing one task on repeat. A supervisor loop is a top loop that spins up several workers in parallel, each running its own prompt, then combines their output into one result. - Token budget — a hard cap on how much the loop can spend before it has to stop. Tokens are what the AI charges for, like minutes on a phone bill. Without a cap, a stuck loop can rack up hundreds overnight. Remember when you write you see words, the Agent sees tokens. - Orchestration vs execution — the loop orchestrates: decides what runs, when, and in what order. The LLM executes: runs the actual prompt and produces the output. Two different jobs. - .md files (markdown) — a plain text file the LLM can read. This is where most of your directions for an AI — instructions, rules, context — live. It's how you tailor an LLM to your project. Common ones: CLAUDE.md / AGENTS.md / GEMINI.md (depends on the LLM you're using) — master instructions for a folder or project. They live in the folder you launch the LLM from. The LLM reads them automatically when it starts working. These are the house rules for your project or workspace. SKILL.md — the instruction file at the heart of a skill. Tells the LLM what the skill is for, when to use it, and how. ADR (Architecture Decision Record) — a decision written as a rule the AI can apply. Format: what was decided, why, and what to do or not do because of it. ADRs are a development artefact, so most non-technical users don't touch them — but using them can substantially improve the output of your agents. If there's a rule you want the AI to always check its work against → write it as an ADR in a .md file. Any skill or loop can then check its output against the ADR before saving. This is one way of "harnessing" the agent — making sure its output matches what you're actually building, from meeting notes to full products. SOP (Standard Operating Procedure) — the process for a recurring task, written step by step so the AI can follow it. One SOP per repeating job, just like any standard process. The skill running the job reads the SOP for the steps. Note on terminology: The concepts above are fairly universal, but exact names, file conventions, and implementation details vary by tool (Claude Code, Cursor, Windsurf, etc.). You might see CLAUDE.md, AGENTS.md, .cursorrules, or different triggers depending on which system you're using. Other things you might be reading/hearing: CLI (Command Line Interface) — your terminal or Command Prompt window, where you type commands instead of clicking buttons. Most coding AIs live in the CLI. MCP (Model Context Protocol) — the standard that lets the LLM talk to outside tools and services. Without MCP, the LLM only sees what you paste in. With MCP, it can fetch your Gmail, read a Notion page, update a Google Doc, post to Slack — directly, on its own. How they fit togetherPrompts live inside skills. Skills live inside loops. Loops initiate via hooks or schedules. All of them read .md files — CLAUDE.md for the house rules, SOPs for the process, ADRs for the rules they have to follow. The prompt is the smallest piece. Everything else is a way of wrapping, packaging, or triggering prompts, so you don't have to type them in by hand.These are the concepts. The specifics — where files live, what triggers what, whether you write a loop or call a built-in one — vary by tool. If i've forgotten anything or you need more info let me know. #AgenticAI #AI

• 
  Tanmoy - Systems & Apps (@godofdarkshadow) reported 11 minutes ago

  Are you that consultant who remembers the client said something… but has no idea where? Slack? Gmail? Notion? Call notes? LinkedIn DM? ChatGPT? The context exists. But when the client asks: What did we decide? You start searching everywhere. That’s not a tools problem. That’s a memory problem. Reply memory and I’ll send you the Claude workflow.

• 
  the racing newsletter (@equinties) reported 13 minutes ago

  @Original_89 @LeeTatum89 Promotions folder for Gmail. Reply to one you’ve received and should fix.

• 
  ASHY CRYPto (@Minerjohn1) reported 21 minutes ago

  @bashorunedward how to login using gmail, my gmail was linked

• 
  𝙎𝙞𝙙𝙧𝙖 𝘼𝙙𝙫𝙞𝙨𝙚𝙧🇸🇦🇶🇦 (@Sidra_adviser) reported 24 minutes ago

  @arafa_abdu67911 @sidrachain @maljefairi The technical team is aware of this issue and is working on an alternative option/solution for users who lost access to their registered Gmail accounts.

• 
  Silem's not a Shiba (@psSilem) reported 24 minutes ago

  @LogicOrScience @ValueWithPrem @gmail Googlemail was used in some countrie because of copyright issues around gmail.

• 
  𝐉𝐞𝐧𝐚 (@wonyid) reported 25 minutes ago

  ૮꒰ ˶• ༝ •˶꒱ა wts acc jan-feb f50-80 y26 ╰┈➤ ⋆ v email only ( dom gmail ) ╰┈➤ ⋆ masuk mt ht with pict ╰┈➤ ⋆ go green ╰┈➤ ⋆ dapet data lengkap ╰┈➤ ⋆ test ht = fix take 💸 3xk/each (ready 10 acc) #zonauang

• 
  J.R. Abella (@CoderOfFiction) reported 27 minutes ago

  @garvin_danny I just checked out your blog. I like it! I'm trying to contact you through email but it's not working for gmail

• 
  Will Hamill (@willhamill) reported 28 minutes ago

  @martinwoodward Outlook on the web or Gmail on the web 🙃. I had a couple of bad experiences years back with thick client apps not syncing my mail so now I only use webmail apps on my laptop - if I can load the site then I'm looking at the latest, no more cache or sync issues.

• 
  Jenna Ortega (@PrinceUsma16861) reported 34 minutes ago

  @Szymansk_ii I have issues with the gmail linked to my soso account which was compromised please I need help

• 
  Irka IRON Pawłowski (@ironirka) reported 34 minutes ago

  The AI word of the week has been "loops" — adding yet another piece of jargon to the non-technical vocabulary. This is leaving a lot of people asking: what are they, how are they different from prompts? In a lot of non-technical circles the level of grey about what the parts of agentic AI actually are (and how to use them) can be overwhelming. What's more, they're not static — as things develop, so do their uses and how they work together. Loops themselves have evolved over the last few years. So, here's a little primer to make things easier: Prompt — we know this one. It's the instruction you write for the LLM. You send it, get your output, and any tweaking happens off the back of that output. Prompts are for one-off tasks. As you build reliable ones, you reuse them by pasting them into the terminal or chat. Agent — (this one we know too) the LLM running on its own, doing a series of steps without you watching each one. You give it a goal and walk away. Call — to invoke something by name so it runs. You "call" a skill (or a loop, a tool, an MCP) by typing its name and the LLM loads it and executes the setup. When you ask your LLM to use a skill, hook or loop you are calling it. Skill — a packaged set of instructions, files, and tools the LLM loads when you call it by name. A prompt is just one-off instructions; a skill brings the working setup with it — what to read, what rules to follow, what tools it can use, what to produce. You call it once and the whole setup runs. Some people stuff all this into their CLAUDE.md, but bloating CLAUDE.md causes context issues and the LLM starts ignoring your instructions. That's why skills are for specific contexts and tasks, not general ones. The rule of thumb is: when you have a task you do over and over, with rules → make it a skill. Call it by name instead of re-explaining the rules every time you want it done. Hook — a rule that says "when X happens, do Y." It executes automatically when triggered — a file is saved, a meeting ends, a session starts — and the hook runs the action you tied to it. These are basic automations. Use them when one task is dependent on a different event. Example: You save a new invoice PDF in your invoices folder → a hook automatically triggers your expense categorization skill and logs it in your accounting sheet. Loop — a small program you write that runs a prompt for you, over and over, and checks the work was done properly. It isn't the prompt itself — it's the thing that runs the prompt without you in the middle. Loops are more complicated than hooks and are not prompts. Where a hook does one thing from start to end when triggered, a loop initiates a process from start to end automatically at a time you define. Where a prompt is instructions, a loop is the directive to use those instructions. Use it for repeatable tasks where you're confident in the output and want them running without starting each one yourself. The loop runs the skill, checks the work, stops when the rules say so. Example: A daily "process inbox" loop that runs every morning at 9 a.m., summarizes new emails, extracts action items, self-verifies, and only pings you if something needs your attention. Loops only work if you set them up properly. A few things worth understanding before you do: - Self-verify — a step inside a loop where the LLM checks its own work against the rules before saving or moving on. Without it, the loop produces confident garbage. With it, the loop catches and fixes its own mistakes. - Simple loop vs supervisor loop — a simple loop is one LLM doing one task on repeat. A supervisor loop is a top loop that spins up several workers in parallel, each running its own prompt, then combines their output into one result. - Token budget — a hard cap on how much the loop can spend before it has to stop. Tokens are what the AI charges for, like minutes on a phone bill. Without a cap, a stuck loop can rack up hundreds overnight. Remember when you write you see words, the Agent sees tokens. - Orchestration vs execution — the loop orchestrates: decides what runs, when, and in what order. The LLM executes: runs the actual prompt and produces the output. Two different jobs. - .md files (markdown) — a plain text file the LLM can read. This is where most of your directions for an AI — instructions, rules, context — live. It's how you tailor an LLM to your project. Common ones: CLAUDE.md / AGENTS.md / GEMINI.md (depends on the LLM you're using) — master instructions for a folder or project. They live in the folder you launch the LLM from. The LLM reads them automatically when it starts working. These are the house rules for your project or workspace. SKILL.md — the instruction file at the heart of a skill. Tells the LLM what the skill is for, when to use it, and how. ADR (Architecture Decision Record) — a decision written as a rule the AI can apply. Format: what was decided, why, and what to do or not do because of it. ADRs are a development artefact, so most non-technical users don't touch them — but using them can substantially improve the output of your agents. If there's a rule you want the AI to always check its work against → write it as an ADR in a .md file. Any skill or loop can then check its output against the ADR before saving. This is one way of "harnessing" the agent — making sure its output matches what you're actually building, from meeting notes to full products. SOP (Standard Operating Procedure) — the process for a recurring task, written step by step so the AI can follow it. One SOP per repeating job, just like any standard process. The skill running the job reads the SOP for the steps. Note on terminology: The concepts above are fairly universal, but exact names, file conventions, and implementation details vary by tool (Claude Code, Cursor, Windsurf, etc.). You might see CLAUDE.md, AGENTS.md, .cursorrules, or different triggers depending on which system you're using. Other things you might be reading/hearing: CLI (Command Line Interface) — your terminal or Command Prompt window, where you type commands instead of clicking buttons. Most coding AIs live in the CLI. MCP (Model Context Protocol) — the standard that lets the LLM talk to outside tools and services. Without MCP, the LLM only sees what you paste in. With MCP, it can fetch your Gmail, read a Notion page, update a Google Doc, post to Slack — directly, on its own. How they fit togetherPrompts live inside skills. Skills live inside loops. Loops initiate via hooks or schedules. All of them read .md files — CLAUDE.md for the house rules, SOPs for the process, ADRs for the rules they have to follow. The prompt is the smallest piece. Everything else is a way of wrapping, packaging, or triggering prompts, so you don't have to type them in by hand.These are the concepts. The specifics — where files live, what triggers what, whether you write a loop or call a built-in one — vary by tool. If i've forgotten anything or you need more info let me know. #AgenticAI #AI

• 
  Erin🏴‍☠️ (@Hotel323) reported 36 minutes ago

  Hi @gmail im having a problem recovering one of my accounts due to session expired, can you help me with this?