server's

[gerash]

But i'm not east coast's, so makes you wander how many people can't log in right now

[Nakarumi]

I'm constantly getting booted from Famfrit and having severe issues trying to log in and stay logged in. I'm part of the east coast here.

[Raist]

But i'm not east coast's, so makes you wander how many people can't log in right now

You most likely get routed through them though. As stated earlier, some issues were caught around Washington/Virginia, and then again at Toronto. TWC forums are also showing posts for issues with XO.net, which is more common for the western half of the US. Ran my traces up the flag pole on their forums to join the crowd complaining over there....if it doesn't improve I'll try going after them through email I guess. Here's a dump of some data I just took:

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ping 199.91.189.30

Pinging 199.91.189.30 with 32 bytes of data:
Reply from 199.91.189.30: bytes=32 time=160ms TTL=239
Reply from 199.91.189.30: bytes=32 time=69ms TTL=239
Reply from 199.91.189.30: bytes=32 time=72ms TTL=239
Reply from 199.91.189.30: bytes=32 time=70ms TTL=239

Ping statistics for 199.91.189.30:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 69ms, Maximum = 160ms, Average = 92ms

C:\Windows\system32>ping 199.91.189.30

Pinging 199.91.189.30 with 32 bytes of data:
Reply from 199.91.189.30: bytes=32 time=70ms TTL=239
Request timed out.
Reply from 199.91.189.30: bytes=32 time=71ms TTL=239
Reply from 199.91.189.30: bytes=32 time=73ms TTL=239

Ping statistics for 199.91.189.30:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 70ms, Maximum = 73ms, Average = 71ms

C:\Windows\system32>ping 199.91.189.31

Pinging 199.91.189.31 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 199.91.189.31: bytes=32 time=69ms TTL=238
Reply from 199.91.189.31: bytes=32 time=72ms TTL=238

Ping statistics for 199.91.189.31:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 69ms, Maximum = 72ms, Average = 70ms

C:\Windows\system32>tracer 199.91.189.30
'tracer' is not recognized as an internal or external command,
operable program or batch file.

C:\Windows\system32>tracert 199.91.189.30

Tracing route to 199.91.189.30 over a maximum of 30 hops

  1     2 ms    <1 ms    <1 ms  LPTSRV [10.10.100.1]
  2     *        *        *     Request timed out.
  3    24 ms    30 ms    31 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    15 ms    11 ms    14 ms  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5    26 ms    27 ms    25 ms  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6    33 ms    33 ms    35 ms  bu-ether35.asbnva1611w-bcr00.tbone.rr.com [107.14.19.42]
  7   148 ms   112 ms    32 ms  0.ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
  8    30 ms    29 ms    30 ms  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9    71 ms    72 ms     *     if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
 10    71 ms     *       73 ms  64.86.85.1
 11     *        *        *     Request timed out.
 12   197 ms   200 ms     *     if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 13    70 ms    70 ms    70 ms  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 14     *        *        *     Request timed out.
 15    92 ms     *       69 ms  192.34.76.2
 16    70 ms     *       70 ms  199.91.189.234
 17    72 ms     *        *     199.91.189.30
 18    72 ms     *        *     199.91.189.30
 19     *       73 ms    73 ms  199.91.189.30

Trace complete.

C:\Windows\system32>tracert neolobby02.ffxiv.com

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  LPTSRV [10.10.100.1]
  2     *        *        *     Request timed out.
  3    21 ms    31 ms    28 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    15 ms    12 ms    12 ms  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5    29 ms    25 ms    25 ms  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6    35 ms    33 ms    35 ms  bu-ether35.asbnva1611w-bcr00.tbone.rr.com [107.14.19.42]
  7    31 ms    57 ms    37 ms  0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
  8   152 ms   162 ms   153 ms  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9    71 ms     *        *     if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
 10     *       72 ms     *     64.86.85.1
 11    71 ms    72 ms    72 ms  if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
 12    71 ms    71 ms    72 ms  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 13    70 ms     *        *     if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 14    71 ms    73 ms     *     66.198.96.50
 15     *       70 ms    73 ms  192.34.76.2
 16     *       72 ms    73 ms  199.91.189.234
 17     *       69 ms    70 ms  199.91.189.74

Trace complete.

C:\Windows\system32>tracert neolobby02.ffxiv.com

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  LPTSRV [10.10.100.1]
  2    11 ms    30 ms    22 ms  cpe-75-176-160-1.sc.res.rr.com [75.176.160.1]
  3    27 ms    30 ms    29 ms  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4    14 ms    11 ms    15 ms  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5    25 ms    22 ms    23 ms  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6    31 ms    33 ms    35 ms  bu-ether35.asbnva1611w-bcr00.tbone.rr.com [107.14.19.42]
  7    30 ms    31 ms    30 ms  0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
  8    82 ms    65 ms    50 ms  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9     *        *        *     Request timed out.
 10     *       70 ms     *     64.86.85.1
 11     *       70 ms    71 ms  if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
 12    69 ms     *       72 ms  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 13     *        *       72 ms  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 14    69 ms     *        *     66.198.96.50
 15    73 ms    72 ms     *     192.34.76.2
 16    70 ms    72 ms    72 ms  199.91.189.234
 17     *       71 ms    72 ms  199.91.189.74

Trace complete.

C:\Windows\system32>pathping neolobby02.ffxiv.com

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:
  0  G75VXLAP [10.10.100.10]
  1  LPTSRV [10.10.100.1]
  2  cpe-75-176-160-1.sc.res.rr.com [75.176.160.1]
  3  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
  4  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
  5  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
  6  bu-ether35.asbnva1611w-bcr00.tbone.rr.com [107.14.19.42]
  7  0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
  8  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9     *     if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
 10  64.86.85.1
 11  if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
 12  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 13  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 14     *        *     66.198.96.50
 15     *        *     192.34.76.2
 16  199.91.189.234
 17  199.91.189.74

Computing statistics for 425 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           G75VXLAP [10.10.100.10]
                                0/ 100 =  0%   |
  1    2ms     0/ 100 =  0%     0/ 100 =  0%  LPTSRV [10.10.100.1]
                                0/ 100 =  0%   |
  2   16ms     0/ 100 =  0%     0/ 100 =  0%  cpe-75-176-160-1.sc.res.rr.com [75.176.160.1]
                                0/ 100 =  0%   |
  3   20ms     0/ 100 =  0%     0/ 100 =  0%  cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
                                0/ 100 =  0%   |
  4   13ms     0/ 100 =  0%     0/ 100 =  0%  clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
                                0/ 100 =  0%   |
  5   25ms     0/ 100 =  0%     0/ 100 =  0%  be33.drhmncev01r.southeast.rr.com [24.93.64.180]
                                0/ 100 =  0%   |
  6   32ms     0/ 100 =  0%     0/ 100 =  0%  bu-ether35.asbnva1611w-bcr00.tbone.rr.com [107.14.19.42]
                                0/ 100 =  0%   |
  7   38ms     1/ 100 =  1%     1/ 100 =  1%  0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
                                0/ 100 =  0%   |
  8   31ms     0/ 100 =  0%     0/ 100 =  0%  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
                                0/ 100 =  0%   |
  9   31ms     0/ 100 =  0%     0/ 100 =  0%  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
                                0/ 100 =  0%   |
 10   49ms     0/ 100 =  0%     0/ 100 =  0%  64.86.85.1
                                0/ 100 =  0%   |
 11   49ms     0/ 100 =  0%     0/ 100 =  0%  if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
                                0/ 100 =  0%   |
 12   49ms     0/ 100 =  0%     0/ 100 =  0%  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
                               36/ 100 = 36%   |
 13   72ms    36/ 100 = 36%     0/ 100 =  0%  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
                                2/ 100 =  2%   |
 14   71ms    38/ 100 = 38%     0/ 100 =  0%  66.198.96.50
                                1/ 100 =  1%   |
 15   74ms    39/ 100 = 39%     0/ 100 =  0%  192.34.76.2
                                1/ 100 =  1%   |
 16   71ms    41/ 100 = 41%     1/ 100 =  1%  199.91.189.234
                                0/ 100 =  0%   |
 17   72ms    40/ 100 = 40%     0/ 100 =  0%  199.91.189.74

Trace complete.

Note that my typical response times along the TATA routes consistently stay below 80ms across the board even during congested primetime periods, with the odd spike to around 100 after 10PM if something major is going on (like presidential debates, superbowl, etc.), but nothing hardly game breaking like this. When TWC puts Cogent in play for me the times are even lower than that until things go south on us. But Level3 is always a nightmare...don't even bother tracking them anymore, since they barely stay in play for even a week.

[Nakarumi]

Yeah, my tests were looking very similar. This sucks. I was just in the middle of trying to help my FC mates with clearing Alex for the first time.

Tracing route to 199.91.189.74 over a maximum of 30 hops

  1     3 ms     2 ms     2 ms  router.belkin [192.168.2.1]
  2     9 ms     8 ms     9 ms  mta-107-13-0-1.nc.rr.com [107.13.0.1]
  3   111 ms    15 ms    29 ms  cpe-174-111-116-093.triad.res.rr.com [174.111.116.93]
  4    15 ms    13 ms    13 ms  cpe-024-025-045-008.ec.res.rr.com [24.25.45.8]
  5    16 ms    18 ms    14 ms  be31.drhmncev01r.southeast.rr.com [24.93.64.184]
  6    21 ms    19 ms    18 ms  bu-ether45.asbnva1611w-bcr00.tbone.rr.com [107.14.19.44]
  7    21 ms    19 ms    21 ms  0.ae0.pr1.dca10.tbone.rr.com [107.14.17.200]
  8    21 ms    18 ms    19 ms  ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9    59 ms    58 ms    61 ms  if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
 10    59 ms    58 ms    59 ms  64.86.85.1
 11    65 ms     *        *     if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
 12     *        *       59 ms  if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
 13    59 ms    58 ms    60 ms  if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
 14     *       57 ms    64 ms  66.198.96.50
 15     *       63 ms    58 ms  192.34.76.2
 16    61 ms    58 ms    57 ms  199.91.189.234
 17    72 ms     *       61 ms  199.91.189.74

Trace complete.

[Lantia]

But i'm not east coast's, so makes you wander how many people can't log in right now

You may not but your ISP route.....