Thanks Brian, I tried traceroute in Windows, didn't work, but with your
tracert command suggestion it works. I get this output:
Tracing route to robertbody.com [22.214.171.124]
over a maximum of 30 hops:
1 * * * Request timed out.
2 8 ms 9 ms 24 ms 126.96.36.199
3 9 ms 9 ms 9 ms 188.8.131.52
4 8 ms 9 ms 10 ms 184.108.40.206
5 9 ms 7 ms 10 ms 220.127.116.11
6 34 ms 33 ms 33 ms gbr1-p40.dvmco.ip.att.net [18.104.22.168]
7 33 ms 32 ms 74 ms tbr1-p013501.dvmco.ip.att.net [22.214.171.124]
8 34 ms 36 ms 35 ms 126.96.36.199
9 32 ms 33 ms 33 ms 188.8.131.52
10 35 ms 33 ms 33 ms p5-0.core01.sjc03.atlas.cogentco.com
11 35 ms 34 ms 35 ms p3-0.core01.sjc01.atlas.cogentco.com
12 80 ms 78 ms 79 ms p14-0.core01.iah01.atlas.cogentco.com
13 * 486 ms 517 ms p4-0.core01.dca01.atlas.cogentco.com
14 643 ms * 487 ms p4-0.core01.phl01.atlas.cogentco.com
15 488 ms 492 ms * p5-0.core02.jfk02.atlas.cogentco.com
16 490 ms 483 ms 487 ms p15-0.core01.jfk02.atlas.cogentco.com
17 487 ms 491 ms 491 ms p12-0.core01.jfk05.atlas.cogentco.com
18 481 ms 481 ms 480 ms Velcom-1433965Ontario.demarc.cogentco.com
19 486 ms 487 ms 490 ms b8000-core-ny.velcom.com [184.108.40.206]
20 * * 481 ms terra.velcom.com [220.127.116.11]
if 486ms starts at entry 13, but is still at 20, can I say that 20 is
playing a part in the horrible delay?
If I run ping:
Reply from 18.104.22.168: bytes=32 time=483ms TTL=46
Reply from 22.214.171.124: bytes=32 time=475ms TTL=42
Reply from 126.96.36.199: bytes=32 time=483ms TTL=42
Reply from 188.8.131.52: bytes=32 time=482ms TTL=42
I get 500ms almost ping, it should be 100 normally. Upload of data is at
4.2K, it should be 40K, and the website host company is telling me they're
pinging my website at 80ms and all is good, but it's not. (host is Velcom)
So can I say from the tracert that they are indeed slowing things down, them
being the last in the chain at 20?
>From: Brian Dessent <[hidden email]>
>Reply-To: [hidden email] >To: [hidden email] >Subject: Re: traceroute command anywhere?
>Date: Sun, 11 Dec 2005 09:40:50 -0800
>Robert Body wrote:
> > Hi, I looked in www.cygwin.com/packages that must be the best way to
> > for what's inside packages right?
>In all honesty it is the very best way, at least if you are only
>interested in finding official Cygwin packages. There are of course
>other repositories of non-official packages.
>If you are using a recent snapshot you can also use "cygcheck -p
><query>" from the command line which queries the same list.
> > and I can't find traceroute which pings a website but also shows how
> > got there, with the 11 or so hits of IPs it does along the way
> > is there a pre-built binary for traceroute out there?
>The "tracert" command is part of windows and should be on any PC. While
>not a Cygwin app it should work fine from within Cygwin. Is there a
>reason this will not work for your needs?
>Alternatively, find the source tarballs of other implementations of the
>the various traceroute utilities (e.g. lft, mtr) and see if they will
>compile. See for example
>Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple >Problem reports: http://cygwin.com/problems.html >Documentation: http://cygwin.com/docs.html >FAQ: http://cygwin.com/faq/ >
> 9 32 ms 33 ms 33 ms 184.108.40.206
> 10 35 ms 33 ms 33 ms p5-0.core01.sjc03.atlas.cogentco.com
> 11 35 ms 34 ms 35 ms p3-0.core01.sjc01.atlas.cogentco.com
> 12 80 ms 78 ms 79 ms p14-0.core01.iah01.atlas.cogentco.com
> 13 * 486 ms 517 ms p4-0.core01.dca01.atlas.cogentco.com
> 14 643 ms * 487 ms p4-0.core01.phl01.atlas.cogentco.com
> if 486ms starts at entry 13, but is still at 20, can I say that 20 is
> playing a part in the horrible delay?
From that output it would appear that there is some serious congestion
somewhere in Cogent's network that is causing your high latency. From
traceroute it's not always possible to tell exactly where or what is
going on, but it does seem clear that there is probably an overloaded or
misconfigured router, or a saturated link, etc.
One thing that you should also be aware of is that the windows version
of traceroute uses ICMP echo - the same kind of packet used by ping. In
fact it's really just doing a number of sequential pings, each with an
increased TTL. Anyway, ping is not always a good tool to judge network
congestion because it is not processed in the same way by routers as
normal IP flows. More here:
Finally, this isn't Cygwin specific so if you want to dig deeper you
should find a newsgroup or mailing list devoted to networking.