Diablo III Patch 1.03 is already available in the Americas region. Scheduled maintenance started today (June 19) at 3 a.m. PDT (GMT-7). Servers even went back online ahead of schedule, at 9:45 a.m. instead of 1 p.m.
It will then be deployed in Europe, tomorrow morning (June 20), between 3 a.m. and 1 p.m. CEST (UTC+2).
Finally, Asian servers will receive the update on June 21, between 4 a.m. and 2 p.m. GMT+8.
This patch includes numerous bugfixes, and brings several changes to monsters and items:
For a lot of people they would rather do something frustrating or boring in Inferno Act IV (such as having Tyrael fight for them or breaking vases) for a chance at a "top-tier" upgrade, rather than fight hordes of monsters in Inferno Act I.
Inferno balance right now has a difficulty gap in which Act I feels about right, but Act II feels like trying to bust through a brick wall. In patch 1.0.3 we’re going to be lowering that wall by adjusting the damage and health of monsters in Inferno Act II, III and IV. We feel like Act I Inferno is in a pretty good place.
Blizzard acknowledges that legendary items should be better than blue items, and that it is not the case at the moment, but they will not be fixed in Patch 1.03.
Similarly, class tuning is not the main priority of this patch.
Class tuning will be an ongoing process, and we’re targeting the 1.1 patch for most class tweaks, with a focus on punching build diversity up a few more notches.
Some players reported problems such as: not being able to earn any XP, followers reverting to level 13, and/or the game showing "Starter Edition". Apparently, all of those problems can be solved by changing your Battle.net password, and restarting the game.
FOLLOWERS LEVEL 13/CAN'T EARN XP/MUST UPGRADE
If you run into this behavior, please attempt the following.
1. Log out and close Diablo III
2. Perform a Password Reset: https://us.battle.net/account/support/password-reset.html
3. After you've changed your password, log back in and try again.
*update 6/19/2012 4:00 PM PDT- This issue should now be resolved