Diablo 3 Beta Server Update

Posted 20 March 2012 by Nizaris

UPDATE: Diablo is back up! 9PM it is!

UPDATE: Three hours later… we’re getting a message now that maintenance will conclude at 8PM-9PM. Predictions are holding true!

It looks like another update is coming – nothing like a patch, or anything. The outage is assumed to be approximately one hour. Let us all hope we don’t see something like last weekend’s fiasco with beta patch 15. Since this is just a server update, I don’t think we’ll be seeing an outage like last time.

We are currently in the process of performing a small server update and will be bringing the Diablo III beta offline for maintenance shortly. We anticipate that downtime as a result of this update will be minimal, lasting for approximately 1 hour.

Many people have been experience more lag than normal, so hopefully this update will address some of the issues players have been experiencing lately.

  • 6 hours it is then.

    PS: I’m not in the beta…I just enjoy pain and suffering of others. 

  • Ill just recived my key and have been struggeling with the download for 5h with my slow internet. Finnaly when i got my things togheter and are launching the game i’ll get hit by this.
    Just my luck…. 

    • Where did you get that key from ?? I’m being so Geek about D3 why can’t I deserve one ?!
       
      Pitiful disappointment I know.

      • My friend write articles for one of the fansites out there. He happend to have 3 extra so he gave me one.
         

  • Fixing some latency issues? good to hear… Anyway I didn’t face any problem tonight. 2 hours of fun on the beta

  • My bet is 4 hours… I think they are doing this purposely so that people renew their WoW subs while the servers are down.

  • Black maintenance still bars our way

  • With Blizzard’s concept of time… I would be 276 1/2 years old …
     

  • I just hate blizzards messages. Why cant they just say it will take about 3 hours. And if it is up after 1, then hey, good job. They do not really act clever in my eyes. 

    • It’s a developer thing. You wouldn’t understand. 

      Here is how it works:

      What Developers say > What Developers mean
      ——————- ——————–

      1) Essentially complete > It’s half done

      2) Schedule exposure > It slipped three weeks ago

      3) We predict > We hope to God

      4) Screen design is lagging > Not a single screen exists

      5) Risk is high but acceptable > 100 to 1 odds; or, with 10 times the budget and 10 times the people, we stand a 50/50 chance

      6) Potential show stopper > The team has updated their resumes

      7) Serious but not insurmountable > It’ll take a miracle
      problems

      8) Basic agreement has been > The &%$#@’s won’t even talk to us
      reached

      9) Results are being quantified > We’re massaging the numbers so that they will agree with our conclusions

      10) Task force to review > 7 people who are incompetent at their regular jobs have been loaned to the project

      11) Not well defined > Nobody’s even thought about it

      12) Still scoping the requirements See answer to number 11.

      13) Not well understood > Now that we’ve thought about it, we don’t want to think about it anymore

      14) Requires further analysis > Totally out of control
      and management attention

      15) Results are encouraging > Power-on produced no smoke

       

  • Augh, I was about to get to SK with my new Monk.

    fixitfixitfixitfixitfixit