Hyperion/Primal issues today

[HyoMinPark]

I'm still convinced this is a weather issue, but I think it should be noted that Level3 is responding to tweets about what's going on with FFXIV today, and are saying they will look into whatever is going on. Again, I don't think this is a Level3 issue, but it would be interesting to see what they say. (Other than "DownDetector is not accurate"...even if that statement is true.)

My last tracert (about 15 minutes ago) routed me through Level3 again. Took 18 hops to reach the server...and tons of packet loss along the way. Even with SE's post about most being able to have a "mostly stable connection" now, I still cannot connect to Aether.

[valli]

Well, being that I play on PS4, on the screen where you put your login/password...there's a string of "news" that says something along the lines of "we are monitoring the situation, and have maintained a mostly stable connection" for all of the NA servers.

Well, that's something, I guess.

Yep and i saw this and was able to log in, do about 3 hunt mobs and bam.. down again LOL *sigh*

[StayKruel]

I was doing fine for a few hours, logged on and off several times to do various RL things and always got back on. Now I'm back to the lobby error again for the past 30 min.

[DevilsGotAnRPG]

I'm still convinced this is a weather issue, but I think it should be noted that Level3 is responding to tweets about what's going on with FFXIV today, and are saying they will look into whatever is going on. Again, I don't think this is a Level3 issue, but it would be interesting to see what they say. (Other than "DownDetector is not accurate"...even if that statement is true.)

My last tracert (about 15 minutes ago) routed me through Level3 again. Took 18 hops to reach the server...and tons of packet loss along the way. Even with SE's post about most being able to have a "mostly stable connection" now, I still cannot connect to Aether.

It may very well be the weather. I even tried my own tracert thing (I'll be damned if I can translate it though), and strangely, I see nothing about "Level 3" that I've seen in others, so does that mean that I'm not being routed through them?

Screw it, I'll post the result. Feel free to translate.

Tracing route to 199.91.189.30 over a maximum of 30 hops

1 41 ms 40 ms 40 ms 10.0.10.1
2 * * * Request timed out.
3 40 ms 40 ms 40 ms ae18-1914.mia12.ip4.gtt.net [173.205.61.209]
4 79 ms 80 ms 83 ms xe-1-3-0.mtl10.ip4.gtt.net [89.149.184.74]
5 80 ms 81 ms 79 ms ormuco-gw.ip4.gtt.net [216.221.156.110]
6 80 ms 79 ms 80 ms 192.34.76.2
7 79 ms 79 ms 80 ms 199.91.189.234
8 80 ms 79 ms 79 ms 199.91.189.30

Trace complete.

[HyoMinPark]

snip

Based on what I know, Ormuco is also in Montreal, and it appears that you're hitting them on your way to your server. So no, you are not being routed through Level3. Level3 usually shows up as such in a tracert (speaking from my experience):

Montreal2.Level3.net

or

ORMUCO-COMM.Montreal2.Level3.net

or some semblance of those two (Level3 is always in the address, though).

It's been noted by some that Ormuco is also having issues (one poster...I think it was in another thread...posted that the couldn't access their website). Whether or not Ormuco has acknowledged that they are having issues, I haven't really looked into. I couldn't access their website earlier either, though it appears to be up now. But Ormuco is also in Montreal where Level3 has servers. Montreal has had some snow recently according to some people that live there, and I know weather can have a big impact on connectivity. So that's why I think this is ultimately just related to the winter weather, and not the fault of Level3, Ormuco, or SE.

Speaking for my last tracert I did, I was routed through Level3....and never could get any connection. My abomination of a tracert looked like this (starting from hop 4, right before I start getting all the requests timed out...before then was normal):

4 37 ms 57 ms 91 ms 12.83.112.13
5 40 ms 32 ms 32 ms 12.122.141.233
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 293 ms * * ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * 67 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * 92 ms * ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]
22 * * 74 ms 199.91.189.23

I'm no tech specialist, but my tracert still tells me that something is going on with Level3 (again, probably weather), and it's preventing me from having a stable connection to my server. I still can't even connect to my data center...I keep getting 2002 errors and booted. :c

[DevilsGotAnRPG]

GAH! It's gonna be -9 up that way tonight...light snow, but the lakes up that way can always change it. Let's face it- those guys are gonna have a real blast fixing those lines, if indeed it is due to bad weather.

Better break out the Carhartts, because some daddy in Kansas needs his FFXIV fix.

*facepalm*

[koroko220]

Still can't connect either

[LilArsynic]

This has lasted all day.

[Mysticales]

from 1pm EST to 741pm... and still cant get on. =( Then Maint at Midnight... so its like *Table Flip*

[Mysticales]

Tracing route to 199.91.189.23 over a maximum of 30 hops

1 1 ms <1 ms <1 ms MY-IP
2 8 ms 9 ms 8 ms 10.2.208.1
3 11 ms 9 ms 11 ms 100.127.41.22
4 11 ms 11 ms 9 ms 172.22.51.96
5 25 ms 15 ms 13 ms port-channel201.car2.Richmond1.Level3.net [4.26.66.25]
6 16 ms 18 ms 17 ms ae36.cr0-was1.ip4.gtt.net [173.205.53.253]
7 75 ms 50 ms 54 ms xe-9-1-0.mtl10.ip4.gtt.net [89.149.180.218]
8 144 ms 140 ms * ormuco-gw.ip4.gtt.net [216.221.156.110]
9 144 ms * * 192.34.76.2
10 * 137 ms 136 ms 199.91.189.234
11 * 151 ms 130 ms 199.91.189.23

Trace complete.

Did I do this right? Seems like with Cox Cable, Im not going through Level 3 really that would time out. So whats up? Or did I check wrong thing?