I can't tell what's going on

[RegnumMagik]

Today, I had trouble logging in. It took 3 90K's and 10105 for me to actually log in the game.

Then, I tried to farm shiva. Everytime we open the pull, I immediately get 90K'd. But then I would be fine for the rest of the run.

So did something changed over night?

[Fornix]

No problems here (yet), hopefully stays that way.

[AdamFyi]

A little laggy on my end recently, but that's probably just my connection. Game is still playable and no disconnections nor error messages... yet. D:

[Noshpan]

It is most likely coincidence rather than correlation but I tend to frequently get connection issues the closer to patch day it gets. Though it's been rainy for the past few days, which could have affected the hop in San Jose, CA that my connection goes through.

[kidvideo]

It is most likely coincidence rather than correlation but I tend to frequently get connection issues the closer to patch day it gets. Though it's been rainy for the past few days, which could have affected the hop in San Jose, CA that my connection goes through.

I doubt it's the rain. The game runs perfectly for me at 4:30am Pacific, then at 5:30pm the lag becomes abysmal, every night since the 2.45 patch. I usually give up & play Destiny or DAI.

[RegnumMagik]

Well now I got 90K'd and can't log back in anymore.

[Saseal]

I had something similar when Sastasha HM/Qarn HM/Snowclaok/etc came out - I kept disconnecting immediately after Madison was pulled. Atleast 4-5 times in a row... and always right after Madi had been pulled (the party would wipe, then run back to the boss room). Luckily it was in an FC party, so no real drama. It was fine the day after, though.
I had massive lag in there one other time in Sastasha HM in a pugged party - Was fine in a DF before that, running around the outside world and afterwards in a hest (I did it to test if it was my net or if it was instance-related lag), open world and another DF afterwards. o_O

But I've run the same one before then and after then completely fine, so... no idea for both of us. It was more than likely timing coincidence (the amount of time taken between re-logging and the pull)

Possibly the data sent and received at initializing the fight was doing something, too?