Square, your NA/EU data centre has serious issues...

[Istym]

Your jumping on every minute detail and using that to deflect attention from the true issue here. All I am seeing is either a shill, or a fan boy spending a mega amount of time running around the forums defending SE.

Also since maintainence this morning everything has been fine.

So the issue I was having up until this point were down 100% to SE as they obv fixed some issue they were having with their data centre this morning.

GTFO my thread ^^

[worldofneil]

GTFO my thread ^^

SE don't reply to threads on this Technical Support forum, the only people that do are other players, like him. If you don't want these players to post their replies then I'm afraid you're going to get no replies at all.

Unless you're only saying you don't want replies that you don't agree with?

[Istym]

Also since maintainence this morning everything has been fine.

So the issue I was having up until this point were down 100% to SE as they obv fixed some issue they were having with their data centre this morning.

Yeah sure lets carry forward the points we want too and ignore those we don't.

I created this thread to express frustration at being ignored by Support via in game support, which directed me here to then be ignored. So any interjection bejond those points is a derailment of obvious proportions.

[Marishi-Ten]

Your jumping on every minute detail and using that to deflect attention from the true issue here. All I am seeing is either a shill, or a fan boy spending a mega amount of time running around the forums defending SE.

Also since maintainence this morning everything has been fine.

So the issue I was having up until this point were down 100% to SE as they obv fixed some issue they were having with their data centre this morning.

GTFO my thread ^^

I don't believe he's jumping down your throat. He's actually providing accurate advice. You can't judge network stability on a couple tracert runs. You have to run it constantly over the course of a few hours on peak times. You also were timing out and dropping packets which would give you a MD5 flag error and the rubber banding issue.

The issue isn't with the SE data center. It's with the backbone and hops that you are routing through dropping packets due to them seeing so much traffic it's overloading their ports.

You're routing through 6sync.net. That's a virtual server. Are you behind a VPN? Also, you're being routed through Level 3. That's a T1 backbone in the US. Ask your ISP to route you though a different path. I doubt the problem is on them though. T1 backbones don't normally experience node issues as they have so much hardware to back up the traffic.

Check this site out: http://www.internetpulse.net/

This shows Level 3 currently having issues with Cogent/TATA nodes (A KNOWN troublemaker that can't seem to keep anything stable for longer than 30 minutes that about 90% of users route through to get to Montreal). This is more than likely the cause of your latency issues. Request a trouble ticket from your ISP so you can be re routed away from Level 3 until they are able to stabilize the connections.

I've provided some data of trace routes showing the issue on a remote server, not the remote host or client:

4 boid-agw1.inet.qwest.net (184.99.65.65) 20.875 ms 18.362 ms 27.125 ms
5 sea-brdr-02.inet.qwest.net (67.14.41.18) 31.322 ms 44.643 ms 55.797 ms
6 ix-1-0-0-0.tcore1.00s-seattle.as6453.net (64.86.123.77) 31.431 ms 30.914 ms 31.687 ms
7 if-11-0-0-5.core1.00s-seattle.as6453.net (64.86.124.25) 192.185 ms
if-13-0-0-4.core1.00s-seattle.as6453.net (64.86.124.13) 315.271 ms 54.614 ms
8 if-4-1-0-0.tcore2.ct8-chicago.as6453.net (64.86.124.10) 104.565 ms 96.403 ms 95.589 ms
9 if-3-2.tcore1.w6c-montreal.as6453.net (66.198.96.45) 106.126 ms 157.243 ms 97.227 ms
10 66.198.96.50 (66.198.96.50) 99.638 ms 99.754 ms 101.073 ms
11 192.34.76.2 (192.34.76.2) 102.590 ms 103.997 ms 100.751 ms

sudo ping neolobby02.ffxiv.com
PING neolobby02.ffxiv.com (199.91.189.74): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 199.91.189.74: icmp_seq=1 ttl=54 time=537.147 ms
64 bytes from 199.91.189.74: icmp_seq=2 ttl=54 time=458.225 ms
64 bytes from 199.91.189.74: icmp_seq=3 ttl=54 time=379.185 ms
64 bytes from 199.91.189.74: icmp_seq=4 ttl=54 time=386.048 ms
64 bytes from 199.91.189.74: icmp_seq=5 ttl=54 time=169.980 ms
64 bytes from 199.91.189.74: icmp_seq=6 ttl=54 time=134.348 ms
64 bytes from 199.91.189.74: icmp_seq=7 ttl=54 time=115.387 ms
64 bytes from 199.91.189.74: icmp_seq=8 ttl=54 time=108.769 ms
64 bytes from 199.91.189.74: icmp_seq=9 ttl=54 time=104.653 ms
64 bytes from 199.91.189.74: icmp_seq=10 ttl=54 time=103.875 ms

--- neolobby02.ffxiv.com ping statistics ---
457 packets transmitted, 454 packets received, 0.7% packet loss
round-trip min/avg/max/stddev = 99.605/113.363/664.401/51.532 ms

boid-agw1.inet.qwest.net (184.99.65.65) 17.779 ms 18.350 ms 17.408 ms
5 sea-brdr-02.inet.qwest.net (67.14.41.18) 30.822 ms 30.159 ms 30.602 ms
6 ix-1-0-0-0.tcore1.00s-seattle.as6453.net (64.86.123.77) 31.615 ms 32.681 ms 30.775 ms
7 if-0-0-0-2.core1.00s-seattle.as6453.net (64.86.123.2) 30.830 ms
if-1-0-0-3.core1.00s-seattle.as6453.net (64.86.123.6) 31.310 ms
if-0-0-0-2.core1.00s-seattle.as6453.net (64.86.123.2) 31.403 ms
8 if-4-1-0-0.tcore2.ct8-chicago.as6453.net (64.86.124.10) 96.160 ms 516.145 ms 699.067 ms
9 if-3-2.tcore1.w6c-montreal.as6453.net (66.198.96.45) 330.758 ms 222.031 ms 96.910 ms
10 66.198.96.50 (66.198.96.50) 100.557 ms 101.032 ms 100.031 ms

[Mang]

Your jumping on every minute detail and using that to deflect attention from the true issue here. All I am seeing is either a shill, or a fan boy spending a mega amount of time running around the forums defending SE.

Also since maintainence this morning everything has been fine.

So the issue I was having up until this point were down 100% to SE as they obv fixed some issue they were having with their data centre this morning.

GTFO my thread ^^

I don't like you. You suck at arguing, your grammar is terrible as shit, and you at no point refuted a thing Raist said.