Skip to main content

Battle.net outage, 16 November 2026

Battle.net was down for 11 minutes on 16 November 2026, from 07:07 to 07:18 UTC, as measured by HostTracker's checkpoints.

battle.net All times UTC

Resolved

Outage measured by HostTracker's checkpoints

Started
07:07
16 Nov 2026 UTC
Ended
07:18
16 Nov 2026 UTC
Duration
11m
11 minutes
Checkpoints
1
reported a failure
Most common error
Http 502
as reported by our checks

What our checkpoints saw

All times UTC.

The first failed check is the top row, and the recovery is the last one. A row marked "x N" stands for several consecutive checks with the same result from that checkpoint.

Individual checks recorded during the Battle.net outage on 16 November 2026, all times UTC
Time (UTC) Location Result Error
16 Nov 07:18 Sisak, Croatia Failed Http 502

Response time around the outage

183ms low · 13278ms peak

16 Nov 05:46 to 16 Nov 07:18 UTC

13278 ms 183 ms 16 Nov 05:46 UTC 16 Nov 07:18 UTC

The shaded band is the outage window. Points are averaged per bucket across the checkpoints that answered, so a gap in the line is a period where nothing answered at all.

Previous outage

16 Nov 2026 04:14 UTC

Next outage

This is the most recent outage we recorded.

Does your product depend on Battle.net?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Independent measurement by HostTracker. Not affiliated with Battle.net.