JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by Endlex: 9/26/2014 8:47:22 PM
311

Yesteryday's network Issues has caused bugged accounts

I've been on the forums reading about others suffering issues with their accounts since the network hiccup yesterday afternoon/evening (EST) and have come to the conclusion (as others have) that we all suffered some sort of item bug due to a rollback. During the rollback'd period, we had made changes to items (identifying them, depositing them, etc) and this is the cause of our issue. I'm making this post because everyone's issues are being continuously buried under rants and other posts and I have yet to see this issue catching any Bungie employee's attention. If you believe you are experiencing this issue or have any other information that might help further narrow down the cause of this bug please do so. Our centipede errors are not a network issue and WILL NOT sort themselves out on their own or through changes in our network. I've also included below some symptoms for those unsure if they are affected by this issue. Symptoms: - Experienced a rollback yesterday returning items to prior states (from identified to encrypted, back in inventory from vault) - Get Centipede errors when trying to connect after late afternoon (EST) yesterday - Your Bnet Destiny profile is failing to load while logged into your account (and sometimes when not) - Other accounts work on your console/network Please help bring this to Bungie's attention and get us an official response of acknowledgement. EDIT: My experience. In the events leading up to and following yesterday's hiccup I started out in cosmodrome and returned to the tower. In the tower I grabbed my public event reward from the post master and proceeded to deposit three ascendant shard I was awarded into my vault. I may have also turned in a bounty and replaced or with a new one, but i cannot confirm this with full confidence. Afterwards I returned to the cosmodrome (patrol) and continued doing bounties and patrol missions. I was kicked back shortly afterwards and was returned to orbit. I noticed my character had lost the experience gained during the patrol causing me to return to level 7. I loaded up patrol again and leveled myself to 8. After finishing my patrol bounty I began the first mission to kill raksis(or something like that) and was continually kicked to orbit with varying errors including centipede and monkey mostly. After a few failed attempts I decided to log out. Upon trying to reconnect I continually got centipede errors. I decided there may be some network issues and turned my console off. I tried again this morning and the problem persisted and that's when I began my own investigation.

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
  • Edited by BK1240: 9/26/2014 10:36:13 PM
    Yes, this is exactly what I believe happened to me as I can no longer log into my account (error code centipede). but this was my exchange of unusual events that led up to the hiccups. I returned from a mission with 2 Blue engrams to identify. I went to the cryptarch and as I was identifying the 2nd item, I got disconnected due to the network hiccup. When I logged back on, both of the engrams were back in my inventory and hadn't been identified. So I went back to the cryptarch to re identify them, I get 2 level 17 items, the network hiccuped again and I was kicked out. I log back on a 3rd time and the items are back to being engrams again. I go to the cryptarch a 4th time to identify them and this time I get 2 level 20 items. I was DC'd a few more times after this, but now the two items stayed as level 20 items for good. During the time frame where the engrams went back and forth between being items and engrams had to most likely be where the issue arose. There was some loss of data or roll back that reverted the changes and is ultimately causing the errors we are seeing now. If I recall correctly this was sometime around/after 6pm EST. Around 11pm I shut of my Xbox during a Crucible match as I had to take an important phone call, and when I tried to log back in I couldnt get to the character screen. The same error has persisted ever since then. Just my thoughts on all this. Really wish I could play the game I waited 2 weeks after the release to buy to avoid this exact scenario...

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

1 2
You are not allowed to view this content.
;
preload icon
preload icon
preload icon