User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Gaming
hearthstone.blizzard.com · Gaming
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 720 ms · 5 min ago.
No status feed
Hearthstone does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 23:00 | 0 | 0.0 | 158 ms | 0 |
| 23:15 | 0 | 0.0 | 929 ms | 0 |
| 23:30 | 0 | 0.0 | 600 ms | 0 |
| 23:45 | 0 | 0.0 | 211 ms | 0 |
| 00:00 | 0 | 0.0 | 585 ms | 0 |
| 00:15 | 0 | 0.0 | 94 ms | 0 |
| 00:30 | 0 | 0.0 | 751 ms | 0 |
| 00:45 | 0 | 0.0 | 204 ms | 0 |
| 01:00 | 0 | 0.0 | 223 ms | 0 |
| 01:15 | 0 | 0.0 | 344 ms | 0 |
| 01:30 | 0 | 0.0 | 509 ms | 0 |
| 01:45 | 0 | 0.0 | 328 ms | 0 |
| 02:00 | 0 | 0.0 | 576 ms | 0 |
| 02:15 | 0 | 0.0 | 720 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 2 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Hearthstone yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Hearthstone goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Hearthstone alerts to Slack, Discord or a webhook — free.
Checks are succeeding and user reports are near the baseline.
If Hearthstone is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Hearthstone's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.