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-13 21:00:00 | 22 | 1 640 ms | 1 767 ms | 0 | 0 |
| 2026-11-14 00:00:00 | 23 | 1 595 ms | 1 652 ms | 0 | 0 |
| 2026-11-14 03:00:00 | 22 | 1 783 ms | 5 319 ms | 0 | 0 |
| 2026-11-14 06:00:00 | 23 | 1 601 ms | 1 656 ms | 0 | 0 |
| 2026-11-14 09:00:00 | 22 | 1 616 ms | 1 835 ms | 0 | 0 |
| 2026-11-14 12:00:00 | 23 | 1 629 ms | 1 701 ms | 0 | 0 |
| 2026-11-14 15:00:00 | 22 | 1 633 ms | 1 708 ms | 0 | 0 |
| 2026-11-14 18:00:00 | 23 | 1 650 ms | 1 976 ms | 0 | 0 |
| 2026-11-14 21:00:00 | 22 | 1 608 ms | 1 688 ms | 0 | 0 |
| 2026-11-15 00:00:00 | 23 | 1 589 ms | 1 641 ms | 0 | 0 |
| 2026-11-15 03:00:00 | 22 | 1 615 ms | 1 921 ms | 0 | 0 |
| 2026-11-15 06:00:00 | 22 | 1 597 ms | 1 682 ms | 0 | 0 |
| 2026-11-15 09:00:00 | 23 | 1 615 ms | 1 672 ms | 0 | 0 |
| 2026-11-15 12:00:00 | 22 | 1 622 ms | 1 666 ms | 0 | 0 |
| 2026-11-15 15:00:00 | 23 | 1 647 ms | 1 926 ms | 0 | 0 |
| 2026-11-15 18:00:00 | 22 | 3 516 ms | 8 975 ms | 2 | 0 |
| 2026-11-15 21:00:00 | 23 | 4 983 ms | 12 682 ms | 4 | 0 |
| 2026-11-16 00:00:00 | 22 | 4 575 ms | 12 847 ms | 2 | 0 |
| 2026-11-16 03:00:00 | 23 | 6 015 ms | 12 960 ms | 5 | 0 |
| 2026-11-16 06:00:00 | 22 | 5 046 ms | 11 609 ms | 5 | 0 |
| 2026-11-16 09:00:00 | 23 | 6 315 ms | 9 904 ms | 3 | 0 |
| 2026-11-16 12:00:00 | 23 | 5 941 ms | 11 094 ms | 6 | 0 |
| 2026-11-16 15:00:00 | 22 | 4 207 ms | 11 994 ms | 5 | 0 |
| 2026-11-16 18:00:00 | 23 | 2 436 ms | 6 846 ms | 1 | 0 |
| 2026-11-16 21:00:00 | 23 | 2 119 ms | 5 446 ms | 3 | 0 |
| 2026-11-17 00:00:00 | 22 | 1 570 ms | 1 678 ms | 1 | 0 |
| 2026-11-17 03:00:00 | 23 | 3 136 ms | 8 005 ms | 4 | 0 |
| 2026-11-17 06:00:00 | 23 | 2 349 ms | 10 616 ms | 7 | 0 |
| 2026-11-17 09:00:00 | 23 | 2 170 ms | 8 004 ms | 0 | 0 |
| 2026-11-17 12:00:00 | 23 | 2 278 ms | 8 317 ms | 0 | 0 |
| 2026-11-17 15:00:00 | 22 | 2 214 ms | 8 319 ms | 1 | 0 |
| 2026-11-17 18:00:00 | 22 | 2 567 ms | 9 143 ms | 3 | 0 |
| 2026-11-17 21:00:00 | 23 | 1 932 ms | 3 165 ms | 0 | 0 |
| 2026-11-18 00:00:00 | 22 | 1 673 ms | 8 320 ms | 4 | 0 |
| 2026-11-18 03:00:00 | 23 | 1 347 ms | 1 454 ms | 2 | 0 |
| 2026-11-18 06:00:00 | 23 | 1 419 ms | 1 550 ms | 0 | 0 |
| 2026-11-18 09:00:00 | 23 | 1 639 ms | 6 288 ms | 0 | 0 |
| 2026-11-18 12:00:00 | 22 | 1 492 ms | 2 502 ms | 0 | 0 |
| 2026-11-18 15:00:00 | 23 | 1 554 ms | 2 209 ms | 0 | 0 |
| 2026-11-18 18:00:00 | 14 | 1 713 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.