PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Google is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Google. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Google issues today?

As of Oct 12, 2026 16:16 UTC, 0 users had reported issues with Google in the previous 24 hours.

How can I report a Google outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Productivity

Is Google down right now?

UnknownOfficial status last polled Sep 7, 2026 16:54 UTCwww.google.com Official status page

Google Search and core Google service availability, including login, search, accounts, and related platform access.

Are you on the Google team and see something inaccurate? Report it to us. We respond within one business day.

Is Google down right now?

Unknown. Google does not have a conclusive current status. A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health. No current vendor status signal: vendor status was last polled on 2026-09-07, more than 7 days ago. The most recent attempt on 2026-10-12 did not return a verifiable status page.

Status as of Oct 12, 2026 16:16 UTC

Unknown

Google: status unknown

As of Oct 12, 2026 16:16 UTC

Recent qualified checks passed for public DNS over HTTPS A lookup. These results cover only those operations; they do not establish overall service health.

Reports 24h

Last incident

Aug 14, 2026 03:16 UTC

Trend

0/15m

Monitoring

Operation checks passing

Observed health

100/100

1 of 1 assessed samples succeeded within their latency target.

4/4 responses validated in the last 15 minutes. 3 successful samples have no qualified latency target.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Google.

Incident days

No recorded incident

0 min

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Google. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

0 incidents

Busiest day

0 min

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Google outage on August 14 — 19-minute disruption

Aug 14, 02:56 AM → Aug 14, 03:16 AM · 19 minutes · high

Google experienced a service disruption on August 14, 2026, which was initially detected via user reports. The incident, classified as high severity, was resolved on August 14, 2026, at 03:16 UTC.

Duration

19 minutes

tracked by PulseWatch

Impact

The service disruption was detected through user reports, indicating a high-severity incident. While specific issue types, features, or regions were not widely reported, the incident was correlated with official signals. A peak of 8 user reports was observed within a 15-minute period during the outage.

Incident timeline

Aug 14, 02:56 AM
PulseWatch detected elevated report volume (high severity)
Aug 14, 03:00 AM
Peak of 0 reports in 15 minutes (baseline 1.3)
Aug 14, 03:16 AM
Report volume returned to baseline — incident resolved

Official updates

Aug 14, 02:56 AM
Google status page acknowledged the incident.
View official source

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: Google is unknown, so there is no incident history to measure and no uptime figure is shown.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.