damn that sucks... well it should be fixed soon.. Battle.net was taken off line doe to the enormous demand on the server.
Diablo III Problems - Servers Overloaded; Battle.net Taken Offline
By Michael Klappenbach, About.com GuideMay 15, 2012
My Bio
Headlines
Forum
RSS
Follow me on:
Facebook
Twitter
Less than 24 hours into the release of Diablo 3 Blizzard was forced to take Battle.net offline in order to add more servers to handle the overwhelming demand for the game. If you are greeted with error codes that prevent you from logging in, Blizzard has provided some information on the error codes. The most frequent seems to be the "Error 37" which indicated that the Diablo III server has reached maximum capacity. Users have also reported issues with character creation but according to Blizzard most of these issues should have been resolved in an early patch, patch 1.0.1. A full list of issues and error codes can be found on thebattle.net technical support forum.
Blizzard has requested fans be patient as the rush to fix issues as fast as possible, stating that character creation may be slower that normal and that if you're unable to login please wait and try again.
http://compactiongames.about.com/b/2012/05/15/diablo-3-problems-servers-overloaded-battle-net-taken-offline.htm