Is Battle.net down?
We can't tell right now whether Battle.net works
Change country
No connected status feed
We don't read an official status source for Battle.net, so no provider incidents or maintenance are shown here.
Our checks show whether battle.net loads. Website checks: these do not test every feature.
Reports from people
Last 24 hours · Worldwide · times in UTC
No community reports in the last 24 hours. Having trouble? Add your report.
Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.
Latest checks, 19:10-19:50 UTC: 35 of 35 places loaded it, typical 2974 to 4060 ms.
Where this status comes from
Website checks
Our own checks of battle.net
Every 5 minutes, from our probesOur checks from 35 cities: all fine.
- JakartaReachable6593 ms, just now
- New JerseyReachable4290 ms, just now
- QuerétaroReachable2878 ms, just now
- HaminaReachable1900 ms, just now
- New YorkReachable2675 ms, just now
- Tel AvivReachable2836 ms, just now
- AmsterdamReachable637 ms, just now
- AtlantaReachable2584 ms, just now
- SeoulReachable1593 ms, just now
- LondonReachable700 ms, just now
- DelhiReachable9090 ms, 4 min ago
- SantiagoReachable8042 ms, 4 min ago
- St. LouisReachable3092 ms, 4 min ago
- SydneyReachable8738 ms, 4 min ago
- BangaloreReachable10007 ms, 4 min ago
- FrankfurtReachable360 ms, 4 min ago
- PortsmouthReachable997 ms, 4 min ago
- MumbaiReachable9458 ms, 4 min ago
- Hong KongReachable2526 ms, 4 min ago
- OsakaReachable4059 ms, 4 min ago
- DohaReachable5310 ms, 4 min ago
- MadridReachable5154 ms, 4 min ago
- TokyoReachable5804 ms, 4 min ago
- SeattleReachable971 ms, 4 min ago
- MelbourneReachable8156 ms, 4 min ago
- Los AngelesReachable2773 ms, 5 min ago
- SingaporeReachable7038 ms, 5 min ago
- Port LouisReachable14123 ms, 5 min ago
- WarsawReachable1117 ms, 5 min ago
- JohannesburgReachable7746 ms, 5 min ago
- Cape TownReachable11285 ms, 5 min ago
- DallasReachable2870 ms, 5 min ago
- São PauloReachable7510 ms, 5 min ago
- TorontoReachable2466 ms, 5 min ago
- LauterbourgReachable820 ms, 5 min ago
We request battle.net and note whether it answers. These automated checks do not sign in or use the app's features.
Available evidence
We check whether its website loads every 5 minutes. This does not test sign-in, payments, calls or every feature of its app or network. We show a website problem when a quarter of the eligible places cannot load it, and an outage when half cannot. Places that normally cannot reach it are excluded. With too few results, we say we cannot tell.
Outage history
Last 9030 days
History starts with our first readingOf the last 90 days, 0 had a partial or major outage, 0 had maintenance only and 90 have no data. Recent problems are listed in a table further down.
No problems Partial outage Major outage Maintenance No data yet
Recent problems
No history yet. It starts with our first reading of the website.
What can I try?
Having trouble with Battle.net?
- Compare reports and check the latest update above. A quiet chart does not rule out a new or local problem.
- Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
- Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.
Reports describe people's experiences. One report alone does not confirm an outage.
Questions about these results
Questions
Is Battle.net down, or is it just me?
We can't say yet: see the line at the top.
How do we know?
No official status feed is connected for Battle.net. We load battle.net from our probes and note whether it answers. People can report problems here. Their reports appear separately and may reveal issues before a provider update.
How often do we check?
The website every 5 minutes, day and night. We keep 90 days of available check history: a day we have no reading for shows as "no data yet", never as working.
Other services in Gaming
Each card shows that service's own status, not Battle.net's. A problem listed here does not mean Battle.net has one.
BlitzGamingPartial outageTheir status page: 1 of 21 parts affected: Websites / BlitzView statusReport a problem- ShadowGamingPartial outageTheir status page: 1 of 12 parts affected: Shadow PC / Washington DC (USWDC01)View statusReport a problem
BeammpGamingPartial outageTheir status page: 3 of 8 parts affected: Websites / Forum, BeamMP Services / Backend, BeamMP Services /…View statusReport a problem- i3D.netGamingPartial outageTheir status page: 4 of 74 parts affected: Datacenters / Dubai - aedxb1, Datacenters / Hong Kong - hkhkg1…View statusReport a problem
McstatusGamingPartial outageTheir status page: 1 of 5 parts affected: DashboardView statusReport a problem
MinesweeperGamingPartial outageTheir status page: 2 of 43 parts affected: Kazakhstan, Korea (4)View statusReport a problem
NookipediaGamingPartial outageTheir status page: 2 of 5 parts affected: Nookipedia API, Nookipedia Job QueueView statusReport a problem
PaxhistoriaGamingPartial outageTheir status page: 4 of 24 parts affected: Services / Flag Creation, Services / Pax Services - Multiplayer…View statusReport a problem
TruckersmpGamingPartial outageTheir status page: Open incident: Server InstabilityView statusReport a problem