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
64 bytes from 199.91.189.74: icmp_seq=324 ttl=54 time=102.841 ms
64 bytes from 199.91.189.74: icmp_seq=325 ttl=54 time=102.550 ms
64 bytes from 199.91.189.74: icmp_seq=326 ttl=54 time=103.873 ms
64 bytes from 199.91.189.74: icmp_seq=327 ttl=54 time=360.597 ms
64 bytes from 199.91.189.74: icmp_seq=328 ttl=54 time=336.709 ms
64 bytes from 199.91.189.74: icmp_seq=329 ttl=54 time=334.336 ms
64 bytes from 199.91.189.74: icmp_seq=330 ttl=54 time=562.199 ms
Request timeout for icmp_seq 331
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
Ormuco ORMUCO-FIBER-NETWORK (NET-199-91-184-0-1) 199.91.184.0 - 199.91.191.255
Eidos ORMUC-SE (NET-199-91-189-0-1) 199.91.189.0 - 199.91.189.255
Problem on our ISP end? Hardly. See above for verification.
Square; Rerouting traffic away from these backbones will help the latency issues and free up some breathing room for your already taxed server ports. This is what's called a WIN-WIN situation.
If Ormuco doesn't want to do that, I suggest you get a new fiber provider as they are obviously slow to do any kind of fix and is costing you money.
For everyone affected by latency; Some ISP's have the ability to route your connection around nodes that are having obvious issues. It may be worth a shot to request that you not connect to anything as6453.net (aka TATA COMMUNICATIONS). ISP's don't always do this for users and you are basically at the ISP's mercy and also under the condition that there are different node connections that will jump you to the same end IP.

Reply With Quote





