How to interpret the monitoring status
Technical measurements reflect observations from the NexIP monitoring location. A failed or restricted request alone does not confirm a widespread outage.
Gaming
Техническая проверка не позволила подтвердить доступность сервиса.
Technical measurements reflect observations from the NexIP monitoring location. A failed or restricted request alone does not confirm a widespread outage.
Reports over 24 hours, signals over 15 minutes and the outage index measure different periods and conditions. Their values may differ without being contradictory.
Service monitoring
Мониторинг доступности сервиса Battle.net, пользовательских сигналов и технических проверок NexIP.
Reports submitted to NexIP. One report does not prove a widespread outage.
No reports during this period.
30-minute intervals · Moscow time · actual dataLast 7 days
Observation points
Observation history
Actual NexIP primary probe measurements, not user reports
| Time (server) | Checks | Average | Peak | Down | Blocked |
|---|---|---|---|---|---|
| 2026-11-17 04:00:00 | 7 | 3 447 ms | 8 005 ms | 3 | 0 |
| 2026-11-17 05:00:00 | 8 | 3 872 ms | 8 005 ms | 1 | 0 |
| 2026-11-17 06:00:00 | 7 | 2 744 ms | 10 616 ms | 1 | 0 |
| 2026-11-17 07:00:00 | 8 | 2 171 ms | 8 004 ms | 2 | 0 |
| 2026-11-17 08:00:00 | 8 | 2 181 ms | 8 300 ms | 4 | 0 |
| 2026-11-17 09:00:00 | 8 | 2 406 ms | 8 004 ms | 0 | 0 |
| 2026-11-17 10:00:00 | 8 | 2 409 ms | 8 003 ms | 0 | 0 |
| 2026-11-17 11:00:00 | 7 | 1 629 ms | 1 658 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 8 | 3 526 ms | 8 317 ms | 0 | 0 |
| 2026-11-17 13:00:00 | 7 | 1 631 ms | 1 675 ms | 0 | 0 |
| 2026-11-17 14:00:00 | 8 | 1 597 ms | 1 631 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 7 | 1 635 ms | 1 681 ms | 0 | 0 |
| 2026-11-17 16:00:00 | 8 | 1 629 ms | 1 655 ms | 0 | 0 |
| 2026-11-17 17:00:00 | 7 | 3 462 ms | 8 319 ms | 1 | 0 |
| 2026-11-17 18:00:00 | 8 | 2 427 ms | 5 841 ms | 3 | 0 |
| 2026-11-17 19:00:00 | 7 | 3 296 ms | 9 143 ms | 0 | 0 |
| 2026-11-17 20:00:00 | 7 | 1 999 ms | 2 723 ms | 0 | 0 |
| 2026-11-17 21:00:00 | 8 | 2 424 ms | 3 165 ms | 0 | 0 |
| 2026-11-17 22:00:00 | 7 | 1 767 ms | 2 092 ms | 0 | 0 |
| 2026-11-17 23:00:00 | 8 | 1 583 ms | 1 627 ms | 0 | 0 |
| 2026-11-18 00:00:00 | 7 | 1 652 ms | 1 980 ms | 0 | 0 |
| 2026-11-18 01:00:00 | 8 | 1 387 ms | 1 633 ms | 1 | 0 |
| 2026-11-18 02:00:00 | 7 | 2 020 ms | 8 320 ms | 3 | 0 |
| 2026-11-18 03:00:00 | 8 | 1 321 ms | 1 440 ms | 1 | 0 |
| 2026-11-18 04:00:00 | 7 | 1 411 ms | 1 435 ms | 0 | 0 |
| 2026-11-18 05:00:00 | 8 | 1 316 ms | 1 454 ms | 1 | 0 |
| 2026-11-18 06:00:00 | 8 | 1 411 ms | 1 448 ms | 0 | 0 |
| 2026-11-18 07:00:00 | 7 | 1 421 ms | 1 531 ms | 0 | 0 |
| 2026-11-18 08:00:00 | 8 | 1 424 ms | 1 550 ms | 0 | 0 |
| 2026-11-18 09:00:00 | 8 | 2 039 ms | 6 288 ms | 0 | 0 |
| 2026-11-18 10:00:00 | 7 | 1 425 ms | 1 440 ms | 0 | 0 |
| 2026-11-18 11:00:00 | 8 | 1 427 ms | 1 456 ms | 0 | 0 |
| 2026-11-18 12:00:00 | 7 | 1 439 ms | 1 502 ms | 0 | 0 |
| 2026-11-18 13:00:00 | 8 | 1 575 ms | 2 502 ms | 0 | 0 |
| 2026-11-18 14:00:00 | 7 | 1 451 ms | 1 499 ms | 0 | 0 |
| 2026-11-18 15:00:00 | 8 | 1 459 ms | 1 562 ms | 0 | 0 |
| 2026-11-18 16:00:00 | 7 | 1 591 ms | 2 209 ms | 0 | 0 |
| 2026-11-18 17:00:00 | 8 | 1 616 ms | 1 783 ms | 0 | 0 |
| 2026-11-18 18:00:00 | 7 | 1 663 ms | 2 027 ms | 0 | 0 |
| 2026-11-18 19:00:00 | 7 | 1 764 ms | 2 158 ms | 0 | 0 |
Success is up or degraded among recorded primary probe checks. This is not a public uptime SLA. Available history can be shorter than the selected range.
Your signal
Tell us. Registration is not required. The same signal will not be counted repeatedly within a short period.
User opinions are separate from the technical outage status.
No ratings yet
No comments yet.
This page tracks the current observed status of Battle.net, recent incidents, automated availability checks and available user reports. NexIP does not treat a single failed check as proof of a global outage.
Ping · Website availability · Website monitoring · All service outages
NexIP shows the current observed status of Battle.net using automated checks, incident data and available user signals. A local connection problem may differ from a large-scale outage.
Availability can differ by provider, region, DNS, routing, application version or service component. NexIP therefore separates observed signals from confirmed large-scale incidents.
Check the host with Ping, website availability and your own connection. Comparing several independent checks helps distinguish a local problem from a wider outage.