Latency/Packet Loss Issues [Chaos Datacenter]

**Ariellendera** · 03-06-2018 07:01 AM

Originally Posted by AlexanderThorolund

I don’t have any technical stats to post but just wanted to say since the last path I’ve been getting a weird delay. Never happened before in the 3 years I’ve been playing. There is definitely something up server side. Maybe something to do with the 999 inventory increase?

We are asking players who are experiencing these issues to please post a trace route, ISP and location. We are collecting this information to give to the appropriate teams.

Thank you.

**Sheria** · 03-06-2018 07:06 AM

I experienced the same since 4.15, the lags actually got better a little while ago, but last week they came back really strong

1. Trace Route from 5th March 2018 at 23:10 GMT +1 in Frankfurt - Germany

1 <1 ms <1 ms <1 ms 192.168.178.1
2 20 ms 18 ms 19 ms 62.245.142.133
3 19 ms 22 ms 21 ms 82.135.16.242
4 22 ms 21 ms 22 ms 62.140.24.49
5 27 ms 27 ms 27 ms 4.69.163.18
6 27 ms 28 ms 36 ms 212.162.4.98
7 38 ms 27 ms 27 ms 195.82.60.29
8 27 ms 28 ms 28 ms 195.82.61.14
9 28 ms 28 ms 28 ms 195.82.50.234
10 28 ms 27 ms 28 ms 195.82.50.44

2. Provider : M-Net, German Telecommunication-Provider in Munich

**Ariellendera** · 03-06-2018 09:56 AM

Hello!

Thank you for posting the requested information. We will pass this along to our teams.

Thank you for playing Final Fantasy XIV! Hope to see you online.

**Riko_Futatabi** · 03-06-2018 11:08 AM

Trace route showing extreme packet loss on the 4th hop on my route to servers. This node has been troublesome for over 6 months with packet loss ranging from 20~80% and now I guess 98%(New Record!!). o.O

I live in Scotland. My ISP is Sky.

Ignore the 2nd hop having 100% loss, it doesn't allow pinging most of the time due to security reasons. It's normal.

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                          SkyRouter.Home -    0 |  202 |  202 |    0 |    0 |    5 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|             be365.pr2.hobir.isp.sky.com -    0 |  203 |  203 |   16 |   17 |   30 |   18 |
|         lag-102.ear1.London1.Level3.net -   98 |   42 |    1 |    0 |   17 |   17 |   17 |
|   ae-1-3107.edge5.Frankfurt1.Level3.net -    0 |  203 |  203 |   30 |   30 |   51 |   30 |
|                            212.162.4.98 -    0 |  202 |  202 |   30 |   34 |   47 |   32 |
|                            195.82.60.29 -    2 |  195 |  193 |   30 |   39 | 1039 |   38 |
|                            195.82.61.14 -    2 |  195 |  193 |   30 |   32 |  227 |   30 |
|                           195.82.50.234 -    2 |  195 |  193 |   30 |   30 |   39 |   30 |
|                             195.82.50.9 -    2 |  195 |  193 |   30 |   36 | 1035 |   30 |
|________________________________________________|______|______|______|______|______|______|

To make it more clear it's always this node: lag-102.ear1.London1.Level3.net

**TelosNox** · 03-06-2018 03:32 PM

In your case it looks like London1.Level3 is denying ping as well most of the time. Or it is so busy that there is no room for the lower priority ping answer. If you really had 98% packet loss at that node then the following nodes would have that packet loss as well (because their ping answer would be lost at London1 as well).

**Riko_Futatabi** · 03-06-2018 10:41 PM

Originally Posted by TelosNox

In your case it looks like London1.Level3 is denying ping as well most of the time. Or it is so busy that there is no room for the lower priority ping answer. If you really had 98% packet loss at that node then the following nodes would have that packet loss as well (because their ping answer would be lost at London1 as well).

That maybe be so in this case. However, like I said also. That node has always been around 20~80% loss. That 98% is actually surprising and unusually high. Also I failed to mention that this was taken on Tuesday morning at 2:00 AM GMT. Pretty sure that isn't a "peak" time. but I'm not certain.

**Sythen** · 03-06-2018 11:16 PM

Originally Posted by Riko_Futatabi

That maybe be so in this case. However, like I said also. That node has always been around 20~80% loss. That 98% is actually surprising and unusually high. Also I failed to mention that this was taken on Tuesday morning at 2:00 AM GMT. Pretty sure that isn't a "peak" time. but I'm not certain.

Its common for Level3 to do maintenance between 1 and 5 AM, I'm not seeing Loss on that Hop right now.

I've been monitoring this problem since this issue came to light, alot of the packet loss that I've been seeing from this has been coming from
the handover from the Telia-KDDI link.

But there seems to be an issue within the KDDI center in Frankfurt, I've also seen issues from the Chaos DC IP, and the IP that Lich sits on aswell.

Anyways, here is some more results from my point to Chaos. Also, i dont know if this might also be related to the sudden 90k issues that we have been having since 4.15.

**Zak** · 03-07-2018 01:50 AM

I've been having issues ever since 4.2 launch, but today was being harsher than usual, with lag spikes of up to 2 seconds and experiencing weird rollbacks when using skills. Latency shown by resource monitor was also unusually high all the time, fluctuating between 90ms and 130ms when it's usually around 40ms to 80ms. So I did several trace routes while I was playing.

Note that I only notice issues during instanced content. There's never any problem during non-instanced duties or fights.

I hope this helps.

Location: Spain. ISP: R telecomunicaciones.

Code:

tracert 195.82.50.46

Traza a 195.82.50.46 sobre caminos de 30 saltos como máximo.

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     8 ms     9 ms     8 ms  10.131.128.1
  3     9 ms     6 ms     7 ms  212.51.41.130
  4     8 ms     8 ms     6 ms  78.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.78]
  5     9 ms    12 ms     8 ms  82.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.82]
  6    46 ms    45 ms    44 ms  mad-b2-link.telia.net [213.248.74.9]
  7    43 ms    46 ms    42 ms  prs-bb4-link.telia.net [80.91.248.130]
  8    81 ms    82 ms    83 ms  ffm-bb4-link.telia.net [62.115.122.139]
  9    83 ms   100 ms    81 ms  ffm-b1-link.telia.net [62.115.121.11]
 10    88 ms    96 ms    98 ms  kddi-ic-319844-ffm-b1.c.telia.net [62.115.32.106]
 11    82 ms    85 ms     *     195.82.61.14
 12   127 ms    84 ms    80 ms  195.82.50.234
 13    73 ms    78 ms    78 ms  195.82.50.46

Traza completa.

Code:

tracert 195.82.50.46

Traza a 195.82.50.46 sobre caminos de 30 saltos como máximo.

  1     1 ms    <1 ms     1 ms  192.168.0.1
  2     7 ms     6 ms     7 ms  10.131.128.1
  3     8 ms     7 ms     7 ms  212.51.41.130
  4     *        *        7 ms  78.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.78]
  5    14 ms     7 ms     8 ms  82.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.82]
  6    44 ms    44 ms    43 ms  mad-b2-link.telia.net [213.248.74.9]
  7    44 ms    49 ms    42 ms  prs-bb4-link.telia.net [80.91.248.130]
  8    76 ms    76 ms    75 ms  ffm-bb4-link.telia.net [62.115.122.139]
  9    80 ms    77 ms     *     ffm-b1-link.telia.net [62.115.121.11]
 10     *       94 ms    81 ms  kddi-ic-319844-ffm-b1.c.telia.net [62.115.32.106]
 11    81 ms    84 ms    88 ms  195.82.61.14
 12    74 ms    71 ms    74 ms  195.82.50.234
 13    70 ms    71 ms    73 ms  195.82.50.46

Traza completa.

Code:

tracert 195.82.50.46

Traza a 195.82.50.46 sobre caminos de 30 saltos como máximo.

  1     2 ms    <1 ms    <1 ms  192.168.0.1
  2     9 ms     7 ms    13 ms  10.131.128.1
  3     *        7 ms     8 ms  212.51.41.130
  4     9 ms     8 ms     8 ms  78.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.78]
  5     7 ms     7 ms    10 ms  82.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.82]
  6    43 ms    45 ms    43 ms  mad-b2-link.telia.net [213.248.74.9]
  7    50 ms    41 ms    42 ms  prs-bb4-link.telia.net [80.91.248.130]
  8    83 ms    84 ms    86 ms  ffm-bb4-link.telia.net [62.115.122.139]
  9    88 ms    86 ms    90 ms  ffm-b1-link.telia.net [62.115.121.11]
 10    83 ms    89 ms    82 ms  kddi-ic-319844-ffm-b1.c.telia.net [62.115.32.106]
 11    73 ms    74 ms    71 ms  195.82.61.14
 12    71 ms    70 ms    71 ms  195.82.50.234
 13     *       76 ms    78 ms  195.82.50.46

Traza completa.

Code:

tracert 195.82.50.46

Traza a 195.82.50.46 sobre caminos de 30 saltos como máximo.

  1    <1 ms     2 ms    <1 ms  192.168.0.1
  2     8 ms    12 ms    13 ms  10.131.128.1
  3     7 ms     9 ms     6 ms  212.51.41.130
  4    10 ms     9 ms     8 ms  78.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.78]
  5     8 ms     7 ms     9 ms  82.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.82]
  6    45 ms    45 ms    53 ms  mad-b2-link.telia.net [213.248.74.9]
  7    68 ms    41 ms    41 ms  prs-bb4-link.telia.net [80.91.248.130]
  8    89 ms    98 ms    89 ms  ffm-bb4-link.telia.net [62.115.122.139]
  9    83 ms    85 ms    83 ms  ffm-b1-link.telia.net [62.115.121.11]
 10    81 ms    81 ms    87 ms  kddi-ic-319844-ffm-b1.c.telia.net [62.115.32.106]
 11    72 ms    71 ms    75 ms  195.82.61.14
 12    71 ms     *       88 ms  195.82.50.234
 13     *       70 ms    69 ms  195.82.50.46

Traza completa.

Code:

tracert 195.82.50.46

Traza a 195.82.50.46 sobre caminos de 30 saltos como máximo.

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    10 ms     8 ms     7 ms  10.131.128.1
  3     9 ms     9 ms    11 ms  212.51.41.130
  4    10 ms    10 ms    11 ms  78.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.78]
  5     8 ms     7 ms     9 ms  82.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.82]
  6    48 ms    44 ms    46 ms  mad-b2-link.telia.net [213.248.74.9]
  7    42 ms    41 ms    42 ms  prs-bb4-link.telia.net [80.91.248.130]
  8    75 ms    77 ms    77 ms  ffm-bb4-link.telia.net [62.115.122.139]
  9    85 ms    82 ms    82 ms  ffm-b1-link.telia.net [62.115.121.11]
 10   101 ms    76 ms    79 ms  kddi-ic-319844-ffm-b1.c.telia.net [62.115.32.106]
 11    75 ms    71 ms    73 ms  195.82.61.14
 12    75 ms    74 ms    75 ms  195.82.50.234
 13    71 ms    74 ms    74 ms  195.82.50.46

Traza completa.

Code:

tracert 195.82.50.46

Traza a 195.82.50.46 sobre caminos de 30 saltos como máximo.

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     9 ms     7 ms     6 ms  10.131.128.1
  3     9 ms     9 ms     8 ms  212.51.41.130
  4     9 ms     8 ms     7 ms  78.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.78]
  5    10 ms     8 ms    12 ms  82.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.82]
  6    44 ms    43 ms    45 ms  mad-b2-link.telia.net [213.248.74.9]
  7    45 ms    41 ms    43 ms  prs-bb4-link.telia.net [80.91.248.130]
  8    80 ms    79 ms    79 ms  ffm-bb4-link.telia.net [62.115.122.139]
  9   104 ms    86 ms    84 ms  ffm-b1-link.telia.net [62.115.121.11]
 10    83 ms    87 ms    82 ms  kddi-ic-319844-ffm-b1.c.telia.net [62.115.32.106]
 11    74 ms    75 ms    84 ms  195.82.61.14
 12    82 ms    82 ms    89 ms  195.82.50.234
 13     *       68 ms    71 ms  195.82.50.46

Traza completa.

Code:

tracert 195.82.50.46

Traza a 195.82.50.46 sobre caminos de 30 saltos como máximo.

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     8 ms     8 ms     7 ms  10.131.128.1
  3    10 ms     8 ms     8 ms  212.51.41.130
  4     *        6 ms     8 ms  78.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.78]
  5     9 ms    10 ms     7 ms  82.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.82]
  6    43 ms    44 ms    46 ms  mad-b2-link.telia.net [213.248.74.9]
  7    91 ms    43 ms    41 ms  prs-bb4-link.telia.net [80.91.248.130]
  8    80 ms    75 ms     *     ffm-bb4-link.telia.net [62.115.122.139]
  9    76 ms    78 ms    83 ms  ffm-b1-link.telia.net [62.115.121.11]
 10    78 ms    80 ms    80 ms  kddi-ic-319844-ffm-b1.c.telia.net [62.115.32.106]
 11    84 ms     *       80 ms  195.82.61.14
 12    72 ms    75 ms    79 ms  195.82.50.234
 13    70 ms    70 ms    70 ms  195.82.50.46

Traza completa.

Code:

tracert 195.82.50.46

Traza a 195.82.50.46 sobre caminos de 30 saltos como máximo.

  1    <1 ms    <1 ms     1 ms  192.168.0.1
  2     7 ms     7 ms     7 ms  10.131.128.1
  3    22 ms     8 ms     7 ms  212.51.41.130
  4    10 ms     8 ms     7 ms  78.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.78]
  5    32 ms     8 ms     8 ms  82.17.26.77.dynamic.reverse-mundo-r.com [77.26.17.82]
  6    43 ms    46 ms    77 ms  mad-b2-link.telia.net [213.248.74.9]
  7    74 ms    42 ms    45 ms  prs-bb4-link.telia.net [80.91.248.130]
  8    85 ms    81 ms    82 ms  ffm-bb4-link.telia.net [62.115.122.139]
  9    97 ms    84 ms    90 ms  ffm-b1-link.telia.net [62.115.121.11]
 10    90 ms    86 ms     *     kddi-ic-319844-ffm-b1.c.telia.net [62.115.32.106]
 11    79 ms    76 ms    72 ms  195.82.61.14
 12    73 ms    77 ms    78 ms  195.82.50.234
 13    86 ms    75 ms    67 ms  195.82.50.46

Traza completa.

**Roxashe** · 03-07-2018 02:17 AM

I play from Cape Town, South Africa and since 4.21's release have noticed a massive amount of lag and general unplayableness during the evenings (7PM - 1AM GMT+2)

My ISP is Internet Solutions AND my own ISP that I work for (PCN) and both connections do exactly the same, yet use different routes locally to get overseas.

PCN - Cape Town South Africa

Tracing route to 195.82.50.44 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.13.0.1
2 30 ms 30 ms 33 ms 1.1.1.3
3 34 ms 33 ms 33 ms 6500-access03.pcnetwork.co.za [154.66.205.126]
4 32 ms 33 ms 35 ms 196.6.121.217
5 34 ms 35 ms 36 ms cpt-teraco-sw204-vlan2914.as36874.net [196.41.97.37]
6 34 ms 34 ms 35 ms tr212-cpt-te-2501.borwood.net [217.78.92.241]
7 174 ms 176 ms 171 ms th212-lon-po-wacs.borwood.net [217.78.80.205]
8 175 ms 171 ms 175 ms th202-lon-te-4037.borwood.net [217.78.88.221]
9 176 ms 175 ms 172 ms th201-lon-tg-202.borwood.net [217.78.88.129]
10 175 ms 171 ms 177 ms 213.130.48.253
11 173 ms 173 ms 177 ms ae-0.level3.londen10.uk.bb.gin.ntt.net [129.250.9.126]
12 186 ms 183 ms 184 ms ae-1-3107.edge5.Frankfurt1.Level3.net [4.69.163.18]
13 188 ms 187 ms 183 ms 212.162.4.98
14 189 ms 197 ms 197 ms 195.82.60.29
15 192 ms 184 ms * 195.82.61.14
16 185 ms 188 ms 185 ms 195.82.50.234
17 186 ms 186 ms 186 ms 195.82.50.44

Internet Solutions - Cape Town, South Africa:

C:\Users\Roxas>tracert 195.82.50.44

Tracing route to 195.82.50.44 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.13.0.1
2 * * * Request timed out.
3 19 ms 20 ms 19 ms 196.38.75.121
4 71 ms 71 ms 73 ms 196.38.75.122
5 19 ms 19 ms 19 ms 196.38.77.88
6 81 ms 81 ms 79 ms mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.12]
7 206 ms 206 ms 203 ms core1b-dock-ten-0-4-0-0sub8.ip.isnet.net [168.209.246.65]
8 159 ms 159 ms 174 ms 195.50.122.229
9 222 ms 224 ms 228 ms ae-1-3107.edge5.Frankfurt1.Level3.net [4.69.163.18]
10 169 ms * 169 ms 212.162.4.98
11 167 ms 173 ms 172 ms 195.82.60.29
12 186 ms 176 ms 172 ms 195.82.61.14
13 194 ms 192 ms 188 ms 195.82.50.234
14 202 ms 219 ms 209 ms 195.82.50.44

Trace complete.

Something has changed in the network or routing to Square since 4.2/4.21 and I 100% can say that Barely anything works. Note. I normally have around 145-150MS ping and this has shot up considerably as well! Considering I run my own network at the ISP I work for, I can say that nothing on our routing to Square has changed at all. There is something up with either the servers or routing out from Frankfurt.

All my static members also say the same thing, that the missiles freeze in O7s for seconds at a time at night during our raiding days, so it also isn't just me with some insane amount of latency. They are all in the UK/Poland.

**Innervate316** · 03-07-2018 02:35 AM

Playing from Taipei, Taiwan, Using KBRO as my ISP.

Literally seeing players, bosses and missiles teleporting all over the place in Sigmascape Savage.

Tracing route to 195.82.50.44 over a maximum of 30 hops

1 1 ms * 1 ms hitronhub.home [192.168.0.1]
2 9 ms 9 ms 7 ms 10.37.0.1
3 8 ms 9 ms 8 ms 10.4.18.89
4 9 ms 9 ms 8 ms 211-76-114-254.static.kbronet.com.tw [211.76.114.254]
5 8 ms 8 ms 9 ms 219-80-241-237.static.tfn.net.tw [219.80.241.237]
6 7 ms 17 ms 9 ms 60-199-4-225.static.tfn.net.tw [60.199.4.225]
7 8 ms 18 ms 12 ms 60-199-4-153.static.tfn.net.tw [60.199.4.153]
8 148 ms 141 ms 142 ms 60-199-20-34.static.tfn.net.tw [60.199.20.34]
9 * * * Request timed out.
10 280 ms 281 ms 281 ms ae-1-3107.edge5.Frankfurt1.Level3.net [4.69.163.18]
11 281 ms 290 ms 280 ms 212.162.4.98
12 304 ms 299 ms 299 ms 195.82.60.29
13 289 ms 292 ms 291 ms 195.82.61.14
14 266 ms 270 ms 265 ms 195.82.50.234
15 284 ms 284 ms 290 ms 195.82.50.44

Thread: Latency/Packet Loss Issues [Chaos Datacenter]

Thread Tools

Search Thread

Display

Trace Route to Chaos Datacenter.