Noticing bad rubberbanding / lag in game? SE needs to dump their ISP NTT

Quote:

---

Originally Posted by NanaWiloh

Note the FF servers are housed inside NTT data centers. So there is no simple just change ISPs as a fix.

---

It actually is an option, it's not NTT's backbone that is the problem which SE and NTT themselves confirmed. The way it works is each major ISPs have an interconnect hop with NTT, as in each ISP and location has different ways to get into the NTT network. I'm on Google Fiber and we route through the newer NTT Chicago data center to get to the west coast hops.

Someone say on ATT in Dallas would go likely get routed directly to NTT San Jose and hypothetically it's that ATT route hop is where the bottleneck is. It could be a variety of things, equipment to overcapacity at certain hours.

Quote:

---

Originally Posted by technole

It actually is an option, it's not NTT's backbone that is the problem which SE and NTT themselves confirmed. The way it works is each major ISPs have an interconnect hop with NTT, as in each ISP and location has different ways to get into the NTT network. I'm on Google Fiber and we route through the newer NTT Chicago data center to get to the west coast hops.

Someone say on ATT in Dallas would go likely get routed directly to NTT San Jose and hypothetically it's that ATT route hop is where the bottleneck is. It could be a variety of things, equipment to overcapacity at certain hours.

---

My post was aimed at pointing to the OP that SE dumping NTT would not be a simple ISP change it would be a data center move as FF servers are housed in NTT data centers. Dont need to be some expert to know a data center move would be a overkill solution to the problem.

Quote:

---

Originally Posted by technole

It actually is an option, it's not NTT's backbone that is the problem which SE and NTT themselves confirmed. The way it works is each major ISPs have an interconnect hop with NTT, as in each ISP and location has different ways to get into the NTT network. I'm on Google Fiber and we route through the newer NTT Chicago data center to get to the west coast hops.

Someone say on ATT in Dallas would go likely get routed directly to NTT San Jose and hypothetically it's that ATT route hop is where the bottleneck is. It could be a variety of things, equipment to overcapacity at certain hours.

---

From what I read of here and on reddit, it's to do with a negotiation between one of those hops and AT&T, and they aren't able to publicly disclose the details of the negotiation. My guess, their contract is up for renewal and AT&T wants a lower rate and is hoping people will get upset with NTT and put pressure on them to just agree and sign, meanwhile while the contract is in limbo, hops to that backbone from AT&T have lower priority during high traffic times.

Though what NanaWiloh still stands, at least in regard to topic title of telling SE to change their ISP, no matter what ISP the customer is on, you have to go through NTT backbones to get to XIV servers. In this case you also have to hope your personal ISP has a good deal with NTT, or whoever owns your ISP does. If I had to guess from seeing issues like this cropping up over the last year or so, is that Telecom companies are finally playing their hand after net neutrality was repealed and public noise about it had died down.

Quote:

---

Originally Posted by Gralna

From what I read of here and on reddit, it's to do with a negotiation between one of those hops and AT&T, and they aren't able to publicly disclose the details of the negotiation. My guess, their contract is up for renewal and AT&T wants a lower rate and is hoping people will get upset with NTT and put pressure on them to just agree and sign, meanwhile while the contract is in limbo, hops to that backbone from AT&T have lower priority during high traffic times.

Though what NanaWiloh still stands, at least in regard to topic title of telling SE to change their ISP, no matter what ISP the customer is on, you have to go through NTT backbones to get to XIV servers. In this case you also have to hope your personal ISP has a good deal with NTT, or whoever owns your ISP does. If I had to guess from seeing issues like this cropping up over the last year or so, is that Telecom companies are finally playing their hand after net neutrality was repealed and public noise about it had died down.

---

The way it works is basically an exchange ratio. The "last-mile" ISP like ATT is hypothetically appropriated something like a 6:1 megabyte ratio out of NTT in an agreement. Once they go beyond ratios the backbone provider could end up wanting compensation. Most of the time it can be worked out where money doesn't have to exchange hands just better terms for interchanges like scratch your back and scratch mine ordeals, such as bandwidth for other commercial operations. But the fact that SE had relayed that NTT said it's a non-issue on their end, doesn't prove interchange was likely an issue.

As for NTT in-general, that's not going to change, they also power the JP data centers and are a huge conglomerate that SE is in-bed with. The whole reason they pulled out of Montreal in the first place was likely to get cost savings along with capacity while going to one provider for two continents. The whole FFXIV data centers being in Sacremento isn't an NTT issue either. That was a business decision considering NTT has data centers in Dallas and now DC metro.

Quote:

---

Originally Posted by technole

The way it works is basically an exchange ratio. The "last-mile" ISP like ATT is hypothetically appropriated something like a 6:1 megabyte ratio out of NTT in an agreement. Once they go beyond ratios the backbone provider could end up wanting compensation. Most of the time it can be worked out where money doesn't have to exchange hands just better terms for interchanges like scratch your back and scratch mine ordeals, such as bandwidth for other commercial operations. But the fact that SE had relayed that NTT said it's a non-issue on their end, doesn't prove interchange was likely an issue.

As for NTT in-general, that's not going to change, they also power the JP data centers and are a huge conglomerate that SE is in-bed with. The whole reason they pulled out of Montreal in the first place was likely to get cost savings along with capacity while going to one provider for two continents. The whole FFXIV data centers being in Sacremento isn't an NTT issue either. That was a business decision considering NTT has data centers in Dallas and now DC metro.

---

The reason they pulled out of Montreal was environmental. The servers were in the office building SE owned there, and it's data center couldn't support adding any new servers.

Don’t know what’s going on this morning in particular, but it’s early morning on a Sunday and this is the worst lag I have ever seen. Like my character cannot take 3 steps without lagging. I don’t have all the technical know how to find my fps or packet data. I just know this is the worst I’ve ever seen. (East coast, Comcast, if it matters.)

It seems the AT&T/NTT issue may have gotten resolved because the node finally died given what some are saying on the thread on the tech forums about changes they saw in traceroutes and not seeing that bad node anymore.

You might want to go post over there, Khry, since most of us were on AT&T and yours sounds like something could be brewing with Comcast again.