I can't reach the whois servers to get POC information for suranet or bbnplanet, thus I spam y'all. A traceroute from escape.com yields: [6:34pm] ~>traceroute knock.ser.bbnplanet.com traceroute to knock.ser.bbnplanet.com (192.239.16.129), 30 hops max, 40 byte packets 1 Escape-gw.escape.com (198.6.71.1) 4.744 ms 7.341 ms 5.56 ms 2 sl-pen-7-S3/1-T1.sprintlink.net (144.228.67.37) 32.182 ms 25.065 ms 29.628 ms 3 sl-pen-1-F0/0.sprintlink.net (144.228.60.1) 31.623 ms 34.746 ms 48.529 ms 4 sl-dc-6-H2/0-T3.sprintlink.net (144.228.10.33) 41.318 ms 35.605 ms 22.101 ms 5 sl-dc-8-F0/0.sprintlink.net (144.228.20.8) 33.347 ms 14.038 ms 16.873 ms 6 sl-mae-e-H2/0-T3.sprintlink.net (144.228.10.42) 31.242 ms 45.161 ms 22.078 ms 7 cpe3-fddi-0.washington.mci.net (192.41.177.180) 27.496 ms 24.759 ms 25.055 ms 8 borderx2-hssi2-0.Washington.mci.net (204.70.74.117) 38.741 ms 18.782 ms 16.053 ms 9 core1-fddi-1.Washington.mci.net (204.70.3.1) 40.078 ms 24.665 ms 24.12 ms 10 border1-fddi-0.Washington.mci.net (204.70.2.2) 27.5 ms 26.435 ms * 11 suranet-wtn-ds3.Washington.mci.net (204.70.56.6) 81.886 ms 30.823 ms 18.012 ms 12 washdc2-br1.bbnplanet.net (128.167.7.8) 20.383 ms 14.938 ms 19.731 ms 13 collegepk-cr9.bbnplanet.net (128.167.212.1) 20.169 ms 21.512 ms 31.437 ms 14 collegepk-cr2.bbnplanet.net (128.167.252.2) 21.481 ms 27.512 ms 41.851 ms 15 knock.sura.net (192.239.16.129) 46.716 ms 30.679 ms 28.82 ms A traceroute from our server yields: millenium:/tmp$ traceroute knock.ser.bbnplanet.com traceroute to knock.ser.bbnplanet.com (192.239.16.129), 30 hops max, 40 byte pas 1 sa-gw.texas.net (204.96.20.1) 2.285 ms 7.453 ms 11.116 ms 2 border1-serial3-0.Dallas.mci.net (204.70.115.41) 42.385 ms 24.505 ms 17.s 3 core1-fddi-0.Dallas.mci.net (204.70.114.17) 15.846 ms 32.539 ms 41.997 ms 4 core1.Washington.mci.net (204.70.4.129) 85.212 ms 98.95 ms 102.686 ms 5 border1-fddi-0.Washington.mci.net (204.70.2.2) 146.24 ms 79.149 ms 104.7s 6 suranet-wtn-ds3.Washington.mci.net (204.70.56.6) 125.784 ms 166.232 ms 1s 7 * * * 8 * * * 9 * * * 10 * * * [ad nauseum]. I'm guessing either a routing problem by MCI, or by suranet. Can anyone out there help me? I've called and e-mail MCI's trouble system, but can't get any information on suranet's POC's. Thanks, Ed Henigin Texas Networking, Inc.