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 14:25:00 | 1 | 1 448 ms | 1 448 ms | 0 | 0 |
| 2026-11-18 14:35:00 | 1 | 1 499 ms | 1 499 ms | 0 | 0 |
| 2026-11-18 14:40:00 | 1 | 1 451 ms | 1 451 ms | 0 | 0 |
| 2026-11-18 14:50:00 | 1 | 1 393 ms | 1 393 ms | 0 | 0 |
| 2026-11-18 15:00:00 | 1 | 1 562 ms | 1 562 ms | 0 | 0 |
| 2026-11-18 15:05:00 | 1 | 1 438 ms | 1 438 ms | 0 | 0 |
| 2026-11-18 15:15:00 | 1 | 1 442 ms | 1 442 ms | 0 | 0 |
| 2026-11-18 15:20:00 | 1 | 1 419 ms | 1 419 ms | 0 | 0 |
| 2026-11-18 15:30:00 | 1 | 1 421 ms | 1 421 ms | 0 | 0 |
| 2026-11-18 15:40:00 | 1 | 1 436 ms | 1 436 ms | 0 | 0 |
| 2026-11-18 15:45:00 | 1 | 1 477 ms | 1 477 ms | 0 | 0 |
| 2026-11-18 15:55:00 | 1 | 1 474 ms | 1 474 ms | 0 | 0 |
| 2026-11-18 16:00:00 | 1 | 1 442 ms | 1 442 ms | 0 | 0 |
| 2026-11-18 16:10:00 | 1 | 1 473 ms | 1 473 ms | 0 | 0 |
| 2026-11-18 16:20:00 | 1 | 1 575 ms | 1 575 ms | 0 | 0 |
| 2026-11-18 16:25:00 | 1 | 1 400 ms | 1 400 ms | 0 | 0 |
| 2026-11-18 16:35:00 | 1 | 2 209 ms | 2 209 ms | 0 | 0 |
| 2026-11-18 16:40:00 | 1 | 1 475 ms | 1 475 ms | 0 | 0 |
| 2026-11-18 16:50:00 | 1 | 1 560 ms | 1 560 ms | 0 | 0 |
| 2026-11-18 17:00:00 | 1 | 1 436 ms | 1 436 ms | 0 | 0 |
| 2026-11-18 17:05:00 | 1 | 1 587 ms | 1 587 ms | 0 | 0 |
| 2026-11-18 17:15:00 | 1 | 1 720 ms | 1 720 ms | 0 | 0 |
| 2026-11-18 17:20:00 | 1 | 1 683 ms | 1 683 ms | 0 | 0 |
| 2026-11-18 17:30:00 | 1 | 1 591 ms | 1 591 ms | 0 | 0 |
| 2026-11-18 17:40:00 | 1 | 1 694 ms | 1 694 ms | 0 | 0 |
| 2026-11-18 17:45:00 | 1 | 1 783 ms | 1 783 ms | 0 | 0 |
| 2026-11-18 17:55:00 | 1 | 1 435 ms | 1 435 ms | 0 | 0 |
| 2026-11-18 18:00:00 | 1 | 1 460 ms | 1 460 ms | 0 | 0 |
| 2026-11-18 18:10:00 | 1 | 1 779 ms | 1 779 ms | 0 | 0 |
| 2026-11-18 18:20:00 | 1 | 1 568 ms | 1 568 ms | 0 | 0 |
| 2026-11-18 18:25:00 | 1 | 1 544 ms | 1 544 ms | 0 | 0 |
| 2026-11-18 18:35:00 | 1 | 1 552 ms | 1 552 ms | 0 | 0 |
| 2026-11-18 18:40:00 | 1 | 2 027 ms | 2 027 ms | 0 | 0 |
| 2026-11-18 18:50:00 | 1 | 1 710 ms | 1 710 ms | 0 | 0 |
| 2026-11-18 19:00:00 | 1 | 2 158 ms | 2 158 ms | 0 | 0 |
| 2026-11-18 19:05:00 | 1 | 1 617 ms | 1 617 ms | 0 | 0 |
| 2026-11-18 19:15:00 | 1 | 1 755 ms | 1 755 ms | 0 | 0 |
| 2026-11-18 19:20:00 | 1 | 1 432 ms | 1 432 ms | 0 | 0 |
| 2026-11-18 19:30:00 | 1 | 2 021 ms | 2 021 ms | 0 | 0 |
| 2026-11-18 19:40:00 | 1 | 1 609 ms | 1 609 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.