Hi,

I have a bunch of IPs which I need you to help me ping and traceroute.

The IPs are: 202.136.4.213 and 210.193.6.182 and 203.124.126.12

Please paste your ping summaries and traceroute reports here. Thanks!

C:\WINDOWS>tracert 202.136.4.213

Bezig met volgen van route naar 202.136.4.213 voor maximaal 30 hops

1 28 ms 20 ms 20 ms 1.70-200-80.adsl.skynet.be [80.200.70.1]
2 19 ms 20 ms 20 ms 233.255-136-217.adsl-fix.skynet.be [217.136.255.
233]
3 28 ms 19 ms 20 ms ae0-0.intlbnc3.skynet.be [194.78.0.42]
4 28 ms 20 ms 20 ms gigabitethernet8-1.hsa2.Brussels1.Level3.net [21
2.3.234.177]
5 19 ms 20 ms 20 ms so-4-0-0.mp2.Brussels1.Level3.net [212.3.239.165
]
6 25 ms 29 ms 29 ms so-1-0-0.mp1.London2.Level3.net [212.187.128.49]

7 97 ms 99 ms 99 ms so-1-0-0.bbr1.Washington1.level3.net [212.187.12
8.138]
8 187 ms 180 ms 179 ms so-0-0-0.mp1.SanJose1.level3.net [64.159.1.133]

9 184 ms 179 ms 179 ms so-7-0-0.gar3.SanJose1.Level3.net [209.247.14.2]

10 188 ms 194 ms 187 ms 65.57.244.2
11 183 ms 182 ms 180 ms p6-1.plapx-cr1.ix.singtel.com [203.208.172.45]
12 288 ms 290 ms 289 ms p6-4.sngtp-cr2.ix.singtel.com [203.208.172.1]
13 287 ms 289 ms 290 ms 202.160.250.134
14 358 ms 390 ms 379 ms 203.208.145.94
15 409 ms 420 ms 390 ms 202.56.129.12
16 361 ms 360 ms 360 ms 202.136.4.213

8 187 ms 180 ms 179 ms so-0-0-0.mp1.SanJose1.level3.net [64.159.1.133]

9 184 ms 179 ms 179 ms so-7-0-0.gar3.SanJose1.Level3.net [209.247.14.2]

10 188 ms 194 ms 187 ms 65.57.244.2
11 183 ms 182 ms 180 ms p6-1.plapx-cr1.ix.singtel.com [203.208.172.45]
12 288 ms 290 ms 289 ms p6-4.sngtp-cr2.ix.singtel.com [203.208.172.1]
13 287 ms 289 ms 290 ms 202.160.250.134
14 358 ms 390 ms 379 ms 203.208.145.94
15 409 ms 420 ms 390 ms 202.56.129.12
16 361 ms 360 ms 360 ms 202.136.4.213

trace voltooid.

C:\WINDOWS>tracert 202.136.4.213

--

C:\WINDOWS>tracert 202.136.4.213 ping
Kan naam van doelsysteem 202.136.4.213 niet converteren.

C:\WINDOWS>ping 202.136.4.213

Pingen naar 202.136.4.213 met 32 byte gegevens:

Antwoord van 202.136.4.213: bytes=32 time=377ms TTL=240
Antwoord van 202.136.4.213: bytes=32 time=361ms TTL=240
Antwoord van 202.136.4.213: bytes=32 time=359ms TTL=240
Antwoord van 202.136.4.213: bytes=32 time=358ms TTL=240

Pingstatistieken voor 202.136.4.213:
Packets: verzonden = 4, ontvangen = 4, kwijtgeraakt = 0 (0% verlies),
Retourtijd bij benadering in milliseconden:
Minimum = 358ms, Maximum = 377ms, Gemiddeld = 363ms

C:\WINDOWS>

-----------------------------------------------
-----------------------------------------------

C:\WINDOWS>tracert 210.193.6.182

Bezig met volgen van route naar 210.193.6.182 voor maximaal 30 hops

1 21 ms 19 ms 19 ms 1.70-200-80.adsl.skynet.be [80.200.70.1]
2 27 ms 30 ms 30 ms 209.255-136-217.adsl-fix.skynet.be [217.136.255.
209]
3 32 ms 19 ms 20 ms ae1-0.intlbnc3.skynet.be [194.78.0.142]
4 29 ms 20 ms 20 ms gigabitethernet8-1.hsa2.Brussels1.Level3.net [21
2.3.234.177]
5 24 ms 20 ms 20 ms unknown.Level3.net [212.3.239.161]
6 31 ms 30 ms 30 ms so-3-0-0.mp1.Amsterdam1.Level3.net [212.187.128.
14]
7 28 ms 30 ms 30 ms gige1-0.core1.Amsterdam1.Level3.net [213.244.165
.13]
8 27 ms 30 ms 30 ms GBLX-Level3.level3.net [213.244.165.238]
9 29 ms 30 ms 30 ms so4-0-0-2488M.cr2.AMS2.gblx.net [67.17.65.241]
10 308 ms 310 ms 310 ms so1-2-1-155M.cr2.HKG1.gblx.net [203.192.134.141]

11 384 ms 377 ms 389 ms pos1-0-0-155M.ar2.SIN1.gblx.net [203.192.163.85]

12 371 ms 369 ms 370 ms 203.192.168.138
13 368 ms 362 ms 369 ms alpha002.qala.com.sg [210.193.2.2]
14 371 ms 369 ms 368 ms 210.193.6.182

Trace voltooid.

C:\WINDOWS>


--

C:\WINDOWS>ping 210.193.6.182

Pingen naar 210.193.6.182 met 32 byte gegevens:

Antwoord van 210.193.6.182: bytes=32 time=372ms TTL=51
Antwoord van 210.193.6.182: bytes=32 time=370ms TTL=51
Antwoord van 210.193.6.182: bytes=32 time=369ms TTL=51
Antwoord van 210.193.6.182: bytes=32 time=368ms TTL=51

Pingstatistieken voor 210.193.6.182:
Packets: verzonden = 4, ontvangen = 4, kwijtgeraakt = 0 (0% verlies),
Retourtijd bij benadering in milliseconden:
Minimum = 368ms, Maximum = 372ms, Gemiddeld = 369ms

C:\WINDOWS>

-----------------------------------------------
-----------------------------------------------


C:\WINDOWS>tracert 203.124.126.12

Bezig met volgen van route naar 203.124.126.12 voor maximaal 30 hops

1 27 ms 19 ms 19 ms 1.70-200-80.adsl.skynet.be [80.200.70.1]
2 27 ms 19 ms 19 ms at-0-0-0-47.adsl1.02bnc.skynet.be [194.78.255.69
]
3 27 ms 19 ms 19 ms ae1-0.intlbnc3.skynet.be [194.78.0.142]
4 27 ms 29 ms 19 ms unknown.Level3.net [212.3.234.61]
5 27 ms 19 ms 29 ms so-4-0-0.mp2.Brussels1.Level3.net [212.3.239.165
]
6 27 ms 29 ms 29 ms so-1-0-0.mp1.London2.Level3.net [212.187.128.49]

7 107 ms 99 ms 99 ms so-1-0-0.bbr1.Washington1.level3.net [212.187.12
8.138]
8 187 ms 179 ms 179 ms so-0-0-0.mp1.SanJose1.level3.net [64.159.1.133]

9 187 ms 189 ms 189 ms so-7-0-0.gar3.SanJose1.Level3.net [209.247.14.2]

10 187 ms 189 ms 189 ms 65.57.244.2
11 187 ms 189 ms 189 ms 203.208.182.21
12 308 ms 299 ms 300 ms 203.208.182.129
13 308 ms 299 ms 299 ms 202.160.250.226
C:\WINDOWS>tracert 203.124.126.12

Bezig met volgen van route naar 203.124.126.12 voor maximaal 30 hops

1 27 ms 19 ms 19 ms 1.70-200-80.adsl.skynet.be [80.200.70.1]
2 27 ms 19 ms 19 ms at-0-0-0-47.adsl1.02bnc.skynet.be [194.78.255.69
]
3 27 ms 19 ms 19 ms ae1-0.intlbnc3.skynet.be [194.78.0.142]
4 27 ms 29 ms 19 ms unknown.Level3.net [212.3.234.61]
5 27 ms 19 ms 29 ms so-4-0-0.mp2.Brussels1.Level3.net [212.3.239.165
]
6 27 ms 29 ms 29 ms so-1-0-0.mp1.London2.Level3.net [212.187.128.49]

7 107 ms 99 ms 99 ms so-1-0-0.bbr1.Washington1.level3.net [212.187.12
8.138]
8 187 ms 179 ms 179 ms so-0-0-0.mp1.SanJose1.level3.net [64.159.1.133]

9 187 ms 189 ms 189 ms so-7-0-0.gar3.SanJose1.Level3.net [209.247.14.2]

10 187 ms 189 ms 189 ms 65.57.244.2
11 187 ms 189 ms 189 ms 203.208.182.21
12 308 ms 299 ms 300 ms 203.208.182.129
13 308 ms 299 ms 299 ms 202.160.250.226
C:\WINDOWS>tracert 203.124.126.12

Bezig met volgen van route naar 203.124.126.12 voor maximaal 30 hops

1 27 ms 19 ms 19 ms 1.70-200-80.adsl.skynet.be [80.200.70.1]
2 27 ms 19 ms 19 ms at-0-0-0-47.adsl1.02bnc.skynet.be [194.78.255.69
]
3 27 ms 19 ms 19 ms ae1-0.intlbnc3.skynet.be [194.78.0.142]
4 27 ms 29 ms 19 ms unknown.Level3.net [212.3.234.61]
5 27 ms 19 ms 29 ms so-4-0-0.mp2.Brussels1.Level3.net [212.3.239.165
]
6 27 ms 29 ms 29 ms so-1-0-0.mp1.London2.Level3.net [212.187.128.49]

7 107 ms 99 ms 99 ms so-1-0-0.bbr1.Washington1.level3.net [212.187.12
8.138]
8 187 ms 179 ms 179 ms so-0-0-0.mp1.SanJose1.level3.net [64.159.1.133]

9 187 ms 189 ms 189 ms so-7-0-0.gar3.SanJose1.Level3.net [209.247.14.2]

10 187 ms 189 ms 189 ms 65.57.244.2
11 187 ms 189 ms 189 ms 203.208.182.21
12 308 ms 299 ms 300 ms 203.208.182.129
13 308 ms 299 ms 299 ms 202.160.250.226
14 307 ms 300 ms 300 ms 203.208.232.50
15 309 ms 300 ms 300 ms 203.208.232.57
16 307 ms 299 ms 309 ms 203.208.224.114
17 306 ms 309 ms 299 ms 203.208.137.2
18 303 ms 299 ms 309 ms 203.124.126.12

Trace voltooid.

C:\WINDOWS>


--


C:\WINDOWS> ping 203.124.126.12

Pingen naar 203.124.126.12 met 32 byte gegevens:

Antwoord van 203.124.126.12: bytes=32 time=303ms TTL=49
Antwoord van 203.124.126.12: bytes=32 time=306ms TTL=49
Antwoord van 203.124.126.12: bytes=32 time=296ms TTL=49
Antwoord van 203.124.126.12: bytes=32 time=296ms TTL=49

Pingstatistieken voor 203.124.126.12:
Packets: verzonden = 4, ontvangen = 4, kwijtgeraakt = 0 (0% verlies),
Retourtijd bij benadering in milliseconden:
Minimum = 296ms, Maximum = 306ms, Gemiddeld = 300ms

C:\WINDOWS>

Ah.. Very nice.. Thanks Skize for the pings and traceroutes from .BE.

Now could anyone from the US or other countries please do me this favour.

Thanks.

im from ny...
here ya go!
this is for: 202.136.4.213
-------------------------------
C:\Documents and Settings\Ilya.DESKTOP>ping 202.136.4.213

Pinging 202.136.4.213 with 32 bytes of data:

Reply from 202.136.4.213: bytes=32 time=285ms TTL=237
Reply from 202.136.4.213: bytes=32 time=286ms TTL=237
Reply from 202.136.4.213: bytes=32 time=287ms TTL=237
Reply from 202.136.4.213: bytes=32 time=286ms TTL=237

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

C:\Documents and Settings\Ilya.DESKTOP>tracert 202.136.4.213

Tracing route to 202.136.4.213 over a maximum of 30 hops

1 * * * Request timed out.
2 9 ms 16 ms 7 ms srp1-0.nycmny1-rtr1.si.rr.com [24.164.128.1]
3 10 ms 18 ms 9 ms pos1-0-nycmnya-rtr2.nyc.rr.com [24.29.100.113]
4 11 ms 10 ms 11 ms pop2-new-P0-3.atdn.net [66.185.137.21]
5 9 ms 11 ms 10 ms bb2-new-P0-1.atdn.net [66.185.137.18]
6 9 ms 7 ms 11 ms bb1-nye-P4-0.atdn.net [66.185.152.196]
7 31 ms 11 ms 15 ms pop1-nye-P0-0.atdn.net [66.185.151.49]
8 11 ms 18 ms 13 ms so-2/0/0.BR1.NYC4.ALTER.NET [204.255.173.33]
9 12 ms 10 ms 12 ms 0.so-6-0-0.XL1.NYC4.ALTER.NET [152.63.21.78]
10 23 ms 10 ms 12 ms 0.so-4-0-0.TL1.NYC9.ALTER.NET [152.63.0.173]
11 91 ms 91 ms 89 ms 0.so-5-0-0.TL1.LAX9.ALTER.NET [152.63.10.94]
12 90 ms 91 ms 91 ms 0.POS6-0.IR1.LAX9.ALTER.NET [152.63.0.145]
13 92 ms 91 ms 90 ms so-7-1-0.IR1.LAX12.ALTER.NET [137.39.31.225]
14 297 ms 298 ms 298 ms 0.so-3-1-0.TR1.SIN2.ALTER.Net [210.80.49.221]
15 294 ms 295 ms 298 ms 0.so-3-2-0.XR2.SIN2.ALTER.Net [210.80.49.238]
16 295 ms 300 ms 301 ms 12.POS8-0-0.GW3.SIN2.ALTER.NET [210.80.38.26]
17 298 ms 312 ms 301 ms dataone-gw-sg.aspac.customer.alter.net [202.95.64.102]
18 305 ms 300 ms 301 ms 202.56.129.11
19 301 ms 301 ms 298 ms 202.56.129.12
20 285 ms 288 ms 288 ms 202.136.4.213

Trace complete.

this is for: 210.193.6.182
-------------------------------
C:\Documents and Settings\Ilya.DESKTOP>ping 210.193.6.182

Pinging 210.193.6.182 with 32 bytes of data:

Reply from 210.193.6.182: bytes=32 time=288ms TTL=46
Reply from 210.193.6.182: bytes=32 time=278ms TTL=46
Reply from 210.193.6.182: bytes=32 time=281ms TTL=46
Reply from 210.193.6.182: bytes=32 time=288ms TTL=46

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

C:\Documents and Settings\Ilya.DESKTOP>tracert 210.193.6.182

Tracing route to 210.193.6.182 over a maximum of 30 hops

1 * * * Request timed out.
2 6 ms 8 ms 9 ms srp1-0.nycmny1-rtr1.si.rr.com [24.164.128.1]
3 8 ms 8 ms 11 ms pos1-0-nycmnya-rtr2.nyc.rr.com [24.29.100.113]
4 12 ms 11 ms 9 ms pop2-new-P0-3.atdn.net [66.185.137.21]
5 19 ms 21 ms 10 ms bb2-new-P0-1.atdn.net [66.185.137.18]
6 10 ms 8 ms 8 ms bb1-nye-P4-0.atdn.net [66.185.152.196]
7 11 ms 9 ms 9 ms bb1-nyc-P5-0.atdn.net [66.185.152.82]
8 16 ms 16 ms 13 ms bb1-dcl-P2-0.atdn.net [66.185.152.222]
9 13 ms 27 ms 14 ms pop1-dcl-P5-1.atdn.net [66.185.145.213]
10 17 ms 18 ms 23 ms GlobalCrossing.atdn.net [66.185.145.238]
11 15 ms 24 ms 13 ms pos2-0-2488M.cr2.WDC2.gblx.net [208.178.174.61]
12 231 ms 228 ms 225 ms so1-0-0-622M.cr2.HKG1.gblx.net [203.192.134.118]
13 283 ms 292 ms 283 ms pos1-0-0-155M.ar2.SIN1.gblx.net [203.192.163.85]
14 289 ms 290 ms 279 ms 203.192.168.138
15 307 ms 293 ms 291 ms alpha002.qala.com.sg [210.193.2.2]
16 290 ms 279 ms 290 ms 210.193.6.182

Trace complete.

this is for: 203.124.126.12
-------------------------------
C:\Documents and Settings\Ilya.DESKTOP>ping 203.124.126.12

Pinging 203.124.126.12 with 32 bytes of data:

Reply from 203.124.126.12: bytes=32 time=252ms TTL=45
Reply from 203.124.126.12: bytes=32 time=255ms TTL=45
Reply from 203.124.126.12: bytes=32 time=253ms TTL=45
Reply from 203.124.126.12: bytes=32 time=254ms TTL=45

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

C:\Documents and Settings\Ilya.DESKTOP>tracert 203.124.126.12

Tracing route to 203.124.126.12 over a maximum of 30 hops

1 * * * Request timed out.
2 9 ms 7 ms 28 ms srp1-0.nycmny1-rtr1.si.rr.com [24.164.128.1]
3 31 ms 7 ms 8 ms pos1-0-nycmnya-rtr2.nyc.rr.com [24.29.100.113]
4 17 ms 8 ms 9 ms pop2-new-P0-3.atdn.net [66.185.137.21]
5 10 ms 9 ms 12 ms bb2-new-P0-1.atdn.net [66.185.137.18]
6 14 ms 11 ms 23 ms bb1-nye-P4-0.atdn.net [66.185.152.196]
7 10 ms 10 ms 8 ms pop1-nye-P0-0.atdn.net [66.185.151.49]
8 18 ms 9 ms 9 ms sl-gw37-nyc-12-0.sprintlink.net [144.232.228.73]
9 35 ms 30 ms 12 ms sl-bb21-nyc-4-0.sprintlink.net [144.232.13.65]
10 9 ms 9 ms 11 ms sl-bb22-nyc-14-0.sprintlink.net [144.232.7.102]
11 38 ms 53 ms 32 ms sl-bb21-chi-9-0.sprintlink.net [144.232.9.149]
12 44 ms 32 ms 69 ms sl-bb25-chi-13-0.sprintlink.net [144.232.26.90]
13 52 ms 51 ms 54 ms sl-bb23-fw-10-3.sprintlink.net [144.232.9.26]
14 87 ms 89 ms 89 ms sl-bb20-ana-8-0.sprintlink.net [144.232.18.242]
15 85 ms 93 ms 86 ms sl-st20-la-15-1.sprintlink.net [144.232.20.128]
16 87 ms 88 ms 86 ms leg-63-169-235-134-CHI.sprinthome.com [63.169.235.134]
17 89 ms 89 ms 89 ms 203.208.168.221
18 262 ms 261 ms 262 ms 203.208.182.133
19 272 ms 259 ms 253 ms 203.208.172.129
20 283 ms 269 ms 271 ms 202.160.250.230
21 287 ms 287 ms 289 ms 203.208.232.38
22 272 ms 279 ms 275 ms 203.208.232.53
23 261 ms 279 ms 256 ms 203.208.137.2
24 252 ms 255 ms 253 ms 203.124.126.12

Trace complete.

[i broke it up so it would be easier to read]

PING 202.136.4.213 (202.136.4.213): 56 octets data
64 octets from 202.136.4.213: icmp_seq=0 ttl=239 time=359.3 ms
64 octets from 202.136.4.213: icmp_seq=1 ttl=239 time=360.2 ms
64 octets from 202.136.4.213: icmp_seq=2 ttl=239 time=359.2 ms
64 octets from 202.136.4.213: icmp_seq=3 ttl=239 time=359.9 ms
64 octets from 202.136.4.213: icmp_seq=4 ttl=239 time=367.0 ms

--- 202.136.4.213 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 359.2/361.1/367.0 ms
ethx@monalisa:ethx$ traceroute 210.193.6.182
traceroute to 210.193.6.182 (210.193.6.182), 30 hops max, 40 byte packets
1 islandtelecom241-254.islandtelecom.com (142.177.241.254) 21.029 ms 17.086 ms 37.952 ms
2 142.166.182.114 (142.166.182.114) 17.228 ms 17.338 ms 16.920 ms
3 alnb-cr01-pos7-3.aliant.net (142.166.181.45) 21.523 ms 21.401 ms 21.037 ms
4 64.230.231.113 (64.230.231.113) 33.509 ms 31.380 ms 38.328 ms
5 core4-montreal02-pos0-1.in.bellnexxia.net (206.108.99.173) 34.162 ms 34.689 ms 33.346 ms
6 core1-newyork83-pos0-0.in.bellnexxia.net (206.108.99.190) 41.427 ms 41.213 ms 40.606 ms
7 HSE-Sherbrooke-ppp98979.qc.sympatico.ca (64.230.223.118) 41.558 ms 42.205 ms 40.485 ms
8 208.50.13.129 (208.50.13.129) 40.663 ms 41.391 ms 40.468 ms
9 pos2-0-2488M.cr2.NYC1.gblx.net (67.17.64.153) 40.953 ms pos2-0-2488M.cr1.NYC1.gblx.net (67.17.64.145) 40.538 ms 41.733 ms
10 so1-2-1-155M.cr2.HKG1.gblx.net (203.192.134.141) 253.940 ms 252.208 ms 253.917 ms
11 pos1-0-0-155M.ar2.SIN1.gblx.net (203.192.163.85) 314.243 ms 314.053 ms 315.368 ms
12 203.192.168.138 (203.192.168.138) 323.117 ms 324.093 ms 324.262 ms
13 alpha002.qala.com.sg (210.193.2.2) 324.294 ms 324.892 ms 324.305 ms
14 210.193.6.182 (210.193.6.182) 326.216 ms 324.997 ms 324.216 ms

PING 210.193.6.182 (210.193.6.182): 56 octets data
64 octets from 210.193.6.182: icmp_seq=0 ttl=49 time=327.1 ms
64 octets from 210.193.6.182: icmp_seq=1 ttl=49 time=326.2 ms
64 octets from 210.193.6.182: icmp_seq=2 ttl=49 time=328.9 ms
64 octets from 210.193.6.182: icmp_seq=3 ttl=49 time=329.3 ms
64 octets from 210.193.6.182: icmp_seq=4 ttl=49 time=325.8 ms

--- 210.193.6.182 ping statistics ---
6 packets transmitted, 5 packets received, 16% packet loss
round-trip min/avg/max = 325.8/327.4/329.3 ms
ethx@monalisa:ethx$ traceroute 210.193.6.182
traceroute to 210.193.6.182 (210.193.6.182), 30 hops max, 40 byte packets
1 islandtelecom241-254.islandtelecom.com (142.177.241.254) 651.144 ms 58.282 ms 41.633 ms
2 142.166.182.114 (142.166.182.114) 17.426 ms 18.326 ms 18.750 ms
3 alnb-cr01-pos7-3.aliant.net (142.166.181.45) 21.339 ms 22.134 ms 20.736 ms
4 64.230.231.113 (64.230.231.113) 40.214 ms 33.442 ms 33.635 ms
5 core4-montreal02-pos0-1.in.bellnexxia.net (206.108.99.173) 32.409 ms 33.264 ms 33.692 ms
6 core1-newyork83-pos0-0.in.bellnexxia.net (206.108.99.190) 41.478 ms 41.276 ms 41.369 ms
7 HSE-Sherbrooke-ppp98979.qc.sympatico.ca (64.230.223.118) 40.847 ms 78.157 ms 40.824 ms
8 208.50.13.129 (208.50.13.129) 41.437 ms 40.676 ms 39.722 ms
9 pos2-0-2488M.cr2.NYC1.gblx.net (67.17.64.153) 44.668 ms pos2-0-2488M.cr1.NYC1.gblx.net (67.17.64.145) 41.727 ms 41.730 ms
10 so1-2-1-155M.cr2.HKG1.gblx.net (203.192.134.141) 255.319 ms 252.906 ms 254.121 ms
11 pos1-0-0-155M.ar2.SIN1.gblx.net (203.192.163.85) 314.280 ms 315.174 ms 314.283 ms
12 203.192.168.138 (203.192.168.138) 325.039 ms 325.248 ms 324.300 ms
13 alpha002.qala.com.sg (210.193.2.2) 325.052 ms 331.559 ms 325.113 ms
14 210.193.6.182 (210.193.6.182) 324.243 ms 328.313 ms 327.372 ms

PING 203.124.126.12 (203.124.126.12): 56 octets data
64 octets from 203.124.126.12: icmp_seq=0 ttl=47 time=296.4 ms
64 octets from 203.124.126.12: icmp_seq=1 ttl=47 time=297.7 ms
64 octets from 203.124.126.12: icmp_seq=2 ttl=47 time=299.6 ms
64 octets from 203.124.126.12: icmp_seq=3 ttl=47 time=297.2 ms
64 octets from 203.124.126.12: icmp_seq=4 ttl=47 time=297.4 ms

--- 203.124.126.12 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 296.4/297.6/299.6 ms
ethx@monalisa:ethx$ traceroute 203.124.126.12
traceroute to 203.124.126.12 (203.124.126.12), 30 hops max, 40 byte packets
1 islandtelecom241-254.islandtelecom.com (142.177.241.254) 16.515 ms 18.318 ms 19.126 ms
2 142.166.182.114 (142.166.182.114) 17.945 ms 19.831 ms 16.714 ms
3 alnb-cr01-pos7-3.aliant.net (142.166.181.45) 32.025 ms 20.822 ms 20.780 ms
4 64.230.231.113 (64.230.231.113) 33.154 ms 33.055 ms 33.910 ms
5 core4-montreal02-pos0-1.in.bellnexxia.net (206.108.99.173) 32.874 ms 33.287 ms 32.425 ms
6 core3-toronto63-pos6-1.in.bellnexxia.net (64.230.243.238) 43.049 ms 42.891 ms 41.995 ms
7 core1-vancouver-pos10-2.in.bellnexxia.net (64.230.229.38) 104.118 ms 102.708 ms 105.219 ms
8 core2-seattle-pos0-0.in.bellnexxia.net (206.108.102.190) 121.987 ms 122.554 ms 121.414 ms
9 core1-paloalto01-pos1-0.in.bellnexxia.net (206.108.108.150) 119.955 ms 119.830 ms 120.040 ms
10 bx1-paloalto01-srp2-0.in.bellnexxia.net (206.108.102.250) 120.061 ms 119.807 ms 120.043 ms
11 g1-0-0.plapx-ar1.ix.singtel.com (198.32.176.50) 120.043 ms 137.135 ms 136.680 ms
12 203.208.182.21 (203.208.182.21) 122.053 ms 127.867 ms 122.946 ms
13 203.208.182.129 (203.208.182.129) 309.345 ms 307.281 ms 308.186 ms
14 202.160.250.226 (202.160.250.226) 308.274 ms 308.062 ms 309.557 ms
15 203.208.232.50 (203.208.232.50) 308.924 ms 306.810 ms 309.380 ms
16 203.208.232.33 (203.208.232.33) 327.069 ms 326.160 ms 327.068 ms
17 203.208.232.53 (203.208.232.53) 313.372 ms 294.937 ms 296.279 ms
18 203.208.137.2 (203.208.137.2) 295.303 ms 297.232 ms 296.181 ms
19 203.124.126.12 (203.124.126.12) 302.516 ms 295.072 ms 295.056 ms

[btw im on cable]

Target Name: (resolving host name)
IP: 202.136.4.213
Date/Time: 8/4/2003 7:00:22 PM

1 1 ms [192.168.0.1]
2 42 ms [10.69.64.1]
3 29 ms 24.213.28.33.kzo.mi.chartermi.net [24.213.28.33]
4 16 ms 24.247.60.181.gha.mi.chartermi.net [24.247.60.181]
5 15 ms [12.124.15.105]
6 26 ms gbr2-p70.dtrmi.ip.att.net [12.123.139.26]
7 53 ms tbr2-p012701.cgcil.ip.att.net [12.122.2.194]
8 36 ms ggr2-p390.cgcil.ip.att.net [12.123.6.37]
9 31 ms so-1-1-0.edge1.Chicago1.Level3.net [209.0.227.77]
10 25 ms so-2-1-0.bbr2.Chicago1.level3.net [209.244.8.13]
11 73 ms so-1-0-0.mp1.SanJose1.level3.net [209.247.9.118]
12 71 ms so-7-0-0.gar3.SanJose1.Level3.net [209.247.14.2]
13 70 ms [65.57.244.2]
14 71 ms p6-1.plapx-cr1.ix.singtel.com [203.208.172.45]
15 250 ms p6-8.sngtp-cr2.ix.singtel.com [203.208.172.29]
16 245 ms [202.160.250.134]
17 307 ms [203.208.145.94]
18 281 ms [202.56.129.12]
19 265 ms [202.136.4.213]


Target Name: (resolving host name)
IP: 210.193.6.182
Date/Time: 8/4/2003 7:00:41 PM

1 1 ms [192.168.0.1]
2 27 ms [10.69.64.1]
3 25 ms 24.213.28.33.kzo.mi.chartermi.net [24.213.28.33]
4 11 ms 24.247.60.181.gha.mi.chartermi.net [24.247.60.181]
5 16 ms [12.124.15.105]
6 15 ms gbr2-p70.dtrmi.ip.att.net [12.123.139.26]
7 23 ms tbr2-p013002.cgcil.ip.att.net [12.122.10.113]
8 19 ms ggr1-p370.cgcil.ip.att.net [12.123.5.149]
9 57 ms so3-0-0-622M.br2.CHI1.gblx.net [208.51.6.25]
10 38 ms pos6-0-2488M.cr1.CHI1.gblx.net [208.49.59.205]
11 227 ms so1-2-1-155M.cr2.HKG1.gblx.net [203.192.134.141]
12 286 ms pos1-0-0-155M.ar2.SIN1.gblx.net [203.192.163.85]
13 304 ms [203.192.168.138]
14 288 ms alpha002.qala.com.sg [210.193.2.2]
15 279 ms [210.193.6.182]


Target Name: (resolving host name)
IP: 203.124.126.12
Date/Time: 8/4/2003 7:00:58 PM

1 1 ms [192.168.0.1]
2 11 ms [10.69.64.1]
3 14 ms 24.213.28.33.kzo.mi.chartermi.net [24.213.28.33]
4 10 ms 24.247.60.181.gha.mi.chartermi.net [24.247.60.181]
5 14 ms [12.124.15.105]
6 13 ms gbr2-p70.dtrmi.ip.att.net [12.123.139.26]
7 23 ms tbr2-p013002.cgcil.ip.att.net [12.122.10.113]
8 20 ms ggr2-p390.cgcil.ip.att.net [12.123.6.37]
9 22 ms so-1-1-0.edge1.Chicago1.Level3.net [209.0.227.77]
10 20 ms so-2-1-0.bbr2.Chicago1.level3.net [209.244.8.13]
11 70 ms so-1-0-0.mp1.SanJose1.level3.net [209.247.9.118]
12 69 ms so-7-0-0.gar3.SanJose1.Level3.net [209.247.14.2]
13 70 ms [65.57.244.2]
14 113 ms [203.208.182.21]
15 280 ms [203.208.182.129]
16 262 ms [202.160.250.226]
17 259 ms [203.208.232.50]
18 274 ms [203.208.232.33]
19 242 ms [203.208.232.53]
20 243 ms [203.208.137.2]
21 244 ms [203.124.126.12]


All from cable in southwest michigan