Monday, July 31, 2006

How many hops to get your site?

Sometimes if we are going to a website, it takes a long time until the page is being loaded.
Why does this happen? It's a many reason to explain this. I'll describe one. The hops. Yes, the hops.

More and more a hops you get, more and more a time to take.
If you are a Windows users you can using tracert command and if you are a Linux users you can using traceroute command.

Type this command below on your DOS prompt :

tracert asepandria.blogspot.com

or on your Linux terminal type :

traceroute asepandria.blogspot.com

And then the DOS prompt or Linux terminal would echoing the hops of your destination site. For example, it would echoing something like this :

Tracing route to blogspot.blogger.com [66.102.15.101]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.16.1.3
2 <1 ms <1 ms <1 ms ws2.yogya-ho.melsa.net.id [202.138.229.195]
3 10 ms 7 ms 10 ms fe3-1-gw3-bdg.melsa.net.id [202.138.237.129]
4 16 ms 13 ms 7 ms fe0-3-gw-bdg.melsa.net.id [202.138.225.81]
5 74 ms 16 ms 64 ms fe1-1-gw-jkt.melsa.net.id [202.138.225.26]
6 * 91 ms 112 ms ip-240049 [202.93.240.49]
7 98 ms * 17 ms 202.93.240.18
8 44 ms 57 ms 29 ms 202.152.164.185
9 18 ms 22 ms 96 ms 202.93.46.189
10 * * * Request timed out.
11 304 ms 324 ms 230 ms 12.118.124.89
12 291 ms 279 ms 335 ms tbr1-p012101.la2ca.ip.att.net [12.122.2.250]
13 235 ms 312 ms 391 ms ggr2-p310.la2ca.ip.att.net [12.123.222.25]
14 374 ms 249 ms 269 ms so-8-1.car4.LosAngeles1.Level3.net [4.68.127.133]
15 241 ms 302 ms 266 ms ae-2-56.bbr2.LosAngeles1.Level3.net [4.68.102.161]
16 229 ms 313 ms 280 ms as-2-0.bbr2.SanJose1.Level3.net [4.68.128.157]
17 308 ms 306 ms 237 ms ae-22-52.car2.SanJose1.Level3.net [4.68.123.48]
18 251 ms 278 ms 403 ms unknown.Level3.net [209.247.202.218]
19 267 ms 234 ms 254 ms 66.249.94.227
20 346 ms 288 ms 242 ms 72.14.233.123
21 287 ms 237 ms 248 ms 66.102.15.101

Trace complete.

No comments: