So to alleviate load and latency on our global database, each region–NA, EU, and Asia–has individual databases that also store your character’s information and progress, and your region’s database will periodically write to the global one. As you can imagine, that’s a big task for one database, and wouldn’t cope on its own. First, there’s our global database, which exists as the single source of truth for all your character information and progress. Let’s start at the beginning.īefore we talk about the problems, we’ll briefly give you some context as to how our server databases work. We’re going to get a little bit into the weeds here with some engineering specifics, but we hope that overall this helps you understand why these outages have been occurring and what we’ve been doing to address each instance, as well as how we’re investigating the overall root cause. Our team, with the help of others at Blizzard, are working to bring the game experience to a place that feels good for everyone. This is not a complete solve to us, and we are continuing to work on this issue. A small number of players have experienced character progression loss–moving forward, any loss due to a server crash should be limited to several minutes. Tl dr: Our server outages have not been caused by a singular issue we are solving each problem as they arise, with both mitigating solves and longer-term architectural changes. We also want to give you some insight into how we’re moving forward. Since the launch of Diablo II: Resurrected, we have been experiencing multiple server issues, and we wanted to provide some transparency around what is causing these issues and the steps we have taken so far to address them. I’m not joking, it’s a massive explanation of what’s going on which you can read in full below, but in short, “Sorry, we’re trying to fix as fast as we can”. Blizzard have posted a very lengthy explanation of why Diablo 2 Resurrected has been hit with server issues from launch.
0 kommentar(er)
