Diablo outages and problems
In the past 24 hours, 56 user reports came in for Diablo. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 6 reports, about 2 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Diablo in October 2026
- Problem reports in October (since 6 October)
- 231
Monthly report for October 2026
What went wrong
What people said was wrong in recent problem reports for Diablo worldwide.
Share of 12 recent reports that said what was wrong, from every country listed below.
Diablo reports around the world
In the last 24 hours, 54 problem reports about Diablo came in from 12 countries. Right now reports are at the usual level in every country.
- Outage now
- Problems now
- Normal
| Country | Now | Last hour | 24 hours |
|---|---|---|---|
| The US numbers above | Normal | 1 | 36 |
| France | Normal | 1 | 6 |
| Australia | Normal | 0 | 2 |
| The UK | Normal | 0 | 2 |
| Brazil | Normal | 0 | 1 |
| Poland | Normal | 0 | 1 |
| Belgium | Normal | 0 | 1 |
| Japan | Normal | 0 | 1 |
| Austria | Normal | 0 | 1 |
| Israel | Normal | 0 | 1 |
| Vietnam | Normal | 0 | 1 |
| Algeria | Normal | 0 | 1 |
Each country's status compares its reports with the usual level there. 60 more countries had 0 reports in the last 24 hours. Map outlines: Natural Earth.
Diablo problem spikes, last 30 days
Since 6 October, Diablo had no outage spikes, but 1 period of elevated reports.
- Fri 2 Oct: no data
- Sat 3 Oct: no data
- Sun 4 Oct: no data
- Mon 5 Oct: no data
- Tue 6 Oct: 1 report
- Wed 7 Oct: 3 reports
- Thu 8 Oct: 0 reports
- Fri 9 Oct: 0 reports
- Sat 10 Oct: 0 reports
- Sun 11 Oct: 0 reports
- Mon 12 Oct: 1 report
- Tue 13 Oct: 0 reports
- Wed 14 Oct: 0 reports
- Thu 15 Oct: 1 report
- Fri 16 Oct: 0 reports
- Sat 17 Oct: 0 reports
- Sun 18 Oct: 0 reports
- Mon 19 Oct: 0 reports
- Tue 20 Oct: 1 report
- Wed 21 Oct: no data
- Thu 22 Oct: 1 report
- Fri 23 Oct: 0 reports
- Sat 24 Oct: 0 reports
- Sun 25 Oct: 0 reports
- Mon 26 Oct: 0 reports
- Tue 27 Oct: 0 reports
- Wed 28 Oct: 29 reports
- Thu 29 Oct: 79 reports (elevated reports that day)
- Fri 30 Oct: 63 reports
- Sat 31 Oct: 52 reports
-
Elevated reports
Thu 29 Oct, 02:11–02:29Lasted 19 min11peak reports
By country
Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.
- The US178
- Australia64
- France17
- New Zealand13
- Japan12
- Singapore12
- Canada11
- Brazil10
Country history starts on 28 October 2026. Days run from midnight to midnight, Central European time.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 6 October 2026. Monthly reports for all services
How to fix Diablo not working
Diablo is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach diablo.blizzard.com over your own connection, right now. Nothing is sent to us or stored.
Check Diablo service status first
Check operational, 100.00%, and 56 before changing settings. If you are asking, "is Diablo down" or "is Diablo down right now", compare those figures with the Diablo server status and wait if reports are rising.
Restart the Diablo client and sign in again
If Diablo not working today affects only your account, close the game, restart your device, and sign in again. Check is Diablo working after the restart, since a stuck session can block launch or matchmaking.
Check your network and DNS
Restart your router, test another connection, and flush DNS if Diablo cannot connect. Search Diablo down detector, Diablo network status, or Diablo outage today 2026, then compare the results with more than 24 hours ago before changing local settings.
Common Diablo error messages
What each message means and what to try. The wording can differ a little between app versions.
-
The servers are busy at this time. Please try again later. (Error 37)
- Means
- The login servers are getting more connection attempts than they can handle, so the game turns you away before you reach the character select screen.
- Fix
- Wait a few minutes and sign in again. Nothing on your machine caused it, and it clears on its own once the rush passes.
While Diablo is down: what to use instead
- Path of Exile A similar loot loop waits here if the servers will not let you in.
- Torchlight Pick this for a lighter dungeon crawl when you still want gear drops and build tinkering.
- Last Epoch It works offline, so try it when the service is down.
- Grim Dawn Play this for a slower, darker action RPG when the online service is the only thing failing.
Fix Diablo on Windows, Mac, Android and iPhone
Diablo on Windows
- Fix
- Restart the Battle.net desktop app and run the 'Scan and Repair' tool to fix corrupted Diablo game files. Also, ensure your graphics drivers are updated and allow Diablo through your Windows Defender Firewall.
- Check
- Check the Battle.net launcher for server maintenance alerts or visit the official Blizzard Customer Support Twitter page for Diablo server status. You can also try launching Diablo to see if you receive a connection error code.
ping diablo.blizzard.comTest whether Diablo's servers replynslookup diablo.blizzard.comCheck that Diablo's DNS resolvestracert diablo.blizzard.comTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadDiablo on Mac
- Fix
- Restart the Battle.net client and use the 'Scan and Repair' option in the game settings to fix Diablo installation issues. You can also try resetting your local network router to resolve connection drops.
- Check
- Look for maintenance notifications in the Battle.net launcher or attempt to log into Diablo to see if you get stuck on the authentication screen. Checking official Blizzard support forums is also a reliable way to verify outages.
ping -c 4 diablo.blizzard.comTest whether Diablo's servers replynslookup diablo.blizzard.comCheck that Diablo's DNS resolvestraceroute diablo.blizzard.comTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadDiablo on Android
- Fix
- Clear the Diablo app cache through your Android device settings and check the Google Play Store for any pending updates. If the game still won't load, try switching from mobile data to a stable Wi-Fi network.
- Check
- Check the Google Play Store for server status details or try launching Diablo to see if it fails to connect to the game servers. You can also check community forums to see if other Android users are reporting issues.
Diablo on iPhone and iPad
- Fix
- Force close the Diablo app, restart your iOS device, and check the App Store for any available game updates. If connection issues persist, reinstall the app to ensure all files are intact.
- Check
- Open the App Store to see if there is an active update for Diablo, or try launching the app to see if it gets stuck on the loading screen. You can also check the official Diablo social channels for server status updates.
Problems at the same time as Diablo
Since 6 October, Diablo's only spike in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
During the latest spike
Diablo: Thu 29 Oct, 02:11 to 02:29
- ESPN Fantasy Football, outage,27 Oct 19:50 to 30 Oct 05:40
- Character.AI, outage,28 Oct 12:25 to 04:19
- ADP, outage,28 Oct 14:21 to 04:50
- Fanduel, outage,28 Oct 15:41 to 05:45
- USPS, outage,28 Oct 15:47 to 04:27
- Ziply Fiber, outage,28 Oct 22:54 to 02:21
- TikTok, outage,00:18 to 02:32
- CapCut, outage,00:24 to 02:16
32 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report Diablo problems
The busiest hour for reports about Diablo is 01:00 to 02:00 Central European time, and the busiest day is Thursday.
By hour of the day
- 00:00 to 01:00: 0.72 reports on an average day
- 01:00 to 02:00: 0.91 reports on an average day
- 02:00 to 03:00: 0.54 reports on an average day
- 03:00 to 04:00: 0.4 reports on an average day
- 04:00 to 05:00: 0.39 reports on an average day
- 05:00 to 06:00: 0.59 reports on an average day
- 06:00 to 07:00: 0.42 reports on an average day
- 07:00 to 08:00: 0.2 reports on an average day
- 08:00 to 09:00: 0.09 reports on an average day
- 09:00 to 10:00: 0.01 reports on an average day
- 10:00 to 11:00: 0.04 reports on an average day
- 11:00 to 12:00: 0.03 reports on an average day
- 12:00 to 13:00: 0.1 reports on an average day
- 13:00 to 14:00: 0.08 reports on an average day
- 14:00 to 15:00: 0.11 reports on an average day
- 15:00 to 16:00: 0.26 reports on an average day
- 16:00 to 17:00: 0.33 reports on an average day
- 17:00 to 18:00: 0.34 reports on an average day
- 18:00 to 19:00: 0.31 reports on an average day
- 19:00 to 20:00: 0.71 reports on an average day
- 20:00 to 21:00: 0.51 reports on an average day
- 21:00 to 22:00: 0.65 reports on an average day
- 22:00 to 23:00: 0.59 reports on an average day
- 23:00 to 00:00: 0.81 reports on an average day
By day of the week
- Monday: 0.29 reports on an average Monday
- Tuesday: 0.5 reports on an average Tuesday
- Wednesday: 11 reports on an average Wednesday
- Thursday: 24 reports on an average Thursday
- Friday: 16 reports on an average Friday
- Saturday: 13 reports on an average Saturday
- Sunday: 0 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 24 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
What happens when Diablo goes down
Diablo is Blizzard's action role-playing game service, and uptime matters when you are trying to sign in or keep a session alive. If you searched "is Diablo down right now," live checks show 100.00% uptime over the past 24 hours.
A Diablo outage can block login or disconnect a live session, while a local connection fault can look similar. 56 outage reports came in over the past 24 hours, so compare the symptom with the wider pattern before changing settings.
Diablo IP address, servers and network
- IPv4 addresses
- 52.48.135.140
Show all 2
- 63.33.128.112
- IPv6
- Not offered
- Network
- AS16509 · Amazon.com, Inc., registered in the United States
- Served through
- Amazon Web Services
- DNS hosted by
- Amazon Route 53
- HTTPS certificate
- Issued by Amazon, valid until 12 Apr 2027 (162 days)
- HTTP/3
- Not advertised
- Our check
- Answered in 646 ms
Checked from our server in Frankfurt, Germany, 3 days ago, for diablo4.blizzard.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 11 places around the world
All 11 locations got an answer from diablo4.blizzard.com. Fastest from Tokyo (43 ms), slowest from São Paulo (913 ms). The answers came through 2 networks: Amazon.com, Inc. (AS16509) and Amazon.com, Inc. (AS14618).
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 307 | 96 ms | 52.48.135.140Amazon.com, Inc. |
| ViennaAustria | Up · HTTP 307 | 152 ms | 63.33.128.112Amazon.com, Inc. |
| MilanItaly | Up · HTTP 307 | 122 ms | 52.48.135.140Amazon.com, Inc. |
| ParisFrance | Up · HTTP 307 | 118 ms | 52.48.135.140Amazon.com, Inc. |
| AmsterdamNetherlands | Up · HTTP 307 | 68 ms | 63.33.128.112Amazon.com, Inc. |
| MadridSpain | Up · HTTP 307 | 125 ms | 63.33.128.112Amazon.com, Inc. |
| WarsawPoland | Up · HTTP 307 | 167 ms | 63.33.128.112Amazon.com, Inc. |
| Los AngelesUSA | Up · HTTP 307 | 203 ms | 44.208.117.196Amazon.com, Inc. |
| São PauloBrazil | Up · HTTP 307 | 913 ms | 52.48.135.140Amazon.com, Inc. |
| SingaporeSingapore | Up · HTTP 307 | 244 ms | 16.76.75.246Amazon.com, Inc. |
| TokyoJapan | Up · HTTP 307 | 43 ms | 3.115.245.91Amazon.com, Inc. |
Checked with check-host.net from its servers in these cities 3 days ago, for diablo4.blizzard.com. Time is how long each server took to load the page.
Diablo FAQ
Is Diablo down right now?
What is the Diablo server status?
Why is Diablo not working today?
How do I check if Diablo is down?
How we track Diablo
The status on this page comes from user-submitted problem reports for Diablo, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Diablo, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. Diablo doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.