Forum Feedback Please submit ping and tracert data

Status
Not open for further replies.
Safin

Safin

Inactive
Forerunner
Founding Member
Hello Guys,
Need help in troubleshooting why the server is responding slowly.
Can you all please submit tracert and ping data for techenclave.

Please go to start->run-> type cmd

then do

ping techenclave.com

after it completes, do

tracert techenclave.com
I need atleast 10 entries from different locations. Thanks.
 
Pinging techenclave.com [207.58.182.106] with 32 bytes of data:

Reply from 207.58.182.106: bytes=32 time=307ms TTL=49

Reply from 207.58.182.106: bytes=32 time=298ms TTL=49

Reply from 207.58.182.106: bytes=32 time=306ms TTL=49

Reply from 207.58.182.106: bytes=32 time=305ms TTL=49

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 = 307ms, Average = 304ms

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

Tracing route to techenclave.com [207.58.182.106]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms segment-124-7.sify.net [124.7.41.1]

2 <1 ms <1 ms <1 ms 10.1.60.25

3 <1 ms <1 ms <1 ms segment-124-7.sify.net [124.7.237.210]

4 1 ms <1 ms <1 ms lan-202-144-74-118.sify.net [202.144.74.118]

5 <1 ms <1 ms <1 ms 119.227.4.86

6 35 ms 35 ms 35 ms segment-124-7.sify.net [124.7.187.98]

7 232 ms * 232 ms segment-124-7.sify.net [124.7.187.126]

8 234 ms 234 ms 232 ms segment-124-7.sify.net [124.7.187.78]

9 235 ms 233 ms 233 ms 12.116.103.61

10 235 ms 234 ms 243 ms tbr1.la2ca.ip.att.net [12.122.104.18]

11 233 ms * 233 ms 12.127.3.217

12 230 ms 227 ms 226 ms 192.205.33.218

13 298 ms 292 ms 292 ms cr1-bundle-pos1.Washington.savvis.net [204.70.197.25]

14 291 ms * 293 ms msr1-tengig-0-0-0-0.Washington.savvis.net [204.70.196.94]

15 290 ms 289 ms 289 ms er1-gig-3-0-0.dck.savvis.net [204.70.203.2]

16 290 ms 290 ms 290 ms corporate-executive-board.Washington.savvis.net

[208.174.119.98]

17 306 ms 306 ms 306 ms sc-smv2977.servint.net [209.50.237.14]

18 307 ms 312 ms 307 ms vps.techenclave.com [207.58.182.106]

Trace complete.
 
Here is my Data. Using Hathway connection from Pune.
pingtracertsz0.jpg
 
E:\>tracert Indian Technology and Computer Discussion Portal - TechEnclave

Tracing route to techenclave.com [207.58.182.106]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.24.198.9

2 <1 ms <1 ms <1 ms 172.24.198.1

3 <1 ms <1 ms 1 ms 172.31.145.13

4 <1 ms 1 ms 1 ms 172.31.66.66

5 * * * Request timed out.

6 * * * Request timed out.

7 * * * Request timed out.

8 * * * Request timed out.

9 * * * Request timed out.

10 * * ^C

E:\>ping Indian Technology and Computer Discussion Portal - TechEnclave

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

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 207.58.182.106:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 
Data from Mumbai:

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

Reply from 207.58.182.106: bytes=32 time=284ms TTL=51
Reply from 207.58.182.106: bytes=32 time=284ms TTL=50
Reply from 207.58.182.106: bytes=32 time=284ms TTL=51
Reply from 207.58.182.106: bytes=32 time=284ms TTL=51

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

C:\Documents and Settings\dkrishna>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 128.88.211.1
2 <1 ms <1 ms <1 ms 220.227.71.115
3 8 ms 1 ms 2 ms 220.227.102.82
4 12 ms 149 ms 63 ms 220.224.185.50
5 2 ms 2 ms 2 ms 220.224.185.45
6 2 ms 2 ms 2 ms so-1-1-0.0.cjr01.mmb003.flagtel.com [62.216.145.57]

7 2 ms 2 ms 2 ms so-1-1-0.0.cjr01.mmb003.flagtel.com [62.216.145.57]

8 71 ms 71 ms 71 ms ge-0-2-0.0.pjr02.mmb004.flagtel.com [85.95.25.70]

9 71 ms 71 ms 71 ms ge-1-1-0.0.pjr01.mmb004.flagtel.com [85.95.25.73]

10 71 ms 71 ms 71 ms so-1-0-0.0.ejr03.sin001.flagtel.com [85.95.25.98]

11 70 ms 71 ms 70 ms ge-1-0-0.0.ejr02.sin001.flagtel.com [62.216.137.154]

12 71 ms 71 ms 71 ms 202.79.197.7
13 358 ms 351 ms 408 ms 217.239.41.6
14 350 ms 350 ms 353 ms 62.153.203.126
15 284 ms 284 ms 284 ms 209.50.254.66
16 284 ms 284 ms 284 ms sc-smv2977.servint.net [209.50.237.14]
17 284 ms 284 ms 284 ms vps.techenclave.com [207.58.182.106]

Trace complete.
 
Here you go (Delhi) -

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

Reply from 207.58.182.106: bytes=32 time=290ms TTL=45
Reply from 207.58.182.106: bytes=32 time=285ms TTL=45
Reply from 207.58.182.106: bytes=32 time=285ms TTL=45
Reply from 207.58.182.106: bytes=32 time=285ms TTL=45

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

C:\Users\toshiba>tracert techenclave.com

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

1 2 ms 1 ms 1 ms segment-210-214-186-1.maa.sify.net [210.214.186.
1]
2 2 ms 2 ms 2 ms 210.18.2.10.sify.net [210.18.2.10]
3 219 ms 217 ms 218 ms 210.18.7.131.sify.net [210.18.7.131]
4 217 ms * 217 ms 119.227.4.25
5 217 ms 216 ms 220 ms 119.227.4.9
6 216 ms 216 ms 216 ms 119.227.4.62
7 216 ms 216 ms 217 ms segment-124-7.sify.net [124.7.187.2]
8 216 ms 216 ms 216 ms segment-124-7.sify.net [124.7.187.6]
9 215 ms 216 ms 216 ms segment-124-7.sify.net [124.7.187.30]
10 280 ms 281 ms 281 ms if-13-0.core2.NTO-NewYork.as6453.net [216.6.97.3
7]
11 281 ms 289 ms 280 ms cr2-pos-0-8-0-3.nyr.savvis.net [208.173.129.29]

12 283 ms 281 ms 281 ms cr1-pos-0-0-0-0.Washington.savvis.net [204.70.19
2.1]
13 285 ms 285 ms 285 ms msr1-tengig-0-0-0-0.Washington.savvis.net [204.7
0.196.94]
14 286 ms 287 ms 287 ms er1-gig-3-0-0.dck.savvis.net [204.70.203.2]
15 285 ms 286 ms 285 ms corporate-executive-board.Washington.savvis.net
[208.174.119.98]
16 284 ms 285 ms 289 ms sc-smv2977.servint.net [209.50.237.14]
17 285 ms 288 ms 285 ms vps.techenclave.com [207.58.182.106]

Trace complete.
 
Chennai

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

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

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

Reply from 207.58.182.106: bytes=32 time=281ms TTL=56
Reply from 207.58.182.106: bytes=32 time=281ms TTL=56
Reply from 207.58.182.106: bytes=32 time=281ms TTL=56
Reply from 207.58.182.106: bytes=32 time=281ms 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 = 281ms, Maximum = 281ms, Average = 281ms
C:\Documents and Settings\Chhangte>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 192.168.1.254
2 26 ms 25 ms 25 ms ABTS-TN-dynamic-001.48.164.122.airtelbroadband.i
n [122.164.48.1]
3 26 ms 24 ms 25 ms 61.246.253.225
4 24 ms 24 ms 24 ms 61.95.240.129
5 24 ms 25 ms 24 ms 125.21.167.29
6 149 ms 153 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 266 ms 279 ms 264 ms 217.239.41.6
9 265 ms 265 ms 264 ms 62.153.203.126
10 302 ms 277 ms 285 ms 209.50.254.66
11 281 ms 296 ms 280 ms sc-smv2977.servint.net [209.50.237.14]
12 280 ms 281 ms 281 ms vps.techenclave.com [207.58.182.106]

Trace complete.

C:\Documents and Settings\Chhangte>
 
Posting from Pune over BSNL broadband:

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

Reply from 207.58.182.106: bytes=32 time=323ms TTL=49

Reply from 207.58.182.106: bytes=32 time=322ms TTL=49

Reply from 207.58.182.106: bytes=32 time=379ms TTL=49

Reply from 207.58.182.106: bytes=32 time=351ms TTL=49

Ping statistics for 207.58.182.106:

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

Approximate round trip times in milli-seconds:

Minimum = 322ms, Maximum = 379ms, Average = 343ms
Click to expand...

Tracing route to techenclave.com [207.58.182.106]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1

2 46 ms 30 ms 32 ms 59.95.56.1

3 * * * Request timed out.

4 * * * Request timed out.

5 64 ms 73 ms 61 ms 125.17.12.9

6 74 ms 58 ms 64 ms 125.21.167.29

7 323 ms 324 ms 327 ms pal2-bharti-1.pal.seabone.net [213.144.181.85]

8 319 ms 318 ms 319 ms dtag-1-mil51.seabone.net [195.22.192.6]

9 316 ms 323 ms 316 ms 217.239.41.6

10 326 ms 323 ms 317 ms 62.153.203.126

11 322 ms 321 ms 322 ms 209.50.254.66

12 323 ms 321 ms 322 ms sc-smv2977.servint.net [209.50.237.14]

13 327 ms 322 ms 323 ms vps.techenclave.com [207.58.182.106]

Trace complete.
Click to expand...
 
Reply from 207.58.182.106: bytes=32 time=227ms TTL=44
Reply from 207.58.182.106: bytes=32 time=227ms TTL=44
Reply from 207.58.182.106: bytes=32 time=227ms TTL=44
Reply from 207.58.182.106: bytes=32 time=227ms TTL=44

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

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

1 * * * Request timed out.
2 <1 ms <1 ms <1 ms 59.165.9.65.man-static.vsnl.net.in [59.165.9.65]

3 <1 ms <1 ms <1 ms 172.31.152.33
4 1 ms 1 ms 1 ms 172.31.80.2
5 1 ms 1 ms 1 ms 172.31.80.21
6 * * * Request timed out.
7 22 ms 21 ms 22 ms 59.163.59.37.static.vsnl.net.in [59.163.59.37]
8 213 ms 214 ms 214 ms 59.163.55.206.static.vsnl.net.in [59.163.55.206]

9 222 ms 223 ms 222 ms if-2-11.mse1.NW8-NewYork.as6453.net [209.58.75.3
7]
10 222 ms 222 ms 223 ms if-7-0.core1.NTO-NewYork.as6453.net [216.6.82.61
]
11 222 ms 221 ms 221 ms if-4-0-0.core2.NTO-NewYork.as6453.net [216.6.82.
66]
12 222 ms 222 ms 222 ms cr2-pos-0-8-0-3.nyr.savvis.net [208.173.129.29]

13 228 ms 228 ms 227 ms cr1-pos-0-0-0-0.Washington.savvis.net [204.70.19
2.1]
14 230 ms 232 ms 231 ms msr1-tengig-0-0-0-0.Washington.savvis.net [204.7
0.196.94]
15 227 ms 227 ms 227 ms er1-gig-3-0-0.dck.savvis.net [204.70.203.2]
16 227 ms 227 ms 227 ms 208.174.119.98
17 228 ms 228 ms 227 ms sc-smv2977.servint.net [209.50.237.14]
18 227 ms 227 ms 227 ms vps.techenclave.com [207.58.182.106]

Trace complete.
 
Nagpur, Bsnl..

C:\Users\------>ping techenclave.com

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

Reply from 207.58.182.106: bytes=32 time=332ms TTL=51

Reply from 207.58.182.106: bytes=32 time=402ms TTL=51

Reply from 207.58.182.106: bytes=32 time=323ms TTL=51

Reply from 207.58.182.106: bytes=32 time=345ms TTL=51

Ping statistics for 207.58.182.106:

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

Approximate round trip times in milli-seconds:

Minimum = 323ms, Maximum = 402ms, Average = 350ms

C:\Users\----->tracert techenclave.com

Tracing route to techenclave.com [207.58.182.106]

over a maximum of 30 hops:

1 24 ms 25 ms 26 ms 59.95.64.1

2 * * * Request timed out.

3 56 ms * 46 ms 218.248.255.26

4 98 ms 102 ms 97 ms 203.197.20.102.static.vsnl.net.in [203.197.20.10

2]

5 119 ms 100 ms 96 ms 202.54.2.161

6 242 ms 248 ms 300 ms 59.163.55.198.static.vsnl.net.in [59.163.55.198]

7 324 ms 303 ms 310 ms if-2-11.mse1.NW8-NewYork.as6453.net [209.58.75.3

7]

8 327 ms 305 ms 310 ms if-7-0.core1.NTO-NewYork.as6453.net [216.6.82.61

]

9 327 ms 305 ms 311 ms if-4-0-0.core2.NTO-NewYork.as6453.net [216.6.82.

66]

10 337 ms 302 ms 297 ms cr2-pos-0-8-0-3.nyr.savvis.net [208.173.129.29]

11 322 ms 401 ms 305 ms cr2-tengig-0-7-0-0.Washington.savvis.net [204.70

.196.106]

12 325 ms 310 ms 301 ms msr1-tengig-0-3-0-0.Washington.savvis.net [204.7

0.196.98]

13 323 ms 311 ms 296 ms er1-gig-3-0-0.dck.savvis.net [204.70.203.2]

14 317 ms 296 ms 313 ms corporate-executive-board.Washington.savvis.net

[208.174.119.98]

15 334 ms 309 ms 293 ms sc-smv2977.servint.net [209.50.237.14]

16 313 ms 305 ms 312 ms vps.techenclave.com [207.58.182.106]

Trace complete.
Click to expand...
 
Pinging techenclave.com [207.58.182.106] with 32 bytes of data:

Reply from 207.58.182.106: bytes=32 time=336ms TTL=54
Reply from 207.58.182.106: bytes=32 time=340ms TTL=54
Reply from 207.58.182.106: bytes=32 time=358ms TTL=54
Reply from 207.58.182.106: bytes=32 time=349ms TTL=54

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

1 <1 ms <1 ms <1 ms local.gateway [192.168.1.1]
2 12 ms 11 ms 11 ms **.**.***.*
3 * * * Request timed out.
4 * * * Request timed out.
5 50 ms 49 ms 51 ms AES-Static-005.131.17.125.airtel.in [125.17.131.
5]
6 49 ms 49 ms 52 ms 125.21.167.25
7 182 ms 184 ms 187 ms pal2-bharti-1.pal.seabone.net [213.144.181.85]
8 223 ms 223 ms 229 ms dtag-2-mil51.seabone.net [195.22.192.10]
9 297 ms 299 ms 295 ms 217.239.41.6
10 332 ms 332 ms 336 ms 62.153.203.126
11 353 ms 352 ms 355 ms 209.50.254.66
12 328 ms 328 ms 328 ms sc-smv2977.servint.net [209.50.237.14]
13 411 ms 401 ms 371 ms vps.techenclave.com [207.58.182.106]

Trace complete.
Click to expand...

ISP BSNL Dataone Location : Surat, Gujarat
 
Mumbai, Reliance Broadnet wimax.

C:\Users\Shripad>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=320ms TTL=52

Reply from 207.58.182.106: bytes=32 time=319ms TTL=52

Reply from 207.58.182.106: bytes=32 time=329ms TTL=52

Reply from 207.58.182.106: bytes=32 time=317ms 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 = 317ms, Maximum = 329ms, Average = 321ms

C:\Users\Shripad>tracert Indian Technology and Computer Discussion Portal - TechEnclave

Tracing route to techenclave.com [207.58.182.106]

over a maximum of 30 hops:

1 32 ms 39 ms 39 ms 124.125.EDITED ON PURPOSE.HEHE

2 38 ms 39 ms 39 ms 220.224.140.141

3 37 ms 40 ms 39 ms 220.224.140.98

4 38 ms 39 ms 39 ms so-1-1-0.0.cjr01.mmb003.flagtel.com [62.216.145.

57]

5 37 ms 39 ms 39 ms so-1-1-0.0.cjr01.mmb003.flagtel.com [62.216.145.

57]

6 108 ms 109 ms 109 ms ge-0-2-0.0.pjr02.mmb004.flagtel.com [85.95.25.70

]

7 108 ms 109 ms 119 ms ge-1-1-0.0.pjr01.mmb004.flagtel.com [85.95.25.73

]

8 98 ms 109 ms 100 ms so-1-0-0.0.ejr03.sin001.flagtel.com [85.95.25.98

]

9 99 ms 109 ms 99 ms ge-1-0-0.0.ejr02.sin001.flagtel.com [62.216.137.

154]

10 108 ms 109 ms 109 ms 202.79.197.7

11 367 ms 370 ms 369 ms 217.239.41.6

12 368 ms 369 ms 369 ms 62.153.203.126

13 317 ms 321 ms 318 ms 209.50.254.70

14 317 ms 318 ms 319 ms sc-smv2977.servint.net [209.50.237.14]

15 318 ms 319 ms 319 ms vps.techenclave.com [207.58.182.106]

Trace complete.
Click to expand...

tttttttttttttttttttttttttttttttttttttttttttttt
 
AIRTEL , COIMBATORE , TAMILNADU

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=311ms TTL=55

Reply from 207.58.182.106: bytes=32 time=310ms TTL=55

Reply from 207.58.182.106: bytes=32 time=312ms TTL=55

Reply from 207.58.182.106: bytes=32 time=314ms 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 = 310ms, Maximum = 314ms, Average = 311ms

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 unknown [192.168.11.1]

2 1 ms 1 ms 1 ms 192.168.1.1

3 62 ms 76 ms 59 ms ABTS-TN-dynamic-001.48.164.122.airtelbroadband.i

n [122.164.48.1]

4 57 ms 59 ms 58 ms 61.246.253.225

5 57 ms 60 ms 60 ms 61.95.240.129

6 58 ms 63 ms 55 ms 125.21.167.29

7 185 ms 183 ms 180 ms pal2-bharti-2.pal.seabone.net [195.22.197.121]

8 251 ms 249 ms 249 ms dtag-2-mil51.seabone.net [195.22.192.10]

9 306 ms 299 ms 300 ms 217.239.41.6

10 302 ms 299 ms 300 ms 62.153.203.126

11 314 ms 313 ms 313 ms 209.50.254.66

12 321 ms 318 ms 318 ms sc-smv2977.servint.net [209.50.237.14]

13 311 ms 321 ms 311 ms vps.techenclave.com [207.58.182.106]

Trace complete.
 
Bangalore, Airtel Broadband

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=306ms TTL=53
Reply from 207.58.182.106: bytes=32 time=303ms TTL=53
Reply from 207.58.182.106: bytes=32 time=303ms 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 = 303ms, Maximum = 318ms, Average = 307ms
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 192.168.1.1
2 75 ms 27 ms 52 ms ABTS-KK-Dynamic-001.0.167.122.airtelbroadband.in [122.167.0.1]
3 27 ms 32 ms 28 ms ABTS-KK-Static-173.32.166.122.airtelbroadband.in [122.166.32.173]
4 32 ms 38 ms 27 ms ABTS-KK-Static-009.32.166.122.airtelbroadband.in [122.166.32.9]
5 28 ms 28 ms 28 ms 122.175.255.29
6 69 ms 122 ms 36 ms 125.21.167.25
7 171 ms 162 ms 217 ms pal2-bharti-1.pal.seabone.net [213.144.181.85]
8 213 ms 202 ms 202 ms dtag-2-mil51.seabone.net [195.22.192.10]
9 279 ms 313 ms 276 ms 217.239.41.6
10 315 ms 305 ms 306 ms 62.153.203.126
11 406 ms 430 ms * 209.50.254.66
12 325 ms 299 ms 299 ms sc-smv2977.servint.net [209.50.237.14]
13 318 ms 307 ms 308 ms vps.techenclave.com [207.58.182.106]

Trace complete.
 
BSNL,Bhopal

Ping-

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

Reply from 207.58.182.106: bytes=32 time=326ms TTL=49
Reply from 207.58.182.106: bytes=32 time=322ms TTL=49
Reply from 207.58.182.106: bytes=32 time=322ms TTL=49
Reply from 207.58.182.106: bytes=32 time=324ms TTL=49

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

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

1 <1 ms <1 ms <1 ms 10.0.0.1
2 2 ms 1 ms 1 ms 192.168.1.1
3 * 43 ms 43 ms 117.199.16.1
4 46 ms 44 ms 44 ms 218.248.170.134
5 * 60 ms 58 ms 218.248.255.18
6 86 ms 84 ms 85 ms 125.17.0.157
7 90 ms 87 ms 87 ms 125.21.167.25
8 222 ms 224 ms 219 ms pal2-bharti-1.pal.seabone.net [213.144.181.85]
9 263 ms 262 ms 263 ms dtag-1-mil51.seabone.net [195.22.192.6]
10 334 ms 356 ms 335 ms 217.239.41.6
11 360 ms 363 ms 364 ms 62.153.203.126
12 * 358 ms 359 ms 209.50.254.70
13 359 ms 362 ms 362 ms sc-smv2977.servint.net [209.50.237.14]
14 357 ms 359 ms 356 ms vps.techenclave.com [207.58.182.106]

Trace complete.
 
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=50 time=279 ms

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

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

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

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

--- techenclave.com ping statistics ---

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

rtt min/avg/max/mdev = 276.551/277.986/279.444/1.358 ms

traceroute to techenclave.com (207.58.182.106), 30 hops max, 40 byte packets

1 192.168.1.100 (192.168.1.100) 6.393 ms 12.095 ms *

2 * * *

3 * * *

4 * * *

5 * * *

6 * 59.163.55.194.static.vsnl.net.in (59.163.55.194) 260.224 ms *

7 * * *

8 * * *

9 * * *

10 * * *

11 cr2-tengig-0-7-0-0.Washington.savvis.net (204.70.196.106) 347.261 ms 351.686 ms *

12 msr1-tengig-0-3-0-0.Washington.savvis.net (204.70.196.98) 281.026 ms 282.778 ms 280.895 ms

13 * er1-gig-3-0-0.dck.savvis.net (204.70.203.2) 276.905 ms 278.192 ms

14 corporate-executive-board.Washington.savvis.net (208.174.119.98) 277.561 ms 278.748 ms 276.896 ms

15 sc-smv2977.servint.net (209.50.237.14) 280.419 ms 277.789 ms 279.258 ms

16 vps.techenclave.com (207.58.182.106) 278.129 ms 277.402 ms 278.242 ms

BSNL Trivandrum :)
 
Status
Not open for further replies.
Top Bottom