So, I'm pretty sure this isn't the first time that something like this has been posted, but I think I have a little extra to add on that may help in the longrun for those that can't access accounts and possibly for Bungie's research into the current issues.
I was forcibly disconnected and signed out during the update earlier while in a fireteam with my close buddies. I attempted to sign back in about 2 or 3 minutes later and was promptly denied access to Bungie's servers.
Ok. No big deal. They were probably still being rebooted.
3 hours, 2 router resets, 1 NAT type change, 4 attempts without ethernet cable, and overall ~25-30 attempts later, I gave up. After generating a bit of hatred from attempting to login to my main, I decided to say "why not?" and try to generate a new character... aaaaaaaaaaaaaaaaaaand it worked.
I can freely access the new character, but I currently can't access my lv 24 warlock. So, my current assumption is that my main's save file was corrupted when it was booted out. If anyone else has the same issue, let it be known.
-
Edited by kemo: 9/26/2014 10:36:18 AMyep, same problem here, it's on their end. Nothing to do with our connections in the most cases. I was able to play without even single problem until the moment I got disconnected and had a little "roll back" where actions I did, were not saved. So I went off and today there's "Unable to load Destiny account. Please try again later." on my profile while I can't get into the game on my main character. Other PSN accounts on my console works as expected. Bungie did you just rushed the last update to fix the Cave farming morons and broke something on your end?