Bad lag again with NTT's NA server network

[Ruined-Childhood]

I dunno there's also a post on the ATT forums, unrelated to FFXIV, where OP's company uses NTT's services and is also being told it's a peering issue between ATT and NTT.

[Elizara]

Also from what I saw on the ATT Forums; Please make sure you ID this as a peering issue for sure. There's this thread over there: https://forums.att.com/conversations...f8a752501d13bc . That guy is having trouble and said so with the NTT backbone, might not be related to FFXIV but I'd recommend directing your howls there, otherwise you may keep getting canned responses. MAKE SURE YOU SAY PEERING ISSUE. That's the magic words.

[edit] Jynx! Guess you saw the same post, Ruined-Childhood.

[Ahumaya]

It's good to see that there are other services than just FFXIV that are being affected by this issue. The post on the AT&T forum, however, is still only a single post from an affected user, and does not include any technical data. At best they claim they were "told" it was a "peering issue between AT&T and the backbone of (their) ISP provider which uses NTT"

Even in this thread, people have claimed that NTT have said that it's AT&Ts fault, but the data simply doesn't line up with what we can see. To reiterate, as far as our data provides, the issue occurs on the inter/intraconnection between the Dallas and Los Angeles NTT DCs. This is technically a "peering" connection, and if this connection is operated by AT&T, it could lead some credence to the allegation by NTT that it is an AT&T issue, however as I have said in my last post, if the connection between the Dallas and Los Angeles was run solely by AT&T, it would affect all customers both up and downstream.

As we continue to have no word from a reputable source (and even the AT&T response in that thread is simply "we think the peering team might best assist you based on what you described), the actual data that we have continues to indicate NTT as the culprit in these issues. I'm not saying that contacting AT&T is fruitless, nor that we shouldn't attempt to spread the word on this far and wide, but if we take the pressure off of NTT (which is what NTT wants us to do, based on their alleged responses), and if it IS an NTT issue, as suspected, then it will let NTT continue to get away with it while people chase red herrings anywhere else.

I don't believe that this is as simple as saying "It's Company Y's fault". I do believe that there are many hands in the pot which has fallen over here. However, with the data we have, the largest hand in that pot is NTT, and as such, they should be the ones who at least make a public, technical announcement which at least acknowledges the problem, and preferably identifies the path towards a solution. If it's the inter/intraconnection between their DCs and that peering is operated by AT&T through a direct contact with AT&T, then sure, but that still wouldn't explain why this became an issue overnight on such a regular, exact, and predictable schedule.

Something smells fishy with this whole issue, and I doubt we'll ever know everything.

Here's hoping for the best. Much love.

[ArcadiaP]

I was not expecting other people to be running into NTT issues. If this is impacting people on an even larger scale than just XIV users because of NTT, a fire might be lit and that's good. Absolutely terrible experience and garbage how long this has been going on.

[Illyrian94]

As of right now, I'm seeing significantly different behavior than the "normal" we've had over the past 10+ days. Ping is bouncing around some, but it isn't pegged above 100ms and so far no packet loss. Going to leave Ping Plotter running while I work this afternoon and see if/when things start to get dicey.

[Krojack]

Same crap new day for me. It does seems to be getting off to a slower start though. Maybe other businesses that host with NTT are moving their services to other hosting providers?

[Rekts]

Reading the answers from AT&T on their forums is discouraging at best. Over and over "send traceroutes" or "you can track who the node belongs to". We get it AT&T, it's an NTT node. But it's *their* customers who are affected. They seem to just want to pass the buck instead of getting answers too.

Anyone ever find out how we can contact NTT directly?

[Illyrian94]

Just checked after a meeting and now we're back to having ping pegged around 100ms+ and packet loss. Starting later in the day (for me at least) but definitely still broken.

[Krojack]

Reading the answers from AT&T on their forums is discouraging at best. Over and over "send traceroutes" or "you can track who the node belongs to". We get it AT&T, it's an NTT node. But it's *their* customers who are affected. They seem to just want to pass the buck instead of getting answers too.

Anyone ever find out how we can contact NTT directly?

Some people have contacted NTT and that's how we found it was a peer problem between ATT and NTT but NTT said they can't say more because of an NDA. Most likely AT&T made them sign this with the peer connection.

[Elizara]

I think that says it all. I ain't playing this afternoon. Not on Uverse.

Also checked with my phone. NOPE. No go with that either /sigh. Guess I'm playing in the morning or doing island until this is fixed; ugh.