public inbox for [email protected]
help / color / mirror / Atom feedFrom: Gavin M. Roy <[email protected]>
To: Tom Lane <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: [email protected]
Subject: Re: bt.postgresql.org
Date: Wed, 07 Apr 2004 19:51:10 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
bash-2.05b$ /usr/sbin/traceroute bt.postgresql.org
traceroute to 66.98.251.159 (66.98.251.159), 30 hops max, 40 byte packets
1 homeportal.gateway.2wire.net (172.16.0.1) 1.821 ms 1.129 ms 0.405 ms
2 adsl-67-125-159-254.dsl.irvnca.pacbell.net (67.125.159.254) 31.418
ms 15.318 ms 15.731 ms
3 dist1-vlan60.irvnca.pbi.net (67.114.48.130) 17.754 ms 19.288 ms
17.687 ms
4 bb1-g8-3-0.irvnca.pbi.net (67.114.48.250) 17.992 ms 17.635 ms
17.441 ms
5 bb2-p13-0.lsan03.sbcglobal.net (151.164.190.214) 22.569 ms 18.089
ms 17.692 ms
6 bb1-p6-0.lsan03.sbcglobal.net (151.164.191.161) 29.559 ms 56.814
ms 211.041 ms
7 ex1-p3-0.eqlaca.sbcglobal.net (151.164.241.101) 21.301 ms 20.020
ms 17.810 ms
8 asn2548-allegiance.eqlaca.sbcglobal.net (151.164.248.190) 34.109
ms 19.994 ms 19.522 ms
9 lax3-core1-pos6-0.atlas.algx.net (165.117.200.193) 59.405 ms
61.317 ms 61.134 ms
10 lax10-core1-so-7-0-0-0.atlas.algx.net (165.117.200.122) 19.647 ms
22.857 ms 18.388 ms
11 lax10-core2-so-0-1-0-0.atlas.algx.net (165.117.192.26) 19.483 ms
21.381 ms 19.697 ms
12 san11-core1-so-0-2-0-0.atlas.algx.net (165.117.200.66) 23.548 ms
23.894 ms 23.778 ms
13 san11-core2-so-0-1-0-0.atlas.algx.net (165.117.192.38) 25.015 ms
25.510 ms 23.392 ms
14 dfw10-core1-so-0-2-0-0.atlas.algx.net (165.117.200.45) 55.277 ms
55.843 ms 55.056 ms
15 iah10-core2-so-2-0-0-0.atlas.algx.net (165.117.200.54) 59.137 ms
62.354 ms 60.945 ms
16 iah10-edge1-pos7-0.atlas.algx.net (165.117.192.146) 59.043 ms
58.789 ms 59.089 ms
17 64.245.101.10 (64.245.101.10) 59.239 ms 58.782 ms 59.100 ms
18 ivhou-207-218-223-22.ev1.net (207.218.223.22) 59.081 ms 59.728 ms
59.001 ms
19 gphou-66-98-241-226.ev1.net (66.98.241.226) 59.372 ms 59.275 ms
59.445 ms
20 gphou-66-98-241-125.ev1.net (66.98.241.125) 56.810 ms 55.735 ms
54.885 ms
21 66.98.251.159 (66.98.251.159) 55.389 ms 58.910 ms 57.122 ms
Tom Lane wrote:
>"Gavin M. Roy" <[email protected]> writes:
>
>
>>Both work via SBC DSL in Southern California.
>>
>>
>
>Interesting ... maybe a routing issue? Traceroute shows me
>
>$ traceroute bt.postgresql.org
>traceroute to svr4.postgresql.org (66.98.251.159), 30 hops max, 20 byte packets
> 1 router1.sss.pgh.pa.us (192.168.168.5) 1 ms 1 ms 1 ms
> 2 192.168.252.29 (192.168.252.29) 7 ms 4 ms 4 ms
> 3 gateway.aspStation.net (66.207.128.1) 4 ms 4 ms 4 ms
> 4 130.94.199.253 (130.94.199.253) 6 ms 6 ms 6 ms
> 5 ge-0-3-0.a01.pitbpa05.us.ra.verio.net (129.250.58.113) 7 ms 6 ms 6 ms
> 6 p4-0-1-0.r02.asbnva01.us.bb.verio.net (129.250.16.42) 26 ms 25 ms 28 ms
> 7 p16-1-0-0.r20.asbnva01.us.bb.verio.net (129.250.2.82) 26 ms 26 ms 26 ms
> 8 p16-0-1-1.r21.dllstx09.us.bb.verio.net (129.250.5.34) 58 ms
> p16-0-0-0.r00.atlnga03.us.bb.verio.net (129.250.2.49) 42 ms
> p16-0-1-1.r21.dllstx09.us.bb.verio.net (129.250.5.34) 57 ms
> 9 p16-2-0-0.r01.atlnga03.us.bb.verio.net (129.250.5.17) 46 ms 42 ms
> p16-6-0-0.r02.hstntx01.us.bb.verio.net (129.250.5.101) 64 ms
>10 p16-1-0-2.r20.dllstx09.us.bb.verio.net (129.250.4.194) 66 ms
> ge-6.ev1.hstntx01.us.bb.verio.net (129.250.10.190) 69 ms 69 ms
>11 p16-6-0-0.r00.hstntx01.us.bb.verio.net (129.250.5.5) 69 ms
> gphou-66-98-241-125.ev1.net (66.98.241.125) 66 ms
> p16-6-0-0.r00.hstntx01.us.bb.verio.net (129.250.5.5) 69 ms
>12 ge-2.ev1.hstntx01.us.bb.verio.net (129.250.10.106) 72 ms * 72 ms
>13 * *
> gphou-66-98-241-125.ev1.net (66.98.241.125) 72 ms
>14 * * *
>15 * * *
>(nothing after that...)
>
>What do you get?
>
> regards, tom lane
>
>
view thread (9+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: bt.postgresql.org
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox