Loading
D2R.ORG
Region · Battle.net · checked every minute while watchedCan a Diablo II: Resurrected client reach Battle.net right now? We open the same TLS connection the game opens to each region's login front (:1119) and keep 30 days of the answers — latency, uptime and every outage we saw. It is a reachability check from our server, not Blizzard's own status.
No — every login front answered.
Last check · checking now… · 0 open incidents · 100% over 24 h
No incidents since checks began on Fri 18 Sep — 2,724 checks, every one answered.
An incident runs from the first failed check to the first good one after it. We check about once a minute while someone is watching and with every ladder pass otherwise, so start and end are accurate to that gap. Slow periods need two slow checks in a row.
Ladder serviceOur collector signs in to Battle.net and reads the ladder boards. A completed pass means the Battle.net ladder service answered; a missed pass can be our collector, not Blizzard. Open the ladder
If steps 1–3 fail, nobody in that region can log in — the classic “Battle.net is down”. Lag or “realm going down” messages with a reachable front are a different failure, which this page can't see.
Under ~300 ms is normal from the same continent; over 1.5 s is flagged slow; a timeout (6 s) or a refused connection is unreachable. All three regions are checked from one place, so the farthest region always reads highest. It uses the newest TLS the front offers (1.3); the game's TLS 1.2 handshake needs one more round trip, so a real client's handshake takes about one TCP time longer than shown.
The cards show the TLS version, the cipher and when the certificate expires. An expired or replaced certificate is one of the rare front failures a client sees as a connection error while the servers are fine.