Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Osicom(FIBR) -- Ignore unavailable to you. Want to Upgrade?

To: Brian who wrote (9110)	1/12/1999 7:42:00 PM
From: Brian	Read Replies (1) \| Respond to of 10479

Gruns over on raging bull produced a trace route for the Osicom web site at 1:17 p.m. (see below) WOW, same day RESULTS. Check out osicom.com now and notice the difference. Thank you Gruns. <<e: Osicom Site Performance I did a trace route from my office (using an SDSL connection at 1040 Kb/s) to Osicom.com. Below please find the results. My comments are preceeded by asterisks explaining what these things mean. A trace route command (tracert under most OSes) counts the hops between end points and record the time spent "hopping." I am in beverly hills and it took 16 hops to get to Osicom. Which, in theory, makes no sense since they are in Santa Monica (4 miles away). But herein lies the details. See below. 1 2 ms 1 ms 4 ms gate.titan-ca.com [209.250.123.193] ** My office router * 2 18 ms 16 ms 16 ms gate.pictureframer.com [209.250.123.177] 3 9 ms 8 ms 8 ms exodus-gw2.irv.ienet.com [209.185.207.82] 4 50 ms 8 ms 8 ms irca-01-f1-0-0-vl900.core.exodus.net [209.67.128.2] 5 7 ms 8 ms 8 ms bbr02-p1-0.irvn01.exodus.net [209.185.249.18] 6 88 ms 88 ms 88 ms bbr02-p00x01.hrnd01.exodus.net [209.185.9.205] 7 88 ms 89 ms 88 ms dcr01-p1-0-0.hrnd01.exodus.net [209.185.249.33] 8 88 ms 88 ms 88 ms ibr02-f5-0-0.hrnd01.exodus.net [209.185.249.161] * Last hop for my ISP / upstream provider *** 9 117 ms 150 ms 131 ms exodus-px.heva.bbnplanet.com [209.1.169.246] * 1st hop to BBN Planet (aka GTE) *** 10 101 ms 103 ms 103 ms p2-0.vienna1-nbr2.bbnplanet.net [4.0.5.49] 11 116 ms 112 ms 119 ms p4-1.washdc3-ba1.bbnplanet.net [4.24.4.189] 12 138 ms 165 ms 166 ms p1-0.washdc3-ba2.bbnplanet.net [4.24.4.102] 13 106 ms 111 ms 118 ms p2-3.cambridge1-nbr1.bbnplanet.net [4.0.5.42] 14 118 ms 102 ms 110 ms p3-0.cambridge1-nbr2.bbnplanet.net [4.0.5.18] 15 150 ms 149 ms 132 ms p0-0-0.cambridge1-cr21.bbnplanet.net [4.0.1.210] * You'll notice that I had to go through both the DC and Cambridge NAPS on BBN Planet before hitting the Osi server. No reason to go through so many hops on GTEs backbone other than bad network management. Also note that the seek times (listed in miliseconds) are not excessive. Anything over 400 ms is bad. *** 16 116 ms 107 ms 110 ms s1.osicom.bbnplanet.net [206.34.74.14] * BBN Planet is hosting the Osi web page on their server. **** 17 141 ms 166 ms 216 ms osicom.com [131.143.8.10] GTE (great telephone experiment) bought BBN Planet about 18 months ago. BBN was one of the first ISPs. They are a tier 1 ISP and had a good product. I think GTE has corrupted them and ruined their performance (I have GTE at home via ISDN) and it's slow too. It's not the web page or Osi's connection to the Internet in Santa Monica, but BBN (nee GTEs) network backbone. They could use a few Gigamuxes I am sure>>