Jump to content

APAC/Oceanic/West Coast North America Players: Help Me Test Connectivity To Oceanic Server Locations

Started by Mike Forst, Jun 18 2015 09:57 AM

83 replies to this topic

#21 ShinVector

    Liao Mercenary

  • PipPipPipPipPipPipPipPipPip
  • The Hammer
  • The Hammer
  • 3,711 posts

Posted 18 June 2015 - 05:22 PM

Location: Singapore
ISP: M1

|------------------------------------------------------------------------------------------|
|									  WinMTR statistics								   |
|					   Host			  -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|							  10.0.0.138 -	0 |  193 |  193 |	0 |	0 |	2 |	0 |
|						   116.197.224.1 -	0 |  193 |  193 |	1 |   15 |  188 |   13 |
|						  202.65.245.129 -	0 |  193 |  193 |	3 |	5 |   21 |	4 |
|						  202.65.245.130 -	0 |  193 |  193 |	2 |	2 |   43 |	2 |
|							202.65.246.9 -	2 |  185 |  183 |	1 |	2 |   40 |	2 |
|						   202.65.246.37 -	0 |  193 |  193 |	2 |	9 |   62 |   11 |
|						   202.65.246.21 -	0 |  193 |  193 |	2 |	5 |   66 |	2 |
|						  202.79.197.178 -	0 |  193 |  193 |	2 |	2 |   41 |	7 |
|							 103.9.100.1 -	0 |  193 |  193 |	2 |	3 |   41 |	3 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider



|------------------------------------------------------------------------------------------|
|									  WinMTR statistics								   |
|					   Host			  -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|							  10.0.0.138 -	0 |  181 |  181 |	0 |	0 |	0 |	0 |
|						   116.197.224.1 -	0 |  181 |  181 |	2 |   15 |  171 |	2 |
|						  202.65.245.129 -	0 |  181 |  181 |	3 |	5 |  117 |	5 |
|						  202.65.245.130 -	0 |  181 |  181 |	2 |	3 |   46 |	2 |
|							202.65.246.9 -	1 |  177 |  176 |	2 |	6 |   82 |	3 |
|						   202.65.246.37 -	0 |  181 |  181 |	1 |	4 |   63 |	2 |
|						   202.65.246.21 -	0 |  181 |  181 |	2 |	4 |   36 |	2 |
|						  202.79.197.159 -	0 |  181 |  181 |	1 |	2 |   19 |	2 |
|						  203.175.175.53 -	0 |  181 |  181 |	3 |	4 |   20 |	3 |
|						 203.175.175.129 -	0 |  181 |  181 |	3 |	4 |	9 |	6 |
|						 203.175.175.203 -	0 |  181 |  181 |	3 |	3 |	5 |	3 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Edited by ShinVector, 18 June 2015 - 05:24 PM.

#22 Wizarth

    Member

  • Pip
  • Mercenary
  • 11 posts

Posted 18 June 2015 - 05:53 PM 

Ping statistics for 103.9.100.1:
Minimum = 309ms, Maximum = 313ms, Average = 310ms
Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  DSL-2870B [192.168.45.1]
  2    21 ms    21 ms    21 ms  10.20.21.188
  3    48 ms    33 ms    35 ms  syd-sot-ken-int1-be-10.tpgi.com.au [203.219.35.3]
  4   237 ms   235 ms   231 ms  ix-11-1-0-0.tcore2.TV2-Tokyo.as6453.net [116.0.88.21]
  5   295 ms   296 ms   294 ms  if-6-2.tcore1.SVW-Singapore.as6453.net [180.87.12.109]
  6   296 ms   295 ms   295 ms  if-2-2.tcore2.SVW-Singapore.as6453.net [180.87.12.2]
  7   296 ms   324 ms   294 ms  if-20-2.tcore1.SVQ-Singapore.as6453.net [180.87.96.21]
  8   308 ms   307 ms   309 ms  180.87.96.2
  9   308 ms   307 ms   307 ms  73.168.22.103.in-addr.arpa [103.22.168.73]
10   310 ms   309 ms   309 ms  tl1.sg.vodien.com [103.9.100.1]
(Dayum, that Sydney to Tokyo link)
Ping statistics for 203.175.175.203:
Minimum = 178ms, Maximum = 181ms, Average = 179ms
Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  DSL-2870B [192.168.45.1]
  2    21 ms    21 ms    20 ms  10.20.21.188
  3    30 ms    33 ms    30 ms  syd-gls-har-int2-be-10.tpgi.com.au [203.29.129.132]
  4   145 ms   144 ms   144 ms  sggs2-10G.hkix.net [123.255.90.102]
  5   167 ms   207 ms   170 ms  core-1.v30.hk1.sg.gs [124.6.32.21]
  6   178 ms   179 ms   180 ms  core-1.v53.sg3.sg.gs [103.14.244.100]
  7   186 ms   212 ms   203 ms  core-1.v41.sg1.sg.gs [203.175.175.129]
  8   189 ms   198 ms   179 ms  dns.sg.gs [203.175.175.203]
Geographic location: Melbourne, Australia
ISP: TPG


For reference, my current normal ping is 330ms

Edited by Wizarth, 18 June 2015 - 05:53 PM.

#23 Vezm

    Member

  • PipPipPipPipPip
  • Liquid Metal
  • Liquid Metal
  • 127 posts
  • LocationWellington

Posted 18 June 2015 - 06:11 PM

Wellington New Zealand
Vodafone Cable (Telstra network)

Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:
Spoiler



Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:
Spoiler


Pretty much the same as I get to the current game server.

#24 SixstringSamurai

    Member

  • PipPipPipPipPipPipPip
  • The 1 Percent
  • 930 posts
  • Twitch: Link
  • LocationYou Guys Are So Bad I'm Moving To The Moon

Posted 18 June 2015 - 06:36 PM

Testing from: Las Vegas, NV
Provider: Cox Cable

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=178ms TTL=56
Reply from 103.9.100.1: bytes=32 time=178ms TTL=56
Reply from 103.9.100.1: bytes=32 time=178ms TTL=56
Reply from 103.9.100.1: bytes=32 time=179ms TTL=56

Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
Minimum = 178ms, Maximum = 179ms, Average = 178ms


Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=308ms TTL=52
Reply from 203.175.175.203: bytes=32 time=323ms TTL=52
Reply from 203.175.175.203: bytes=32 time=333ms TTL=52
Reply from 203.175.175.203: bytes=32 time=310ms TTL=52

Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
Minimum = 308ms, Maximum = 333ms, Average = 318ms


Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 8 ms 7 ms 7 ms 100.127.0.144
4 14 ms 6 ms 7 ms 24-234-6-44.ptp.lvcm.net [24.234.6.44]
5 20 ms 20 ms 19 ms langbprj01-ae7.0.rd.la.cox.net [68.1.0.149]
6 13 ms 13 ms 13 ms 68.105.30.159
7 186 ms 179 ms 177 ms TenGE4-2.br02.sin02.pccwbtn.net [63.218.228.82]

8 178 ms 178 ms 177 ms TenGE4-2.br02.sin02.pccwbtn.net [63.218.228.82]

9 2453 ms 184 ms 185 ms 63-218-213-182.static.pccwglobal.net [63.218.213
.182]
10 184 ms 185 ms 186 ms 73.168.22.103.in-addr.arpa [103.22.168.73]
11 178 ms 179 ms 178 ms tl1.sg.vodien.com [103.9.100.1]

Trace complete.


Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 6 ms 7 ms 7 ms 100.127.0.146
4 7 ms 12 ms 7 ms 24-234-6-44.ptp.lvcm.net [24.234.6.44]
5 19 ms 7 ms 12 ms ae54.bar2.LasVegas1.Level3.net [205.129.18.109]

6 12 ms 13 ms 13 ms ae-2-70.edge1.LosAngeles6.Level3.net [4.69.144.8
0]
7 15 ms 14 ms 12 ms ae-2-70.edge1.LosAngeles6.Level3.net [4.69.144.8
0]
8 20 ms 24 ms 20 ms tata-level3-ae.losangeles6.level3.net [4.68.62.1
18]
9 12 ms 14 ms 13 ms if-2-2.tcore1.LVW-Los-Angeles.as6453.net [66.110
.59.1]
10 13 ms 12 ms 13 ms 63.243.197.2
11 1648 ms 36 ms 31 ms core-1.v30.lax1.sg.gs [124.6.40.21]
12 167 ms 172 ms 337 ms core-1.v54.hk1.sg.gs [103.14.244.102]
13 302 ms 311 ms 335 ms core-1.v52.sg3.sg.gs [103.14.244.98]
14 306 ms 299 ms 300 ms core-1.v41.sg1.sg.gs [203.175.175.129]
15 291 ms 298 ms 309 ms dns.sg.gs [203.175.175.203]

Trace complete.

#25 Potato Farmer

    Member

  • PipPipPip
  • The Jaws
  • The Jaws
  • 60 posts
  • LocationSingapore

Posted 18 June 2015 - 06:45 PM

Posted Image

Location: Singapore
ISP: StarHub
Connection: 100 Mbps Cable

#26 Past

    Member

  • PipPipPipPipPipPip
  • 254 posts
  • LocationWestern Australia

Posted 18 June 2015 - 07:06 PM

Location Bunbury Western Australia:
At work atm ISP is Highway1 but i believe it has been renamed Zettanet:

Ping to 103.9.100.1 came up as:
Reply from 103.9.100.1: bytes=32 time=148ms TTL=57
same result for all 12 pings i did.

Ping to 203.175.175.203 came up as
Reply from 203.175.175.203: bytes=32 time=70ms TTL=54
same result for all 12 pings i did.

I use Internode ISP at home ill do it again tonight for you with more detailed results so you can have 2 diff ISP's from the same location

Edited by Past, 18 June 2015 - 07:20 PM.

#27 cleghorn6

    Member

  • PipPipPipPipPipPipPip
  • The Patron Saint
  • The Patron Saint
  • 511 posts

Posted 18 June 2015 - 07:16 PM

Location: Perth, Australia
Service Provider: Westnet (iiNet)

==================================================================================
Ping statistics for 103.9.100.1:
Packets: Sent = 79, Received = 79, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 66ms, Maximum = 257ms, Average = 72ms


Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 17 ms 17 ms 17 ms lo0.bng2.per4.on.ii.net [150.101.32.66]
3 17 ms 17 ms 16 ms cr1.per4.on.ii.net [150.101.33.66]
4 18 ms 25 ms 17 ms ae0.cr1.per1.on.ii.net [150.101.34.171]
5 66 ms 65 ms 66 ms pos1-2-0.bdr1.sin1.on.ii.net [150.101.33.68]
6 81 ms 66 ms 66 ms eie1.eqx1.sg.vodien.com [202.79.197.178]
7 67 ms 69 ms 67 ms tl1.sg.vodien.com [103.9.100.1]

Trace complete.

=====================================================================================

Ping statistics for 203.175.175.203:
Packets: Sent = 63, Received = 63, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 68ms, Average = 65ms


Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.254
2 17 ms 17 ms 17 ms lo0.bng2.per4.on.ii.net [150.101.32.66]
3 17 ms 17 ms 17 ms cr1.per1.on.ii.net [150.101.33.42]
4 64 ms 64 ms 64 ms pos-0-3-1.bdr1.sin1.on.ii.net [150.101.33.176]
5 64 ms 65 ms 64 ms eqix-sg.sg.gs [202.79.197.159]
6 67 ms 65 ms 74 ms core-1.v30.sg3.sg.gs [203.175.175.53]
7 68 ms 66 ms 66 ms core-2.v41.sg1.sg.gs [203.175.175.130]
8 65 ms 65 ms 66 ms dns.sg.gs [203.175.175.203]

Trace complete.

=====================================================================================

WinMTR isn't resolving any of the intermediate steps for some reason so it's a simple trace route for you I'm afraid.

I'm actually getting excited about a sub-100 ping.

Edit: formatting

Edited by cleghorn6, 18 June 2015 - 07:19 PM.

#28 Dingo Battler

    Member

  • PipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 357 posts

Posted 18 June 2015 - 07:52 PM

Melbourne Australia:

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=182ms TTL=48
Reply from 103.9.100.1: bytes=32 time=197ms TTL=48
Reply from 103.9.100.1: bytes=32 time=179ms TTL=48
Reply from 103.9.100.1: bytes=32 time=178ms TTL=48

Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 178ms, Maximum = 197ms, Average = 184ms



Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=342ms TTL=45
Reply from 203.175.175.203: bytes=32 time=371ms TTL=45
Reply from 203.175.175.203: bytes=32 time=342ms TTL=45
Reply from 203.175.175.203: bytes=32 time=341ms TTL=45

Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 341ms, Maximum = 371ms, Average = 349ms

Edited by KBurn85, 18 June 2015 - 07:53 PM.

#29 cx5

    Member

  • PipPipPipPipPip
  • 136 posts
  • LocationHong Kong

Posted 18 June 2015 - 08:12 PM

From Hong Kong, network supplier may be HKBN (brand name) HQ/mother company name may be ctinets???

D:\>ping 103.9.100.1

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=65ms TTL=52
Reply from 103.9.100.1: bytes=32 time=42ms TTL=52
Reply from 103.9.100.1: bytes=32 time=40ms TTL=52
Reply from 103.9.100.1: bytes=32 time=44ms TTL=52

Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 65ms, Average = 47ms

D:\>tracert 103.9.100.1

Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms [IP_deleted]
2 <1 ms <1 ms <1 ms [IP_deleted].ctinets.com [IP_deleted]
3 5 ms 1 ms 1 ms [IP_deleted].ctinets.com [IP_deleted]
4 * * * Request timed out.
5 2 ms 2 ms 3 ms [IP_deleted].ctinets.com [IP_deleted]
6 6 ms 11 ms 9 ms [IP_deleted].ctinets.com [IP_deleted]
7 * 2 ms * [IP_deleted].ctinets.com [IP_deleted]
8 4 ms 3 ms 4 ms 21454.tmhstcar06.cu.telstraglobal.net [134.159.1
28.9]
9 39 ms 11 ms 4 ms ge9-9.br01.hkg05.pccwbtn.net[IP_deleted]
10 46 ms 41 ms 50 ms 63-218-144-253.static.pccwglobal.net [IP_deleted]
11 40 ms 40 ms 40 ms tenge0-4-0-2.cr03.sin02.pccwbtn.net [IP_deleted]
12 61 ms 40 ms 40 ms 73.168.22.103.in-addr.arpa [103.22.168.73]
13 41 ms 40 ms 41 ms tl1.sg.vodien.com [103.9.100.1]

Trace complete.

Original output with IP sent to your PM.

#30 cx5

    Member

  • PipPipPipPipPip
  • 136 posts
  • LocationHong Kong

Posted 18 June 2015 - 08:19 PM

2nd IP results, from Hong Kong again, same source starting point.


D:\>ping 203.175.175.203

Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=39ms TTL=54
Reply from 203.175.175.203: bytes=32 time=39ms TTL=54
Reply from 203.175.175.203: bytes=32 time=55ms TTL=54
Reply from 203.175.175.203: bytes=32 time=39ms TTL=54

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

D:\>tracert 203.175.175.203

Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms [color=#959595][IP_deleted][/color]
2 1 ms <1 ms <1 ms [color=#959595][IP_deleted][/color].ctinets.com [color=#959595][IP_deleted][/color]
3 4 ms 15 ms 1 ms [color=#959595][IP_deleted][/color].ctinets.com [color=#959595][IP_deleted][/color]
4 * * * Request timed out.
5 6 ms 8 ms 5 ms [color=#959595][IP_deleted][/color].ctinets.com [color=#959595][IP_deleted][/color]
6 206 ms 234 ms 246 ms [color=#959595][IP_deleted][/color].ctinets.com [color=#959595][IP_deleted][/color]
7 81 ms 156 ms 9 ms [color=#959595][IP_deleted][/color].ctinets.com [color=#959595][IP_deleted][/color]
8 41 ms 45 ms 48 ms 4657.hkg.equinix.com [119.27.63.54]
9 122 ms 40 ms 40 ms [color=#959595][IP_deleted][/color]
10 107 ms 86 ms 39 ms an-ats-loc11.starhub.net.sg [203.118.15.242]
11 39 ms 39 ms 39 ms starhub-sg.sg.gs [203.116.39.138]
12 40 ms 69 ms 108 ms core-2.v32.sg1.sg.gs [203.175.175.30]
13 41 ms 76 ms 81 ms dns.sg.gs [203.175.175.203]

Trace complete.

D:\>

Full sent to your PM.

#31 ShinVector

    Liao Mercenary

  • PipPipPipPipPipPipPipPipPip
  • The Hammer
  • The Hammer
  • 3,711 posts

Posted 18 June 2015 - 08:44 PM

View PostVezm, on 18 June 2015 - 06:11 PM, said:

Wellington New Zealand
Vodafone Cable (Telstra network)

Pretty much the same as I get to the current game server.


Oh no.. No wonder New Zealand is having issues...
You are really on the outer edge of APAC in the middle of nowhere and there is no undersea cable directly linking you guys to SEA.

http://www.submarinecablemap.com/

Posted Image

Edited by ShinVector, 18 June 2015 - 08:46 PM.

#32 slide

    Member

  • PipPipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 1,768 posts
  • LocationKersbrook South Australia

Posted 18 June 2015 - 09:12 PM

Location: Adelaide, South Australia
ISP: iiNet

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=97ms TTL=58
Reply from 103.9.100.1: bytes=32 time=97ms TTL=58
Reply from 103.9.100.1: bytes=32 time=96ms TTL=58
Reply from 103.9.100.1: bytes=32 time=96ms TTL=58

Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 96ms, Maximum = 97ms, Average = 96ms

Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms iConnectAccess621 [192.168.0.254]
2 16 ms 16 ms 16 ms lo0.bng1.adl6.on.ii.net [150.101.32.32]
3 15 ms 15 ms 16 ms ae7.cr1.adl2.on.ii.net [150.101.33.210]
4 97 ms 97 ms 96 ms ae2.cr1.per4.on.ii.net [150.101.33.39]
5 47 ms 47 ms 47 ms ae0.cr1.per1.on.ii.net [150.101.34.171]
6 95 ms 95 ms 95 ms pos1-2-0.bdr1.sin1.on.ii.net [150.101.33.68]
7 95 ms 95 ms 95 ms eie1.eqx1.sg.vodien.com [202.79.197.178]
8 97 ms 96 ms 96 ms tl1.sg.vodien.com [103.9.100.1]


Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=97ms TTL=55
Reply from 203.175.175.203: bytes=32 time=97ms TTL=55
Reply from 203.175.175.203: bytes=32 time=97ms TTL=55
Reply from 203.175.175.203: bytes=32 time=97ms TTL=55

Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 97ms, Maximum = 97ms, Average = 97ms


Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms iConnectAccess621 [192.168.0.254]
2 16 ms 16 ms 16 ms lo0.bng1.adl6.on.ii.net [150.101.32.32]
3 15 ms 16 ms 15 ms ae7.cr1.adl6.on.ii.net [150.101.33.208]
4 51 ms 50 ms 50 ms ae1.cr1.per1.on.ii.net [150.101.33.37]
5 97 ms 95 ms 96 ms po0-3-0.bdr1.sin1.on.ii.net [203.16.211.229]
6 96 ms 96 ms 96 ms eqix-sg.sg.gs [202.79.197.159]
7 97 ms 98 ms 96 ms core-1.v30.sg3.sg.gs [203.175.175.53]
8 98 ms 98 ms 98 ms core-2.v41.sg1.sg.gs [203.175.175.130]
9 97 ms 97 ms 97 ms dns.sg.gs [203.175.175.203]

Trace complete.

Location: Kersbrook,South Australia 50km NE of Adelaide
ISP: Dodo

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=157ms TTL=49
Reply from 103.9.100.1: bytes=32 time=156ms TTL=49
Reply from 103.9.100.1: bytes=32 time=157ms TTL=49
Reply from 103.9.100.1: bytes=32 time=157ms TTL=49

Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 156ms, Maximum = 157ms, Average = 156ms


Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms 192.168.0.1
2 32 ms 32 ms 31 ms 242.2.2.123.network.m2core.net.au [123.2.2.242]
3 32 ms 33 ms 31 ms be2-v424.bsr02.pmelnxd.vic.m2core.net.au [123.2.
2.129]
4 32 ms 32 ms 32 ms 119.225.19.221
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 156 ms 156 ms 156 ms 59.154.18.10
10 156 ms 155 ms 207 ms 203.208.131.125
11 155 ms 156 ms 156 ms 203.208.158.14
12 157 ms 161 ms 157 ms 203.208.190.38
13 156 ms 156 ms 155 ms 29.168.22.103.in-addr.arpa [103.22.168.29]
14 156 ms 156 ms 157 ms tl1.sg.vodien.com [103.9.100.1]

Trace complete.


Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=126ms TTL=47
Reply from 203.175.175.203: bytes=32 time=125ms TTL=47
Reply from 203.175.175.203: bytes=32 time=124ms TTL=47
Reply from 203.175.175.203: bytes=32 time=124ms TTL=47

Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 124ms, Maximum = 126ms, Average = 124ms



Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms 192.168.0.1
2 31 ms 31 ms 31 ms 242.2.2.123.network.m2core.net.au [123.2.2.242]
3 32 ms 32 ms 31 ms be2-v424.bsr02.pmelnxd.vic.m2core.net.au [123.2.2.129]
4 32 ms 32 ms 31 ms Bundle-Ether17.win17.melbourne.telstra.net [139.130.199.65]
5 34 ms 33 ms 34 ms bundle-ether12.win-core10.melbourne.telstra.net[203.50.11.111]
6 45 ms 47 ms 47 ms bundle-ether6.fli-core1.adelaide.telstra.net [203.50.11.90]
7 77 ms 75 ms 79 ms bundle-ether5.wel-core3.perth.telstra.net [203.50.11.19]
8 78 ms 78 ms 75 ms tengige0-8-0-5-1.pie-core1.perth.telstra.net [203.50.6.198]
9 75 ms 75 ms 75 ms gigabitethernet0-7-0-0.pthp-core01.perth.net.reach.com [203.50.13.246]
10 124 ms 126 ms 124 ms 202.84.143.181
11 127 ms 125 ms 127 ms 202.84.243.82
12 125 ms 124 ms 124 ms 203.116.5.157
13 124 ms 125 ms 124 ms 203.118.15.181
14 124 ms 124 ms 124 ms an-ats-loc11.starhub.net.sg [203.118.15.242]
15 124 ms 155 ms 124 ms starhub-sg.sg.gs [203.116.39.138]
16 125 ms 125 ms 125 ms core-2.v32.sg1.sg.gs [203.175.175.30]
17 124 ms 124 ms 124 ms dns.sg.gs [203.175.175.203]

Trace complete.

Optus still to come

Edited by slide, 19 June 2015 - 05:34 AM.

#33 Taelon Zero

    Member

  • PipPipPipPipPip
  • Fury
  • Fury
  • 123 posts
  • LocationNew Zealand

Posted 18 June 2015 - 09:26 PM

New Zealand
Spark


C:\Users\Taelon>ping 103.9.100.1

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=219ms TTL=48
Reply from 103.9.100.1: bytes=32 time=219ms TTL=48
Reply from 103.9.100.1: bytes=32 time=219ms TTL=48
Reply from 103.9.100.1: bytes=32 time=219ms TTL=48

Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 219ms, Maximum = 219ms, Average = 219ms

C:\Users\Taelon>tracert 103.9.100.1

Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 15 ms 5 ms 4 ms 122-58-236-1.jetstream.xtra.co.nz [122.58.236.1]
3 * * * Request timed out.
4 16 ms 16 ms 16 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 16 ms 16 ms 17 ms ae5-2.akbr7.global-gateway.net.nz [210.55.202.213]
6 40 ms 40 ms 40 ms xe0-0-1.sgbr3.global-gateway.net.nz [202.50.232.110]
7 40 ms 39 ms 39 ms ae2-10.sgbr4.global-gateway.net.nz [202.50.232.246]
8 40 ms 40 ms 40 ms ae-3.a04.sydnau03.au.ra.gin.ntt.net [103.13.80.125]
9 40 ms 40 ms 40 ms ae-3.r05.sydnau01.au.bb.gin.ntt.net [202.68.64.124]
10 152 ms 153 ms 155 ms ae-8.r20.tokyjp05.jp.bb.gin.ntt.net [129.250.3.76]
11 153 ms 153 ms 153 ms ae-15.r01.tokyjp01.jp.bb.gin.ntt.net [129.250.4.91]
12 218 ms 218 ms 219 ms 61.213.145.202
13 219 ms 219 ms 219 ms 203.118.15.181
14 218 ms 218 ms 218 ms an-ats-int11.starhub.net.sg [203.118.15.114]
15 219 ms 218 ms 218 ms sh2.eqx1.sg.vodien.com [203.116.246.18]
16 219 ms 219 ms 221 ms tl1.sg.vodien.com [103.9.100.1]

Trace complete.

C:\Users\Taelon>ping 203.175.175.203

Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=221ms TTL=45
Reply from 203.175.175.203: bytes=32 time=220ms TTL=45
Reply from 203.175.175.203: bytes=32 time=220ms TTL=45
Reply from 203.175.175.203: bytes=32 time=220ms TTL=45

Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 220ms, Maximum = 221ms, Average = 220ms

C:\Users\Taelon>tracert 203.175.175.203

Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 5 ms 5 ms 5 ms 122-58-236-1.jetstream.xtra.co.nz [122.58.236.1]
3 * * * Request timed out.
4 16 ms 16 ms 16 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 16 ms 16 ms 16 ms ae5-2.akbr7.global-gateway.net.nz [210.55.202.213]
6 40 ms 41 ms 40 ms xe7-0-2.sgbr3.global-gateway.net.nz [202.50.232.10]
7 40 ms 40 ms 40 ms ae2-10.sgbr4.global-gateway.net.nz [202.50.232.246]
8 40 ms 40 ms 40 ms ae-3.a04.sydnau03.au.ra.gin.ntt.net [103.13.80.125]
9 40 ms 40 ms 40 ms ae-3.r05.sydnau01.au.bb.gin.ntt.net [202.68.64.124]
10 153 ms 153 ms 153 ms ae-8.r20.tokyjp05.jp.bb.gin.ntt.net [129.250.3.76]
11 154 ms 154 ms 154 ms ae-19.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.6.209]
12 221 ms 226 ms 220 ms ae-3.r21.sngpsi05.sg.bb.gin.ntt.net [129.250.7.35]
13 237 ms 220 ms 221 ms xe-4-1-0.r00.sngpsi03.sg.bb.gin.ntt.net [129.250.6.123]
14 222 ms 222 ms 222 ms ntt-sg.sg.gs [116.51.23.66]
15 222 ms 222 ms 226 ms core-1.v31.sg1.sg.gs [203.175.175.21]
16 220 ms 220 ms 220 ms dns.sg.gs [203.175.175.203]

Trace complete.

#34 K O N D O

    Member

  • PipPipPip
  • CS 2020 Silver Champ
  • CS 2020 Silver Champ
  • 50 posts

Posted 18 June 2015 - 09:40 PM

Location: Toowoomba, QLD, Australia
ISP: Telstra

--------------------------------------------------------------------------------
Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=152ms TTL=47
Reply from 103.9.100.1: bytes=32 time=151ms TTL=47
Reply from 103.9.100.1: bytes=32 time=152ms TTL=47
Reply from 103.9.100.1: bytes=32 time=152ms TTL=47

Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 151ms, Maximum = 152ms, Average = 151ms

Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.16.1.1
2 30 ms 30 ms 29 ms 172.18.212.13
3 30 ms 31 ms 31 ms 172.18.69.149
4 31 ms 30 ms 31 ms bundle-ether4.cha-edge901.brisbane.telstra.net [203.50.44.40]
5 34 ms 31 ms 31 ms bundle-ether6.cha-core4.brisbane.telstra.net [203.50.11.140]
6 45 ms 46 ms 45 ms bundle-ether11.ken-core10.sydney.telstra.net [203.50.11.72]
7 58 ms 59 ms 58 ms bundle-ether12.win-core10.melbourne.telstra.net[203.50.11.123]
8 72 ms 70 ms 71 ms bundle-ether6.fli-core1.adelaide.telstra.net [203.50.11.90]
9 102 ms 103 ms 103 ms bundle-ether5.wel-core3.perth.telstra.net [203.50.11.19]
10 105 ms 103 ms 103 ms tengige0-8-0-5-1.pie-core1.perth.telstra.net [203.50.6.198]
11 101 ms 101 ms 100 ms tengige0-5-1-0.pthp-core01.perth.net.reach.com [203.50.13.254]
12 152 ms 151 ms 151 ms 202.84.143.181
13 154 ms 154 ms 151 ms 202.84.243.82
14 149 ms 149 ms 151 ms 203.116.5.157
15 150 ms 151 ms 151 ms 203.118.15.186
16 150 ms 150 ms 150 ms an-ats-int11.starhub.net.sg [203.118.15.110]
17 151 ms 151 ms 151 ms sh2.eqx1.sg.vodien.com [203.116.246.18]
18 152 ms 151 ms 151 ms tl1.sg.vodien.com [103.9.100.1]
Trace complete.
----------------------------------------------------------------------------------------------


Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=230ms TTL=46
Reply from 203.175.175.203: bytes=32 time=271ms TTL=46
Reply from 203.175.175.203: bytes=32 time=200ms TTL=46
Reply from 203.175.175.203: bytes=32 time=250ms TTL=46

Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 200ms, Maximum = 271ms, Average = 237ms


Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.16.1.1
2 104 ms 83 ms 97 ms 172.18.212.13
3 99 ms 105 ms 95 ms 172.18.69.145
4 79 ms 101 ms 91 ms bundle-ether4.cha-edge901.brisbane.telstra.net [203.50.44.40]
5 113 ms 74 ms 83 ms bundle-ether6.cha-core4.brisbane.telstra.net [203.50.11.140]
6 132 ms 105 ms 120 ms bundle-ether11.ken-core10.sydney.telstra.net [203.50.11.72]
7 87 ms 77 ms 131 ms bundle-ether12.win-core10.melbourne.telstra.net[203.50.11.123]
8 87 ms 153 ms 98 ms bundle-ether6.fli-core1.adelaide.telstra.net [203.50.11.90]
9 138 ms 120 ms 165 ms bundle-ether5.wel-core3.perth.telstra.net [203.50.11.19]
10 176 ms 148 ms 196 ms tengige0-8-0-5-1.pie-core1.perth.telstra.net [203.50.6.198]
11 130 ms 188 ms 108 ms tengige0-0-1-0.pthp-core01.perth.net.reach.com [203.50.13.250]
12 164 ms 225 ms 190 ms 202.84.143.94
13 227 ms 205 ms 253 ms 202.84.243.82
14 207 ms 202 ms 226 ms 203.116.5.157
15 173 ms 153 ms 225 ms 203.118.15.181
16 181 ms 271 ms 170 ms an-ats-loc11.starhub.net.sg [203.118.15.242]
17 165 ms 225 ms 151 ms starhub-sg.sg.gs [203.116.39.138]
18 154 ms 264 ms 302 ms core-2.v32.sg1.sg.gs [203.175.175.30]
19 263 ms 259 ms 201 ms dns.sg.gs [203.175.175.203]

Trace complete.
----------------------------------------------------------------------------------

#35 Vorgen

    Member

  • Pip
  • Legendary Founder
  • Legendary Founder
  • 11 posts

Posted 18 June 2015 - 10:03 PM

My location: Seoul, South Korea
My ISP: Korea Telecom
PING 103.9.100.1 (103.9.100.1) 56(84) bytes of data.
64 bytes from 103.9.100.1: icmp_seq=1 ttl=54 time=99.8 ms
64 bytes from 103.9.100.1: icmp_seq=2 ttl=54 time=99.4 ms
64 bytes from 103.9.100.1: icmp_seq=3 ttl=54 time=97.9 ms
64 bytes from 103.9.100.1: icmp_seq=4 ttl=54 time=99.7 ms
64 bytes from 103.9.100.1: icmp_seq=5 ttl=54 time=97.7 ms
64 bytes from 103.9.100.1: icmp_seq=6 ttl=54 time=98.4 ms
64 bytes from 103.9.100.1: icmp_seq=7 ttl=54 time=98.9 ms
64 bytes from 103.9.100.1: icmp_seq=8 ttl=54 time=100 ms
64 bytes from 103.9.100.1: icmp_seq=9 ttl=54 time=98.7 ms
64 bytes from 103.9.100.1: icmp_seq=10 ttl=54 time=100 ms
^C
--- 103.9.100.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8998ms
rtt min/avg/max/mdev = 97.750/99.124/100.243/0.869 ms


traceroute to 103.9.100.1 (103.9.100.1), 30 hops max, 60 byte packets
1  192.168.1.1 (192.168.1.1)  0.255 ms  0.311 ms  0.365 ms
2  * * *
3  61.78.42.165 (61.78.42.165)  2.756 ms  2.773 ms  2.767 ms
4  112.189.29.69 (112.189.29.69)  12.416 ms  12.432 ms 112.189.28.69 (112.189.28.69)  12.497 ms
5  112.174.57.233 (112.174.57.233)  4.677 ms 112.174.17.249 (112.174.17.249)  5.144 ms 112.174.57.249 (112.174.57.249)  5.854 ms
6  112.174.8.86 (112.174.8.86)  2.755 ms 112.174.48.166 (112.174.48.166)  1.235 ms 112.174.8.202 (112.174.8.202)  1.688 ms
7  112.174.83.126 (112.174.83.126)  1.993 ms 112.174.84.238 (112.174.84.238)  1.438 ms 112.174.83.126 (112.174.83.126)  1.779 ms
8  121.189.3.122 (121.189.3.122)  31.691 ms  31.562 ms  31.076 ms
9  TenGE8-5.br02.sin02.pccwbtn.net (63.218.228.154)  96.999 ms TenGE4-2.br02.sin02.pccwbtn.net (63.218.228.82)  97.309 ms  97.541 ms
10  63-218-213-182.static.pccwglobal.net (63.218.213.182)  97.836 ms  98.315 ms 73.168.22.103.in-addr.arpa (103.22.168.73)  97.655 ms
11  73.168.22.103.in-addr.arpa (103.22.168.73)  97.396 ms *  98.151 ms
12  * * *
(more asterisks until 30 hops)


PING 203.175.175.203 (203.175.175.203) 56(84) bytes of data.
64 bytes from 203.175.175.203: icmp_seq=1 ttl=50 time=107 ms
64 bytes from 203.175.175.203: icmp_seq=2 ttl=50 time=110 ms
64 bytes from 203.175.175.203: icmp_seq=3 ttl=50 time=108 ms
64 bytes from 203.175.175.203: icmp_seq=4 ttl=50 time=107 ms
64 bytes from 203.175.175.203: icmp_seq=5 ttl=50 time=108 ms
64 bytes from 203.175.175.203: icmp_seq=6 ttl=50 time=108 ms
64 bytes from 203.175.175.203: icmp_seq=7 ttl=50 time=109 ms
64 bytes from 203.175.175.203: icmp_seq=8 ttl=50 time=109 ms
64 bytes from 203.175.175.203: icmp_seq=9 ttl=50 time=108 ms
64 bytes from 203.175.175.203: icmp_seq=10 ttl=50 time=108 ms
^C
--- 203.175.175.203 ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 11007ms
rtt min/avg/max/mdev = 107.351/109.045/112.114/1.277 ms


traceroute to 203.175.175.203 (203.175.175.203), 30 hops max, 60 byte packets
1  192.168.1.1 (192.168.1.1)  1.623 ms  1.693 ms  1.779 ms
2  * * *
3  61.78.42.165 (61.78.42.165)  7.279 ms  7.263 ms  7.269 ms
4  112.189.29.69 (112.189.29.69)  7.345 ms  7.432 ms 112.189.28.161 (112.189.28.161)  12.219 ms
5  112.174.17.253 (112.174.17.253)  6.992 ms 112.174.57.253 (112.174.57.253)  7.205 ms 112.174.58.13 (112.174.58.13)  7.391 ms
6  112.174.8.6 (112.174.8.6)  10.276 ms 112.174.48.46 (112.174.48.46)  2.631 ms 112.174.48.166 (112.174.48.166)  2.436 ms
7  112.174.83.54 (112.174.83.54)  2.573 ms 112.174.84.54 (112.174.84.54)  2.624 ms 112.174.83.222 (112.174.83.222)  2.494 ms
8  121.189.3.62 (121.189.3.62)  32.972 ms  32.876 ms  32.895 ms
9  ae-19.r24.tokyjp05.jp.bb.gin.ntt.net (129.250.6.209)  40.501 ms  40.324 ms  40.471 ms
10  ae-3.r21.sngpsi05.sg.bb.gin.ntt.net (129.250.7.35)  101.920 ms  101.969 ms  102.836 ms
11  xe-4-1-0.r00.sngpsi03.sg.bb.gin.ntt.net (129.250.6.123)  150.734 ms  150.806 ms  150.715 ms
12  ntt-sg.sg.gs (116.51.23.66)  113.058 ms  109.295 ms  109.318 ms
13  core-1.v31.sg1.sg.gs (203.175.175.21)  110.122 ms  102.739 ms  109.038 ms
14  dns.sg.gs (203.175.175.203)  110.282 ms  102.615 ms  110.455 ms

#36 Romalb

    Rookie

  • The Patron Saint
  • The Patron Saint
  • 7 posts
  • LocationSydney, Australia

Posted 18 June 2015 - 10:39 PM

Location: Sydney
Telstra Cable

Pinging 103.9.100.1 with 64 bytes of data:[Complete]
Reply from 103.9.100.1: bytes = 64, time = 110 ms
Reply from 103.9.100.1: bytes = 64, time = 110 ms
Reply from 103.9.100.1: bytes = 64, time = 110 ms
3/3 replies received.
min time=110 ms, max time=110 ms, avg time=110
ms

Pinging 203.175.175.203 with 64 bytes of data:[Complete]
Reply from 203.175.175.203: bytes = 64, time = 120 ms
Reply from 203.175.175.203: bytes = 64, time = 120 ms
Reply from 203.175.175.203: bytes = 64, time = 120 ms
3/3 replies received.
min time=110 ms, max time=130 ms, avg time=120
ms

#37 Funkin Disher

    Member

  • PipPipPipPipPipPipPip
  • The Raider
  • The Raider
  • 590 posts
  • LocationPPC Apocalypse Bunker, Sydney

Posted 19 June 2015 - 12:10 AM

Location: Sydney, Australia
Provider: TPG (ADSL)

103.9.100.1
Spoiler


203.175.175.203
Spoiler


Pumped for a ping lower than 300!

Edited by Kane0, 19 June 2015 - 12:13 AM.

#38 FAX MACHINE

    Member

  • Pip
  • 15 posts

Posted 19 June 2015 - 12:42 AM

Location: Darwin, Northern Territory
ISP: iiNet

ping 103.9.100.1

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=125ms TTL=58
Reply from 103.9.100.1: bytes=32 time=125ms TTL=58
Reply from 103.9.100.1: bytes=32 time=126ms TTL=58
Reply from 103.9.100.1: bytes=32 time=127ms TTL=58

Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 125ms, Maximum = 127ms, Average = 125ms

ping 103.9.100.1

Pinging 103.9.100.1 with 32 bytes of data:
Reply from 103.9.100.1: bytes=32 time=128ms TTL=58
Reply from 103.9.100.1: bytes=32 time=126ms TTL=58
Reply from 103.9.100.1: bytes=32 time=127ms TTL=58
Reply from 103.9.100.1: bytes=32 time=126ms TTL=58

Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 126ms, Maximum = 128ms, Average = 126ms

Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 49 ms 51 ms 50 ms lo0.bng1.adl2.on.ii.net [150.101.32.31]
3 49 ms 51 ms 52 ms ae8.cr1.adl2.on.ii.net [150.101.33.212]
4 131 ms 131 ms 131 ms ae2.cr1.per4.on.ii.net [150.101.33.39]
5 109 ms 81 ms 79 ms ae0.cr1.per1.on.ii.net [150.101.34.171]
6 126 ms 127 ms 126 ms pos-0-3-1.bdr1.sin1.on.ii.net [150.101.33.176]
7 127 ms 127 ms 128 ms eie1.eqx1.sg.vodien.com [202.79.197.178]
8 128 ms 128 ms 171 ms tl1.sg.vodien.com [103.9.100.1]

Trace complete.


Tracing route to tl1.sg.vodien.com [103.9.100.1]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 51 ms 101 ms 50 ms lo0.bng1.adl2.on.ii.net [150.101.32.31]
3 50 ms 50 ms 49 ms ae8.cr1.adl2.on.ii.net [150.101.33.212]
4 129 ms 129 ms 128 ms ae2.cr1.per4.on.ii.net [150.101.33.39]
5 80 ms 82 ms 80 ms ae0.cr1.per1.on.ii.net [150.101.34.171]
6 127 ms 127 ms 127 ms pos-0-3-1.bdr1.sin1.on.ii.net [150.101.33.176]
7 129 ms 129 ms 139 ms eie1.eqx1.sg.vodien.com [202.79.197.178]
8 131 ms 131 ms 128 ms tl1.sg.vodien.com [103.9.100.1]

Trace complete.


ping 203.175.175.203

Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=130ms TTL=55
Reply from 203.175.175.203: bytes=32 time=131ms TTL=55
Reply from 203.175.175.203: bytes=32 time=131ms TTL=55
Reply from 203.175.175.203: bytes=32 time=130ms TTL=55

Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 130ms, Maximum = 131ms, Average = 130ms

ping 203.175.175.203

Pinging 203.175.175.203 with 32 bytes of data:
Reply from 203.175.175.203: bytes=32 time=131ms TTL=55
Reply from 203.175.175.203: bytes=32 time=131ms TTL=55
Reply from 203.175.175.203: bytes=32 time=132ms TTL=55
Reply from 203.175.175.203: bytes=32 time=131ms TTL=55

Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 131ms, Maximum = 132ms, Average = 131ms

Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 49 ms 49 ms 48 ms lo0.bng1.adl2.on.ii.net [150.101.32.31]
3 50 ms 51 ms 48 ms ae8.cr1.adl2.on.ii.net [150.101.33.212]
4 129 ms 131 ms 130 ms ae0.cr1.adl6.on.ii.net [150.101.33.3]
5 82 ms 82 ms 83 ms ae1.cr1.per1.on.ii.net [150.101.33.37]
6 131 ms 131 ms 132 ms pos1-2-0.bdr1.sin1.on.ii.net [150.101.33.68]
7 132 ms 132 ms 132 ms eqix-sg.sg.gs [202.79.197.159]
8 133 ms 132 ms 132 ms core-1.v30.sg3.sg.gs [203.175.175.53]
9 134 ms 134 ms 134 ms core-2.v41.sg1.sg.gs [203.175.175.130]
10 132 ms 131 ms 134 ms dns.sg.gs [203.175.175.203]

Trace complete.


Tracing route to dns.sg.gs [203.175.175.203]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 51 ms 50 ms 50 ms lo0.bng1.adl2.on.ii.net [150.101.32.31]
3 50 ms 49 ms 48 ms ae8.cr1.adl2.on.ii.net [150.101.33.212]
4 131 ms 130 ms 130 ms ae0.cr1.adl6.on.ii.net [150.101.33.3]
5 83 ms 83 ms 82 ms ae1.cr1.per1.on.ii.net [150.101.33.37]
6 131 ms 132 ms 131 ms pos1-2-0.bdr1.sin1.on.ii.net [150.101.33.68]
7 131 ms 131 ms 133 ms eqix-sg.sg.gs [202.79.197.159]
8 132 ms 133 ms 133 ms core-1.v30.sg3.sg.gs [203.175.175.53]
9 135 ms 133 ms 133 ms core-2.v41.sg1.sg.gs [203.175.175.130]
10 133 ms 132 ms 133 ms dns.sg.gs [203.175.175.203]

Trace complete.

1st one seems better for me :-)

Edited by FAX MACHINE, 19 June 2015 - 02:21 AM.

#39 Aceramic

    Member

  • PipPipPipPipPip
  • The Scythe
  • The Scythe
  • 110 posts

Posted 19 June 2015 - 12:42 AM

I would, but my ISP is currently Cogent (10Gb fiber). I suspect that's not really the intent of the test, so I'll try to remember to run it when I get home. >.>

(And no, I can't play MWO on it. And no, you can't have it.)

#40 Barakus

    Member

  • PipPipPipPipPip
  • Bad Company
  • Bad Company
  • 105 posts

Posted 19 June 2015 - 12:59 AM

Sydney Australia Friday 7 PM local time
ISP Optus

Ping statistics for 103.9.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 153ms, Maximum = 155ms, Average = 153ms

Ping statistics for 203.175.175.203:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 154ms, Maximum = 168ms, Average = 158ms

Tracing route to tl1.sg.vodien.com [103.9.100.1]
1 22 ms 10 ms 11 ms 10.72.0.1
2 * * * Request timed out.
3 10 ms 13 ms 9 ms 211.29.126.129
4 10 ms 10 ms 9 ms 198.142.139.112
5 23 ms 11 ms 11 ms 198.142.139.128
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 168 ms 170 ms 166 ms tg0-1-0-3.ig11.optus.net.au [202.139.19.33]
10 252 ms 251 ms 249 ms 203.208.131.125
11 249 ms 244 ms 246 ms 203.208.158.18
12 154 ms 153 ms 155 ms 203.208.190.38
13 157 ms 152 ms 153 ms 29.168.22.103.in-addr.arpa [103.22.168.29]
14 154 ms 156 ms 153 ms tl1.sg.vodien.com [103.9.100.1]
Trace complete.

Tracing route to dns.sg.gs [203.175.175.203]
1 11 ms 13 ms 8 ms 10.72.0.1
2 * * * Request timed out.
3 7 ms 12 ms 10 ms 211.29.126.117
4 12 ms 12 ms 10 ms 198.142.139.112
5 23 ms 11 ms 11 ms 198.142.139.128
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 167 ms 172 ms 167 ms tg0-1-0-3.ig11.optus.net.au [202.139.19.33]
10 251 ms 273 ms 252 ms 203.208.131.125
11 243 ms 240 ms 243 ms 203.208.158.14
12 247 ms 246 ms 254 ms 203.208.186.102
13 253 ms 254 ms 255 ms 180.87.97.162
14 267 ms 262 ms 255 ms core-1.v30.sg3.sg.gs [203.175.175.53]
15 161 ms 160 ms 163 ms core-1.v41.sg1.sg.gs [203.175.175.129]
16 164 ms 162 ms 162 ms dns.sg.gs [203.175.175.203]
Trace complete.
Back to Developer Outreach · Next Unread Topic →


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users