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-18 00:00:00 | 3 | 1 615 ms | 1 638 ms | 0 | 0 |
| 2026-11-18 00:30:00 | 4 | 1 680 ms | 1 980 ms | 0 | 0 |
| 2026-11-18 01:00:00 | 4 | 1 248 ms | 1 608 ms | 1 | 0 |
| 2026-11-18 01:30:00 | 4 | 1 526 ms | 1 633 ms | 0 | 0 |
| 2026-11-18 02:00:00 | 4 | 2 636 ms | 8 320 ms | 2 | 0 |
| 2026-11-18 02:30:00 | 3 | 1 199 ms | 1 403 ms | 1 | 0 |
| 2026-11-18 03:00:00 | 4 | 1 403 ms | 1 440 ms | 0 | 0 |
| 2026-11-18 03:30:00 | 4 | 1 238 ms | 1 428 ms | 1 | 0 |
| 2026-11-18 04:00:00 | 4 | 1 399 ms | 1 429 ms | 0 | 0 |
| 2026-11-18 04:30:00 | 3 | 1 428 ms | 1 435 ms | 0 | 0 |
| 2026-11-18 05:00:00 | 4 | 1 212 ms | 1 454 ms | 1 | 0 |
| 2026-11-18 05:30:00 | 4 | 1 421 ms | 1 437 ms | 0 | 0 |
| 2026-11-18 06:00:00 | 4 | 1 394 ms | 1 409 ms | 0 | 0 |
| 2026-11-18 06:30:00 | 4 | 1 428 ms | 1 448 ms | 0 | 0 |
| 2026-11-18 07:00:00 | 3 | 1 434 ms | 1 531 ms | 0 | 0 |
| 2026-11-18 07:30:00 | 4 | 1 412 ms | 1 440 ms | 0 | 0 |
| 2026-11-18 08:00:00 | 4 | 1 401 ms | 1 412 ms | 0 | 0 |
| 2026-11-18 08:30:00 | 4 | 1 447 ms | 1 550 ms | 0 | 0 |
| 2026-11-18 09:00:00 | 4 | 1 420 ms | 1 450 ms | 0 | 0 |
| 2026-11-18 09:30:00 | 4 | 2 657 ms | 6 288 ms | 0 | 0 |
| 2026-11-18 10:00:00 | 3 | 1 416 ms | 1 425 ms | 0 | 0 |
| 2026-11-18 10:30:00 | 4 | 1 431 ms | 1 440 ms | 0 | 0 |
| 2026-11-18 11:00:00 | 4 | 1 428 ms | 1 435 ms | 0 | 0 |
| 2026-11-18 11:30:00 | 4 | 1 427 ms | 1 456 ms | 0 | 0 |
| 2026-11-18 12:00:00 | 4 | 1 427 ms | 1 438 ms | 0 | 0 |
| 2026-11-18 12:30:00 | 3 | 1 455 ms | 1 502 ms | 0 | 0 |
| 2026-11-18 13:00:00 | 4 | 1 446 ms | 1 475 ms | 0 | 0 |
| 2026-11-18 13:30:00 | 4 | 1 704 ms | 2 502 ms | 0 | 0 |
| 2026-11-18 14:00:00 | 4 | 1 454 ms | 1 477 ms | 0 | 0 |
| 2026-11-18 14:30:00 | 3 | 1 448 ms | 1 499 ms | 0 | 0 |
| 2026-11-18 15:00:00 | 4 | 1 465 ms | 1 562 ms | 0 | 0 |
| 2026-11-18 15:30:00 | 4 | 1 452 ms | 1 477 ms | 0 | 0 |
| 2026-11-18 16:00:00 | 4 | 1 473 ms | 1 575 ms | 0 | 0 |
| 2026-11-18 16:30:00 | 3 | 1 748 ms | 2 209 ms | 0 | 0 |
| 2026-11-18 17:00:00 | 4 | 1 607 ms | 1 720 ms | 0 | 0 |
| 2026-11-18 17:30:00 | 4 | 1 626 ms | 1 783 ms | 0 | 0 |
| 2026-11-18 18:00:00 | 4 | 1 588 ms | 1 779 ms | 0 | 0 |
| 2026-11-18 18:30:00 | 3 | 1 763 ms | 2 027 ms | 0 | 0 |
| 2026-11-18 19:00:00 | 4 | 1 741 ms | 2 158 ms | 0 | 0 |
| 2026-11-18 19:30:00 | 3 | 1 794 ms | 2 021 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.