And I forgot to mention - same behavior with BBNplanet. That's AS 1 and AS
174.
Of course, even when we do reach PSInet via UUnet during the day, there's a
300 msec lag at UUnet's last hop before PSInet 
Kevin
Looks from from inside:
access2> traceroute www.psi.net
traceroute to www.psinetus.aa.psiweb.com (38.15.254.104), 30 hops max, 40 byte packets
1 dca1-cpe9-e1-0.atlas.digex.net (205.197.245.1) 4 ms 4 ms 3 ms
2 dca1-core1-fa0-0-0.atlas.digex.net (165.117.17.1) 4 ms 3 ms 4 ms
3 hgr2-core1-h4-0-0.atlas.digex.net (165.117.52.145) 4 ms 5 ms 4 ms
4 dca5-core1-pt3-1-0.atlas.digex.net (165.117.52.142) 9 ms 6 ms 7 ms
5 dca5-core2-fa5-1-0.atlas.digex.net (165.117.56.118) 6 ms 4 ms 7 ms
6 207.238.38.118 (207.238.38.118) 5 ms 6 ms 6 ms
7 38.1.2.25 (38.1.2.25) 89 ms 87 ms 88 ms
8 www.psinetus.aa.psiweb.com (38.15.254.104) 92 ms 87 ms 92 ms
access2> traceroute pair.com
traceroute to pair.com (209.68.1.11), 30 hops max, 40 byte packets
1 dca1-cpe9-e1-0.atlas.digex.net (205.197.245.1) 2 ms 2 ms 2 ms
2 dca1-core5-fa0-0-0.atlas.digex.net (165.117.17.9) 4 ms 2 ms 3 ms
3 pit1-core3-pt1-0-0.atlas.digex.net (165.117.53.254) 10 ms 10 ms 9 ms
4 pit1-core1-fa3-0-0.atlas.digex.net (165.117.53.162) 10 ms 11 ms 10 ms
5 pair-gw.digex.net (206.181.67.137) 10 ms 11 ms 11 ms
6 pair.com (209.68.1.11) 13 ms 12 ms 10 ms
Maybe a route flap?
--Lloyd
Lloyd Taylor -- taylorl@digex.net
Vice President, Technical Operations
DIGEX Web Site Management Group
An Intermedia Company
I'm getting to PSI just fine via both Cerf and BBN...