Forum Feedback Please submit ping and tracert data

lucky_chouhan · Sep 19, 2008

Location : Bhopal, Madhya Pradesh
ISP : Airtel 256 Kbps
C:\>ping Indian Technology and Computer Discussion Portal - TechEnclave
Pinging techenclave.com [207.58.182.106] with 32 bytes of data:

Reply from 207.58.182.106: bytes=32 time=310ms TTL=52
Reply from 207.58.182.106: bytes=32 time=308ms TTL=52
Reply from 207.58.182.106: bytes=32 time=310ms TTL=52
Reply from 207.58.182.106: bytes=32 time=309ms TTL=52

Ping statistics for 207.58.182.106:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 308ms, Maximum = 310ms, Average = 309ms
C:\>Tracert Indian Technology and Computer Discussion Portal - TechEnclave

Tracing route to techenclave.com [207.58.182.106]
over a maximum of 30 hops:

1 29 ms 29 ms 29 ms ABTS-MP-Dynamic-001.4.168.122.airtelbroadband.in
[122.168.4.1]
2 29 ms 29 ms 29 ms 202.56.224.77
3 56 ms 69 ms 64 ms 61.95.240.185
4 62 ms 61 ms 60 ms 125.21.167.29
5 179 ms 179 ms 180 ms pal2-bharti-2.pal.seabone.net [195.22.197.121]
6 243 ms 239 ms 241 ms dtag-1-mil51.seabone.net [195.22.192.6]
7 370 ms 332 ms 333 ms 217.239.41.6
8 303 ms 305 ms 302 ms 62.153.203.126
9 301 ms 299 ms 302 ms 209.50.254.70
10 302 ms 301 ms 300 ms sc-smv2977.servint.net [209.50.237.14]
11 305 ms 308 ms 311 ms vps.techenclave.com [207.58.182.106]

Trace complete.

Jasku · Sep 19, 2008

Airtel - Chennai -384Kbps
C:\Documents and Settings\Administrator>ping techenclave.com

Pinging techenclave.com [207.58.182.106] with 32 bytes of data:

Reply from 207.58.182.106: bytes=32 time=275ms TTL=56
Reply from 207.58.182.106: bytes=32 time=277ms TTL=56
Reply from 207.58.182.106: bytes=32 time=272ms TTL=56
Reply from 207.58.182.106: bytes=32 time=275ms TTL=56

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

C:\Documents and Settings\Administrator>tracert techenclave.com

Tracing route to techenclave.com [207.58.182.106]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms vps.techenclave.com [207.58.182.106]
2 38 ms 30 ms 27 ms ABTS-TN-dynamic-001.48.164.122.airtelbroadband.i
n [122.164.48.1]
3 29 ms 27 ms 29 ms 61.246.253.225
4 27 ms 30 ms 30 ms 61.95.240.129
5 27 ms 25 ms 29 ms 125.21.167.29
6 150 ms 149 ms 149 ms pal2-bharti-1.pal.seabone.net [213.144.181.85]
7 214 ms 214 ms 211 ms dtag-1-mil51.seabone.net [195.22.192.6]
8 325 ms 266 ms 264 ms 217.239.41.6
9 267 ms 264 ms 264 ms 62.153.203.126
10 286 ms 279 ms 282 ms 209.50.254.66
11 280 ms 276 ms 279 ms sc-smv2977.servint.net [209.50.237.14]
12 272 ms 274 ms 274 ms vps.techenclave.com [207.58.182.106]

Trace complete.

C:\Documents and Settings\Administrator>

linuxtechie · Sep 19, 2008

C:\>ping techenclave.com

Pinging techenclave.com [207.58.182.106] with 32 bytes of data:

Reply from 207.58.182.106: bytes=32 time=318ms TTL=53
Reply from 207.58.182.106: bytes=32 time=319ms TTL=53
Reply from 207.58.182.106: bytes=32 time=320ms TTL=53
Reply from 207.58.182.106: bytes=32 time=318ms TTL=53

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

C:\>tracert techenclave.com

Tracing route to techenclave.com [207.58.182.106]
over a maximum of 30 hops:

1 2 ms 1 ms 2 ms khanorkar_router [192.168.175.1]
2 2 ms 2 ms 2 ms 192.168.1.1
3 29 ms 28 ms 27 ms 59.95.32.1
4 * * * Request timed out.
5 * * * Request timed out.
6 48 ms 47 ms 48 ms 203.101.65.181
7 48 ms 48 ms 49 ms 125.21.167.29
8 172 ms 172 ms 173 ms pal2-bharti-2.pal.seabone.net [195.22.197.121]
9 211 ms 212 ms 211 ms dtag-1-mil51.seabone.net [195.22.192.6]
10 288 ms 287 ms 287 ms 217.239.41.6
11 315 ms 313 ms 313 ms 62.153.203.126
12 318 ms 323 ms 320 ms 209.50.254.66
13 314 ms 315 ms 317 ms sc-smv2977.servint.net [209.50.237.14]
14 317 ms 323 ms 319 ms vps.techenclave.com [207.58.182.106]

Trace complete.

Safin · Sep 19, 2008

Thank you guys,

That will be all. I think the speed has improved a bit and we are following up on whats causing the sluggishness. Seems to be a network issue.

Crazy_Eddy · Sep 19, 2008

Ping statistics for 207.58.182.106:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

Approximate round trip times in milli-seconds:

Minimum = 273ms, Maximum = 278ms, Average = 275ms

Tracing route to techenclave.com [207.58.182.106]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms ABTS-TN-dynamic-206.85.164.122.airtelbroadband.in [122.164.85.206]

2 24 ms 23 ms 24 ms 203.145.161.1

3 24 ms 24 ms 24 ms ras-Chn-129.227.95.61.airtelbroadband.in [61.95.227.129]

4 21 ms 24 ms 25 ms 61.95.240.129

5 24 ms 24 ms 24 ms 125.21.167.25

6 146 ms 147 ms 148 ms pal2-bharti-2.pal.seabone.net [195.22.197.121]

7 207 ms 210 ms 208 ms dtag-2-mil51.seabone.net [195.22.192.10]

8 260 ms 259 ms 259 ms 217.239.41.6

9 271 ms 268 ms 268 ms 62.153.203.126

10 291 ms 271 ms 270 ms 209.50.254.66

11 277 ms 318 ms 276 ms sc-smv2977.servint.net [209.50.237.14]

12 274 ms 274 ms 275 ms vps.techenclave.com [207.58.182.106]

Grease Monk · Sep 20, 2008

Road Runner (Time Warner Cable): Cincinnati, Ohio

Code:

C:\>ping techenclave.com

Pinging techenclave.com [207.58.182.106] with 32 bytes of data:

Reply from 207.58.182.106: bytes=32 time=54ms TTL=55
Reply from 207.58.182.106: bytes=32 time=39ms TTL=55
Reply from 207.58.182.106: bytes=32 time=41ms TTL=55
Reply from 207.58.182.106: bytes=32 time=40ms TTL=55

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

Code:

C:\>tracert techenclave.com

Tracing route to techenclave.com [207.58.182.106]
over a maximum of 30 hops:

  1    23 ms    10 ms    13 ms  10.66.128.1
  2     8 ms    10 ms     9 ms  gig2-3.cncnoh1-ybr1.cinci.rr.com [24.29.0.53]
  3   245 ms    81 ms    41 ms  srp13-0.mtgmoh1-rtr3.cinci.rr.com [24.29.2.113]

  4     *        *       12 ms  gig3-1.mtgmoh1-rtr4.cinci.rr.com [24.29.2.102]
  5     9 ms     9 ms    10 ms  tge3-2-0.mtgmoh1-rtr0.mwrtn.rr.com [65.25.137.24
1]
  6    27 ms    17 ms    19 ms  ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
  7    18 ms    18 ms    37 ms  ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
  8    19 ms    19 ms    21 ms  ge9-4.br03.chc01.pccwbtn.net [209.8.108.37]
  9     *       42 ms    41 ms  servint.ge5-12.br01.wdc02.pccwbtn.net [63.218.83
.38]
 10    41 ms    38 ms    40 ms  sc-smv2977.servint.net [209.50.237.14]
 11    40 ms    40 ms    44 ms  vps.techenclave.com [207.58.182.106]

Trace complete.

cool_cat · Sep 20, 2008

OK.it seems mine is the only o/p from GNU/Linux system? eh? even "linuxtechie" dont have o/p from lenex?

Muvattupuzha ,Kochin ,kerala on BSNL broadband :-

Code:

prakash@praka:~$ ping -c5 techenclave.com

PING techenclave.com (207.58.182.106) 56(84) bytes of data.

64 bytes from vps.techenclave.com (207.58.182.106): icmp_seq=1 ttl=56 time=617 ms

64 bytes from vps.techenclave.com (207.58.182.106): icmp_seq=2 ttl=56 time=621 ms

64 bytes from vps.techenclave.com (207.58.182.106): icmp_seq=3 ttl=56 time=587 ms

64 bytes from vps.techenclave.com (207.58.182.106): icmp_seq=4 ttl=56 time=615 ms

64 bytes from vps.techenclave.com (207.58.182.106): icmp_seq=5 ttl=56 time=619 ms

--- techenclave.com ping statistics ---

5 packets transmitted, 5 received, 0% packet loss, time 4753ms

rtt min/avg/max/mdev = 587.879/612.646/621.856/12.555 ms

Code:

prakash@praka:~$ tracepath techenclave.com

 1:  59.93.42.xx (59.93.42.xx)                              0.548ms pmtu 1492

 1:  59.93.42.1 (59.93.42.1)                               56.161ms asymm  2 

 1:  59.93.42.1 (59.93.42.1)                               55.908ms asymm  2 

 2:  218.248.255.58 (218.248.255.58)                       97.941ms 

 3:  218.248.255.58 (218.248.255.58)                       97.395ms asymm  2 

 4:  59.162.0.118.static.vsnl.net.in (59.162.0.118)        97.936ms asymm  7 

 5:  59.163.55.206.static.vsnl.net.in (59.163.55.206)     329.926ms asymm  8 

 6:  if-2-11.mse1.NW8-NewYork.as6453.net (209.58.75.37)   741.912ms 

 7:  if-7-0.core1.NTO-NewYork.as6453.net (216.6.82.61)    729.920ms asymm  5 

 8:  if-4-0-0.core2.NTO-NewYork.as6453.net (216.6.82.66)  721.917ms asymm  5 

 9:  cr2-pos-0-8-0-3.nyr.savvis.net (208.173.129.29)      721.726ms asymm  6 

10:  cr1-pos-0-0-0-0.Washington.savvis.net (204.70.192.1) 721.914ms asymm  7 

11:  msr1-tengig-0-0-0-0.Washington.savvis.net (204.70.196.94) 727.918ms asymm  8 

12:  no reply

13:  corporate-executive-board.Washington.savvis.net (208.174.119.98) 720.610ms asymm 10 

14:  sc-smv2977.servint.net (209.50.237.14)               729.992ms asymm  9 

15:  vps.techenclave.com (207.58.182.106)                 723.959ms reached

     Resume: pmtu 1492 hops 15 back 56

Saiyan · Sep 20, 2008

Tata Indicom, Chennai

Code:

Pinging techenclave.com [207.58.182.106] with 32 bytes of data:

Reply from 207.58.182.106: bytes=32 time=315ms TTL=46
Reply from 207.58.182.106: bytes=32 time=314ms TTL=46
Reply from 207.58.182.106: bytes=32 time=315ms TTL=46
Reply from 207.58.182.106: bytes=32 time=315ms TTL=46

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

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

Code:

Tracing route to techenclave.com [207.58.182.106]
over a maximum of 30 hops:

  1    29 ms    29 ms    28 ms  121.247.216.1.chennai-dynamic-bb.vsnl.net.in [121.247.216.1]
  2    29 ms    30 ms    30 ms  172.31.68.85
  3    30 ms    29 ms    29 ms  172.31.8.145
  4    30 ms    29 ms    29 ms  illchn-static-203.199.247.234.vsnl.net.in [203.199.247.234]
  5   256 ms   403 ms   399 ms  59.163.16.142.static.vsnl.net.in [59.163.16.142]

  6   238 ms   238 ms   238 ms  if-11-0-3.mcore3.PDI-PaloAlto.as6453.net [64.86.84.141]
  7   239 ms   239 ms   239 ms  if-13-0-0.mcore4.PDI-PaloAlto.as6453.net [216.6.29.46]
  8   239 ms   239 ms   239 ms  if-0-0-0.core3.SQN-SanJose.as6453.net [216.6.33.5]
  9   239 ms   239 ms   238 ms  cpr2-pos-10-0.sanjoseequinix.savvis.net [208.175.172.173]
 10   246 ms   246 ms   251 ms  cr1-loopback.sfo.savvis.net [206.24.210.70]
 11   314 ms   314 ms   314 ms  cr2-tengig-0-15-0-0.Washington.savvis.net [204.70.196.102]
 12   312 ms   313 ms   313 ms  msr1-tengig-0-3-0-0.Washington.savvis.net [204.70.196.98]
 13   309 ms   310 ms   310 ms  er1-gig-3-0-0.dck.savvis.net [204.70.203.2]
 14   314 ms   315 ms   315 ms  corporate-executive-board.Washington.savvis.net [208.174.119.98]
 15   315 ms   316 ms   315 ms  sc-smv2977.servint.net [209.50.237.14]
 16   315 ms   315 ms   315 ms  vps.techenclave.com [207.58.182.106]

Trace complete.

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

Airtel, Chennai

Code:

Pinging techenclave.com [207.58.182.106] with 32 bytes of data:

Reply from 207.58.182.106: bytes=32 time=279ms TTL=56
Reply from 207.58.182.106: bytes=32 time=279ms TTL=56
Reply from 207.58.182.106: bytes=32 time=278ms TTL=56
Reply from 207.58.182.106: bytes=32 time=278ms TTL=56

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

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

Code:

Tracing route to techenclave.com [207.58.182.106]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  buffalo.setup [192.168.11.1]
  2    36 ms    25 ms    25 ms  ABTS-TN-dynamic-001.48.164.122.airtelbroadband.in [122.164.48.1]
  3    25 ms    25 ms    24 ms  61.246.253.225
  4    25 ms    24 ms    24 ms  61.95.240.129
  5    24 ms    24 ms    24 ms  125.21.167.25
  6   149 ms   149 ms   149 ms  pal2-bharti-2.pal.seabone.net [195.22.197.121]
  7   213 ms   213 ms   213 ms  dtag-2-mil51.seabone.net [195.22.192.10]
  8   271 ms   271 ms   271 ms  217.239.41.6
  9   265 ms   264 ms   264 ms  62.153.203.126
 10   385 ms   435 ms   295 ms  209.50.254.70
 11   276 ms   275 ms   276 ms  sc-smv2977.servint.net [209.50.237.14]
 12   278 ms   279 ms   278 ms  vps.techenclave.com [207.58.182.106]

Trace complete.

stalker · Sep 20, 2008

MTNL Mumbai

Code:

C:\Documents and Settings\yD>ping techenclave.com

Pinging techenclave.com [207.58.182.106] with 32 bytes of data:

Reply from 207.58.182.106: bytes=32 time=826ms TTL=52
Reply from 207.58.182.106: bytes=32 time=942ms TTL=52
Reply from 207.58.182.106: bytes=32 time=1080ms TTL=52
Reply from 207.58.182.106: bytes=32 time=1030ms TTL=52

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

C:\Documents and Settings\yD>

Code:

C:\Documents and Settings\yD>tracert techenclave.com

Tracing route to techenclave.com [207.58.182.106]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3   519 ms   393 ms   345 ms  triband-mum-59.185.0.161.mtnl.net.in [59.185.0.161]
  4   511 ms   367 ms   185 ms  59.160.30.46.static.vsnl.net.in [59.160.30.46]
  5   536 ms   481 ms   234 ms  59.163.55.206.static.vsnl.net.in [59.163.55.206]
  6   553 ms   271 ms   497 ms  if-2-11.mse1.NW8-NewYork.as6453.net [209.58.75.37]
  7   239 ms   437 ms   489 ms  if-7-0.core1.NTO-NewYork.as6453.net [216.6.82.61]
  8   517 ms   241 ms   497 ms  if-4-0-0.core2.NTO-NewYork.as6453.net [216.6.82.66]
  9   376 ms   565 ms   632 ms  cr2-pos-0-8-0-3.nyr.savvis.net [208.173.129.29]
 10   414 ms   556 ms   451 ms  cr1-pos-0-0-0-0.Washington.savvis.net [204.70.192.1]
 11   674 ms   463 ms   444 ms  msr1-tengig-0-0-0-0.Washington.savvis.net [204.70.196.94]
 12   297 ms   597 ms   259 ms  er1-gig-3-0-0.dck.savvis.net [204.70.203.2]
 13   279 ms   286 ms   769 ms  corporate-executive-board.Washington.savvis.net [208.174.119.98]
 14   257 ms   243 ms   704 ms  sc-smv2977.servint.net [209.50.237.14]
 15   261 ms   539 ms   490 ms  vps.techenclave.com [207.58.182.106]

Trace complete.

C:\Documents and Settings\yD>

kumaranuj · Sep 20, 2008

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

H:\Documents and Settings>ping techenclave.com

Pinging techenclave.com [207.58.182.106] with 32 bytes of data:

Reply from 207.58.182.106: bytes=32 time=657ms TTL=52
Reply from 207.58.182.106: bytes=32 time=650ms TTL=52
Reply from 207.58.182.106: bytes=32 time=640ms TTL=52
Reply from 207.58.182.106: bytes=32 time=696ms TTL=52

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

H:\Documents and Settings>tracert techenclave.com

Tracing route to techenclave.com [207.58.182.106]
over a maximum of 30 hops:

1 130 ms 25 ms 19 ms 117.200.96.1
2 24 ms 23 ms 55 ms 218.248.173.134
3 71 ms * 55 ms 218.248.255.2
4 646 ms 718 ms * 125.16.156.101
5 640 ms 771 ms 628 ms 125.21.167.25
6 967 ms 965 ms 985 ms pal2-bharti-2.pal.seabone.net [195.22.197.121]
7 1111 ms * 952 ms dtag-2-mil51.seabone.net [195.22.192.10]
8 630 ms 643 ms 673 ms 217.239.41.6
9 764 ms 658 ms 732 ms 62.153.203.126
10 774 ms 654 ms 676 ms 209.50.254.70
11 678 ms 820 ms 654 ms sc-smv2977.servint.net [209.50.237.14]
12 428 ms 637 ms 594 ms vps.techenclave.com [207.58.182.106]

Trace complete.

greenhorn · Sep 20, 2008

praka123 said:
OK.it seems mine is the only o/p from GNU/Linux system? eh? even "linuxtechie" dont have o/p from lenex?

check mine

viralbug · Sep 20, 2008

MTNL mumbai

Pinging techenclave.com [207.58.182.106] with 32 bytes of data:

Reply from 207.58.182.106: bytes=32 time=245ms TTL=52
Reply from 207.58.182.106: bytes=32 time=235ms TTL=52
Reply from 207.58.182.106: bytes=32 time=235ms TTL=52
Reply from 207.58.182.106: bytes=32 time=225ms TTL=52

Ping statistics for 207.58.182.106:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 225ms, Maximum = 245ms, Average = 235ms
Tracing route to techenclave.com [207.58.182.106]
over a maximum of 30 hops:

1 731 ms 9 ms 22 ms 192.168.0.1
2 43 ms 38 ms 24 ms triband-mum-59.184.191.254.mtnl.net.in [59.184.1
91.254]
3 37 ms 59 ms * triband-mum-59.185.0.34.mtnl.net.in [59.185.0.34
]
4 71 ms * 51 ms 59.160.30.46.static.vsnl.net.in [59.160.30.46]
5 398 ms 249 ms 239 ms 59.163.55.198.static.vsnl.net.in [59.163.55.198]

6 267 ms * * if-2-11.mse1.NW8-NewYork.as6453.net [209.58.75.3
7]
7 273 ms 446 ms 424 ms if-7-0.core1.NTO-NewYork.as6453.net [216.6.82.61
]
8 315 ms 317 ms 317 ms if-4-0-0.core2.NTO-NewYork.as6453.net [216.6.82.
66]
9 * 273 ms * cr2-pos-0-8-0-3.nyr.savvis.net [208.173.129.29]

10 277 ms 290 ms 296 ms cr1-pos-0-0-0-0.Washington.savvis.net [204.70.19
2.1]
11 * * 297 ms msr1-tengig-0-0-0-0.Washington.savvis.net [204.7
0.196.94]
12 324 ms * 291 ms er1-gig-3-0-0.dck.savvis.net [204.70.203.2]
13 * * 305 ms corporate-executive-board.Washington.savvis.net
[208.174.119.98]
14 * 313 ms 313 ms sc-smv2977.servint.net [209.50.237.14]
15 298 ms 296 ms 291 ms vps.techenclave.com [207.58.182.106]

Trace complete.

abbY · Sep 20, 2008

Location: Jaipur

c:\ping techenclave.com
Pinging techenclave.com [207.58.182.106] with 32 bytes of data:

Reply from 207.58.182.106: bytes=32 time=340ms TTL=48
Reply from 207.58.182.106: bytes=32 time=338ms TTL=48
Reply from 207.58.182.106: bytes=32 time=357ms TTL=48
Reply from 207.58.182.106: bytes=32 time=330ms TTL=48

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

c:\tracert techenclave.com
Tracing route to techenclave.com [207.58.182.106]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.10.120.9
2 <1 ms <1 ms <1 ms 192.168.0.2
3 <1 ms <1 ms <1 ms 210.212.97.241
4 * <1 ms <1 ms 172.24.160.218
5 * * * Request timed out.
6 326 ms 322 ms 338 ms 203.197.20.98.static.vsnl.net.in [203.197.20.98]

7 271 ms 263 ms 254 ms 202.54.2.161
8 337 ms 322 ms 313 ms 59.163.55.194.static.vsnl.net.in [59.163.55.194]

9 409 ms 408 ms 404 ms if-2-11.mse1.nw8-newyork.as6453.net [209.58.75.3
7]
10 631 ms 591 ms 471 ms if-7-0.core1.nto-newyork.as6453.net [216.6.82.61
]
11 337 ms 340 ms 335 ms if-4-0-0.core2.nto-newyork.as6453.net [216.6.82.
66]
12 444 ms 439 ms 437 ms cr2-pos-0-8-0-3.nyr.savvis.net [208.173.129.29]

13 344 ms 333 ms 336 ms cr1-pos-0-0-0-0.washington.savvis.net [204.70.19
2.1]
14 339 ms 346 ms 370 ms msr1-tengig-0-0-0-0.washington.savvis.net [204.7
0.196.94]
15 456 ms 462 ms 469 ms er1-gig-3-0-0.dck.savvis.net [204.70.203.2]
16 545 ms 575 ms 617 ms corporate-executive-board.washington.savvis.net
[208.174.119.98]
17 430 ms 435 ms 416 ms sc-smv2977.servint.net [209.50.237.14]
18 332 ms 336 ms 331 ms vps.techenclave.com [207.58.182.106]

Trace complete.

Gaurish · Sep 20, 2008

BSNL Jaipur

PING techenclave.com (207.58.182.106) 56(84) bytes of data.

64 bytes from vps.techenclave.com (207.58.182.106): icmp_seq=1 ttl=55 time=500 ms

64 bytes from vps.techenclave.com (207.58.182.106): icmp_seq=2 ttl=55 time=483 ms

64 bytes from vps.techenclave.com (207.58.182.106): icmp_seq=3 ttl=55 time=524 ms

64 bytes from vps.techenclave.com (207.58.182.106): icmp_seq=4 ttl=55 time=507 ms

64 bytes from vps.techenclave.com (207.58.182.106): icmp_seq=5 ttl=55 time=478 ms

--- techenclave.com ping statistics ---

5 packets transmitted, 5 received, 0% packet loss, time 8981ms

rtt min/avg/max/mdev = 478.828/498.816/524.097/16.450 ms

raceroute to techenclave.com (207.58.182.106), 30 hops max, 52 byte packets

1 59.95.160.1 (59.95.160.1) 37.732 ms 39.202 ms 37.907 ms

2 * * *

3 * * *

4 125.16.156.229 (125.16.156.229) 298.885 ms 309.574 ms 298.791 ms

5 125.21.168.33 (125.21.168.33) 280.905 ms 277.047 ms 274.959 ms

6 125.21.168.93 (125.21.168.93) 133.482 ms 156.931 ms 149.950 ms

7 125.21.167.25 (125.21.167.25) 172.176 ms 158.071 ms 156.107 ms

8 pal2-bharti-2.pal.seabone.net (195.22.197.121) 310.639 ms 308.034 ms 297.833 ms

9 dtag-1-mil51.seabone.net (195.22.192.6) 319.330 ms 297.939 ms 318.001 ms

10 217.239.41.6 (217.239.41.6) 374.710 ms 360.523 ms 354.949 ms

11 62.153.203.126 (62.153.203.126) 467.247 ms 467.532 ms 458.687 ms

12 209.50.254.66 (209.50.254.66) 575.250 ms 644.222 ms 758.006 ms

13 sc-smv2977.servint.net (209.50.237.14) 450.412 ms 439.311 ms 454.929 ms

14 vps.techenclave.com (207.58.182.106) 430.163 ms 431.427 ms 437.109 ms

Aman27deep · Sep 20, 2008

345ms from bsnl broadband, howrah (kolkata)

Nitari · Sep 20, 2008

location:- South Kolkata

cool_cat · Sep 20, 2008

greenhorn said:
check mine

didnt notice at first.

indy1811 · Sep 20, 2008

Bangalore Airtel 1Mbps

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\******>ping techenclave.com

Pinging techenclave.com [207.58.182.106] with 32 bytes of data:

Reply from 207.58.182.106: bytes=32 time=298ms TTL=52
Reply from 207.58.182.106: bytes=32 time=298ms TTL=52
Reply from 207.58.182.106: bytes=32 time=299ms TTL=52
Reply from 207.58.182.106: bytes=32 time=298ms TTL=52

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

C:\Documents and Settings\*******>tracert techenclave.com

Tracing route to techenclave.com [207.58.182.106]
over a maximum of 30 hops:

1 <1 ms <1 ms 11 ms buffalo.setup [192.168.11.1]
2 1 ms 3 ms <1 ms 192.168.1.1
3 * * * Request timed out.
4 * 25 ms 24 ms ABTS-KK-Static-177.32.166.122.airtelbroadband.in
[122.166.32.177]
5 25 ms 31 ms 25 ms ABTS-KK-Static-009.32.166.122.airtelbroadband.in
[122.166.32.9]
6 24 ms 24 ms 24 ms 122.175.255.29
7 32 ms 32 ms 32 ms 125.21.167.29
8 155 ms 155 ms 154 ms pal2-bharti-2.pal.seabone.net [195.22.197.121]
9 201 ms 201 ms 202 ms dtag-2-mil51.seabone.net [195.22.192.10]
10 275 ms 272 ms 273 ms 217.239.41.6
11 297 ms 299 ms 297 ms 62.153.203.126
12 302 ms 302 ms 302 ms 209.50.254.70
13 298 ms 298 ms 298 ms sc-smv2977.servint.net [209.50.237.14]
14 298 ms 299 ms 297 ms vps.techenclave.com [207.58.182.106]

Trace complete.

thetechmind · Sep 20, 2008

Ok here's mine................ExattNet Mumbai......decent pings...

Pinging techenclave.com [207.58.182.106] with 32 bytes of data :

Reply from 207.58.182.106: bytes=32 time=198ms TTL=50
Reply from 207.58.182.106: bytes=32 time=197ms TTL=50
Reply from 207.58.182.106: bytes=32 time=198ms TTL=50
Reply from 207.58.182.106: bytes=32 time=198ms TTL=50
Reply from 207.58.182.106: bytes=32 time=198ms TTL=50

for some reason......im getting request time outs from the very second tracert result.....

Gaurish · Sep 21, 2008

abhisheksahas said:
Location: Jaipur

Comparing to mine your stats seems good

Search

Search

Forum Feedback Please submit ping and tracert data

lucky_chouhan

Inactive

Jasku

linuxtechie

Inactive

Safin

Inactive

Crazy_Eddy

Grease Monk

Intertoob Ninja & Hamster Hunter Extraordinaire

cool_cat

Inactive

Saiyan

Inactive

stalker

kumaranuj

Inactive

greenhorn

viralbug

Inactive

abbY

Inactive

Gaurish

Inactive

Aman27deep

Nitari

Inactive

cool_cat

Inactive

indy1811

thetechmind

Inactive

Gaurish

Inactive