Why is my Gmail down?

If there's no incident on Google's dashboard, the usual causes are local: the connection, a browser extension, an old app version or a signed-out session. If there is an incident, Google's post says what's affected and when it will update.

Is Gmail down and not receiving emails?

A Gmail outage can delay incoming mail, and the dashboard would show it. If there's no incident, check Spam, your filters and your storage, and ask the sender whether they got a bounce.

Was Gmail down yesterday?

Open Recent Gmail incidents in the panel: it lists the last closed incidents from Google's own history feed, with start and end times. Google's dashboard keeps the previous 365 days; anything Google didn't post won't appear.

Is Gmail down in my area?

This page can't see regional problems Google hasn't posted. Our probe runs from our server's location, not yours. Google's dashboard posts usually describe who is affected when an incident is regional.

Is the Gmail server down?

Our probe connects to smtp.gmail.com, Gmail's sending server, and shows its greeting and response time; a 220 greeting means it was accepting connections when we checked. It also confirms gmail.com's MX records resolve, but it can't connect to the inbound servers because our host blocks outbound port 25.

Is Google Workspace Gmail down?

The Workspace Status Dashboard this page reads is Google's status page for the services that are part of Google Workspace, Gmail among them, so a Workspace Gmail incident shows up in the Gmail panel as soon as Google posts it.

Is Gmail down right now? Live Gmail and Outlook.com status

Is Gmail down right now? This page reads Google's own Workspace Status Dashboard feed for open Gmail incidents and connects to Gmail's mail servers from our server to read their greeting, refreshed every minute. If the dashboard shows no incident and the servers answer, Gmail is up for most people and the problem is probably local.

Reading the official status feeds and probing the mail servers…

SimpleAPI

Sample result

Gmail has no open incident in this sample reading.

Gmail feed: No open incident
Source: Google's status dashboard
Sending server: Greeting read on port 465

What this means for you

If your mail isn't arriving and Gmail is fine, look at your own sending setup next.

Next step:Run the full deliverability audit

Reads Google's own status feed for Gmail
Outlook.com from Microsoft's status page
Reads the sending servers' greeting
Shows the time of every check

Gmail
Outlook
Status

By SimpleVerifier Team · Last updated October 17, 2026

How do I check if Gmail is down?

Open the page. It reads the status feeds and probes the mail servers straight away; each result shows when it was read.
Look at the official status first: an open incident on Google's dashboard or Microsoft's status page is the provider confirming a problem.
Then look at the probe: a 220 greeting means the mail server accepted a connection from us a moment ago.
Press Check again for a fresh reading. Results are cached for a minute, so pressing faster than that returns the same reading.

Example

You enter: Nothing to enter: open the page.
You get: No open Gmail incident on Google's status dashboard, gmail.com MX records resolve, and Gmail's sending server answered on port 465, each with the time it was read.
Limits: Readings are cached for 60 seconds, so checking again sooner returns the same reading.

Is Gmail down right now?

The panel above answers it from two places. First, Google's Workspace Status Dashboard: we read the JSON history feed Google publishes for programmatic access, as its dashboard FAQ describes, and show any Gmail incident that hasn't ended, with Google's own wording and a link to the post. Second, a probe from our server: we look up gmail.com's MX records, then connect to smtp.gmail.com on port 465, the server mail apps send through, read the 220 greeting that RFC 5321 says a server sends when it is ready, and say QUIT. Our host can't open outbound connections on port 25, so we resolve the inbound MX servers rather than connect to them.

We never invent a status. If a feed can't be read, the page says so rather than guessing, and every result carries the time it was taken.

Is Gmail down or is it just me?

If the dashboard shows no open Gmail incident and Gmail's servers answered our probe, the cause is most likely on your side: your connection, a browser extension, a stale app session or something specific to your account. Try Gmail in a private browser window, on another network such as mobile data, or on another device. If it works there, the problem is local.

The dashboard can also trail a real problem: an incident appears only when Google posts it, so early in an outage the feed may still be clear while people already see errors. If our probe fails at the same moment, that is a stronger hint. If the probe works and the dashboard is clear, but Gmail still won't load for you, contact Google through the support routes the dashboard links to.

Why is Gmail not receiving emails?

When Gmail itself is up, missing mail usually comes from the sending side or from settings: the message went to Spam, a filter archived or deleted it, the account is out of storage, or the sender's message bounced. Gmail's help page on bounced or rejected emails lists the errors senders see and what each means.

If you are the sender and your mail to Gmail addresses is bouncing, read the bounce code before blaming an outage. A 421 4.7.0 is Gmail deferring you, often for rate or reputation; a 550 5.1.1 means the mailbox doesn't exist, and no outage causes that. The bounce message analyzer decodes the full message.

Is Outlook down?

The second panel covers Outlook.com, Microsoft's personal email service. Its status comes from Microsoft's public service status page, which Microsoft's service health documentation points to for checking known issues; we read the same JSON that page loads and show the status Microsoft gives Outlook.com, word for word. Microsoft 365 work accounts are reported in the admin center's Service health page instead, which needs an admin sign-in, so they aren't covered here.

The probe resolves outlook.com's MX records and connects to smtp-mail.outlook.com on port 587, the server Outlook apps send through, to read its greeting.

How is this different from Downdetector?

	This page	Crowd-report sites
Evidence	Provider's official feed + server probe	Counts of user reports
Confirms an outage	Only when Google or Microsoft post one	No, it shows a spike in complaints
Catches problems before they're posted	Partly, if the probe fails	Often, if many people report
Last-checked time on every result	Yes	Varies

The two answer different questions: a report spike says many people are having trouble; the dashboard says the provider has confirmed it.

Who uses this tool, and for what?

Cold emailers: When replies stop or sends start failing, rule out a Gmail or Outlook.com incident before pausing campaigns or swapping inboxes.
IT and ops: Answer the 'is email down?' message from the team with the provider's own status and a timestamp, instead of a guess.
Marketers: A spike in deferrals during a send: check whether Google had a delivery incident at that time before reading it as a reputation problem.
Support teams: Link customers who report missing emails to the official status, then move on to spam folders and filters if it's clear.

What can’t this tool tell you?

It only knows what Google and Microsoft publish. A problem they haven't posted yet, or never post, won't show as an incident.
The probe runs from our server, so it shows that Gmail's servers were reachable from there, not from your network or country.
A 220 greeting means the server accepts connections. It doesn't prove that sign-in, the web app or delivery into inboxes are working.
The inbound mail servers are only resolved in DNS, not connected to (our host blocks outbound port 25), so a receiving-side failure behind working DNS won't show in the probe.
It doesn't count user reports the way crowd-sourced outage sites do, and it can't see problems with a single account.

Common questions

Is Gmail down right now?: The live panel at the top of this page answers it: it reads Google's Workspace Status Dashboard for open Gmail incidents and probes Gmail's mail servers, with the time of each reading. No open incident plus servers that answer means Gmail is up for most people.
Is Gmail down or is it just me?: If Google's dashboard shows no Gmail incident and Gmail's servers answered our probe, it's very likely just you: try a private window, another network or another device to narrow it down.
Why is my Gmail down?: If there's no incident on Google's dashboard, the usual causes are local: the connection, a browser extension, an old app version or a signed-out session. If there is an incident, Google's post says what's affected and when it will update.
Is Gmail down and not receiving emails?: A Gmail outage can delay incoming mail, and the dashboard would show it. If there's no incident, check Spam, your filters and your storage, and ask the sender whether they got a bounce.
Was Gmail down yesterday?: Open Recent Gmail incidents in the panel: it lists the last closed incidents from Google's own history feed, with start and end times. Google's dashboard keeps the previous 365 days; anything Google didn't post won't appear.
Is Gmail down in my area?: This page can't see regional problems Google hasn't posted. Our probe runs from our server's location, not yours. Google's dashboard posts usually describe who is affected when an incident is regional.
Is the Gmail server down?: Our probe connects to smtp.gmail.com, Gmail's sending server, and shows its greeting and response time; a 220 greeting means it was accepting connections when we checked. It also confirms gmail.com's MX records resolve, but it can't connect to the inbound servers because our host blocks outbound port 25.
Is Google Workspace Gmail down?: The Workspace Status Dashboard this page reads is Google's status page for the services that are part of Google Workspace, Gmail among them, so a Workspace Gmail incident shows up in the Gmail panel as soon as Google posts it.

Sources

Authentication and capacity are half of deliverability.

The other half is who you send to. Every hard bounce counts against the domain and inboxes you are sending from, and nothing in DNS can tell you which addresses on your list are dead.

Bulk verification with real SMTP mailbox checks
Hard bounces removed before a send, not discovered after
Catch-all, disposable and role detection on every row

Get started — $29.99/mo See the published limits first

One plan, cancel anytime, no contract. Sign in with Google and your first 100 email checks are free, no card. The free tools stay free either way.