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 Battle.net is down?

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

How many people have reported Battle.net issues today?

As of Oct 10, 2026 06:24 UTC, 0 users had reported issues with Battle.net in the previous 24 hours.

How can I report a Battle.net 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.

Gaming

Is Battle.net down right now?

UnknownOfficial status last polled Aug 14, 2026 19:34 UTCbattle.netNo official status page published

Blizzard Battle.net online service

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

Is Battle.net down right now?

Unknown. Battle.net does not have a conclusive current status. Monitoring is active, but current evidence is inconclusive or conflicting. No current vendor status signal: vendor status was last polled on 2026-08-14, more than 7 days ago.

Status as of Oct 10, 2026 06:24 UTC

Unknown

Battle.net: status unknown

As of Oct 10, 2026 06:24 UTC

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

Last incident

May 5, 2026 04:18 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

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 Battle.net.

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 Battle.net. 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

Battle.net outage on May 5 — 19-minute disruption

May 5, 03:58 AM → May 5, 04:18 AM · 19 minutes · high

Battle.net experienced a service disruption on May 5, 2026, which was detected through user reports. The incident began at approximately 03:58 UTC and was resolved by 04:18 UTC.

Peak reports

in 15 min

Total reports

during the incident

Duration

19 minutes

tracked by PulseWatch

Impact

During the disruption, users primarily reported issues with the Battle.net website being inaccessible. A total of four user reports were received, with 'Website down' being the top reported issue type. No specific regional impact was recorded during this incident.

Top reported issues

Website down4

Incident timeline

May 5, 03:58 AM
PulseWatch detected elevated report volume (high severity)
May 5, 04:00 AM
Peak of 0 reports in 15 minutes (baseline 1.3)
May 5, 04:18 AM
Report volume returned to baseline — incident resolved

Official updates

May 5, 04:18 AM
Website down clustered from 3 sources across 6 signals. Suppressed 5 redundant alerts and flagged flapping behavior.

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

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

Other gaming 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.