Lobby Server

Adding my name to the list. Adamantoise server.

I appreciate this isn't any help to you, but I'm not having a problem here (Aether/Sargatanas) and it might be worthwhile you all doing a traceroute. At a guess you're using an ISPs that is routing you through Level3 (traceroute will show if so) which is probably where the issues are as they're notorious for this. This is just a guess through until someone posts a traceroute though :(

I was DCed from Aether server (Adamantoise) 3 times today, and I have a friend that can't make it past the lobby boss on Aether Data server. I won't be surprised if they take down the NA
servers later

Quote:

---

Originally Posted by Syx

Primal DC. Hyperion server. Multiple 90002 disconnects followed by 2002 lobby errors. Doesn't matter what zone I'm in.

---

Same issue here. Getting a lot of disconnects from the game and then the lobby error. Adamantoise server.

Cactuar server. Been disconnected multiple times today and can't stay logged in game.

Quote:

---

Originally Posted by worldofneil

I appreciate this isn't any help to you, but I'm not having a problem here (Aether/Sargatanas) and it might be worthwhile you all doing a traceroute. At a guess you're using an ISPs that is routing you through Level3 (traceroute will show if so) which is probably where the issues are as they're notorious for this. This is just a guess through until someone posts a traceroute though :(

---

Utterly pointless; but to dissuade everyone else from wasting their time with this, I have a 22ms ping response from 199.91.189.74 (the lobby server) and reach there in 15 hops. My ISP routes through Cogent, which is also the Tier 1 ISP SE uses at their CoLo.

SE broke something during maintenance. It's as simple as that.

Quote:

---

Originally Posted by Syx

Utterly pointless; but to dissuade everyone else from wasting their time with this, I have a 22ms ping response from 199.91.189.74 (the lobby server) and reach there in 15 hops. My ISP routes through Cogent, which is also the Tier 1 ISP SE uses at their CoLo.

SE broke something during maintenance. It's as simple as that.

---

I figured I'd post anyway, maybe my tracert has something of use in it.

Code:

---

Tracing route to 199.91.189.74 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  router.Belkin [192.168.2.1]
  2    8 ms    9 ms    9 ms  142.254.208.57
  3    26 ms    21 ms    22 ms  agg40.plmonhbo01h.northeast.rr.com [24.58.224.177]
  4    23 ms    21 ms    22 ms  agg46.ptldmehx02r.northeast.rr.com [24.58.42.96]
  5    31 ms    31 ms    31 ms  be25.albynyyf01r.northeast.rr.com [24.58.32.64]
  6    41 ms    39 ms    39 ms  bu-ether36.nycmny837aw-bcr00.tbone.rr.com [107.14.19.100]
  7    37 ms    62 ms    44 ms  0.ae1.pr1.nyc20.tbone.rr.com [107.14.17.218]
  8    37 ms    38 ms    38 ms  ix-ae-16-0.tcore1.N75-New-York.as6453.net [66.110.96.81]
  9    49 ms    *      50 ms  if-ae-9-2.tcore1.NTO-New-York.as6453.net [63.243.128.121]
 10    50 ms    49 ms    49 ms  if-ae-7-5.tcore1.N0V-New-York.as6453.net [63.243.128.142]
 11    50 ms    49 ms    49 ms  if-ae-2-2.tcore2.N0V-New-York.as6453.net [216.6.90.22]
 12    58 ms    49 ms    58 ms  if-ae-5-2.tcore2.MTT-Montreal.as6453.net [64.86.226.57]
 13    48 ms    49 ms    49 ms  if-ae-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115.89]
 14    50 ms    49 ms    50 ms  if-ae-5-2.tcore1.W6C-Montreal.as6453.net [64.86.31.6]
 15    50 ms    49 ms    49 ms  66.198.96.50
 16    50 ms    53 ms    49 ms  192.34.76.2
 17    50 ms    49 ms    50 ms  199.91.189.234
 18    49 ms    50 ms    50 ms  199.91.189.74

Trace complete.

---

Balmung for the last Hour

Sargatanas for the last 2 hours. Can't stay connected. My net is good. Had my provider test my line. Easily streaming stuff and surfing. I restarted my router and my pc for good measure.Changed zones area.. loggin for 2 mins .. dc symbol 900002 then 2002 .. everything was fine before maint.

I've been getting a lovely mix of 90001, 90002, 2002, with one 10102 Error Trying to log back in. Adamantoise, Aether Data Server. They're probably going to do an emergency maintenance at some point once they figure out what they did wrong.