Connection issue during evenings.

Good day! I would like the know if there are solutions on my problem.

I am located in Japan near Nagoya area. My ISP is Softbank Japan. I play on the server Tonberry(a Japanese-based server). My connection is via ethernet cable CAT-6 and my router is Buffalo Airstation WZR-1750DHP2(Version 2.28).

My problem is, during evenings, I suffer lag spikes and packet losses. Even though I am connected via ethernet cable.

Is there solutions or fixes to this? I hope you can help me. Thank you!

bump.......

Similar issue for me. Since 2 weeks ago i've been suffering lag spikes almost make the game unplayable during the daytime here (Philippines) and eases out at night around 11pm. Also Tonberry server. Doing ping tests to Tonberry's IP does shows timeouts.

ISP is PLDT

Run WinMTR pointed at your server during the times you have this problem.

If it follows the theme we've been seeing in the US and more recently Europe as well... probably there's some overloaded nodes dropping packets between you and the server.

Quote:

---

Originally Posted by Risvertasashi

Run WinMTR pointed at your server during the times you have this problem.

If it follows the theme we've been seeing in the US and more recently Europe as well... probably there's some overloaded nodes dropping packets between you and the server.

---

Is WinMTR a Network Diagnostic Tool? Sorry for delayed reply. How do I run and understand them?

Apparently I've been jinxed as well. I was lagging horribly in The Aery, so I re-logged, but I got signed out of PSN, when I finally got to the loading screen after selecting my character, I got Lobby Server error, so I had to start all over again. Got into the dungeon, then DC'd almost right away, another Lobby Server error, before I finally was able to log into the game. Honestly, the party I had was incredibly patient, they didn't even kick me out.

Play on the American server Balmung myself have been for the last six months (from Europe) and I've had no problems, until recently a few days ago. (Internet speed of 160 Mbps since I need it for work.)

Not exactly a tech expert here either. How wide spread is this problem? Presumably since it's a whole four of us it has something to do with our end or is there actually a wider problem?

I don't think its my connection, I can stream video without issues. I've seen a few people DC'ing in dungeons more often and having lagging issues.

Quote:

---

Originally Posted by keroo

Is WinMTR a Network Diagnostic Tool? Sorry for delayed reply. How do I run and understand them?

---

Yes. http://winmtr.net/download-winmtr/ , and Tonberry's IP is 124.150.157.30

Quote:

---

Originally Posted by Momoro_Momo

Play on the American server Balmung myself have been for the last six months (from Europe) and I've had no problems, until recently a few days ago. (Internet speed of 160 Mbps since I need it for work.)

Not exactly a tech expert here either. How wide spread is this problem? Presumably since it's a whole four of us it has something to do with our end or is there actually a wider problem?

---

It's quite widespread...take a look at some of the maps for services here (if not in the US, links to other regions are at the bottom of the page):

www.downdetector.com/companies

Typically it is an issue amongst the ISP's in play getting us from our localized networks over to SE's ISP. Usually, it's either the third party peering partner's network acting up (like Level3, Verizon's UUnet/Alter.net, Telia, etc.), or it is an issue occurring at the exchange points on either end of their network.

That is why your sessions to other servers may be running just fine. The problem isn't within your local network, but one of the networks along the specific path your ISP has assigned you to get to SE's ISP. Just like you don't take the same highways to go from LA to Atlanta as you would to go from LA to Seattle---you take different routes to get to different ISP's in other regions. The routing is determined by your ISP's policies, and will require their Tier3 team to get involved with investigating and addressing it. Not the guys typically answering the 800 number or the guys that come check your lines (tiers 1 and 2)--you need the Tier3 (Engineers) that work on things deeper into the network. You my do better to contact them through online methods if available--the phone centers are often limited in what they can say and do for you.

You may see some bad spiking at some of these hops in between you and the addresses starting with 199, 124, or 195 if you run a tracert to your lobby server. Here are the registered names for some of them them:

neolobby02.ffxiv.com (Aether - 199.91.189.74)
neolobby04.ffxiv.com (Primal - 199.91.189.93)
neolobby06.ffxiv.com (Chaos - 195.82.50.9)

(never had reason to match up the Japan lobbies, but they use the same name scheme with odd numbers 01, 03, 05--and their IP's start with 124)

Such traces can be an invaluable tool for that same Tier3 department--it gives them a roadmap of the particular route you take, and gives them indications of where they need to be investigating.

Quote:

---

Originally Posted by Raist

It's quite widespread...take a look at some of the maps for services here (if not in the US, links to other regions are at the bottom of the page):

www.downdetector.com/companies

Typically it is an issue amongst the ISP's in play getting us from our localized networks over to SE's ISP. Usually, it's either the third party peering partner's network acting up (like Level3, Verizon's UUnet/Alter.net, Telia, etc.), or it is an issue occurring at the exchange points on either end of their network.

That is why your sessions to other servers may be running just fine. The problem isn't within your local network, but one of the networks along the specific path your ISP has assigned you to get to SE's ISP. Just like you don't take the same highways to go from LA to Atlanta as you would to go from LA to Seattle---you take different routes to get to different ISP's in other regions. The routing is determined by your ISP's policies, and will require their Tier3 team to get involved with investigating and addressing it. Not the guys typically answering the 800 number or the guys that come check your lines (tiers 1 and 2)--you need the Tier3 (Engineers) that work on things deeper into the network. You my do better to contact them through online methods if available--the phone centers are often limited in what they can say and do for you.

You may see some bad spiking at some of these hops in between you and the addresses starting with 199, 124, or 195 if you run a tracert to your lobby server. Here are the registered names for some of them them:

neolobby02.ffxiv.com (Aether - 199.91.189.74)
neolobby04.ffxiv.com (Primal - 199.91.189.93)
neolobby06.ffxiv.com (Chaos - 195.82.50.9)

(never had reason to match up the Japan lobbies, but they use the same name scheme with odd numbers 01, 03, 05--and their IP's start with 124)

Such traces can be an invaluable tool for that same Tier3 department--it gives them a roadmap of the particular route you take, and gives them indications of where they need to be investigating.

---

Thanks for the detailed response Raist it's much appreciated, will be going over the advice thoroughly come the morning since it's 3:00 am here. You're doing gods work!