The constant disconnects

[Squintina]

So after getting disconnected about 4 more times while trying to do the MSQ, I decided to run tracert with the NA data center during a severe lag moment, with a 90006 disconnect about 30 seconds after this finished. Most of it looks normal, except for this section here:

 
  7    45 ms    44 ms    44 ms  ae0.bx01.toro.on.aliant.net [207.231.227.53]
  8    46 ms    44 ms    45 ms  ae52.edge1.Toronto2.Level3.net [4.31.208.9]
  9     *        *        *     Request timed out.
 10    51 ms    49 ms    49 ms  NTT-level3-90G.NewYork1.Level3.net [4.68.110.74]
 11    50 ms    50 ms    52 ms  ae-3.r24.nycmny01.us.bb.gin.ntt.net [129.250.5.61]
 12   119 ms   122 ms   159 ms  ae-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.13]
 13   115 ms   127 ms   114 ms  ae-0.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.54]
 14   129 ms   131 ms   132 ms  ae-3.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.124]
 15   138 ms   136 ms   136 ms  ae-41.r02.snjsca04.us.bb.gin.ntt.net [129.250.6.119]
 16   136 ms   136 ms   136 ms  ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
 17   136 ms   134 ms   136 ms  xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
 18     *      136 ms   135 ms  204.2.229.234
 19   135 ms   136 ms   135 ms  204.2.229.9

Hopefully that can help.

Not sure about everyone else, but yours looks like a level 3 node issue (a hop node your ISP is passing through).

I remember 2 years ago a bunch of Verizon people, myself included, in the US had issues connecting because of a level 3 node they were using while pretty much everyone else was playing fine and the thing we had in common is our traces also timed out after a Level3.net connection.

[Telanthropus]

Not sure about everyone else, but yours looks like a level 3 node issue (a hop node your ISP is passing through).

I remember 2 years ago a bunch of Verizon people, myself included, in the US had issues connecting because of a level 3 node they were using while pretty much everyone else was playing fine and the thing we had in common is our traces also timed out after a Level3.net connection.

I've heard of people having problems with Level3 when I started looking into this, for sure. Was there any solution at the time, or is it just something to wait for Square to sort out?

[Squintina]

I've heard of people having problems with Level3 when I started looking into this, for sure. Was there any solution at the time, or is it just something to wait for Square to sort out?

Well a level3 issue isn't really something SE can do anything about, it's another company (think of it this way, your ISP pays Level 3 to borrow their hops so that they don't have to build their own). But back then a major DDOS attack to FF14 caused the level 3 hop to overload (or something), which didn't just affect FF14 but also other websites/services traffic routed through that same hop node. I remember some (but not all) of my remote clients at work could no longer be accessed. Enough people complained to their ISPs about it after the community lectured people on what level3 meant and eventually the ISPs contacted Level3 and Level3 fixed their pathing.

http://downdetector.com/status/level3/map/

And it looks like they're having issues again.

I also remember another game I was playing (ish, was at endgame, nothing to do) had issues and that game company reached out to level3 directly to report that a bunch of players on their own forum was encountering issues with them. I suppose SE could also do that if other people report the same issue you're having.

Once again, not saying that this is what's affecting everyone, but it could certainly be a % of the people currently having issues.