If you want to see how many hops (routes) your request has to go through to get to our server, you can open up a command prompt on your computer (go to start menu, choose Accessories then choose command prompt) This will bring up a black box on your screen which is the command prompt.
In the command prompt type in tracert
www.citybuildergames.com and hit enter. (
the word "tracert" is not a mispelling, it is the traceroute command name)
You will then be shown how your request for each time you want something from our server goes through all the different routers to get there.
For example here is mine: (MY WRITING IS IN RED BELOW)
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\CB>tracert
www.citybuildergames.comTracing route to
www.citybuildergames.com [208.113.162.82]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms cpe-67-49-240-134.dc.res.rr.com [67.49.240.134] (
This is the first request from my server to my ISP)
2 8 ms 7 ms 7 ms 10.52.192.1
3 7 ms 8 ms 7 ms cpe-66-74-96-137.dc.rr.com [66.74.96.137]
4 9 ms 6 ms 8 ms cpe-66-74-96-133.dc.rr.com [66.74.96.133]
5 11 ms 17 ms 11 ms cpe-66-74-96-182.dc.rr.com [66.74.96.182] [
This is the last request of mine that is on my ISP's own network routers]
6 10 ms 10 ms 10 ms xe-9-0-0.edge3.LosAngeles1.Level3.net [4.71.36.105] [
From here on, my request goes to the Level 3.net routing system]
7 12 ms 11 ms 10 ms ae-12-69.car2.LosAngeles1.Level3.net [4.68.20.4]
8 11 ms 10 ms 12 ms INTERNAP-NE.car2.Level3.net [4.71.36.78]
9 11 ms 11 ms 11 ms border20.t4-1-bbnet2.lax.pnap.net [216.52.255.101] [
HERE IT is handed off to another companies routers ]
10 11 ms 11 ms 11 ms newdream-8.border20.lax.pnap.net [216.52.220.146]
HERE IT is handed off to another companies routers ]
11 12 ms 11 ms 14 ms ip-66-33-201-67.dreamhost.com [66.33.201.67] [Here my request finally makes it to my webhost]
12 11 ms 12 ms 11 ms apache2-igloo.frappe.dreamhost.com [208.113.162.82] [
AND HERE THE REQUEST HAS FINALLY MADE IT TO MY SPECIFIC WEB SERFER AT MY WEBHOST THAT OUR WEBSITES SIT ON ]
Trace complete.
tHE INTERESTING THING TO NOTE IS THAT while the time to "hop" around from router to router while in my ISP's network is kept to a maximum of 9 milliseconds, once it gets to Level3.net it goes up to 11 milliseconds, and by hop 11 hit has made it up to 12ms (hop 11 is my webhost).
Try this yourself and see how many hops it takes you to get to our server, it might be interesting to compare.
After you get the data back from the command prompt, you should right click on it, and choose "select all" this will turn the command window white, then press your Enter key, the data from that window is now copied to the windows clipboard, so create a new message in this thread and simply right click in your message body and choose "paste" and it will paste your traceroute to our sever and we can all see how many hops each of us has to go to get to the end server.
The tracert command is usefull when you can't get a website to load up or it's slow. If you find a website that is extremely slow or can't be found etc, then do a tracert to that host and you'll likely see where the hold up, you might get to the 30th hop and it times out, or you might get through all the way to the host, but one of the hops along the way put out a response time of 15,856 milliseconds which would indicate that router is the problem along the way and will need to be reset or fixed. If on the other hand you find that everything is showing low response times, say below 20ms except the last one, then you know it's the host that is causing the problem, and sometimes it may be so bad that one of the routers along the way has completely crapped out, and won't pass any data through it at all, and the tracert will let you know by stopping at that route and saying something about timing out.
When I had road runner cable in Hollywood they had a bad router that was beyond their control, and it kept all of it's hollywood and part of Los Angeles customers off of the internet for about 4 days because they didn't have anybody experienced enough in their organization to reroute the data through another route. We all ended up getting a free months service for their 4 days of downtime because I wrote the better business beaureau as well as our states governor and a bunch of other officials. They finally offered me and everybody else a free mnths credit for their bill which I gladly took although it really didn't make up for leaving everybody without internet for 4 days which we have all become quite accustomed to having.