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.

Non-Tech : CyBerCorp.com -- Ignore unavailable to you. Want to Upgrade?

To: Wes Stevens who wrote (711)	6/4/2000 2:09:00 AM
From: Mark Davis	Read Replies (4) \| Respond to of 1001

Here's a pair of traceroutes done at 2AM Eastern on Saturday. The first is the reverse trace from Cyber to me done using the test.cybercorp.com url. Note the pitiful ping times and packet loss problems. I am on 600k DSL. The second trace done at the SAME TIME, from me to Cyber is fast and golden. I think Cyber needs to address this issue, and promptly. It usually is NOTt this bad during the day, but at the very least , Cyber needs to do something about the extremely intolerant parameters they use in kicking us out of the server. Analysis: Node '45.87.144.41' was found in 15 hops (TTL=116). Connections to HTTP port 80 are being rejected. ---------------------------------------------------------------------------------------------------------------------------------------------- \| Hop \| Err \| IP Address \| Node Name \| Location \| ms \| Graph \| Network \| ---------------------------------------------------------------------------------------------------------------------------------------------- \| 0 \| \| 206.242.238.99 \| - \| * \| \| \| Cyber Corp. \| \| 1 \| \| 206.242.238.2 \| zeus-br1.gw2.aus.noc.cybercorp.com \| Austin, TX, USA \| 0 \| x \| Cyber Corp. \| \| 2 \| \| 157.130.135.221 \| 500.Serial12-1-0.GW1.AUS1.ALTER.NET \| Austin, TX, USA \| 0 \| x \| UUNET Technologies, Inc. \| \| 3 \| 1 \| 152.63.100.110 \| 131.ATM2-0.XR2.DFW4.ALTER.NET \| Dallas, TX, USA \| 58 \| -x---- \| UUNET Technologies, Inc. \| \| 4 \| \| 152.63.96.166 \| 294.at-2-0-0.XR2.DFW9.ALTER.NET \| Dallas, TX, USA \| 68 \| --x---- \| UUNET Technologies, Inc. \| \| 5 \| \| 152.63.98.129 \| 184.atm6-0.br1.dfw9.alter.net \| Dallas, TX, USA \| 0 \| x \| UUNET Technologies, Inc. \| \| 6 \| \| 209.245.240.137 \| atm4-0.core2.Dallas1.Level3.net \| ?Louisville, CO 80027 \| 7 \| x \| Level 3 Communications, LLC \| \| 7 \| \| 209.247.10.101 \| so-6-0-0.mp1.Dallas1.level3.net \| ?Louisville, CO 80027 \| 83 \| --x-- \| Level 3 Communications, LLC \| \| 8 \| 3 \| 209.247.8.30 \| so-0-0-0.mp1.Atlanta1.level3.net \| ?Louisville, CO 80027 \| 107 \| --x-- \| Level 3 Communications, LLC \| \| 9 \| \| 209.247.8.34 \| so-3-0-0.mp2.Atlanta1.level3.net \| ?Louisville, CO 80027 \| 41 \| x- \| Level 3 Communications, LLC \| \| 10 \| 1 \| 209.247.8.38 \| so-1-0-0.mp1.Washington1.level3.net \| ?Louisville, CO 80027 \| 105 \| ---x-- \| Level 3 Communications, LLC \| \| 11 \| 1 \| 209.247.8.41 \| so-3-0-0.mp1.Washington1.level3.net \| ?Louisville, CO 80027 \| 134 \| --x-- \| Level 3 Communications, LLC \| \| 12 \| 3 \| 209.247.8.46 \| so-0-0-0.mp1.Weehawken1.level3.net \| ?Louisville, CO 80027 \| 89 \| x---- \| Level 3 Communications, LLC \| \| 13 \| \| 209.247.8.2 \| so-3-0-0.mp2.Weehawken1.level3.net \| ?Louisville, CO 80027 \| 40 \| x \| Level 3 Communications, LLC \| \| 14 \| 1 \| 209.247.8.6 \| so-1-0-0.mp1.NewYork1.level3.net \| ?Louisville, CO 80027 \| 140 \| ---x-- \| Level 3 Communications, LLC \| \| 15 \| \| 45.87.144.41 \| dsl-64-192-144-41 \| ?Cupertino, CA 95014 \| 160 \| ---x--- \| \| ---------------------------------------------------------------------------------------------------------------------------------------------- NeoTrace Version 2.02 - Shareware (7-18-99) Destination: www.cybercorp.com -#--------------Node Name---------------IP Address------Location-----------RT--High---Low---Avg-Tot---D-Who 1 45.87.144.41 40.601N, 73.945W 0 0 0 0 1 0 2 dsl-64-192-144-41 45.87.144.41 Unknown 1 1 1 1 1 0 3 10.20.43.1 Unknown 19 19 19 19 1 0 4 fe1-2-core2.nyc.tlct.net 64.34.48.97 Unknown 25 25 25 25 1 0 5 166.90.137.209 Unknown 23 23 23 23 1 0 6 gigaethernet5-0.core2.newyork1.level3.net 209.244.12.45 40.750N, 74.000W 21 21 21 21 1 0 7 posip.gw3.nyc4.alter.net 157.130.16.201 40.742N, 73.992W 25 25 25 25 1 0 8 110.atm3-0.xr2.nyc4.alter.net 152.63.21.198 40.742N, 73.992W 24 24 24 24 1 0 9 188.atm3-0.tr2.nyc1.alter.net 146.188.179.38 40.742N, 73.992W 24 24 24 24 1 0 10 104.atm7-0.tr2.hou4.alter.net 146.188.137.105 29.758N, 95.358W 78 78 78 78 1 0 11 196.atm6-0.xr2.hou4.alter.net 146.188.240.177 29.758N, 95.358W 64 64 64 64 1 0 12 192.atm8-0-0.gw1.aus1.alter.net 152.63.100.117 30.267N, 97.742W 67 67 67 67 1 0 13 cybercorp-t3.customer.alter.net 157.130.135.222 Unknown 68 68 68 68 1 0 14 www.cybercorp.com 206.242.238.200 Unknown 62 62 62 62 1 0 -------------------------------------------------------------------------------------------------------- All times in milliseconds (ms), D=Dropped packets ------------------------------------------------------------------------------------------------------------

To: Wes Stevens who wrote (711)	6/4/2000 1:12:00 PM
From: jebj	Respond to of 1001

>Seems the problem with getting the data to you is with a router on the backbone. Can it be fixed?? Sure it can. But the people that control the backbone are the ones that have to fix it not Cyber. All Cyber can do is call up and bitch. YEs, agree - was commenting on the suggest - by both Cyber Software support AND our new arrival on the board - that it is MY ISP that can control the situation. Only Cyber and Cyber's ISP/backbone provider can control problems related to their data coming TO ME. > The only thing else Cyber could do is change isp's and backbones. Agree - and as you mention,that may not solve the problem. But Cyber is not just your usuall customer to their ISP - as we are seeing here and on several threads/boards that traders are on - there has been a very noticable upturn in the number of people having problems with their Cyber data dropping offline. IF this is due to packet loss or net bottleneck delays then it is in Cyber's best interest to raise enough H*** to see that the problem is fixed - there is NOTHING we customers can do about it. >You really have three choices: 1)keep calling and bitching, it may get fixed some day. 2)change isp's 3)change brokers Yup - agree again - but wouldn't it be nice if Cyber would let us know that THEY KNOW the problem exist AND WHAT THEY are doing to solve it? :) >As far as cyber making the software not drop when it is getting bad data, that is an option. They can just ignore a certain number of dropped packets, but a some point it gets dangerous to trade and you are better dropping the connection and trying to get it back up cleaner. Again, agree. >I don't know why Cyber has not answered your questions, but it may be because they have no good answers to give. Certainly is out of character for them - they use to be the unquestioned best company I had ever seen to respond to problems with honest answers in a timely manner. As I mentioned, there seems to be a major change in responding to customer problems of late - right along about the time the problems started to pick up AND the buyout was announced jb