High Pings! Xbox live is a no go :(

Connection issues, drop outs or speed related faults for ADSL and ADSL2+ services
Post Reply
my99
Posts: 21
Joined: Thu Mar 24, 2011 9:18 pm
Location: Hunter

High Pings! Xbox live is a no go :(

Post by my99 » Tue Apr 02, 2013 10:10 pm

Hi exetel

I been have terrible issues with ping/jitter for a while now. normally pings around 30ms. But of late it's around 200ms to the closest servers.
Could someone please help me with these issues. Thanks

Image

Dazzled
Volunteer Site Admin
Posts: 6003
Joined: Mon Nov 13, 2006 1:16 pm
Location: Sydney

Re: High Pings! Xbox live is a no go :(

Post by Dazzled » Tue Apr 02, 2013 10:33 pm

That looks nasty. It might be useful if you ran a sequence of pings to an Exetel server (any of the website, DNS, etc) to confirm if this is associated with your local line, exchange, or backhaul to Exetel.

udara
Exetel Staff
Posts: 362
Joined: Thu Dec 17, 2009 11:06 am

Re: High Pings! Xbox live is a no go :(

Post by udara » Tue Apr 02, 2013 10:48 pm

Hi exetel

I been have terrible issues with ping/jitter for a while now. normally pings around 30ms. But of late it's around 200ms to the closest servers.
Could someone please help me with these issues. Thanks
Hi my99,

Could you please PM me your service number , so that I can have a look into your connection :)
To Log a fault ticket, please click Here or alternatively call Exetel VOIP numbers (02) 8030 1000 or 1300 788 141 (log faults 24x7)

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

my99
Posts: 21
Joined: Thu Mar 24, 2011 9:18 pm
Location: Hunter

Re: High Pings! Xbox live is a no go :(

Post by my99 » Tue Apr 02, 2013 11:03 pm

Dazzled wrote:That looks nasty. It might be useful if you ran a sequence of pings to an Exetel server (any of the website, DNS, etc) to confirm if this is associated with your local line, exchange, or backhaul to Exetel.
Do you mean a Traceroute? to http://www.exetel.com.au

Seems good now. I changed my ip it slowly got better or it's just gone off peak time now.
will see how it goes tomorrow night

Image
Last edited by my99 on Tue Apr 02, 2013 11:07 pm, edited 2 times in total.

my99
Posts: 21
Joined: Thu Mar 24, 2011 9:18 pm
Location: Hunter

Re: High Pings! Xbox live is a no go :(

Post by my99 » Tue Apr 02, 2013 11:03 pm

udara wrote:
Hi exetel

I been have terrible issues with ping/jitter for a while now. normally pings around 30ms. But of late it's around 200ms to the closest servers.
Could someone please help me with these issues. Thanks
Hi my99,

Could you please PM me your service number , so that I can have a look into your connection :)
Done :)

my99
Posts: 21
Joined: Thu Mar 24, 2011 9:18 pm
Location: Hunter

Re: High Pings! Xbox live is a no go :(

Post by my99 » Wed Apr 03, 2013 9:35 pm

This morning
Image


Now (atrocious)
Image

Dazzled
Volunteer Site Admin
Posts: 6003
Joined: Mon Nov 13, 2006 1:16 pm
Location: Sydney

Re: High Pings! Xbox live is a no go :(

Post by Dazzled » Wed Apr 03, 2013 9:50 pm

Try ping www.exetel.com.au for a dozen or two repeats. For a Windows machine, ping -n 24 www.exetel.com.au. That way you remove the extra trip to the Pingtest server from the problem. Jitter is a measure of the variance, and if excessive may suggest local exchange or backhaul congestion - this is usually only a problem in peak hours.

Unfortunately Windows tools are limited, and much abused, and you don't always get servers giving them any priority.

my99
Posts: 21
Joined: Thu Mar 24, 2011 9:18 pm
Location: Hunter

Re: High Pings! Xbox live is a no go :(

Post by my99 » Wed Apr 03, 2013 10:41 pm

Thanks Dazzled

Results seem fairly erratic :(

C:\Users\Jake>ping -n 24 http://www.exetel.com.au

Pinging http://www.exetel.com.au [220.233.0.9] with 32
Reply from 220.233.0.9: bytes=32 time=118ms TTL
Reply from 220.233.0.9: bytes=32 time=54ms TTL=
Reply from 220.233.0.9: bytes=32 time=101ms TTL
Reply from 220.233.0.9: bytes=32 time=115ms TTL
Reply from 220.233.0.9: bytes=32 time=56ms TTL=
Reply from 220.233.0.9: bytes=32 time=77ms TTL=
Reply from 220.233.0.9: bytes=32 time=94ms TTL=
Reply from 220.233.0.9: bytes=32 time=189ms TTL
Reply from 220.233.0.9: bytes=32 time=33ms TTL=
Reply from 220.233.0.9: bytes=32 time=195ms TTL
Reply from 220.233.0.9: bytes=32 time=187ms TTL
Reply from 220.233.0.9: bytes=32 time=236ms TTL
Reply from 220.233.0.9: bytes=32 time=268ms TTL
Reply from 220.233.0.9: bytes=32 time=227ms TTL
Reply from 220.233.0.9: bytes=32 time=313ms TTL
Reply from 220.233.0.9: bytes=32 time=167ms TTL
Reply from 220.233.0.9: bytes=32 time=158ms TTL
Reply from 220.233.0.9: bytes=32 time=28ms TTL=
Reply from 220.233.0.9: bytes=32 time=63ms TTL=
Reply from 220.233.0.9: bytes=32 time=85ms TTL=
Reply from 220.233.0.9: bytes=32 time=99ms TTL=
Reply from 220.233.0.9: bytes=32 time=197ms TTL
Reply from 220.233.0.9: bytes=32 time=227ms TTL
Reply from 220.233.0.9: bytes=32 time=47ms TTL=

Ping statistics for 220.233.0.9:
Packets: Sent = 24, Received = 24, Lost = 0
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 313ms, Average = 138ms

C:\Users\Jake>ping -n 24 http://www.exetel.com.au

Pinging http://www.exetel.com.au [220.233.0.9] with 32
Reply from 220.233.0.9: bytes=32 time=133ms TTL
Reply from 220.233.0.9: bytes=32 time=123ms TTL
Reply from 220.233.0.9: bytes=32 time=189ms TTL
Reply from 220.233.0.9: bytes=32 time=144ms TTL
Reply from 220.233.0.9: bytes=32 time=46ms TTL=
Reply from 220.233.0.9: bytes=32 time=155ms TTL
Reply from 220.233.0.9: bytes=32 time=31ms TTL=
Reply from 220.233.0.9: bytes=32 time=158ms TTL
Reply from 220.233.0.9: bytes=32 time=78ms TTL=
Reply from 220.233.0.9: bytes=32 time=110ms TTL
Reply from 220.233.0.9: bytes=32 time=38ms TTL=
Reply from 220.233.0.9: bytes=32 time=118ms TTL
Reply from 220.233.0.9: bytes=32 time=174ms TTL
Reply from 220.233.0.9: bytes=32 time=116ms TTL
Reply from 220.233.0.9: bytes=32 time=63ms TTL=
Reply from 220.233.0.9: bytes=32 time=154ms TTL
Reply from 220.233.0.9: bytes=32 time=58ms TTL=
Reply from 220.233.0.9: bytes=32 time=70ms TTL=
Reply from 220.233.0.9: bytes=32 time=91ms TTL=
Reply from 220.233.0.9: bytes=32 time=41ms TTL=
Reply from 220.233.0.9: bytes=32 time=66ms TTL=
Reply from 220.233.0.9: bytes=32 time=60ms TTL=
Reply from 220.233.0.9: bytes=32 time=46ms TTL=
Reply from 220.233.0.9: bytes=32 time=175ms TTL

Ping statistics for 220.233.0.9:
Packets: Sent = 24, Received = 24, Lost = 0
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 189ms, Average = 101ms

C:\Users\Jake>ping -n 24 http://www.exetel.com.au

Pinging http://www.exetel.com.au [220.233.0.9] with 32
Reply from 220.233.0.9: bytes=32 time=76ms TTL=
Reply from 220.233.0.9: bytes=32 time=50ms TTL=
Reply from 220.233.0.9: bytes=32 time=59ms TTL=
Reply from 220.233.0.9: bytes=32 time=166ms TTL
Reply from 220.233.0.9: bytes=32 time=67ms TTL=
Reply from 220.233.0.9: bytes=32 time=276ms TTL
Reply from 220.233.0.9: bytes=32 time=131ms TTL
Reply from 220.233.0.9: bytes=32 time=48ms TTL=
Reply from 220.233.0.9: bytes=32 time=128ms TTL
Reply from 220.233.0.9: bytes=32 time=265ms TTL
Reply from 220.233.0.9: bytes=32 time=208ms TTL
Reply from 220.233.0.9: bytes=32 time=177ms TTL
Reply from 220.233.0.9: bytes=32 time=246ms TTL
Reply from 220.233.0.9: bytes=32 time=86ms TTL=
Reply from 220.233.0.9: bytes=32 time=164ms TTL
Reply from 220.233.0.9: bytes=32 time=30ms TTL=
Reply from 220.233.0.9: bytes=32 time=58ms TTL=
Reply from 220.233.0.9: bytes=32 time=123ms TTL
Reply from 220.233.0.9: bytes=32 time=124ms TTL
Reply from 220.233.0.9: bytes=32 time=143ms TTL
Reply from 220.233.0.9: bytes=32 time=248ms TTL
Reply from 220.233.0.9: bytes=32 time=164ms TTL
Reply from 220.233.0.9: bytes=32 time=33ms TTL=
Reply from 220.233.0.9: bytes=32 time=222ms TTL

Ping statistics for 220.233.0.9:
Packets: Sent = 24, Received = 24, Lost = 0
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 276ms, Average = 137ms

saadbafik
Exetel Staff
Posts: 146
Joined: Tue Feb 14, 2012 11:12 pm
Location: Sri Lanka

Re: High Pings! Xbox live is a no go :(

Post by saadbafik » Wed Apr 03, 2013 11:40 pm

my99 wrote:Thanks Dazzled

Results seem fairly erratic :(

C:\Users\Jake>ping -n 24 http://www.exetel.com.au

Pinging http://www.exetel.com.au [220.233.0.9] with 32
Reply from 220.233.0.9: bytes=32 time=118ms TTL
Reply from 220.233.0.9: bytes=32 time=54ms TTL=
Reply from 220.233.0.9: bytes=32 time=101ms TTL
Reply from 220.233.0.9: bytes=32 time=115ms TTL
Reply from 220.233.0.9: bytes=32 time=56ms TTL=
Reply from 220.233.0.9: bytes=32 time=77ms TTL=
Reply from 220.233.0.9: bytes=32 time=94ms TTL=
Reply from 220.233.0.9: bytes=32 time=189ms TTL
Reply from 220.233.0.9: bytes=32 time=33ms TTL=
Reply from 220.233.0.9: bytes=32 time=195ms TTL
Reply from 220.233.0.9: bytes=32 time=187ms TTL
Reply from 220.233.0.9: bytes=32 time=236ms TTL
Reply from 220.233.0.9: bytes=32 time=268ms TTL
Reply from 220.233.0.9: bytes=32 time=227ms TTL
Reply from 220.233.0.9: bytes=32 time=313ms TTL
Reply from 220.233.0.9: bytes=32 time=167ms TTL
Reply from 220.233.0.9: bytes=32 time=158ms TTL
Reply from 220.233.0.9: bytes=32 time=28ms TTL=
Reply from 220.233.0.9: bytes=32 time=63ms TTL=
Reply from 220.233.0.9: bytes=32 time=85ms TTL=
Reply from 220.233.0.9: bytes=32 time=99ms TTL=
Reply from 220.233.0.9: bytes=32 time=197ms TTL
Reply from 220.233.0.9: bytes=32 time=227ms TTL
Reply from 220.233.0.9: bytes=32 time=47ms TTL=

Ping statistics for 220.233.0.9:
Packets: Sent = 24, Received = 24, Lost = 0
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 313ms, Average = 138ms

C:\Users\Jake>ping -n 24 http://www.exetel.com.au

Pinging http://www.exetel.com.au [220.233.0.9] with 32
Reply from 220.233.0.9: bytes=32 time=133ms TTL
Reply from 220.233.0.9: bytes=32 time=123ms TTL
Reply from 220.233.0.9: bytes=32 time=189ms TTL
Reply from 220.233.0.9: bytes=32 time=144ms TTL
Reply from 220.233.0.9: bytes=32 time=46ms TTL=
Reply from 220.233.0.9: bytes=32 time=155ms TTL
Reply from 220.233.0.9: bytes=32 time=31ms TTL=
Reply from 220.233.0.9: bytes=32 time=158ms TTL
Reply from 220.233.0.9: bytes=32 time=78ms TTL=
Reply from 220.233.0.9: bytes=32 time=110ms TTL
Reply from 220.233.0.9: bytes=32 time=38ms TTL=
Reply from 220.233.0.9: bytes=32 time=118ms TTL
Reply from 220.233.0.9: bytes=32 time=174ms TTL
Reply from 220.233.0.9: bytes=32 time=116ms TTL
Reply from 220.233.0.9: bytes=32 time=63ms TTL=
Reply from 220.233.0.9: bytes=32 time=154ms TTL
Reply from 220.233.0.9: bytes=32 time=58ms TTL=
Reply from 220.233.0.9: bytes=32 time=70ms TTL=
Reply from 220.233.0.9: bytes=32 time=91ms TTL=
Reply from 220.233.0.9: bytes=32 time=41ms TTL=
Reply from 220.233.0.9: bytes=32 time=66ms TTL=
Reply from 220.233.0.9: bytes=32 time=60ms TTL=
Reply from 220.233.0.9: bytes=32 time=46ms TTL=
Reply from 220.233.0.9: bytes=32 time=175ms TTL

Ping statistics for 220.233.0.9:
Packets: Sent = 24, Received = 24, Lost = 0
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 189ms, Average = 101ms

C:\Users\Jake>ping -n 24 http://www.exetel.com.au

Pinging http://www.exetel.com.au [220.233.0.9] with 32
Reply from 220.233.0.9: bytes=32 time=76ms TTL=
Reply from 220.233.0.9: bytes=32 time=50ms TTL=
Reply from 220.233.0.9: bytes=32 time=59ms TTL=
Reply from 220.233.0.9: bytes=32 time=166ms TTL
Reply from 220.233.0.9: bytes=32 time=67ms TTL=
Reply from 220.233.0.9: bytes=32 time=276ms TTL
Reply from 220.233.0.9: bytes=32 time=131ms TTL
Reply from 220.233.0.9: bytes=32 time=48ms TTL=
Reply from 220.233.0.9: bytes=32 time=128ms TTL
Reply from 220.233.0.9: bytes=32 time=265ms TTL
Reply from 220.233.0.9: bytes=32 time=208ms TTL
Reply from 220.233.0.9: bytes=32 time=177ms TTL
Reply from 220.233.0.9: bytes=32 time=246ms TTL
Reply from 220.233.0.9: bytes=32 time=86ms TTL=
Reply from 220.233.0.9: bytes=32 time=164ms TTL
Reply from 220.233.0.9: bytes=32 time=30ms TTL=
Reply from 220.233.0.9: bytes=32 time=58ms TTL=
Reply from 220.233.0.9: bytes=32 time=123ms TTL
Reply from 220.233.0.9: bytes=32 time=124ms TTL
Reply from 220.233.0.9: bytes=32 time=143ms TTL
Reply from 220.233.0.9: bytes=32 time=248ms TTL
Reply from 220.233.0.9: bytes=32 time=164ms TTL
Reply from 220.233.0.9: bytes=32 time=33ms TTL=
Reply from 220.233.0.9: bytes=32 time=222ms TTL

Ping statistics for 220.233.0.9:
Packets: Sent = 24, Received = 24, Lost = 0
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 276ms, Average = 137ms

Hi,

We have escalated your service issue to our Wholesale Supplier under reference number 6382802.

We will get back to you as soon as we received an update.

Regards,
Saad B

my99
Posts: 21
Joined: Thu Mar 24, 2011 9:18 pm
Location: Hunter

Re: High Pings! Xbox live is a no go :(

Post by my99 » Thu Apr 04, 2013 11:10 pm

saadbafik wrote:
Hi,

We have escalated your service issue to our Wholesale Supplier under reference number 6382802.

We will get back to you as soon as we received an update.

Regards,
Saad B
Thats great, Thank you :)

I seem to have no issues tonight :shock: unlike the last month or so.. lets hope this continues :)

6.50pm

C:\Users\Jake>ping -n 24 http://www.exetel.com.au

Pinging http://www.exetel.com.au [220.233.0.9] with 32 bytes of data:
Reply from 220.233.0.9: bytes=32 time=22ms TTL=60
Reply from 220.233.0.9: bytes=32 time=32ms TTL=60
Reply from 220.233.0.9: bytes=32 time=34ms TTL=60
Reply from 220.233.0.9: bytes=32 time=22ms TTL=60
Reply from 220.233.0.9: bytes=32 time=22ms TTL=60
Reply from 220.233.0.9: bytes=32 time=22ms TTL=60
Reply from 220.233.0.9: bytes=32 time=23ms TTL=60
Reply from 220.233.0.9: bytes=32 time=23ms TTL=60
Reply from 220.233.0.9: bytes=32 time=25ms TTL=60
Reply from 220.233.0.9: bytes=32 time=27ms TTL=60
Reply from 220.233.0.9: bytes=32 time=23ms TTL=60
Reply from 220.233.0.9: bytes=32 time=25ms TTL=60
Reply from 220.233.0.9: bytes=32 time=21ms TTL=60
Reply from 220.233.0.9: bytes=32 time=22ms TTL=60
Reply from 220.233.0.9: bytes=32 time=25ms TTL=60
Reply from 220.233.0.9: bytes=32 time=41ms TTL=60
Reply from 220.233.0.9: bytes=32 time=24ms TTL=60
Reply from 220.233.0.9: bytes=32 time=25ms TTL=60
Reply from 220.233.0.9: bytes=32 time=21ms TTL=60
Reply from 220.233.0.9: bytes=32 time=30ms TTL=60
Reply from 220.233.0.9: bytes=32 time=20ms TTL=60
Reply from 220.233.0.9: bytes=32 time=32ms TTL=60
Reply from 220.233.0.9: bytes=32 time=22ms TTL=60
Reply from 220.233.0.9: bytes=32 time=21ms TTL=60

Ping statistics for 220.233.0.9:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 41ms, Average = 25ms

8.12pm

C:\Users\Jake>ping -n 24 http://www.exetel.com.au

Pinging http://www.exetel.com.au [220.233.0.9] with 32 bytes of data:
Reply from 220.233.0.9: bytes=32 time=24ms TTL=60
Reply from 220.233.0.9: bytes=32 time=26ms TTL=60
Reply from 220.233.0.9: bytes=32 time=22ms TTL=60
Reply from 220.233.0.9: bytes=32 time=23ms TTL=60
Reply from 220.233.0.9: bytes=32 time=24ms TTL=60
Reply from 220.233.0.9: bytes=32 time=27ms TTL=60
Reply from 220.233.0.9: bytes=32 time=21ms TTL=60
Reply from 220.233.0.9: bytes=32 time=25ms TTL=60
Reply from 220.233.0.9: bytes=32 time=23ms TTL=60
Reply from 220.233.0.9: bytes=32 time=23ms TTL=60
Reply from 220.233.0.9: bytes=32 time=22ms TTL=60
Reply from 220.233.0.9: bytes=32 time=39ms TTL=60
Reply from 220.233.0.9: bytes=32 time=30ms TTL=60
Reply from 220.233.0.9: bytes=32 time=23ms TTL=60
Reply from 220.233.0.9: bytes=32 time=23ms TTL=60
Reply from 220.233.0.9: bytes=32 time=21ms TTL=60
Reply from 220.233.0.9: bytes=32 time=23ms TTL=60
Reply from 220.233.0.9: bytes=32 time=22ms TTL=60
Reply from 220.233.0.9: bytes=32 time=23ms TTL=60
Reply from 220.233.0.9: bytes=32 time=24ms TTL=60
Reply from 220.233.0.9: bytes=32 time=24ms TTL=60
Reply from 220.233.0.9: bytes=32 time=22ms TTL=60
Reply from 220.233.0.9: bytes=32 time=22ms TTL=60
Reply from 220.233.0.9: bytes=32 time=23ms TTL=60

Ping statistics for 220.233.0.9:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 39ms, Average = 24ms

9.30pm

C:\Users\Jake>ping -n 24 http://www.exetel.com.au

Pinging http://www.exetel.com.au [220.233.0.9] with 32 bytes of data:
Reply from 220.233.0.9: bytes=32 time=25ms TTL=60
Reply from 220.233.0.9: bytes=32 time=25ms TTL=60
Reply from 220.233.0.9: bytes=32 time=27ms TTL=60
Reply from 220.233.0.9: bytes=32 time=25ms TTL=60
Reply from 220.233.0.9: bytes=32 time=24ms TTL=60
Reply from 220.233.0.9: bytes=32 time=24ms TTL=60
Reply from 220.233.0.9: bytes=32 time=38ms TTL=60
Reply from 220.233.0.9: bytes=32 time=23ms TTL=60
Reply from 220.233.0.9: bytes=32 time=37ms TTL=60
Reply from 220.233.0.9: bytes=32 time=29ms TTL=60
Reply from 220.233.0.9: bytes=32 time=26ms TTL=60
Reply from 220.233.0.9: bytes=32 time=24ms TTL=60
Reply from 220.233.0.9: bytes=32 time=25ms TTL=60
Reply from 220.233.0.9: bytes=32 time=36ms TTL=60
Reply from 220.233.0.9: bytes=32 time=31ms TTL=60
Reply from 220.233.0.9: bytes=32 time=61ms TTL=60
Reply from 220.233.0.9: bytes=32 time=23ms TTL=60
Reply from 220.233.0.9: bytes=32 time=26ms TTL=60
Reply from 220.233.0.9: bytes=32 time=29ms TTL=60
Reply from 220.233.0.9: bytes=32 time=28ms TTL=60
Reply from 220.233.0.9: bytes=32 time=45ms TTL=60
Reply from 220.233.0.9: bytes=32 time=24ms TTL=60
Reply from 220.233.0.9: bytes=32 time=24ms TTL=60
Reply from 220.233.0.9: bytes=32 time=39ms TTL=60

Ping statistics for 220.233.0.9:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 61ms, Average = 29ms

11pm

C:\Users\Jake>ping -n 24 http://www.exetel.com.au

Pinging http://www.exetel.com.au [220.233.0.9] with 32 bytes of data:
Reply from 220.233.0.9: bytes=32 time=18ms TTL=60
Reply from 220.233.0.9: bytes=32 time=18ms TTL=60
Reply from 220.233.0.9: bytes=32 time=19ms TTL=60
Reply from 220.233.0.9: bytes=32 time=21ms TTL=60
Reply from 220.233.0.9: bytes=32 time=18ms TTL=60
Reply from 220.233.0.9: bytes=32 time=18ms TTL=60
Reply from 220.233.0.9: bytes=32 time=20ms TTL=60
Reply from 220.233.0.9: bytes=32 time=20ms TTL=60
Reply from 220.233.0.9: bytes=32 time=20ms TTL=60
Reply from 220.233.0.9: bytes=32 time=19ms TTL=60
Reply from 220.233.0.9: bytes=32 time=18ms TTL=60
Reply from 220.233.0.9: bytes=32 time=19ms TTL=60
Reply from 220.233.0.9: bytes=32 time=18ms TTL=60
Reply from 220.233.0.9: bytes=32 time=18ms TTL=60
Reply from 220.233.0.9: bytes=32 time=19ms TTL=60
Reply from 220.233.0.9: bytes=32 time=22ms TTL=60
Reply from 220.233.0.9: bytes=32 time=19ms TTL=60
Reply from 220.233.0.9: bytes=32 time=19ms TTL=60
Reply from 220.233.0.9: bytes=32 time=19ms TTL=60
Reply from 220.233.0.9: bytes=32 time=19ms TTL=60
Reply from 220.233.0.9: bytes=32 time=18ms TTL=60
Reply from 220.233.0.9: bytes=32 time=18ms TTL=60
Reply from 220.233.0.9: bytes=32 time=20ms TTL=60
Reply from 220.233.0.9: bytes=32 time=18ms TTL=60

Ping statistics for 220.233.0.9:
Packets: Sent = 24, Received = 24, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 22ms, Average = 18ms

Post Reply