Erratic Ping - Como Exchange
Posted: Mon Oct 17, 2011 6:27 pm
Hi,
Since last Tuesday I have been experiencing an erratic high ping to a gaming server that is causing extreme lag and disconnection issues etc.
I have tried the following:
1. Isolate Line.
2. Reset Modem.
3. Checked all cable connections.
4. Ensure no other programs running or downloads occuring.
5. Run Virus, Malware scans etc.
6. Shitdown Firewall temporarily.
7. Run Speed Tests all normal speed ok.
My usual Ping to this gaming server(in WA) is <100mS - see attached Trace Route:
Tracing route to 116.212.196.244 over a maximum of 30 hops
1 * * * Request timed out.
2 9 ms 9 ms 10 ms 129.6.96.58.static.exetel.com.au [58.96.6.129]
3 11 ms 10 ms 9 ms ip-11-2-100-218.static.pipenetworks.com [218.100
.2.11]
4 59 ms 59 ms 59 ms ge2-4.br02.wa.amcom.net.au [203.161.65.5]
5 58 ms 59 ms 61 ms te7-1.cr02.wa.amcom.net.au [203.161.65.74]
6 59 ms 59 ms 58 ms te4-1.gw02.v6.wa.amcom.net.au [203.161.64.65]
7 60 ms 59 ms 58 ms 116.212.196.244
The ping now varies between 700 to 1600mS when it is performing erratically(this last for a few hours appears to not just be at peak times) at other times it still returns to normal, I have attached a couple of Trace Routes that have been run over last few days:
Tracing route to 116.212.196.244 over a maximum of 30 hops
1 * * * Request timed out.
2 1310 ms 975 ms 1209 ms 129.6.96.58.static.exetel.com.au [58.96.6.129]
3 1363 ms 1339 ms 1155 ms ip-11-2-100-218.static.pipenetworks.com [218.100
.2.11]
4 1525 ms 1576 ms 1737 ms ge2-4.br02.wa.amcom.net.au [203.161.65.5]
5 1153 ms 1162 ms 1338 ms te7-1.cr02.wa.amcom.net.au [203.161.65.74]
6 1706 ms 1969 ms 1812 ms te4-1.gw02.v6.wa.amcom.net.au [203.161.64.65]
7 1515 ms 1497 ms 1589 ms 116.212.196.244
Trace complete.
Tracing route to 116.212.196.244 over a maximum of 30 hops
1 * * * Request timed out.
2 1373 ms 1470 ms 1412 ms 129.6.96.58.static.exetel.com.au [58.96.6.129]
3 1101 ms 719 ms 648 ms ip-11-2-100-218.static.pipenetworks.com [218.100
.2.11]
4 1022 ms 751 ms 802 ms ge2-4.br02.wa.amcom.net.au [203.161.65.5]
5 632 ms 638 ms 796 ms te7-1.cr02.wa.amcom.net.au [203.161.65.74]
6 837 ms 496 ms 703 ms te4-1.gw02.v6.wa.amcom.net.au [203.161.64.65]
7 734 ms 685 ms 891 ms 116.212.196.244
I have also tried Trace Route to Exetel which shows folloing results when bad :
Tracing route to candlenut-web.exetel.com.au [220.233.0.9]
over a maximum of 30 hops:
1 * * * Request timed out.
2 558 ms 662 ms 539 ms 129.6.96.58.static.exetel.com.au [58.96.6.129]
3 630 ms 673 ms 712 ms 139.6.96.58.static.exetel.com.au [58.96.6.139]
4 534 ms 606 ms 624 ms candlenut-web.exetel.com.au [220.233.0.9]
And when good :
Tracing route to candlenut-web.exetel.com.au [220.233.0.9]
over a maximum of 30 hops:
1 * * * Request timed out.
2 9 ms 9 ms 9 ms 129.6.96.58.static.exetel.com.au [58.96.6.129]
3 10 ms 10 ms 9 ms 139.6.96.58.static.exetel.com.au [58.96.6.139]
4 11 ms 11 ms 11 ms candlenut-web.exetel.com.au [220.233.0.9]
Trace complete.
1. Is there a problem with maintenance etc at Como Exchange or Exetel at present that will be causing this problem?
2. Is there any other diagnostics that can be advised?
3. Please can you advise when problem can be investigated/rectfied?
Thanks,
Chrs, Pat
Since last Tuesday I have been experiencing an erratic high ping to a gaming server that is causing extreme lag and disconnection issues etc.
I have tried the following:
1. Isolate Line.
2. Reset Modem.
3. Checked all cable connections.
4. Ensure no other programs running or downloads occuring.
5. Run Virus, Malware scans etc.
6. Shitdown Firewall temporarily.
7. Run Speed Tests all normal speed ok.
My usual Ping to this gaming server(in WA) is <100mS - see attached Trace Route:
Tracing route to 116.212.196.244 over a maximum of 30 hops
1 * * * Request timed out.
2 9 ms 9 ms 10 ms 129.6.96.58.static.exetel.com.au [58.96.6.129]
3 11 ms 10 ms 9 ms ip-11-2-100-218.static.pipenetworks.com [218.100
.2.11]
4 59 ms 59 ms 59 ms ge2-4.br02.wa.amcom.net.au [203.161.65.5]
5 58 ms 59 ms 61 ms te7-1.cr02.wa.amcom.net.au [203.161.65.74]
6 59 ms 59 ms 58 ms te4-1.gw02.v6.wa.amcom.net.au [203.161.64.65]
7 60 ms 59 ms 58 ms 116.212.196.244
The ping now varies between 700 to 1600mS when it is performing erratically(this last for a few hours appears to not just be at peak times) at other times it still returns to normal, I have attached a couple of Trace Routes that have been run over last few days:
Tracing route to 116.212.196.244 over a maximum of 30 hops
1 * * * Request timed out.
2 1310 ms 975 ms 1209 ms 129.6.96.58.static.exetel.com.au [58.96.6.129]
3 1363 ms 1339 ms 1155 ms ip-11-2-100-218.static.pipenetworks.com [218.100
.2.11]
4 1525 ms 1576 ms 1737 ms ge2-4.br02.wa.amcom.net.au [203.161.65.5]
5 1153 ms 1162 ms 1338 ms te7-1.cr02.wa.amcom.net.au [203.161.65.74]
6 1706 ms 1969 ms 1812 ms te4-1.gw02.v6.wa.amcom.net.au [203.161.64.65]
7 1515 ms 1497 ms 1589 ms 116.212.196.244
Trace complete.
Tracing route to 116.212.196.244 over a maximum of 30 hops
1 * * * Request timed out.
2 1373 ms 1470 ms 1412 ms 129.6.96.58.static.exetel.com.au [58.96.6.129]
3 1101 ms 719 ms 648 ms ip-11-2-100-218.static.pipenetworks.com [218.100
.2.11]
4 1022 ms 751 ms 802 ms ge2-4.br02.wa.amcom.net.au [203.161.65.5]
5 632 ms 638 ms 796 ms te7-1.cr02.wa.amcom.net.au [203.161.65.74]
6 837 ms 496 ms 703 ms te4-1.gw02.v6.wa.amcom.net.au [203.161.64.65]
7 734 ms 685 ms 891 ms 116.212.196.244
I have also tried Trace Route to Exetel which shows folloing results when bad :
Tracing route to candlenut-web.exetel.com.au [220.233.0.9]
over a maximum of 30 hops:
1 * * * Request timed out.
2 558 ms 662 ms 539 ms 129.6.96.58.static.exetel.com.au [58.96.6.129]
3 630 ms 673 ms 712 ms 139.6.96.58.static.exetel.com.au [58.96.6.139]
4 534 ms 606 ms 624 ms candlenut-web.exetel.com.au [220.233.0.9]
And when good :
Tracing route to candlenut-web.exetel.com.au [220.233.0.9]
over a maximum of 30 hops:
1 * * * Request timed out.
2 9 ms 9 ms 9 ms 129.6.96.58.static.exetel.com.au [58.96.6.129]
3 10 ms 10 ms 9 ms 139.6.96.58.static.exetel.com.au [58.96.6.139]
4 11 ms 11 ms 11 ms candlenut-web.exetel.com.au [220.233.0.9]
Trace complete.
1. Is there a problem with maintenance etc at Como Exchange or Exetel at present that will be causing this problem?
2. Is there any other diagnostics that can be advised?
3. Please can you advise when problem can be investigated/rectfied?
Thanks,
Chrs, Pat