Gmail almost always fails for one of four reasons: your device cannot reach Google's servers (network or DNS), the browser or app is holding bad cached state, your account is being blocked by a security or policy control, or the message never left the sender's side because of mail authentication rules. The symptom you see — a spinner, a bounce, a missing email — points to which layer broke. Most fixes work by isolating that layer rather than changing settings at random.
The delivery path and where it breaks
Every Gmail action travels a chain: your device's DNS resolver turns gmail.com into an IP address, a TCP/TLS connection opens to a Google front-end, your session cookie or OAuth token authenticates you, and the web or IMAP layer pulls message state. A failure anywhere upstream of the interface looks identical to the user — "Gmail is down" — even when Gmail is fine.
Incoming mail adds a second path. A sender's server looks up your domain's MX records, opens an SMTP connection, and Gmail evaluates the message against SPF, DKIM, and DMARC before accepting or rejecting it. Google publishes recommended authentication practice through its sender guidelines, and rejected mail often never reaches your inbox at all — it bounces back to the sender with an error code you never see.
That split matters. Outbound failures (you cannot send) and inbound failures (you cannot receive) have almost no fixes in common, yet both get reported as "Gmail not working."
Quantified context: how often and how long
Gmail's own status dashboard is the authoritative source for outages, and it historically resolves most incidents within a few hours rather than days. Google publishes incident history through its Workspace Status Dashboard, which distinguishes service-wide outages from degraded performance.
Client-side causes are far more common than server outages. Cache and cookie corruption, expired OAuth tokens, and stale app versions account for the majority of "not working" reports that resolve without any Google-side change. Storage is a separate hard limit: free accounts get 15 GB shared across Gmail, Drive, and Photos, and once that fills, incoming mail is rejected rather than queued indefinitely.
Verification codes are time-boxed. Google's two-step verification codes expire within minutes, so a delayed code often means a delivery-path problem on your phone, not a Gmail outage.
Edge cases that mimic outages
A full mailbox rejects new mail with a bounce to the sender, so your inbox simply stops receiving while the interface works normally. A misconfigured custom domain — wrong MX records, a lapsed SPF record — breaks delivery for one address while Gmail itself is healthy.
Corporate and school accounts add policy layers. An administrator can disable IMAP, restrict third-party app access, or force re-authentication, and the user experiences this as Gmail "not syncing." Offline mode and flaky Wi-Fi produce partial loads that look like server errors. Browser extensions that block scripts or manipulate cookies can break the web interface on one machine while the mobile app works fine.
Red flag: repeated password prompts with correct credentials suggest a session or token problem, not a forgotten password. Red flag: mail bounces back to senders with a 5xx code means delivery was refused, not delayed. Red flag: only one device fails points to local cache, app version, or extension conflict. Red flag: account recovery prompts you did not initiate indicate a possible compromise — change your password and review active sessions immediately. Red flag: a "storage full" banner means new mail is being rejected until space is freed.
Misconceptions that waste time
The most common error is assuming a service outage. Checking the status dashboard first takes seconds and rules out the cause you cannot fix. The second is treating a sync delay as data loss: Gmail stores mail server-side, so a device that fails to sync has not deleted anything.
A counterintuitive detail professionals rely on: clearing the browser cache can log you out of unrelated sites and does not always fix Gmail, while a private/incognito window — which loads clean state without touching stored data — tests the same hypothesis in one step. If Gmail works in incognito, the problem is cached state or an extension, not Google.
Another misconception: "deleting the app and reinstalling" fixes account-level blocks. It does not. Policy and security controls live on the account, so reinstalling changes nothing if the block is server-side.
Practical actions and thresholds
Work from the outside in, and stop when the symptom changes.
Confirm scope: check the Google Workspace Status Dashboard, then test Gmail in a private window and on a second device. If all fail, wait for the incident; if one works, the fault is local. Test the network layer: load another site, then another Google service. Consistent failure across sites points to DNS or connectivity, so switch networks or flush DNS. Clear local state: remove Gmail cookies or clear the app cache, sign out and back in, and update the browser or app to the current version. Check account controls: review security alerts and active sessions, confirm two-step verification is receiving codes, and for work or school accounts ask the administrator whether policy changed. Check storage: free the 15 GB pool if a storage banner appears, since incoming mail is refused when it fills. For send/receive faults, read the bounce code: 5xx means refused, and the text names the failing authentication record.
A practical threshold: if a fix does not change the symptom after two attempts, stop repeating it and move to the next layer. Most local problems resolve within one session of this sequence.
| Symptom | Most likely layer | First test | Typical fix |
|---|---|---|---|
| Spinner, nothing loads | Network or DNS | Load another site | Switch network, flush DNS |
| Works in private window only | Cache or extension | Private window test | Clear cookies, disable extensions |
| Password loop | Session or token | Second device | Sign out fully, re-authenticate |
| Senders get bounces | Mail authentication | Read bounce code | Fix SPF/DKIM/DMARC |
| No new mail, interface fine | Storage or filters | Check storage banner | Free space, review filters |
| One app fails, web works | App version or cache | Update app | Reinstall, re-grant access |
| Time | What typically happens |
|---|---|
| 0–5 min | Local cache and network faults surface; retry and scope test |
| 5–30 min | Status dashboard updates during real incidents |
| 1–4 hours | Most service incidents resolve or degrade to partial function |
| Same day | Authentication and policy blocks persist until changed |
| 24–72 hours | DNS and MX record changes propagate across resolvers |
| Days | Storage-full rejection continues until space is freed |
Limits of what you can diagnose
You cannot see Google's internal routing, and the status dashboard reports service health, not your account's state. Bounce codes describe why a message was refused but not always which record failed. DNS propagation timing varies by resolver and TTL, so "it should work now" is never precise. Without the actual bounce text or a status entry, the most honest conclusion is which layer is suspect — not a guaranteed cause.
This article is general educational information about how email and account systems behave, not a diagnosis of your specific account or a security assessment. For account compromise, billing disputes, or workplace policy questions, contact Google Support or your organization's IT administrator.