
Originally Posted by
Jeza
So the entire internet is broken....I suggest SQ-ENIX starts making some phone calls to get access to their servers cleaned up then because all these individuals are becoming bigger and bigger crowds everyday and while they CAN'T play FFXIV they CAN play other games just fine on the broken internet. Will spread the word, thanks for all the um...helpful...information....
Sorry if you don't find the factual information and actual real-time maps that I've been posting out there demonstrating the issue helpful. Not to mention all the tracerts and discussions about how my ISP keeps changing my route frequently to stay ahead of the congested corridors. It in fact happened again tonight... was on Cogent last week, and it started getting wonky last night. Today, while I was in Main Scenario Roulette, they bounced my modem and switched me to TATA... and the route is spot on with <60ms latency from here in South Carolina. Once my modem finished rebooting and my login timed out, I was able to finish the roulette, got my 230 myth and have been playing for about 4 hours non-stop doing fates, beast tribes, and killed diablos to finish a Skyfire 1 book.
All of these corrections are being done because I've been in touch with my Tier3 techs about the issue off and on since Beta4. YMMV depending on your customer support people, but for me it's worked like a charm to keep me playing with minimal issues (pretty much only have real trouble when my modem reboots if they get to the problem before I contact them and bounce the modem myself).
Code:
Tracing route to 199.91.189.30 over a maximum of 30 hops
1 <1 ms 1 ms <1 ms LPTSRV [10.10.100.1]
2 34 ms 13 ms 32 ms cpe-066-026-112-001.sc.res.rr.com [66.26.112.1]
3 20 ms 17 ms 17 ms cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
4 13 ms 15 ms 17 ms clmasoutheastmyr-rtr2.sc.rr.com [24.31.196.210]
5 23 ms 27 ms 27 ms be33.drhmncev01r.southeast.rr.com [24.93.64.180]
6 34 ms 31 ms 36 ms 107.14.19.20
7 29 ms 32 ms 49 ms ae-4-0.a0.lax91.tbone.rr.com [66.109.1.113]
8 30 ms 31 ms 41 ms ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
9 53 ms 53 ms 53 ms if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
10 53 ms 53 ms 53 ms 64.86.85.1
11 58 ms 53 ms 52 ms if-10-2.tcore1.TTT-Toronto.as6453.net [64.86.32.33]
12 56 ms 51 ms 53 ms if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25]
13 52 ms 53 ms 53 ms if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61]
14 54 ms 54 ms 52 ms 66.198.96.50
15 54 ms 53 ms 54 ms 192.34.76.2
16 52 ms 57 ms 58 ms 199.91.189.234
17 64 ms 56 ms 53 ms 199.91.189.30
Trace complete.
C:\Windows\System32>ping 199.91.189.30 -n 10
Pinging 199.91.189.30 with 32 bytes of data:
Reply from 199.91.189.30: bytes=32 time=53ms TTL=239
Reply from 199.91.189.30: bytes=32 time=54ms TTL=239
Reply from 199.91.189.30: bytes=32 time=52ms TTL=239
Reply from 199.91.189.30: bytes=32 time=54ms TTL=239
Reply from 199.91.189.30: bytes=32 time=53ms TTL=239
Reply from 199.91.189.30: bytes=32 time=51ms TTL=239
Reply from 199.91.189.30: bytes=32 time=53ms TTL=239
Reply from 199.91.189.30: bytes=32 time=52ms TTL=239
Reply from 199.91.189.30: bytes=32 time=52ms TTL=239
Reply from 199.91.189.30: bytes=32 time=54ms TTL=239
Ping statistics for 199.91.189.30:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 54ms, Average = 52ms