D2r site down for 2+days tells us there are serious problems with Blizzard/Microsoft. The problem is we don’t know how serious at this time. A few hours down, we understand. But DAYS? Are they rebuilding the Ark? Or what? Were they DOGE’D by doofus? Makes no sense–unless their intent is to publicly document their inability to manage/protect Internet hardware/software. That then makes investment in their stock a bad idea. If they are that vulnerable, run from both for self preservation?
Other than the few blips of the authentication servers going down over the past week or so, there have been no issues (for me anyway) with the D2:R servers.
When you say “D2r site down for 2+days”, are you meaning 2+days straight, as in not able to play the game AT ALL for 48+hours? Or just 2+ days with at least one blip of connection problems?
2 Likes
I’ve had no issues playing online with my switch all week long…
Can’t play at all. Click on D2r on desktop, goes to bnet which can NOT go any further. I could see the "connect to Bnet* link and it would spin forever–never connect. All my other Internet stuff worked fine. Just not anything related to D2r. Path of Diablo could also not be played. No idea why unless Bnet was taken down and it took 2 days to get it up again. Can now get on D2r–soon after noon Chicago time (Sat, March 15). Chars still lag noticeably online. Click wait moves, etc. Did not do that before Bnet went down on 3/11. Been doing that ever since.
On Friday (3/14), I deleted D2r from my computer, downloaded the entire game, and reinstalled it. No change to problems. So, it is not me or my D2r causing the problems.
It sounds like there might be some network infrastructure issue going on. A main line could be down that your traffic for D2:R normally took, and whatever path is being used to reroute is also experiencing issues, perhaps due to being overloaded. Maybe some jackwagon with a backhoe dug up a fiber line, or DDoS traffic is flooding the available bandwidth.
Dude… nothing can hurt Diablo 2 except incompetent design teams trying to change it!
Nope. If there is work going on, we get told of it. AND I see it if/when it happens. The ONLY lag is D2r. Everything else does fine.
The only lag is on D2r. It is visible and verifiable independently in town. Easy to see, just look.
Pal aura Might is a bunch of long thin triangles going around his feet on the ground. You can SEE the light pattern of each one lit-then-off going all around in a circle. I do NOT see a circular light pattern. I see three light up side-by-side, then three more across doing the same, then three more next to the first three, then three more next to second three, and so on. This is NOT the normal circular light pattern of Might around his feet–unless it is a lagged pattern.
You aren’t going to be notified about every possible internet hop that is having trouble.
If you want to rule out connection issues, take your computer over to a friends house to test. Have a good old lan party.
Did you tried to turn your PC off and on again?
Could be a routing/ISP issue. Those often affect specific IPs or domains while everything else works fine.
1 Like
Problems are only with Battle.net (1.0 and 2.0), which means many others would be having the same problem if it was related to Bnet. So, not Bnet. Path of Diablo also does not work.
Zero issues for me as well. Funny how everyone else can tell you we’ve all had no problems but you still want to blame the big bad “corporate elite”. I can tell by the terms you’ve used you don’t do any reading or self serving, but require everything else to bend around you and give you a solution.
No offense or anything, but it’s clearly not a bnet issue. I’ve been playing just fine and so has apparently everyone else who has posted here. Although, judging by your previous replies, this is just me talking to a wall.
Edit: My barbarian won’t stop shouting everywhere, he’s calling it “singing”, but it’s terribly loud. Wondering if this is causing your disturbance?
Not everyone is going to be knowledgeable on how the internet works. The layman will almost always assign blame for issues on the host of the game, even if the host isn’t at fault.
I ran a winMTR test on both North American D2:R IPs for 3 hours straight… No excessive lag, and zero loss. My connection is rock solid stable, being only a few hops away from a major backbone that runs through the US, so it isn’t a problem on their end.
OP lives with his mama and she figured out how to use the router to block all blizz games from connecting online, gg
.
Nothing has hurt Diablo 2 more than people preventing it to be improved
1 Like
d2r EU has been iffy for at least 3 weeks for me and others. And quite a few other euros are telling me they are experiencing the same things. Switching to NA at occasions has been fine for me. Asia has the expected lag, but no connection issues. D3 EU has been fine.
So just because you have a few folks on this forum saying everything is nice and dandy doesn’t mean it is.
No offense. 
When did you run those tests? After the 3/11 crash? Did anyone play D2r during and through the crash? There were more than a few who lost stuff as a result–both SC and HC. Idea is to see if this 3/11 incident was a server crash (which seemed most likely at the time) or if it was a router in the path in/out of D2r. Depending on where the trace rt ends, I see routers out–but some of the Bliz servers do not respond to a trace rt (which is why they never reach the final destination–but get close). uswest-battle-net does not respond (so never reach it) but battle-net does. None of the routers near me would cause significant delays–they were just checked. All fine. I see one out in tracert, but quickly bypassed with a re-route (shown in tracert). Closer to the west coast, I see three routers in a row out–all eventually get by-passed and tracert reaches the destination. And I still see the clear lag, in both solo and public games.
I’ve ran multiple winMTR tests during and in between the spikes where people were booted… It’s not the game servers, it’s the authentication servers causing the problems with people getting kicked out, as it not only affects players in D2:R, but other Blizzard games as well.
I’m not able to reproduce what you are describing in game.
Are those servers continuously authenticating accts or just when they join Bnet or when join/exit games or when? It also depends on the method used to authenticate each acct playing on the service.
My best guess is the D2:R servers are checking the authentication servers on a regular basis if players are signed in to Battle.net. If the player signs out or otherwise goes offline according to the authentication servers, then the D2:R servers immediately disconnect the player.
Now the way it should work IMO is IF the D2:R servers see the player sign out or otherwise disconnect from the authentication servers BUT are still connected to the D2:R servers, the D2:R server should start spamming a message to the player that they are about to be dropped from the game. (Say a grace period of 60 seconds) That way any players can stop what they’re doing, and properly leave the game. It would save a lot of players the headaches from losing hardcore characters due to problems with the authentication servers.