Get short, timely messages from BlizzardCS.

Twitter is a rich source of instantly updated information. It's easy to stay updated on an incredibly wide variety of topics. Join today and follow @BlizzardCS.

Get updates via SMS by texting follow BlizzardCS to 40404 in the United States
Codes for other countries

Two-way (sending and receiving) short codes:
Country Code For customers of
Australia
  • 0198089488 Telstra
Canada
  • 21212 (any)
United Kingdom
  • 86444 Vodafone, Orange, 3, O2
Indonesia
  • 89887 AXIS, 3, Telkomsel
Ireland
  • 51210 O2
India
  • 53000 Bharti Airtel, Videocon
Jordan
  • 90903 Zain
New Zealand
  • 8987 Vodafone, Telecom NZ
United States
  • 40404 (any)

BlizzardCS

  1. @ataraxia_status it is an app used with World of Warcraft. :)
  2. The issues with the Mobile Armory should be resolved. You may need to restart the app before being able to log in.
  3. We are aware of issues accessing the Mobile Armory. While we do not have an ETA on when it may be resolved it is under investigation.
  4. @Hungpowshrimp Make sure you have created a BattleTag and have selected it in order to post on the D3 Forums.
  5. @Wyverenight it usually means you have been disconnected or are unable to connect. If it persists please visit D3 Tech bit.ly/KriyBB
  6. @skysignor you should be contacted through the Support Site. bit.ly/lGGy0B
  7. @wdharrisjr I don't believe it will show up until after the initial review. Hopefully you'll hear something soon. Good luck!
  8. @rawblol The digital copy cannot currently be gifted. It is automatically applied directly to the account purchasing it.
  9. @Verius If you are still having an issue you may want to visit our Tech Support forum for D3. Start here: bit.ly/Kwj7uE
  10. @CynthiaWilder He should be able to cancel the transaction by visiting the History/Status section under Character Transfers.
  11. @_TheAri_ queue times are unfortunately longer than we'd like. They are working through those tickets as quickly as they can to get to yours
  12. @R0bVance Completely understandable, especially when told that it was resolved. You should be set now. Can you give it a try?
  13. @R0bVance odd, the notes I see indicate that it should have been. I'll see what I can find out.
  14. @georgewow it is currently under investigation. We hope to have the issue resolved as soon as we can.
  15. @lexiecgreys that is very possible. You'll need to contact our Account Services department. bit.ly/tu3Kf5
  16. @msherretz it appears it is currently under investigation. We hope to have the matter resolved as soon as we can.
  17. @KadriW it is currently being looked into. Hopefully it is a minor hiccup that can be resolved soon.
  18. @Tanker82372634 we do not provide internal logs to the public. We would absolutely verify if there was an issue on our end though.
  19. @Tanker82372634 To play devil's advocate, you could easily say the information was fabricated if we did.
  20. @wdharrisjr the link at the bottom of the page will allow you to report the compromise if you have not already.