How to fix Diablo 4 Error 300008 "Your request has timed out"?

Diablo 4 error 300008 means the game asked Blizzard's servers to log you in and no answer came back in time. Most often the login servers are overloaded or faulty, as on the first day of a season, and you can only wait. First check Blizzard's notices, then restart your modem and router.

Facts checked on 14 October 2026. Steps written for Diablo IV on Battle.net for Windows 11 (25H2 and 26H2) and Windows 10 22H2, with the console steps read from Blizzard's, Sony's and Microsoft's support pages.

What Diablo 4 error 300008 means and how it is written

Code 300008 is a timeout. The game sent a request to Blizzard, waited for the answer and gave up when the waiting time ran out. Blizzard's support article for the code carries the message "Your login attempt has timed out. Please try again (Code 300008)" and calls it a connection issue.

A timeout tells you that the answer did not arrive. It does not tell you where it got lost. The request may have died in your Wi-Fi, at your internet provider or inside Blizzard's login servers, and the message looks the same each time. That is why the first job is to find out whose side it is.

Is it Blizzard's servers or your connection? How to check

Blizzard's own list for this code starts with the servers, not with your PC. Step 1 reads: "Check for breaking news on the login screen or follow @BlizzardCS on Twitter for service updates." Only after that come the router, the Wi-Fi and the firewall.

Blizzard's articles name no live status page for Diablo IV. The general connection article says to check a status page "or" the support account and adds "if your game doesn't have a Service Status page, continue troubleshooting". For this game the notices above are the status page.

Error 300008 on PC, PlayStation and Xbox: what differs

The code and its meaning are the same everywhere, but your options are not. On a PC you control the firewall, the proxy, the VPN and the game files. On a console you control the network and little else, and Blizzard's console article is three steps long for that reason.

• A fault can hit one platform only. Blizzard's first notice on 15 September 2026 was about login servers "for #DiabloIV on PlayStation". A friend on PC who gets in does not prove that your PS5 is at fault.
• Switch 2. Blizzard's console article also links Nintendo's support for a connection test. We could not read those steps from a primary source today, so this guide has none for that console.

What causes error 300008, from most to least common

Most often the cause is on Blizzard's side: login servers under load or with a fault. Less often your home network drops or delays the request. Rarely something on the PC blocks it. The order below follows Blizzard's own list and what Blizzard confirmed in 2026. Blizzard publishes no numbers on how often each cause occurs.

How to fix Diablo 4 error 300008

Fix 1 and Fix 2 decide whether you can do anything at all, and they take two minutes. Fix 3 and Fix 4 are Blizzard's network steps for every platform. Fix 5 is for PlayStation and Xbox. Fix 6 to Fix 8 are for Windows PCs only. Stop as soon as the character screen appears.

Fix 1. Check Blizzard's notices before you change anything

2 minutesNo riskEveryone, on every platform, before any other step.

This is step 1 of Blizzard's own article for the code. When the login or authentication servers have a fault, the timeout happens inside Blizzard's network, and no setting on your PC, console or router can shorten it.

1. Start Diablo IV and read the breaking news on the login screen, if a notice is shown there.
2. Open Blizzard's support account: @BlizzardCS on X for the Americas, @BlizzardCSEU_EN for Europe, or @support.blizzard.com on Bluesky.
3. Look for a post from the last hours that names Diablo IV, #D4, #Bnet, login servers or authentication servers.
4. Open the Weekly Maintenance Schedule on Blizzard's support site and check whether Diablo IV is listed for today. Mind the time zone: PDT for the Americas, CEST for Europe.
5. Open the Diablo IV forums, category Technical Support, and look at the newest threads. Many new threads about code 300008 within one hour point at the servers.
6. If you find a notice or a wave of reports, stop here. Try again every 10 to 15 minutes, or come back when Blizzard posts that the issue is resolved.

• A notice can lag behind. On 27 April 2026 a community manager confirmed the problem in a forum thread nine minutes after a player opened it. The forum is often the fastest signal.
• Read the newest post, not the first one you see. Support accounts also post tips and news. Only a post about servers, logins or authentication counts.

Fix 2. Stay in the login queue and retry the right way

5 to 60 minutes of waitingNo riskA season, an expansion or a patch started today, or you see a queue box before the code.

Blizzard says login queues occur when more players than normal log in, and names expansion launches, new seasons and game patches. A timeout during such hours is the crowd, and leaving the line only sends you to its end.

1. Start the game once and log in.
2. If a loading box with an estimated wait timer appears, leave it alone. That box is the queue.
3. Do not close the game, the launcher or the console while the timer runs.
4. If the box with Code 300008 appears, close it with its button (Accept in the 2023 version) and log in again.
5. If it fails several times in a row, wait 10 to 15 minutes before the next attempt instead of pressing the button without a pause.
6. On PC, enter your password and your authenticator code promptly when the Battle.net app asks for them.

• The queue does not keep your place. Blizzard's article on the Battle.net login queue says the queue will not save your place if you leave or are removed, and advises: "Stay in the queue until it finishes. Do not leave or restart the client."
• Support cannot move you forward. The Diablo IV queue article states that customer support is unable to change or bypass queue times.

Fix 3. Power cycle the modem and the router

5 minutesLow riskThere is no notice from Blizzard, or you want to rule out your home network. Works for PC and console.

This is step 2 of Blizzard's list for the code: reset your network devices "to make sure your router hasn't become flooded with data". The console article says the same step resolves most network problems. A full power cycle makes the modem build a new link to your provider.

1. Close Diablo IV.
2. Shut down the PC or turn the console off completely. Rest mode or sleep is not enough.
3. Power down and unplug the modem, and the router if you have a separate one.
4. Leave them unplugged for 60 seconds.
5. Plug in the modem first, then the router, and turn them on.
6. Wait until the connection lights on the front of the modem are steady.
7. Start the PC or console, wait until it has fully started, then start Diablo IV and log in.

• A modem with a backup battery does not restart when you unplug it. Blizzard's note: take the battery out or use the reset button on the modem.
• Sony asks for a longer pause. Its help page for a PlayStation connection error says to turn the modem or router off and wait 5 minutes. On a PlayStation, use the longer pause.
• Old router firmware. Blizzard's firewall article advises updating the router firmware and, for configuration errors, a factory reset with the maker's instructions. A factory reset erases your Wi-Fi name, password and provider settings, so keep it for last.

Fix 4. Use a cable and free up the connection

5 to 10 minutesNo riskYou play over Wi-Fi, on a shared or slow line, or on a satellite or mobile connection.

Step 3 of Blizzard's list tells wireless players to rule out the connection itself. A login is a short exchange with a deadline, and a Wi-Fi link that drops for a moment can miss it even when the servers are fine.

1. Close other programs that use the internet: downloads, updates, cloud backups and video streams. On a console, pause downloads that run in the background.
2. Connect the PC or console to the router with a network cable. Blizzard notes that wireless connections can have difficulties with online gaming.
3. Check that the device now uses the cable. On Windows 11 open Start > Settings > Network & internet: the top of the page shows the active connection.
4. Start Diablo IV and log in.
5. If the code is gone, the Wi-Fi was the weak link. Keep the cable, or move the router closer.

• Satellite, mobile and WiMax. Blizzard states that these connections are "entirely unsupported for PC gameplay". If you play that way, timeouts can come from the line itself, and Blizzard will not troubleshoot it.
• A phone hotspot as a one-time test. If the login works at once over a hotspot, your home line or router is the cause. If it times out there too, the servers are the likelier cause. Do not keep playing on it: see the point above.
• A wider check of the home network on Windows: How to check your internet connection in Windows

Fix 5. On PlayStation or Xbox: check the platform status and run the connection test

10 minutesNo riskYou play on PS5, PS4, Xbox Series X|S or Xbox One, and Fix 1 showed no notice from Blizzard.

Blizzard's console article ends with the console's built-in connection test, because a console has no firewall settings or game repair to try. The test and the maker's status page show whether the console reaches the internet and its own network at all.

1. Open the status page of your platform on a phone or PC: PlayStation Status at status.playstation.com, or Xbox Status on support.xbox.com.
2. If the page shows a failure, maintenance, Limited or Major outage, wait until it is back to normal.
3. Close Diablo IV completely, then turn the console off fully and do the power cycle from Fix 3.
4. PS5: open Settings > Network > Connection Status > Test Internet Connection.
5. PS4: open Settings > Network > Test Internet Connection.
6. Xbox: press the Xbox button, then open Profile & system > Settings > General > Network settings > Test network connection.
7. If the test fails, the problem is the network and not the game. Connect a LAN cable and run the test again.
8. When the test passes, start Diablo IV and log in.

Fix 6. On PC: reset the Windows Firewall and check security software, VPN and proxy

10 minutesRead the warningA Windows PC where only Diablo IV fails, above all with a VPN, a proxy or a third-party security program installed.

Step 4 of Blizzard's list is to check the network configuration for firewall, router or port problems. Blizzard explains that firewalls can restrict packets or change their priority, which causes problems connecting to its services, and that security software sometimes blocks its games by mistake.

1. Press Win + R.
2. Type Firewall.cpl and press Enter.
3. Select Restore Defaults in the menu on the left.
4. Select the Restore Defaults button.
5. Select Yes to confirm.
6. Start Diablo IV. When Windows asks whether to allow the game or the Battle.net app through the firewall, allow it.

Next, the programs that sit between the game and the internet. Blizzard counts antivirus programs, firewalls and VPNs as security software and gives the order: update the program first, then add the game client to its exception list, and only then pause it for a test.

1. Disconnect your VPN and close its app, then try to log in.
2. Update your third-party security program and add Battle.net and Diablo IV to its exception list. The maker's help pages show where that list is.
3. Press Win + R, type inetcpl.cpl and select OK.
4. Open the Connections tab and select LAN settings.
5. Clear Use a proxy server for your LAN. If it was already clear, switch Automatically detect settings off and on once.
6. Select OK and try to log in.

• A proxy you never set. Blizzard warns that proxy settings can be turned on by malware without your knowledge and advises an antivirus scan after you clear them: How to scan for malware with Microsoft Defender
• Pausing protection is a test, not a fix. Blizzard's second option is to pause the security program until its maker fixes the conflict and to run another one, such as Microsoft Defender, in the meantime. If a short pause proves the point, turn it back on and add the exception: Turn off Microsoft Defender protection for a moment

Fix 7. On PC: release and renew the IP address and flush DNS

3 minutesLow riskA Windows PC that still times out after the router restart, while other devices on the same network log in.

Blizzard's general article for players who cannot connect lists this step "to resolve any network conflicts". The PC asks the router for a fresh address and forgets stored server addresses, so the next login looks the servers up again.

1. Close Diablo IV and the Battle.net app.
2. Press the Windows key and type cmd.
3. Right-click Command Prompt and select Run as administrator, then Yes.
4. Type ipconfig /release and press Enter. Wait a few seconds for the reply. The connection drops.
5. Type ipconfig /renew and press Enter. Wait until an address is shown again.
6. Type ipconfig /flushdns and press Enter.
7. Close the window, start the game and log in.

The three commands, in Blizzard's order

ipconfig /release
ipconfig /renew
ipconfig /flushdns

• Not in the 300008 article. This step comes from Blizzard's article "Disconnected from Blizzard Services", not from the short list for this code. It is safe, quick and worth one try.
• No command line? Blizzard says that restarting the computer may produce the same effects.
• Winsock and TCP/IP resets. The old version of this guide added netsh winsock reset. Blizzard's article does not list it. The full network reset is here: Reset the network and flush DNS

Fix 8. On PC: update the game, then run Scan and Repair

10 to 30 minutesNo riskA Windows PC where the game crashed or lost its connection before the code appeared, or where a game update is waiting.

Blizzard's article for code 300008 does not list a repair, so this is the last fix and not the first. It is here for the case in the question above: Blizzard's steps for a login that fails after an abrupt disconnect begin with the repair tool.

1. Open Battle.net. Open the Battle.net desktop app.
2. Select the game. Select the icon of the game you want to repair.
3. Check for updates first. Select the cogwheel next to the Play button and select Check for Updates. An update often fixes the problem on its own.
4. Open Scan and Repair. If the game is up to date, select the cogwheel again and select Scan and Repair.
5. Begin the scan. Select Begin Scan and wait for the repair to finish.

These steps were written for Battle.net on Windows. The full page with the other versions and what each result means: How to verify game files in Steam, Epic Games, Xbox app, EA app, Battle.net and GOG Galaxy

• Update first. Blizzard's repair article says that updating the game often resolves such problems and asks you to check for updates before the repair.
• Steam. The Battle.net tool is not available there. Use Verify integrity of game files on the Installed Files tab of the game's properties, as shown on the Steam tab of the procedure above.
• Code 395002 after a crash. If that code shows up next to 300008, Blizzard says it normally follows an abrupt disconnect and typically resolves within 15 minutes. Wait that long before you repair anything.

If error 300008 is still there: what to collect and where to send it

Blizzard's article for the code ends with one line: if the steps did not resolve the problem, visit the Diablo IV forums. There is no ticket form behind that link. So the useful thing you can do is post a report that staff and other players can work with.

• Platform and store: PC with Battle.net, PC with Steam, PS5, PS4, Xbox Series X|S or Xbox One.
• Region and time: your country, the date and the time with the time zone of the first failure.
• The exact text: "Your login attempt has timed out", "Your request has timed out" or "Quick Join Time Expired", and any second code such as 395002 or 315306.
• Your connection: cable or Wi-Fi, the provider, and whether a second device on the same network logs in.
• What you tried: the fixes above by name, and on a console the result of the connection test.
• Where to post: the Technical Support category of the Diablo IV forum for PC, and Console Bug Report for PlayStation and Xbox. Blizzard runs forums for North America, Europe, Germany, France, Korea and Taiwan.

• When it is your provider or your hardware: other online games time out too, the console's connection test fails, or the trouble follows the router and not the device. Blizzard's connection article ends with the internet provider, and with a local network technician when all else is exhausted.
• When it is Blizzard: only Diablo IV fails, on a connection that passes every test, and other players report the same code in the same hours. Customer support cannot bypass a queue or a server fault for one account.
• When it is only the party feature: if you can log in and play, and the code appears only on Quick Join or in the party finder, your connection is working. A player reported exactly that on 27 September 2026 in a thread with no staff answer. Report it in the bug forum.

How to avoid error 300008 next season

The honest part: you cannot prevent the common case. A season or expansion launch brings more players than normal, and Blizzard confirmed login server trouble on such a day in September 2026. Plan for a delay on the first evening.

Frequently asked questions

What does error code 300008 mean in Diablo 4?

It means a request from your game to Blizzard's servers got no answer in time. Blizzard's support article gives the message as "Your login attempt has timed out. Please try again (Code 300008)" and treats it as a connection issue. The code does not say where the answer got lost. It can be Blizzard's login servers, which is the usual case on the first day of a season, or your own router, Wi-Fi or firewall. That is why Blizzard's list starts with checking for breaking news and only then turns to your network.

Is Diablo 4 down right now, and how do I check?

Blizzard names no live status page for Diablo IV, so you check its notices. Look at the breaking news on the game's login screen, then at Blizzard's support account: @BlizzardCS on X for the Americas, @BlizzardCSEU_EN for Europe, or @support.blizzard.com on Bluesky. Planned downtime is in the Weekly Maintenance Schedule on the support site. The Technical Support category of the Diablo IV forum shows whether many players have the same code in the same hour. A wave of new threads can come before the official notice.

How long does error 300008 last?

There is no fixed length, and Blizzard gives none. When the cause is your own network, it ends as soon as the router restart or the cable fixes the link, usually within minutes. When the cause is a server fault, it ends when Blizzard repairs it. On 15 September 2026 Blizzard posted a first notice about login servers at 09:15 UTC and another about authentication servers at 16:50 UTC, and players on the forum wrote that they waited for hours. Follow Blizzard's support account and try again every 10 to 15 minutes.

How do I fix error 300008 on PS5 or PS4?

Check Blizzard's notices first, because the fault can be on Blizzard's side for PlayStation only, as on 15 September 2026. Then open status.playstation.com to see whether Sony's network has trouble. Turn the console off fully and unplug the modem and router. Blizzard asks for 60 seconds, Sony for 5 minutes. On PS5 run Settings > Network > Connection Status > Test Internet Connection, on PS4 Settings > Network > Test Internet Connection. If the test fails, use a LAN cable and repeat it. If everything passes and the code stays, post on Blizzard's Console Bug Report forum.

How do I fix error 300008 on Xbox?

The steps match the PlayStation ones with Microsoft's names. Read Blizzard's notices, then open the Xbox Status page on support.xbox.com and check that no service is marked Limited or Major outage. Power cycle the modem and router with the console fully off. Then press the Xbox button and open Profile & system > Settings > General > Network settings > Test network connection. A failed test means the console's connection is the problem, and a LAN cable is the first thing to try. A passed test with clean status pages points back at Blizzard's servers.

Does error 300008 mean my account is banned or my character is lost?

Nothing we read from Blizzard says so. The support article describes the code as a connection issue and offers only network steps. A timeout carries no information about your account. Players do sometimes see a second message after a failed login, such as code 395002 about a character that has not finished being saved. Blizzard says that one normally follows an abrupt disconnect and typically resolves within 15 minutes. If a character stays unreachable long after logins work again, report it on the forum.

Why do I get "Quick Join Time Expired" with code 300008 when I can log in?

Because the same timeout code is used for party requests, not only for the login. Players reported "Quick Join Time Expired (Code 300008)" on Blizzard's forum in July 2025, and in September 2026 one player posted log lines in which a quick join failed with a general timeout carrying this number. Blizzard has published no article and, as far as we found, no staff answer on this case. Your connection is working if you can log in and play. Try again later, and report it in the bug forum with the time and your platform.

Will reinstalling Diablo 4 fix error 300008?

Almost never, and Blizzard does not ask for it. The article for the code lists four things: breaking news, the network devices, the wireless connection and the firewall or router settings. A reinstall touches none of them, and it costs a long download. On a PC the Scan and Repair tool in the Battle.net app replaces damaged files without that cost, and Blizzard asks you to check for updates before using it. A player on the European forum wrote in January 2026 that two reinstalls did not remove the code.

Will a VPN get me past error 300008?

We found no Blizzard source that says it does. Blizzard's guidance points the other way: it counts VPNs as security software that can wrongly block its games, and it states that it does not directly support proxies, firewalls or routers. If you already use a VPN, disconnect it for one login attempt, because it adds another place where the request can time out. If the cause is Blizzard's login servers, the route you take to them makes no difference, since the delay is at the destination.