The issue isn't the traceroute the issue is you moved the server 3000 miles away from me.
The issue isn't the traceroute the issue is you moved the server 3000 miles away from me.
Hello,
Type of Issue/Feedback: Ping goes up after server move, from 160 to 260
Name of your Internet Service Provider (ISP): Net Virtua
State/Country: Rio de Janeiro / Brasil
Date/Time: Entire time
World Name: Behemoth
Frequency: Entire time
Hi!
I do not know what my ping was before the move, but I do know it is now between 170-190.
Type of Issue/Feedback: I seem to be having skill related issues. I use a skill and its not going being used properly (I press it and the skill goes to CD but I did not see any animation or any damage) or it is not registering that the skill has been used and have to press multiple times. Maybe its lag spikes?
Name of your Internet Service Provider (ISP): BT - Fiber optic. (British Telecom)
State/Country: UK
Date/Time: (When did the issue start happening, at what specific times does this issue arise, if any.) Date issue started: 17/05 (server move) time: 7pm BST onwards (british summer time) - it happens any time of day now, but this is when it started.
World Name: Malboro
Frequency: All the time now.
Type of Issue/Feedback: Ping went up from 160-180 to 220ms, skills are not going off as before, some require several hits to work. Upon healing there was instance where I see animation fly off, my skill is on CD, I see the animation of the HP cured but not my HP being cured and I died as result. Swiftcast requires 3 or so ticks before it can be combined with a spell otherwise I hardcast even if i have swift cast on.
Name of your Internet Service Provider (ISP): BTC ADSL
State/Country: Bulgaria, EU
Date/Time: Since server move
World Name: Malboro
Frequency: All the time.
Pretty much same thing here
ISP: Frontier
State/Country: Illinois/NA
World: Balmung
Frequency: All the time, more noticeable in evenings. Makes healing unplayableJust to double check have no problems running World of Warcraft, FFXI, and Guild Wars 2.
Tracing route to 204.2.229.84 over a maximum of 30 hops
1 102 ms 1 ms 2 ms dslrouter.netgear.com [192.168.254.254]
2 17 ms 59 ms 20 ms adr01.bltn.il.frontiernet.net [74.42.148.202]
3 28 ms 17 ms 16 ms ae0---0.car02.bltn.il.frontiernet.net [74.42.151.53]
4 27 ms 23 ms 24 ms ae10---0.cor02.chcg.il.frontiernet.net [74.40.3.34]
5 21 ms * 20 ms ae1---0.cbr01.chcg.il.frontiernet.net [74.40.4.142]
6 137 ms 22 ms 27 ms xe-0.equinix.chcgil09.us.bb.gin.ntt.NET [206.223.119.12]
7 * 24 ms 22 ms ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.205]
8 88 ms 88 ms 88 ms ae-5.r22.snjsca04.us.bb.gin.ntt.net [129.250.5.17]
9 * 92 ms 93 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
10 92 ms 91 ms 91 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
11 * 94 ms 92 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
12 * 92 ms 91 ms 204.2.229.234
13 96 ms 93 ms 92 ms 204.2.229.84
Last edited by Ozzie; 05-21-2017 at 12:04 PM.
Type of Issue/Feedback: Ping was 35 average, 180 average at its worst with some packet loss. Every day's experience has been different, some ok, some where I have died due to random freezing due to packet loss.
Name of your Internet Service Provider (ISP):Comcast
State/Country: West Virginia / USA
Date/Time: After the server move
World Name: Sargatanas
Frequency: Daily
Traceroute records
Tracing route to 204.2.229.81 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Linksys01640 [192.168.1.1]
2 12 ms 8 ms 7 ms 96.120.62.9
3 8 ms 7 ms 7 ms te-0-1-0-0-sur02.steubenville.oh.pitt.comcast.net [69.139.166.101]
4 14 ms 13 ms 14 ms te-8-3-ur02.ross.pa.pitt.comcast.net [68.85.75.229]
5 20 ms 21 ms 21 ms be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
6 17 ms 19 ms 17 ms hu-0-11-0-4-pe07.ashburn.va.ibone.comcast.net [68.86.88.158]
7 37 ms 27 ms 23 ms ae-16.a02.asbnva02.us.bb.gin.ntt.net [129.250.66.49]
8 88 ms 89 ms 87 ms ae-69.r06.asbnva02.us.bb.gin.ntt.net [129.250.5.193]
9 20 ms 19 ms 18 ms ae-2.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.132]
10 84 ms 85 ms 83 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
11 88 ms 88 ms 89 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
12 88 ms 87 ms 88 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
13 95 ms 90 ms 89 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
14 89 ms 87 ms 87 ms 204.2.229.234
15 88 ms 99 ms 89 ms 204.2.229.81
Trace complete.
Type of Issue/Feedback: Unstable connectivity to FF servers. Lag spikes causing missed skills, teleporting players, and occasionally full game freeze which then catches up a few seconds later. See frequency below, but I've been running a ping to the server 204.2.229.100 and will normally see packet loss when I'm having issues, but starting last night it looked fine in pings but I still had issues once I was in a feast game with the above lag related problems. Very frustrating. In testing I see no problems on the comcast side, only once I get into the NTT network either in ashburn or further west. I should also note during these times my ping will go up from the normal 90ms to 120ms and varies around there.
Name of your Internet Service Provider (ISP): Comcast
State/Country: Maryland, USA
Date/Time: After server move, most issues in evenings.
World Name: Leviathan
Frequency: It's happening every night but only in short bursts of maybe 10-30 minutes at a time. I normally don't notice until I'm in instanced content then shortly after I'm out it settles down. It's making PVP very difficult and will make raid terrible come stormblood.
Traceroute records: (removed first 3 hop locations)
Tracing route to 204.2.229.100 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms
2 8 ms 8 ms 8 ms
3 9 ms 8 ms 10 ms
4 11 ms 10 ms 10 ms ae-43-0-ar01.capitolhghts.md.bad.comcast.net [68.85.115.250]
5 15 ms 13 ms 13 ms be-33657-cr02.ashburn.va.ibone.comcast.net [68.86.90.57]
6 12 ms 12 ms 11 ms hu-0-10-0-1-pe07.ashburn.va.ibone.comcast.net [68.86.83.70]
7 40 ms 42 ms 40 ms ae-16.a02.asbnva02.us.bb.gin.ntt.net [129.250.66.49]
8 84 ms 83 ms 82 ms ae-69.r05.asbnva02.us.bb.gin.ntt.net [129.250.5.191]
9 11 ms 51 ms 15 ms ae-8.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.23]
10 84 ms 85 ms 86 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
11 89 ms 89 ms 91 ms ae-19.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.27]
12 89 ms 93 ms 88 ms ae-1.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.31]
13 89 ms 89 ms 90 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
14 89 ms 89 ms * 204.2.229.234
15 94 ms 90 ms 95 ms 204.2.229.100
Character : Mature Rudlum
Name of your Internet Service Provider (ISP): Sky UK
State/Country: Leeds/UK
Date/Time: from Wednesday 17th- Saturday 20th of May
World Name: Ultros
Frequency: the 24 hours. Ping increased from 110ms to 187/200ms since the move. Latency makes the game very laggy specially when trying to avoid aoes or trying to dismount mounts. Clipping of actions like blood letter and mudras as ninjas. Trying to combo fester after Bio 2 miasma bio missing Bio making the attack less powerful due to the latency (missing bio)
Type of Issue/Feedback: Large increase in ping times (minimum is now in the 80ms range up from 30-40ms), up to 120-150ms during prime times with packet loss (making game difficult to play). Character rubberbanding, and cooldown and macro lags. It all largely exists within the NTT backbone hops (WTFast alleviates the issue by avoiding NTT, and keeps ping at a steady 80-85ms with little to no packet loss or lags).
Name of your Internet Service Provider (ISP): Comcast
State/Country: New Jersey, USA
Date/Time: After server move, the problem is at it worst at night during prime times (from 8pm to past 12 am EDT, which my raid time when my group picks up again is from 10 pm to 12 am EDT).
World Name: Balmung
Frequency: It's happening all day, and especially every night, with large bursts of maybe 10-30 minutes at a time during the prime time windows.
Tracing route to 204.2.229.82 over a maximum of 30 hops (removed personal IP addresses on first two hops).
1 <1 ms <1 ms <1 ms
2 9 ms 8 ms 8 ms
3 9 ms 15 ms 9 ms xe-5-3-0-sur02.turnersville.nj.panjde.comcast.net [68.86.212.201]
4 8 ms 16 ms 9 ms ae-0-0-sur01.turnersville.nj.panjde.comcast.net [68.86.152.26]
5 17 ms 9 ms 9 ms be-11-ar03.audubon.nj.panjde.comcast.net [68.85.63.57]
6 16 ms 14 ms 14 ms be-33659-cr02.ashburn.va.ibone.comcast.net [68.86.94.97]
7 13 ms 13 ms 13 ms hu-0-11-0-2-pe07.ashburn.va.ibone.comcast.net [68.86.83.2]
8 176 ms 116 ms 127 ms ae-16.a02.asbnva02.us.bb.gin.ntt.net [129.250.66.49]
9 * 118 ms 116 ms ae-69.r05.asbnva02.us.bb.gin.ntt.net [129.250.5.191]
10 103 ms 120 ms 111 ms ae-8.r23.asbnva02.us.bb.gin.ntt.net [129.250.2.23]
11 * 114 ms 114 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
12 117 ms * 116 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
13 117 ms 117 ms 118 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
14 117 ms 126 ms 116 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
15 * 119 ms 119 ms 204.2.229.234
16 117 ms 118 ms * 204.2.229.82
17 118 ms 116 ms 118 ms 204.2.229.82
This tracert is from 11 pm EDT, the laggy hops are from hop 8 onward with packet loss/timeouts and all of them are within the NTT backbone. But even during the day, it is more laggy than it likely should be. When WTFast keeps the ping at a steady 80-85ms, the game is extremely playable (as if we never left the montreal data center). Without it, the game is fairly laggy and bard is very difficult to play properly. (I really would like to not have to pay an additional $10 a month to keep playing the game the way I always have).
Last edited by ReverieReinheart; 05-22-2017 at 12:03 PM.
Type of Issue/Feedback: After server migration ping increased from 180-200 to 380-400
Name of your Internet Service Provider (ISP): Vivo (Telefonica)
State/Country: Sao Paulo / Brazil
Date/Time: Since migration of NA datacenters. Constant and so far no fluctuations.
World Name: Midgardsorm
Frequency: Constantly
1 1 ms <1 ms <1 ms intelbras-win240 [10.0.0.1]
2 * * * Esgotado o tempo limite do pedido.
3 57 ms 43 ms 41 ms 187-100-198-42.dsl.telesp.net.br [187.100.198.42]
4 47 ms 47 ms 49 ms 187-100-86-48.dsl.telesp.net.br [187.100.86.48]
5 50 ms 51 ms 49 ms 187-100-83-4.dsl.telesp.net.br [187.100.83.4]
6 50 ms 51 ms 50 ms 84.16.6.102
7 170 ms 175 ms 175 ms 94.142.98.159
8 208 ms 210 ms 211 ms xe6-0-6-0-grtnycpt3.net.telefonicaglobalsolutions.com [213.140.49.68]
9 327 ms 310 ms 295 ms 94.142.117.239
10 302 ms 318 ms 278 ms 5.53.3.20
11 297 ms 297 ms 298 ms ae1-0-ntt-grtamstc1.net.telefonicaglobalsolutions.com [213.140.53.97]
12 283 ms 283 ms 283 ms ae-4.r25.amstnl02.nl.bb.gin.ntt.net [129.250.2.146]
13 291 ms 291 ms 291 ms ae-5.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.162]
14 341 ms 342 ms 363 ms ae-10.r22.snjsca04.us.bb.gin.ntt.net [129.250.6.237]
15 346 ms 345 ms 346 ms ae-40.r02.snjsca04.us.bb.gin.ntt.net [129.250.3.121]
16 344 ms 344 ms 343 ms ae-2.r00.scrmca02.us.bb.gin.ntt.net [129.250.7.33]
17 342 ms 343 ms 344 ms xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net [129.250.195.46]
18 343 ms 343 ms 341 ms 204.2.229.234
19 342 ms 343 ms 344 ms 204.2.229.85
There seems to be an issue with Telefonica routing through Amsterdan,
|
![]() |
![]() |
![]() |
|