Constant packet loss, latency spikes and dropouts

Services provided via NBN Co, Opticomm, Open Networks, Red Train, LBN Co, and TPG FttB
Post Reply
jwoo
Posts: 3
Joined: Wed Nov 27, 2019 5:37 pm

Constant packet loss, latency spikes and dropouts

Post by jwoo » Wed Nov 27, 2019 9:08 pm

Have been happening about once or twice a day for the last month but today starting from at least 9am it has been completely unusable. Every 5 to 15 minutes I'll get something like this before it resumes and works normally again.

Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Request timed out.
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=13ms TTL=56
Request timed out.
Reply from 216.58.203.110: bytes=32 time=13ms TTL=56
Reply from 216.58.203.110: bytes=32 time=13ms TTL=56
Reply from 216.58.203.110: bytes=32 time=13ms TTL=56
Request timed out.
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=13ms TTL=56
Reply from 216.58.203.110: bytes=32 time=13ms TTL=56
Request timed out.
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=15ms TTL=56
Reply from 216.58.203.110: bytes=32 time=13ms TTL=56

Every now and then the latency will increase to 250-600ms for several minutes.
The Exetel provided Netcomm modem maintains all its green lights.
I have also setup a direct PPPoE connection from PC to wall in case it was the modem. Same issues.
I use this LBN co service 99% for gaming so the latency and packet loss make it completely unusable.
I am in CBD Melbourne where I see no planned outages.

rasikak
Exetel Staff
Posts: 289
Joined: Fri Jun 02, 2017 1:34 pm
Location: North Sydney

Re: Constant packet loss, latency spikes and dropouts

Post by rasikak » Thu Nov 28, 2019 1:50 pm

jwoo wrote:
Wed Nov 27, 2019 9:08 pm
Have been happening about once or twice a day for the last month but today starting from at least 9am it has been completely unusable. Every 5 to 15 minutes I'll get something like this before it resumes and works normally again.

Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Request timed out.
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=13ms TTL=56
Request timed out.
Reply from 216.58.203.110: bytes=32 time=13ms TTL=56
Reply from 216.58.203.110: bytes=32 time=13ms TTL=56
Reply from 216.58.203.110: bytes=32 time=13ms TTL=56
Request timed out.
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=13ms TTL=56
Reply from 216.58.203.110: bytes=32 time=13ms TTL=56
Request timed out.
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=14ms TTL=56
Reply from 216.58.203.110: bytes=32 time=15ms TTL=56
Reply from 216.58.203.110: bytes=32 time=13ms TTL=56

Every now and then the latency will increase to 250-600ms for several minutes.
The Exetel provided Netcomm modem maintains all its green lights.
I have also setup a direct PPPoE connection from PC to wall in case it was the modem. Same issues.
I use this LBN co service 99% for gaming so the latency and packet loss make it completely unusable.
I am in CBD Melbourne where I see no planned outages.
Thank you for contacting Exetel. Please note that your service issue has been raised with the wholesale supplier and they are further investigating the issue. We will follow this up and provide an update. #16416641

vanavanavana
Posts: 4
Joined: Thu Nov 28, 2019 2:16 pm

Re: Constant packet loss, latency spikes and dropouts

Post by vanavanavana » Thu Nov 28, 2019 8:23 pm

I'm experiencing the same thing. Also in Melbourne CBD (Upper West Side specifically) on the LBN Co network, so I think this is the same issue.

This is happening at all times of the day and resulting in an unstable connection which means that everything from web browsing to online gaming and video streaming becomes unresponsive. My connection is unusable and I'm tethering mobile internet right now.

I raised a ticket and my ticket number is #16418334.

Here are some ping and tracert results to the World of Warcraft US West (137.221.105.2) and Oceanic (103.4.115.248) servers. The IP addresses come direct from Blizzard's help article (https://us.battle.net/support/en/article/7870).

> ping 137.221.105.2 -n 50
Pinging 137.221.105.2 with 32 bytes of data:
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Request timed out.
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Request timed out.
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Request timed out.
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240

Ping statistics for 137.221.105.2:
Packets: Sent = 50, Received = 47, Lost = 3 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 175ms, Maximum = 175ms, Average = 175ms

> ping 137.221.105.2 -n 50
Pinging 137.221.105.2 with 32 bytes of data:
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Request timed out.
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Request timed out.
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Request timed out.
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Request timed out.
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Request timed out.
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240
Reply from 137.221.105.2: bytes=32 time=175ms TTL=240

Ping statistics for 137.221.105.2:
Packets: Sent = 50, Received = 39, Lost = 11 (22% loss),
Approximate round trip times in milli-seconds:
Minimum = 175ms, Maximum = 175ms, Average = 175ms

> tracert 137.221.105.2
Tracing route to 137.221.105.2 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 40.1.233.220.static.exetel.com.au [220.233.1.40]
3 1 ms <1 ms <1 ms 106.2.96.58.static.exetel.com.au [58.96.2.106]
4 1 ms 1 ms 1 ms TenGigE0-0-0-35.bdr01-ipt-826lorim-mel.au.superloop.com [27.122.124.208]
5 163 ms 163 ms 163 ms FortyGigE0-0-1-3.bdr01-ipt-530colli-mel.au.superloop.com [103.200.13.101]
6 163 ms 163 ms 163 ms HundredGigE0-0-1-2.106.bdr01-ipt-47bourke-syd.au.superloop.com [103.200.13.112]
7 163 ms 163 ms 163 ms FortyGigE0-0-1-2.120.bdr01-ipt-624sgran-lax.us.superloop.com [103.200.13.168]
8 163 ms 163 ms 163 ms any2ix.coresite.com [206.72.211.247]
9 175 ms 194 ms 175 ms ae1-br01-csla1.as57976.net [137.221.89.33]
10 175 ms 175 ms 175 ms xe-0-0-1-3-br01-eqla1.as57976.net [137.221.65.30]
11 175 ms 175 ms 175 ms et-0-0-2-br01-swlv10.as57976.net [137.221.65.69]
12 175 ms 175 ms 175 ms et-0-0-31-pe02-swlv10.as57976.net [137.221.83.69]
13 175 ms 175 ms 175 ms 137.221.105.2

Trace complete.

> ping 103.4.115.248 -n 50
Pinging 103.4.115.248 with 32 bytes of data:
Request timed out.
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Request timed out.
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Request timed out.
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Request timed out.
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Request timed out.
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Request timed out.
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Request timed out.
Request timed out.
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249

Ping statistics for 103.4.115.248:
Packets: Sent = 50, Received = 42, Lost = 8 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms

> ping 103.4.115.248 -n 50
Pinging 103.4.115.248 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=12ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249
Reply from 103.4.115.248: bytes=32 time=11ms TTL=249

Ping statistics for 103.4.115.248:
Packets: Sent = 50, Received = 44, Lost = 6 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms

> tracert 103.4.115.248
Tracing route to 103.4.115.248 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms 40.1.233.220.static.exetel.com.au [220.233.1.40]
3 1 ms <1 ms <1 ms 10.1.31.197
4 1 ms 1 ms 1 ms TenGigE0-0-0-35.bdr01-ipt-826lorim-mel.au.superloop.com [27.122.124.208]
5 34 ms 12 ms 12 ms as58580.vic.ix.asn.au [218.100.78.37]
6 13 ms 13 ms 12 ms 137.221.85.35
7 78 ms 64 ms 12 ms et-0-0-0-pe02-eqsy4.as57976.net [137.221.85.71]
8 12 ms 11 ms 11 ms 103.4.115.248

Trace complete.

nilushid
Exetel Staff
Posts: 756
Joined: Tue Jan 10, 2017 2:18 pm
Location: sydney

Re: Constant packet loss, latency spikes and dropouts

Post by nilushid » Thu Nov 28, 2019 10:03 pm

vanavanavana wrote:
Thu Nov 28, 2019 8:23 pm
I'm experiencing the same thing. Also in Melbourne CBD (Upper West Side specifically) on the LBN Co network, so I think this is the same issue.

This is happening at all times of the day and resulting in an unstable connection which means that everything from web browsing to online gaming and video streaming becomes unresponsive. My connection is unusable and I'm tethering mobile internet right now.

I raised a ticket and my ticket number is #16418334.

Here are some ping and tracert results to the World of Warcraft US West (137.221.105.2) and Oceanic (103.4.115.248) servers. The IP addresses come direct from Blizzard's help article (https://us.battle.net/support/en/article/7870).

Trace complete.
We are sorry about the inconveniences caused. Your service issue is also raised with LBN Co under ref #16426902 and they are currently investigating the matter. We will get back to you as soon as new updates are available via Ref 16418334

jwoo
Posts: 3
Joined: Wed Nov 27, 2019 5:37 pm

Re: Constant packet loss, latency spikes and dropouts

Post by jwoo » Fri Nov 29, 2019 4:14 pm

Yes it is definitely a LBN co problem as I am in Upper West Side as well. Tracert will show nothing except during high latencies as traffic tunnels through LBN co's network to reach Exetel.

Out of curiosity are you on a low floor? Your latency to WoW oceanic server is 1-2ms better than mine!

rehanj
Exetel Staff
Posts: 577
Joined: Wed Jun 17, 2015 10:26 am
Location: Colombo

Re: Constant packet loss, latency spikes and dropouts

Post by rehanj » Fri Nov 29, 2019 4:56 pm

jwoo wrote:
Fri Nov 29, 2019 4:14 pm
Yes it is definitely a LBN co problem as I am in Upper West Side as well. Tracert will show nothing except during high latencies as traffic tunnels through LBN co's network to reach Exetel.

Out of curiosity are you on a low floor? Your latency to WoW oceanic server is 1-2ms better than mine!
Hi, please note that a response has been provided to you regarding your service issue via the email thread bearing reference number #16418334. Please be kind enough to review this email and provide us with a response. Could you also provide us with a bit of additional clarification regarding your query about Exetel's latency to WoW oceanic server's?

jwoo
Posts: 3
Joined: Wed Nov 27, 2019 5:37 pm

Re: Constant packet loss, latency spikes and dropouts

Post by jwoo » Fri Nov 29, 2019 6:45 pm

I can confirm the service has been working fine again for the last 2.5 hours. Thanks for escalating this.

My last post was directed at other user vanavanavana who lives in the same complex but has tiny bit better latency. So I am curious about which building/floor. I am in hudson tower lvl 13

vanavanavana
Posts: 4
Joined: Thu Nov 28, 2019 2:16 pm

Re: Constant packet loss, latency spikes and dropouts

Post by vanavanavana » Sat Nov 30, 2019 10:21 am

My connection appears to have been restored too. I was online for a few hours last night and it was all smooth. Thanks for addressing this.
jwoo wrote:
Fri Nov 29, 2019 6:45 pm
My last post was directed at other user vanavanavana who lives in the same complex but has tiny bit better latency. So I am curious about which building/floor. I am in hudson tower lvl 13
Hudson L18

Post Reply