ping loss and high latency on ADSL2

Connection issues, drop outs or speed related faults for ADSL and ADSL2+ services
Post Reply
gordoncxf
Posts: 1
Joined: Fri Feb 03, 2012 6:40 pm
Location: Sydney

ping loss and high latency on ADSL2

Post by gordoncxf » Fri Mar 02, 2012 4:27 pm

I am using Exetel ADSL2 at home and investment property. My home one is very stable. However, the one in my investment property is experiencing problem. Most of the time, It is slow to open web pages or watch online video. There is no phone connected to this line, only the ADSL device. I use Router + modem with PPPOE.

I tested the ping result and found that the ping loss is high (between 10 to 20%). Latency is high varying from between 30 to 200. I performed same tests on my home connection and did not have such problem. The ping loss at my home is 2% at most and latency is less than 50.

I reported the problem to Exetel. Tech Support has done some troubleshooting with me, i.e. changing another modem and router, line test, switching the ADSL profile and so on. It did not resolve the issue. Finally, Optus sent tech onsite. The tech changed something in the hub or switch on the street and told me that the line voltage was a bit too high. He connect his modem and found the connection speed is on 10MB. Then, he claimed the problem is resolved and therefore Exetel closed the ticket. Unfortunately, I am still experiencing the same issues.

Below are the tracert and ping results.

Tracing route to http://www.google.com [173.194.38.82] over a maximum of 20 hops

(Tracert http://www.google.com)
1 * * * Request timed out.
2 165ms 142ms 157ms 220.233.2.33
3 128ms 230ms * Request timed out.
4 66ms 150ms 236ms 220.233.2.5
5 204ms 114ms 153ms 202.68.67.50
6 * 122ms 15ms 139.130.74.5
7 116ms 49ms 167ms 203.50.20.1
8 183ms 107ms 132ms 203.50.6.146
9 55ms 39ms * Request timed out.
10 46ms 27ms 65ms 66.249.95.224
11 25ms 193ms 59ms 66.249.95.166
12 162ms 102ms 191ms 64.233.175.1
13 110ms * 32ms 209.85.251.237
14 147ms 4ms 42ms 173.194.38.82

Trace complete.

(pinging Extel DNS server)
Pinging 220.233.0.4 with 64 bytes of data:

Reply from 220.233.0.4: bytes=64 time=96 TTL=61 seq=1
Request timed out.
Reply from 220.233.0.4: bytes=64 time=74 TTL=61 seq=3
Request timed out.
Request timed out.
Reply from 220.233.0.4: bytes=64 time=55 TTL=61 seq=6
Reply from 220.233.0.4: bytes=64 time=52 TTL=61 seq=7
Reply from 220.233.0.4: bytes=64 time=31 TTL=61 seq=8
Reply from 220.233.0.4: bytes=64 time=84 TTL=61 seq=9
Reply from 220.233.0.4: bytes=64 time=74 TTL=61 seq=10
Reply from 220.233.0.4: bytes=64 time=84 TTL=61 seq=11
Reply from 220.233.0.4: bytes=64 time=65 TTL=61 seq=12
Request timed out.
Request timed out.
Reply from 220.233.0.4: bytes=64 time=161 TTL=61 seq=15
Reply from 220.233.0.4: bytes=64 time=79 TTL=61 seq=16
Request timed out.
Reply from 220.233.0.4: bytes=64 time=79 TTL=61 seq=18
Reply from 220.233.0.4: bytes=64 time=67 TTL=61 seq=19
Reply from 220.233.0.4: bytes=64 time=57 TTL=61 seq=20
Reply from 220.233.0.4: bytes=64 time=100 TTL=61 seq=21
Reply from 220.233.0.4: bytes=64 time=130 TTL=61 seq=22
Reply from 220.233.0.4: bytes=64 time=135 TTL=61 seq=23
Reply from 220.233.0.4: bytes=64 time=127 TTL=61 seq=24
Reply from 220.233.0.4: bytes=64 time=96 TTL=61 seq=25
Reply from 220.233.0.4: bytes=64 time=52 TTL=61 seq=26
Reply from 220.233.0.4: bytes=64 time=60 TTL=61 seq=27
Reply from 220.233.0.4: bytes=64 time=110 TTL=61 seq=28
Reply from 220.233.0.4: bytes=64 time=104 TTL=61 seq=29
Reply from 220.233.0.4: bytes=64 time=103 TTL=61 seq=30
Reply from 220.233.0.4: bytes=64 time=58 TTL=61 seq=31
Reply from 220.233.0.4: bytes=64 time=68 TTL=61 seq=32
Reply from 220.233.0.4: bytes=64 time=139 TTL=61 seq=33
Reply from 220.233.0.4: bytes=64 time=90 TTL=61 seq=34
Request timed out.
Reply from 220.233.0.4: bytes=64 time=33 TTL=61 seq=36
Request timed out.
Request timed out.
Reply from 220.233.0.4: bytes=64 time=53 TTL=61 seq=39
Reply from 220.233.0.4: bytes=64 time=155 TTL=61 seq=40
Reply from 220.233.0.4: bytes=64 time=24 TTL=61 seq=41
Reply from 220.233.0.4: bytes=64 time=123 TTL=61 seq=42
Reply from 220.233.0.4: bytes=64 time=31 TTL=61 seq=43
Reply from 220.233.0.4: bytes=64 time=55 TTL=61 seq=44
Request timed out.
Reply from 220.233.0.4: bytes=64 time=55 TTL=61 seq=46
Reply from 220.233.0.4: bytes=64 time=19 TTL=61 seq=47
Reply from 220.233.0.4: bytes=64 time=137 TTL=61 seq=48
Reply from 220.233.0.4: bytes=64 time=107 TTL=61 seq=49
Reply from 220.233.0.4: bytes=64 time=124 TTL=61 seq=50

Ping statistics for 220.233.0.4
Packets: Sent = 50, Received = 40, Lost = 10 (20% loss),
Approximate round trip times in milliseconds:
Minimum = 19, Maximum = 161, Average = 83

I am driven mad by this problem and wondering if someone could help or give me a clue. :cry:

Thanks in advance!

stevecJ
Forum Admin
Posts: 1041
Joined: Wed Jan 06, 2010 9:48 am

Re: ping loss and high latency on ADSL2

Post by stevecJ » Fri Mar 02, 2012 4:56 pm

gordoncxf wrote:I am using Exetel ADSL2 at home and investment property. My home one is very stable. However, the one in my investment property is experiencing problem. Most of the time, It is slow to open web pages or watch online video. There is no phone connected to this line, only the ADSL device. I use Router + modem with PPPOE.

I tested the ping result and found that the ping loss is high (between 10 to 20%). Latency is high varying from between 30 to 200. I performed same tests on my home connection and did not have such problem. The ping loss at my home is 2% at most and latency is less than 50.

I reported the problem to Exetel. Tech Support has done some troubleshooting with me, i.e. changing another modem and router, line test, switching the ADSL profile and so on. It did not resolve the issue. Finally, Optus sent tech onsite. The tech changed something in the hub or switch on the street and told me that the line voltage was a bit too high. He connect his modem and found the connection speed is on 10MB. Then, he claimed the problem is resolved and therefore Exetel closed the ticket. Unfortunately, I am still experiencing the same issues.

Below are the tracert and ping results.

Tracing route to http://www.google.com [173.194.38.82] over a maximum of 20 hops

(Tracert http://www.google.com)
1 * * * Request timed out.
2 165ms 142ms 157ms 220.233.2.33
3 128ms 230ms * Request timed out.
4 66ms 150ms 236ms 220.233.2.5
5 204ms 114ms 153ms 202.68.67.50
6 * 122ms 15ms 139.130.74.5
7 116ms 49ms 167ms 203.50.20.1
8 183ms 107ms 132ms 203.50.6.146
9 55ms 39ms * Request timed out.
10 46ms 27ms 65ms 66.249.95.224
11 25ms 193ms 59ms 66.249.95.166
12 162ms 102ms 191ms 64.233.175.1
13 110ms * 32ms 209.85.251.237
14 147ms 4ms 42ms 173.194.38.82

Trace complete.

(pinging Extel DNS server)
Pinging 220.233.0.4 with 64 bytes of data:

Reply from 220.233.0.4: bytes=64 time=96 TTL=61 seq=1
Request timed out.
Reply from 220.233.0.4: bytes=64 time=74 TTL=61 seq=3
Request timed out.
Request timed out.
Reply from 220.233.0.4: bytes=64 time=55 TTL=61 seq=6
Reply from 220.233.0.4: bytes=64 time=52 TTL=61 seq=7
Reply from 220.233.0.4: bytes=64 time=31 TTL=61 seq=8
Reply from 220.233.0.4: bytes=64 time=84 TTL=61 seq=9
Reply from 220.233.0.4: bytes=64 time=74 TTL=61 seq=10
Reply from 220.233.0.4: bytes=64 time=84 TTL=61 seq=11
Reply from 220.233.0.4: bytes=64 time=65 TTL=61 seq=12
Request timed out.
Request timed out.
Reply from 220.233.0.4: bytes=64 time=161 TTL=61 seq=15
Reply from 220.233.0.4: bytes=64 time=79 TTL=61 seq=16
Request timed out.
Reply from 220.233.0.4: bytes=64 time=79 TTL=61 seq=18
Reply from 220.233.0.4: bytes=64 time=67 TTL=61 seq=19
Reply from 220.233.0.4: bytes=64 time=57 TTL=61 seq=20
Reply from 220.233.0.4: bytes=64 time=100 TTL=61 seq=21
Reply from 220.233.0.4: bytes=64 time=130 TTL=61 seq=22
Reply from 220.233.0.4: bytes=64 time=135 TTL=61 seq=23
Reply from 220.233.0.4: bytes=64 time=127 TTL=61 seq=24
Reply from 220.233.0.4: bytes=64 time=96 TTL=61 seq=25
Reply from 220.233.0.4: bytes=64 time=52 TTL=61 seq=26
Reply from 220.233.0.4: bytes=64 time=60 TTL=61 seq=27
Reply from 220.233.0.4: bytes=64 time=110 TTL=61 seq=28
Reply from 220.233.0.4: bytes=64 time=104 TTL=61 seq=29
Reply from 220.233.0.4: bytes=64 time=103 TTL=61 seq=30
Reply from 220.233.0.4: bytes=64 time=58 TTL=61 seq=31
Reply from 220.233.0.4: bytes=64 time=68 TTL=61 seq=32
Reply from 220.233.0.4: bytes=64 time=139 TTL=61 seq=33
Reply from 220.233.0.4: bytes=64 time=90 TTL=61 seq=34
Request timed out.
Reply from 220.233.0.4: bytes=64 time=33 TTL=61 seq=36
Request timed out.
Request timed out.
Reply from 220.233.0.4: bytes=64 time=53 TTL=61 seq=39
Reply from 220.233.0.4: bytes=64 time=155 TTL=61 seq=40
Reply from 220.233.0.4: bytes=64 time=24 TTL=61 seq=41
Reply from 220.233.0.4: bytes=64 time=123 TTL=61 seq=42
Reply from 220.233.0.4: bytes=64 time=31 TTL=61 seq=43
Reply from 220.233.0.4: bytes=64 time=55 TTL=61 seq=44
Request timed out.
Reply from 220.233.0.4: bytes=64 time=55 TTL=61 seq=46
Reply from 220.233.0.4: bytes=64 time=19 TTL=61 seq=47
Reply from 220.233.0.4: bytes=64 time=137 TTL=61 seq=48
Reply from 220.233.0.4: bytes=64 time=107 TTL=61 seq=49
Reply from 220.233.0.4: bytes=64 time=124 TTL=61 seq=50

Ping statistics for 220.233.0.4
Packets: Sent = 50, Received = 40, Lost = 10 (20% loss),
Approximate round trip times in milliseconds:
Minimum = 19, Maximum = 161, Average = 83

I am driven mad by this problem and wondering if someone could help or give me a clue. :cry:

Thanks in advance!
Hi,

Could you please PM me your service number or the ticket number, so I can look in to this for you :?:
To Log a fault ticket, please click click here or alternatively call Exetel VOIP numbers (02) 8030 1000 or 1300 788 141 (log faults 24x7)

=================
Exetel Support Portal
=================

RichS
Posts: 22
Joined: Tue Jun 27, 2006 8:42 am
Location: Sydney, Northern Beaches

Re: ping loss and high latency on ADSL2

Post by RichS » Tue Mar 20, 2012 8:58 pm

Hi,

I have similar issues to the above, what was the resolution for this ?

Pinging the gateway reported by the modem results below :

ping -w 5000 -n 50 220.233.1.45

Pinging 220.233.1.45 with 32 bytes of data:
Reply from 220.233.1.45: bytes=32 time=53ms TTL=254
Reply from 220.233.1.45: bytes=32 time=56ms TTL=254
Request timed out.
Request timed out.
Reply from 220.233.1.45: bytes=32 time=74ms TTL=254
Request timed out.
Reply from 220.233.1.45: bytes=32 time=73ms TTL=254
Request timed out.
Reply from 220.233.1.45: bytes=32 time=55ms TTL=254
Request timed out.
Reply from 220.233.1.45: bytes=32 time=52ms TTL=254
Reply from 220.233.1.45: bytes=32 time=60ms TTL=254
Reply from 220.233.1.45: bytes=32 time=54ms TTL=254
Reply from 220.233.1.45: bytes=32 time=59ms TTL=254
Reply from 220.233.1.45: bytes=32 time=96ms TTL=254
Reply from 220.233.1.45: bytes=32 time=97ms TTL=254
Request timed out.
Request timed out.
Reply from 220.233.1.45: bytes=32 time=88ms TTL=254
Reply from 220.233.1.45: bytes=32 time=54ms TTL=254
Reply from 220.233.1.45: bytes=32 time=57ms TTL=254
Reply from 220.233.1.45: bytes=32 time=58ms TTL=254
Reply from 220.233.1.45: bytes=32 time=69ms TTL=254
Reply from 220.233.1.45: bytes=32 time=75ms TTL=254
Reply from 220.233.1.45: bytes=32 time=83ms TTL=254
Request timed out.
Reply from 220.233.1.45: bytes=32 time=65ms TTL=254
Reply from 220.233.1.45: bytes=32 time=54ms TTL=254
Reply from 220.233.1.45: bytes=32 time=61ms TTL=254
Reply from 220.233.1.45: bytes=32 time=75ms TTL=254
Reply from 220.233.1.45: bytes=32 time=59ms TTL=254
Reply from 220.233.1.45: bytes=32 time=68ms TTL=254
Reply from 220.233.1.45: bytes=32 time=58ms TTL=254
Reply from 220.233.1.45: bytes=32 time=106ms TTL=254
Reply from 220.233.1.45: bytes=32 time=58ms TTL=254
Reply from 220.233.1.45: bytes=32 time=52ms TTL=254
Reply from 220.233.1.45: bytes=32 time=78ms TTL=254
Reply from 220.233.1.45: bytes=32 time=48ms TTL=254
Reply from 220.233.1.45: bytes=32 time=73ms TTL=254
Reply from 220.233.1.45: bytes=32 time=61ms TTL=254
Reply from 220.233.1.45: bytes=32 time=90ms TTL=254
Reply from 220.233.1.45: bytes=32 time=88ms TTL=254
Reply from 220.233.1.45: bytes=32 time=72ms TTL=254
Reply from 220.233.1.45: bytes=32 time=102ms TTL=254
Reply from 220.233.1.45: bytes=32 time=69ms TTL=254
Reply from 220.233.1.45: bytes=32 time=58ms TTL=254
Reply from 220.233.1.45: bytes=32 time=56ms TTL=254
Reply from 220.233.1.45: bytes=32 time=69ms TTL=254
Reply from 220.233.1.45: bytes=32 time=142ms TTL=254
Reply from 220.233.1.45: bytes=32 time=131ms TTL=254

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

Cheers
Rich

KavindaS
Forum Admin
Posts: 2549
Joined: Wed Dec 23, 2009 3:59 pm
Location: Sydney

Re: ping loss and high latency on ADSL2

Post by KavindaS » Tue Mar 20, 2012 9:44 pm

RichS wrote:Hi,

I have similar issues to the above, what was the resolution for this ?

Pinging the gateway reported by the modem results below :

ping -w 5000 -n 50 220.233.1.45

Pinging 220.233.1.45 with 32 bytes of data:
Reply from 220.233.1.45: bytes=32 time=53ms TTL=254
Reply from 220.233.1.45: bytes=32 time=56ms TTL=254
Request timed out.
Request timed out.
Reply from 220.233.1.45: bytes=32 time=74ms TTL=254
Request timed out.
Reply from 220.233.1.45: bytes=32 time=73ms TTL=254
Request timed out.
Reply from 220.233.1.45: bytes=32 time=55ms TTL=254
Request timed out.
Reply from 220.233.1.45: bytes=32 time=52ms TTL=254
Reply from 220.233.1.45: bytes=32 time=60ms TTL=254
Reply from 220.233.1.45: bytes=32 time=54ms TTL=254
Reply from 220.233.1.45: bytes=32 time=59ms TTL=254
Reply from 220.233.1.45: bytes=32 time=96ms TTL=254
Reply from 220.233.1.45: bytes=32 time=97ms TTL=254
Request timed out.
Request timed out.
Reply from 220.233.1.45: bytes=32 time=88ms TTL=254
Reply from 220.233.1.45: bytes=32 time=54ms TTL=254
Reply from 220.233.1.45: bytes=32 time=57ms TTL=254
Reply from 220.233.1.45: bytes=32 time=58ms TTL=254
Reply from 220.233.1.45: bytes=32 time=69ms TTL=254
Reply from 220.233.1.45: bytes=32 time=75ms TTL=254
Reply from 220.233.1.45: bytes=32 time=83ms TTL=254
Request timed out.
Reply from 220.233.1.45: bytes=32 time=65ms TTL=254
Reply from 220.233.1.45: bytes=32 time=54ms TTL=254
Reply from 220.233.1.45: bytes=32 time=61ms TTL=254
Reply from 220.233.1.45: bytes=32 time=75ms TTL=254
Reply from 220.233.1.45: bytes=32 time=59ms TTL=254
Reply from 220.233.1.45: bytes=32 time=68ms TTL=254
Reply from 220.233.1.45: bytes=32 time=58ms TTL=254
Reply from 220.233.1.45: bytes=32 time=106ms TTL=254
Reply from 220.233.1.45: bytes=32 time=58ms TTL=254
Reply from 220.233.1.45: bytes=32 time=52ms TTL=254
Reply from 220.233.1.45: bytes=32 time=78ms TTL=254
Reply from 220.233.1.45: bytes=32 time=48ms TTL=254
Reply from 220.233.1.45: bytes=32 time=73ms TTL=254
Reply from 220.233.1.45: bytes=32 time=61ms TTL=254
Reply from 220.233.1.45: bytes=32 time=90ms TTL=254
Reply from 220.233.1.45: bytes=32 time=88ms TTL=254
Reply from 220.233.1.45: bytes=32 time=72ms TTL=254
Reply from 220.233.1.45: bytes=32 time=102ms TTL=254
Reply from 220.233.1.45: bytes=32 time=69ms TTL=254
Reply from 220.233.1.45: bytes=32 time=58ms TTL=254
Reply from 220.233.1.45: bytes=32 time=56ms TTL=254
Reply from 220.233.1.45: bytes=32 time=69ms TTL=254
Reply from 220.233.1.45: bytes=32 time=142ms TTL=254
Reply from 220.233.1.45: bytes=32 time=131ms TTL=254

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

Cheers
Rich
Hi Rich,

Could you please update this with pings to 220.233.0.4 and a trace to the same 220.233.0.4 for further check on this.

RichS
Posts: 22
Joined: Tue Jun 27, 2006 8:42 am
Location: Sydney, Northern Beaches

Re: ping loss and high latency on ADSL2

Post by RichS » Tue Mar 20, 2012 10:19 pm

C:\Users\Richard>ping -w 5000 -n 50 220.233.0.4

Pinging 220.233.0.4 with 32 bytes of data:
Request timed out.
Reply from 220.233.0.4: bytes=32 time=44ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Reply from 220.233.0.4: bytes=32 time=41ms TTL=60
Reply from 220.233.0.4: bytes=32 time=44ms TTL=60
Reply from 220.233.0.4: bytes=32 time=41ms TTL=60
Reply from 220.233.0.4: bytes=32 time=42ms TTL=60
Reply from 220.233.0.4: bytes=32 time=40ms TTL=60
Request timed out.
Reply from 220.233.0.4: bytes=32 time=42ms TTL=60
Request timed out.
Request timed out.
Request timed out.
Reply from 220.233.0.4: bytes=32 time=42ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Reply from 220.233.0.4: bytes=32 time=41ms TTL=60
Reply from 220.233.0.4: bytes=32 time=40ms TTL=60
Reply from 220.233.0.4: bytes=32 time=43ms TTL=60
Reply from 220.233.0.4: bytes=32 time=43ms TTL=60
Reply from 220.233.0.4: bytes=32 time=45ms TTL=60
Reply from 220.233.0.4: bytes=32 time=43ms TTL=60
Reply from 220.233.0.4: bytes=32 time=41ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Reply from 220.233.0.4: bytes=32 time=44ms TTL=60
Reply from 220.233.0.4: bytes=32 time=43ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Request timed out.
Reply from 220.233.0.4: bytes=32 time=42ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Reply from 220.233.0.4: bytes=32 time=50ms TTL=60
Reply from 220.233.0.4: bytes=32 time=42ms TTL=60
Reply from 220.233.0.4: bytes=32 time=61ms TTL=60
Reply from 220.233.0.4: bytes=32 time=58ms TTL=60
Reply from 220.233.0.4: bytes=32 time=45ms TTL=60
Reply from 220.233.0.4: bytes=32 time=40ms TTL=60
Request timed out.
Reply from 220.233.0.4: bytes=32 time=42ms TTL=60
Request timed out.
Reply from 220.233.0.4: bytes=32 time=45ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Reply from 220.233.0.4: bytes=32 time=44ms TTL=60
Reply from 220.233.0.4: bytes=32 time=41ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Request timed out.
Reply from 220.233.0.4: bytes=32 time=38ms TTL=60
Request timed out.
Reply from 220.233.0.4: bytes=32 time=41ms TTL=60
Reply from 220.233.0.4: bytes=32 time=45ms TTL=60
Reply from 220.233.0.4: bytes=32 time=42ms TTL=60

Ping statistics for 220.233.0.4:
Packets: Sent = 50, Received = 40, Lost = 10 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 61ms, Average = 42ms

C:\Users\Richard>tracert 220.233.0.4

Tracing route to kolanut2-dns.exetel.com.au [220.233.0.4]
over a maximum of 30 hops:

1 2 ms 1 ms 2 ms sandra.home [192.168.3.1]
2 * * * Request timed out.
3 42 ms 39 ms * 58.96.6.129
4 * * * Request timed out.
5 41 ms 39 ms 40 ms kolanut2-dns.exetel.com.au [220.233.0.4]

Trace complete.

repeat of trace :
C:\Users\Richard>tracert 220.233.0.4

Tracing route to kolanut2-dns.exetel.com.au [220.233.0.4]
over a maximum of 30 hops:

1 3 ms 2 ms 2 ms sandra.home [192.168.3.1]
2 * * * Request timed out.
3 * 63 ms * 129.6.96.58.static.exetel.com.au [58.96.6.129]
4 51 ms 42 ms 49 ms 139.6.96.58.static.exetel.com.au [58.96.6.139]
5 55 ms 60 ms 49 ms kolanut2-dns.exetel.com.au [220.233.0.4]

Trace complete.

Orkon
Posts: 81
Joined: Sat Sep 29, 2007 12:38 pm
Location: Sydney, Australia

Re: ping loss and high latency on ADSL2

Post by Orkon » Tue Mar 20, 2012 11:00 pm

Evening

I'm also experiencing this slowness/latency

Code: Select all

ping 220.233.0.4

Pinging 220.233.0.4 with 32 bytes of data:

Reply from 220.233.0.4: bytes=32 time=103ms TTL=60
Reply from 220.233.0.4: bytes=32 time=44ms TTL=60
Reply from 220.233.0.4: bytes=32 time=119ms TTL=60
Reply from 220.233.0.4: bytes=32 time=221ms TTL=60
Reply from 220.233.0.4: bytes=32 time=279ms TTL=60
Reply from 220.233.0.4: bytes=32 time=95ms TTL=60
Reply from 220.233.0.4: bytes=32 time=79ms TTL=60
Reply from 220.233.0.4: bytes=32 time=50ms TTL=60
Reply from 220.233.0.4: bytes=32 time=166ms TTL=60
Reply from 220.233.0.4: bytes=32 time=115ms TTL=60
Reply from 220.233.0.4: bytes=32 time=84ms TTL=60
Reply from 220.233.0.4: bytes=32 time=77ms TTL=60
Reply from 220.233.0.4: bytes=32 time=176ms TTL=60
Reply from 220.233.0.4: bytes=32 time=165ms TTL=60
Reply from 220.233.0.4: bytes=32 time=43ms TTL=60
Reply from 220.233.0.4: bytes=32 time=101ms TTL=60
Reply from 220.233.0.4: bytes=32 time=41ms TTL=60
Reply from 220.233.0.4: bytes=32 time=207ms TTL=60
Reply from 220.233.0.4: bytes=32 time=246ms TTL=60
Reply from 220.233.0.4: bytes=32 time=219ms TTL=60
Reply from 220.233.0.4: bytes=32 time=215ms TTL=60
Reply from 220.233.0.4: bytes=32 time=200ms TTL=60
Reply from 220.233.0.4: bytes=32 time=145ms TTL=60
Reply from 220.233.0.4: bytes=32 time=64ms TTL=60
Reply from 220.233.0.4: bytes=32 time=151ms TTL=60
Reply from 220.233.0.4: bytes=32 time=140ms TTL=60
Reply from 220.233.0.4: bytes=32 time=244ms TTL=60
Reply from 220.233.0.4: bytes=32 time=130ms TTL=60
Reply from 220.233.0.4: bytes=32 time=104ms TTL=60
Reply from 220.233.0.4: bytes=32 time=168ms TTL=60
Reply from 220.233.0.4: bytes=32 time=190ms TTL=60
Reply from 220.233.0.4: bytes=32 time=86ms TTL=60
Reply from 220.233.0.4: bytes=32 time=139ms TTL=60
Reply from 220.233.0.4: bytes=32 time=51ms TTL=60
Reply from 220.233.0.4: bytes=32 time=53ms TTL=60
Reply from 220.233.0.4: bytes=32 time=69ms TTL=60
Reply from 220.233.0.4: bytes=32 time=162ms TTL=60
Reply from 220.233.0.4: bytes=32 time=140ms TTL=60
Reply from 220.233.0.4: bytes=32 time=145ms TTL=60
Reply from 220.233.0.4: bytes=32 time=73ms TTL=60
Reply from 220.233.0.4: bytes=32 time=50ms TTL=60
Reply from 220.233.0.4: bytes=32 time=73ms TTL=60
Reply from 220.233.0.4: bytes=32 time=53ms TTL=60
Reply from 220.233.0.4: bytes=32 time=185ms TTL=60
Reply from 220.233.0.4: bytes=32 time=197ms TTL=60
Reply from 220.233.0.4: bytes=32 time=53ms TTL=60
Reply from 220.233.0.4: bytes=32 time=111ms TTL=60
Reply from 220.233.0.4: bytes=32 time=130ms TTL=60
Reply from 220.233.0.4: bytes=32 time=120ms TTL=60
Reply from 220.233.0.4: bytes=32 time=177ms TTL=60
Reply from 220.233.0.4: bytes=32 time=66ms TTL=60
Reply from 220.233.0.4: bytes=32 time=209ms TTL=60
Reply from 220.233.0.4: bytes=32 time=142ms TTL=60
Reply from 220.233.0.4: bytes=32 time=245ms TTL=60
Reply from 220.233.0.4: bytes=32 time=182ms TTL=60
Reply from 220.233.0.4: bytes=32 time=145ms TTL=60
Reply from 220.233.0.4: bytes=32 time=211ms TTL=60
Reply from 220.233.0.4: bytes=32 time=239ms TTL=60
Reply from 220.233.0.4: bytes=32 time=40ms TTL=60
Reply from 220.233.0.4: bytes=32 time=163ms TTL=60
Reply from 220.233.0.4: bytes=32 time=178ms TTL=60
Reply from 220.233.0.4: bytes=32 time=272ms TTL=60
Reply from 220.233.0.4: bytes=32 time=33ms TTL=60
Reply from 220.233.0.4: bytes=32 time=34ms TTL=60
Reply from 220.233.0.4: bytes=32 time=214ms TTL=60
Reply from 220.233.0.4: bytes=32 time=147ms TTL=60
Reply from 220.233.0.4: bytes=32 time=132ms TTL=60
Reply from 220.233.0.4: bytes=32 time=165ms TTL=60
Reply from 220.233.0.4: bytes=32 time=201ms TTL=60
Reply from 220.233.0.4: bytes=32 time=80ms TTL=60
Reply from 220.233.0.4: bytes=32 time=167ms TTL=60
Reply from 220.233.0.4: bytes=32 time=298ms TTL=60
Reply from 220.233.0.4: bytes=32 time=85ms TTL=60
Reply from 220.233.0.4: bytes=32 time=144ms TTL=60
Reply from 220.233.0.4: bytes=32 time=36ms TTL=60
Reply from 220.233.0.4: bytes=32 time=108ms TTL=60
Reply from 220.233.0.4: bytes=32 time=53ms TTL=60
Reply from 220.233.0.4: bytes=32 time=61ms TTL=60
Reply from 220.233.0.4: bytes=32 time=33ms TTL=60
Reply from 220.233.0.4: bytes=32 time=93ms TTL=60
Reply from 220.233.0.4: bytes=32 time=100ms TTL=60
Reply from 220.233.0.4: bytes=32 time=132ms TTL=60
Reply from 220.233.0.4: bytes=32 time=202ms TTL=60
Reply from 220.233.0.4: bytes=32 time=111ms TTL=60
Reply from 220.233.0.4: bytes=32 time=106ms TTL=60
Reply from 220.233.0.4: bytes=32 time=177ms TTL=60
Reply from 220.233.0.4: bytes=32 time=225ms TTL=60
Reply from 220.233.0.4: bytes=32 time=152ms TTL=60

Ping statistics for 220.233.0.4:
    Packets: Sent = 88, Received = 88, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 298ms, Average = 134ms
Has only been tonight this has happened. Haven't had any other issues recently.

Regards
Scott

lasithah
Exetel Staff
Posts: 235
Joined: Mon Sep 05, 2011 5:42 pm
Location: Australia

Re: ping loss and high latency on ADSL2

Post by lasithah » Wed Mar 21, 2012 8:43 am

RichS wrote:C:\Users\Richard>ping -w 5000 -n 50 220.233.0.4

Pinging 220.233.0.4 with 32 bytes of data:
Request timed out.
Reply from 220.233.0.4: bytes=32 time=44ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Reply from 220.233.0.4: bytes=32 time=41ms TTL=60
Reply from 220.233.0.4: bytes=32 time=44ms TTL=60
Reply from 220.233.0.4: bytes=32 time=41ms TTL=60
Reply from 220.233.0.4: bytes=32 time=42ms TTL=60
Reply from 220.233.0.4: bytes=32 time=40ms TTL=60
Request timed out.
Reply from 220.233.0.4: bytes=32 time=42ms TTL=60
Request timed out.
Request timed out.
Request timed out.
Reply from 220.233.0.4: bytes=32 time=42ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Reply from 220.233.0.4: bytes=32 time=41ms TTL=60
Reply from 220.233.0.4: bytes=32 time=40ms TTL=60
Reply from 220.233.0.4: bytes=32 time=43ms TTL=60
Reply from 220.233.0.4: bytes=32 time=43ms TTL=60
Reply from 220.233.0.4: bytes=32 time=45ms TTL=60
Reply from 220.233.0.4: bytes=32 time=43ms TTL=60
Reply from 220.233.0.4: bytes=32 time=41ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Reply from 220.233.0.4: bytes=32 time=44ms TTL=60
Reply from 220.233.0.4: bytes=32 time=43ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Request timed out.
Reply from 220.233.0.4: bytes=32 time=42ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Reply from 220.233.0.4: bytes=32 time=50ms TTL=60
Reply from 220.233.0.4: bytes=32 time=42ms TTL=60
Reply from 220.233.0.4: bytes=32 time=61ms TTL=60
Reply from 220.233.0.4: bytes=32 time=58ms TTL=60
Reply from 220.233.0.4: bytes=32 time=45ms TTL=60
Reply from 220.233.0.4: bytes=32 time=40ms TTL=60
Request timed out.
Reply from 220.233.0.4: bytes=32 time=42ms TTL=60
Request timed out.
Reply from 220.233.0.4: bytes=32 time=45ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Reply from 220.233.0.4: bytes=32 time=44ms TTL=60
Reply from 220.233.0.4: bytes=32 time=41ms TTL=60
Reply from 220.233.0.4: bytes=32 time=39ms TTL=60
Request timed out.
Reply from 220.233.0.4: bytes=32 time=38ms TTL=60
Request timed out.
Reply from 220.233.0.4: bytes=32 time=41ms TTL=60
Reply from 220.233.0.4: bytes=32 time=45ms TTL=60
Reply from 220.233.0.4: bytes=32 time=42ms TTL=60

Ping statistics for 220.233.0.4:
Packets: Sent = 50, Received = 40, Lost = 10 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 61ms, Average = 42ms

C:\Users\Richard>tracert 220.233.0.4

Tracing route to kolanut2-dns.exetel.com.au [220.233.0.4]
over a maximum of 30 hops:

1 2 ms 1 ms 2 ms sandra.home [192.168.3.1]
2 * * * Request timed out.
3 42 ms 39 ms * 58.96.6.129
4 * * * Request timed out.
5 41 ms 39 ms 40 ms kolanut2-dns.exetel.com.au [220.233.0.4]

Trace complete.

repeat of trace :
C:\Users\Richard>tracert 220.233.0.4

Tracing route to kolanut2-dns.exetel.com.au [220.233.0.4]
over a maximum of 30 hops:

1 3 ms 2 ms 2 ms sandra.home [192.168.3.1]
2 * * * Request timed out.
3 * 63 ms * 129.6.96.58.static.exetel.com.au [58.96.6.129]
4 51 ms 42 ms 49 ms 139.6.96.58.static.exetel.com.au [58.96.6.139]
5 55 ms 60 ms 49 ms kolanut2-dns.exetel.com.au [220.233.0.4]

Trace complete.
Hi RichS,

I have checked the connection logs ans there are some dropouts for your connection. Line test shows the Noise margin is in a good level that couldn't cause any dropout. If there is a filter connected to the modem, remove it and check with only the modem. I have cleared the current connected circuit and created a ticket ID 4988896 for you. Please email or contact Exetel support quoting this number if the issue persist.

Cheers :)

lasithah
Exetel Staff
Posts: 235
Joined: Mon Sep 05, 2011 5:42 pm
Location: Australia

Re: ping loss and high latency on ADSL2

Post by lasithah » Wed Mar 21, 2012 8:50 am

Orkon wrote:Evening

I'm also experiencing this slowness/latency

Code: Select all

ping 220.233.0.4

Pinging 220.233.0.4 with 32 bytes of data:

Reply from 220.233.0.4: bytes=32 time=103ms TTL=60
Reply from 220.233.0.4: bytes=32 time=44ms TTL=60
Reply from 220.233.0.4: bytes=32 time=119ms TTL=60
Reply from 220.233.0.4: bytes=32 time=221ms TTL=60
Reply from 220.233.0.4: bytes=32 time=279ms TTL=60
Reply from 220.233.0.4: bytes=32 time=95ms TTL=60
Reply from 220.233.0.4: bytes=32 time=79ms TTL=60
Reply from 220.233.0.4: bytes=32 time=50ms TTL=60
Reply from 220.233.0.4: bytes=32 time=166ms TTL=60
Reply from 220.233.0.4: bytes=32 time=115ms TTL=60
Reply from 220.233.0.4: bytes=32 time=84ms TTL=60
Reply from 220.233.0.4: bytes=32 time=77ms TTL=60
Reply from 220.233.0.4: bytes=32 time=176ms TTL=60
Reply from 220.233.0.4: bytes=32 time=165ms TTL=60
Reply from 220.233.0.4: bytes=32 time=43ms TTL=60
Reply from 220.233.0.4: bytes=32 time=101ms TTL=60
Reply from 220.233.0.4: bytes=32 time=41ms TTL=60
Reply from 220.233.0.4: bytes=32 time=207ms TTL=60
Reply from 220.233.0.4: bytes=32 time=246ms TTL=60
Reply from 220.233.0.4: bytes=32 time=219ms TTL=60
Reply from 220.233.0.4: bytes=32 time=215ms TTL=60
Reply from 220.233.0.4: bytes=32 time=200ms TTL=60
Reply from 220.233.0.4: bytes=32 time=145ms TTL=60
Reply from 220.233.0.4: bytes=32 time=64ms TTL=60
Reply from 220.233.0.4: bytes=32 time=151ms TTL=60
Reply from 220.233.0.4: bytes=32 time=140ms TTL=60
Reply from 220.233.0.4: bytes=32 time=244ms TTL=60
Reply from 220.233.0.4: bytes=32 time=130ms TTL=60
Reply from 220.233.0.4: bytes=32 time=104ms TTL=60
Reply from 220.233.0.4: bytes=32 time=168ms TTL=60
Reply from 220.233.0.4: bytes=32 time=190ms TTL=60
Reply from 220.233.0.4: bytes=32 time=86ms TTL=60
Reply from 220.233.0.4: bytes=32 time=139ms TTL=60
Reply from 220.233.0.4: bytes=32 time=51ms TTL=60
Reply from 220.233.0.4: bytes=32 time=53ms TTL=60
Reply from 220.233.0.4: bytes=32 time=69ms TTL=60
Reply from 220.233.0.4: bytes=32 time=162ms TTL=60
Reply from 220.233.0.4: bytes=32 time=140ms TTL=60
Reply from 220.233.0.4: bytes=32 time=145ms TTL=60
Reply from 220.233.0.4: bytes=32 time=73ms TTL=60
Reply from 220.233.0.4: bytes=32 time=50ms TTL=60
Reply from 220.233.0.4: bytes=32 time=73ms TTL=60
Reply from 220.233.0.4: bytes=32 time=53ms TTL=60
Reply from 220.233.0.4: bytes=32 time=185ms TTL=60
Reply from 220.233.0.4: bytes=32 time=197ms TTL=60
Reply from 220.233.0.4: bytes=32 time=53ms TTL=60
Reply from 220.233.0.4: bytes=32 time=111ms TTL=60
Reply from 220.233.0.4: bytes=32 time=130ms TTL=60
Reply from 220.233.0.4: bytes=32 time=120ms TTL=60
Reply from 220.233.0.4: bytes=32 time=177ms TTL=60
Reply from 220.233.0.4: bytes=32 time=66ms TTL=60
Reply from 220.233.0.4: bytes=32 time=209ms TTL=60
Reply from 220.233.0.4: bytes=32 time=142ms TTL=60
Reply from 220.233.0.4: bytes=32 time=245ms TTL=60
Reply from 220.233.0.4: bytes=32 time=182ms TTL=60
Reply from 220.233.0.4: bytes=32 time=145ms TTL=60
Reply from 220.233.0.4: bytes=32 time=211ms TTL=60
Reply from 220.233.0.4: bytes=32 time=239ms TTL=60
Reply from 220.233.0.4: bytes=32 time=40ms TTL=60
Reply from 220.233.0.4: bytes=32 time=163ms TTL=60
Reply from 220.233.0.4: bytes=32 time=178ms TTL=60
Reply from 220.233.0.4: bytes=32 time=272ms TTL=60
Reply from 220.233.0.4: bytes=32 time=33ms TTL=60
Reply from 220.233.0.4: bytes=32 time=34ms TTL=60
Reply from 220.233.0.4: bytes=32 time=214ms TTL=60
Reply from 220.233.0.4: bytes=32 time=147ms TTL=60
Reply from 220.233.0.4: bytes=32 time=132ms TTL=60
Reply from 220.233.0.4: bytes=32 time=165ms TTL=60
Reply from 220.233.0.4: bytes=32 time=201ms TTL=60
Reply from 220.233.0.4: bytes=32 time=80ms TTL=60
Reply from 220.233.0.4: bytes=32 time=167ms TTL=60
Reply from 220.233.0.4: bytes=32 time=298ms TTL=60
Reply from 220.233.0.4: bytes=32 time=85ms TTL=60
Reply from 220.233.0.4: bytes=32 time=144ms TTL=60
Reply from 220.233.0.4: bytes=32 time=36ms TTL=60
Reply from 220.233.0.4: bytes=32 time=108ms TTL=60
Reply from 220.233.0.4: bytes=32 time=53ms TTL=60
Reply from 220.233.0.4: bytes=32 time=61ms TTL=60
Reply from 220.233.0.4: bytes=32 time=33ms TTL=60
Reply from 220.233.0.4: bytes=32 time=93ms TTL=60
Reply from 220.233.0.4: bytes=32 time=100ms TTL=60
Reply from 220.233.0.4: bytes=32 time=132ms TTL=60
Reply from 220.233.0.4: bytes=32 time=202ms TTL=60
Reply from 220.233.0.4: bytes=32 time=111ms TTL=60
Reply from 220.233.0.4: bytes=32 time=106ms TTL=60
Reply from 220.233.0.4: bytes=32 time=177ms TTL=60
Reply from 220.233.0.4: bytes=32 time=225ms TTL=60
Reply from 220.233.0.4: bytes=32 time=152ms TTL=60

Ping statistics for 220.233.0.4:
    Packets: Sent = 88, Received = 88, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 298ms, Average = 134ms
Has only been tonight this has happened. Haven't had any other issues recently.

Regards
Scott
Hi Scott,

I have done a line resync to your line that could reduce the latency that you are getting. :)

let us know if it remains the same :(

Cheers,

Orkon
Posts: 81
Joined: Sat Sep 29, 2007 12:38 pm
Location: Sydney, Australia

Re: ping loss and high latency on ADSL2

Post by Orkon » Wed Mar 21, 2012 6:34 pm

lasithah wrote:
Orkon wrote:Evening

I'm also experiencing this slowness/latency

Code: Select all

ping 220.233.0.4

...

Ping statistics for 220.233.0.4:
    Packets: Sent = 88, Received = 88, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 298ms, Average = 134ms
Has only been tonight this has happened. Haven't had any other issues recently.

Regards
Scott
Hi Scott,

I have done a line resync to your line that could reduce the latency that you are getting. :)

let us know if it remains the same :(

Cheers,
Thanks for that - i'll check again tonight. I have a ticket thats been open for a while due to conjestion on my exchange. Is it worth giving you that one to see if that is related?

Thanks
Scott

KavindaS
Forum Admin
Posts: 2549
Joined: Wed Dec 23, 2009 3:59 pm
Location: Sydney

Re: ping loss and high latency on ADSL2

Post by KavindaS » Wed Mar 21, 2012 6:53 pm

Orkon wrote:
lasithah wrote:
Orkon wrote:Evening

I'm also experiencing this slowness/latency

Code: Select all

ping 220.233.0.4

...

Ping statistics for 220.233.0.4:
    Packets: Sent = 88, Received = 88, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 298ms, Average = 134ms
Has only been tonight this has happened. Haven't had any other issues recently.

Regards
Scott
Hi Scott,

I have done a line resync to your line that could reduce the latency that you are getting. :)

let us know if it remains the same :(

Cheers,
Thanks for that - i'll check again tonight. I have a ticket thats been open for a while due to conjestion on my exchange. Is it worth giving you that one to see if that is related?

Thanks
Scott

Hi Scott,
Yes when you check that tonight if the issue persist you may update the thread with that ticket id.

Post Reply