Are you having issues? Provide feedback to Battle by selecting the option you are having issues with.
HTTP/1.1 200 200 Date: Wed, 09 Feb 2022 23:04:56 GMT Server: Apache Retry-After: 600 Set-Cookie: login.cookies=1; Domain=battle.net; Path=/ Set-Cookie: XSRF-TOKEN=82f2495e-a2d4-4d87-b45b-a4fe27cccaf2; Path=/; Secure Set-Cookie: loc=en-us; Max-Age=2592000; Expires=Fri, 11-Mar-2022 23:04:56 GMT; Domain=battle.net; Path=/ X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Cache-Control: no-cache, no-store, max-age=0, must-revalidate Pragma: no-cache Expires: 0 Strict-Transport-Security: max-age=31536000 ; includeSubDomains Referrer-Policy: no-referrer-when-downgrade Content-Length: 8274 Vary: Accept-Encoding Content-Type: text/html;charset=UTF-8
The DNS is up. We have tried pinging Battle.net. There are no DNS Issues detected!
Type | Name | Value | Class | TTL |
A | battle.net | 137.221.106.104 | IN | 300 |
NS | battle.net | IN | 86400 | |
NS | battle.net | IN | 86400 |
We have tried pinging Battle.net using our servers and the Battle.net server responded on time, indicating that there are no current Battle.net problems today.
If Battle.net is down for you too, the server might be overloaded or unreachable because of network problems, outages or a website maintenance is in progress.
If Battle.net is UP for us but you cannot access it, try these solutions: