Thanks for your reports, everyone! We are investigating this issue and believe the login error (“A character with that name already exists”) and the loading screen disconnects that began last night (July 2) are related.
We’ll share updates in this thread as they become available. I’m sorry for the disruption this causes in the meantime. Retrying is the only known “workaround” at this time.