SI
SI
discoversearch

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 : Quote.com QCharts -- Ignore unavailable to you. Want to Upgrade?


To: Richard Estes who wrote (4738)12/5/1999 9:33:00 PM
From: -  Respond to of 17977
 
Hi Richard, Welcome to 'the wall', man -- you've got plenty of company here. The sport of the thread has been, beat up on the whiners and maintain deniability :)) Actually, this is understandable since those not experiencing problems, who are QC fans, are going to naturally take offense to what they perceive as unjustified complaining. Now that the issue is proven / out in the open and owned up to by Quote.com, everyone should be able to chill out from the thread-war while Quote.com puts a solution in place, as their resources/priorities permit.

An example - when the guy complained on onelist Friday, I had been having problems (intermittent charts) all day (trying to pull up NASDAQ charts), and like him, QCharts was giving me zippo in the way of charts at the time. So, I'm definitely having more problems than you are. Such is the 'luck of the draw' when servers have limited capacity.

Yes, you're correct -- I think you, Matt and some others are just some of the lucky ones. I'm going to do a little bit of diagnostic homework this week with the help of my ever-so-competent friends at my Mainstreet/Walltech ISP, we ran the following trace this evening (below) to the main Quote.com site. This week, if the QC servers are acting up, I will run a similar tracert diagnostic directly to the QCharts server from my workstation and report in on the results.

Regards and good trading, -Steve

========

The www.quote.com site looks like this from mainstreet's router:

sj02-1800>trace www.quote.com
Translating "www.quote.com"...domain server (207.5.0.50) [OK]
Type escape sequence to abort.
Tracing the route to www.quote.com (204.71.196.2)

1 bbn.mainstreet.net (207.5.1.254) 0 msec 0 msec 8 msec
2 sj02.mainstreet.net (207.5.0.81) 0 msec 8 msec 4 msec
3 fddi3-0.cr1.SJC.globalcenter.net (198.32.136.58) 8 msec 0 msec 0 msec
4 pos5-0-155M.cr1.SJC.gblx.net (206.132.150.61) [AS 3549] 4 msec 8 msec 4 msec
5 pos4-0-622M.cr1.NUQ.gblx.net (206.132.254.2) [AS 3549] 4 msec 4 msec 4 msec
6 pos4-0-0-155M.br1.NUQ.gblx.net (206.132.160.26) [AS 3549] 8 msec 4 msec 4 msec
7 fe-globalcenter.quote.com (206.251.6.74) [AS 3549] 4 msec 4 msec 12 msec
8 www.quote.com (204.71.196.2) [AS 11803] 4 msec 4 msec 4 msec

>From my ps4.walltech.com system (over a T1):

$ traceroute www.quote.com
traceroute to www.quote.com (204.71.196.2), 30 hops max, 40 byte packets
1 207.5.79.6 (207.5.79.6) 1.902 ms 1.480 ms 1.422 ms
2 rtr0-065.mainstreet.net (207.5.0.65) 7.274 ms 16.263 ms 4.941 ms
3 fddi3-0.cr1.SJC.globalcenter.net (198.32.136.58) 5.885 ms 6.823 ms 7.120 ms
4 pos4-0-155M.cr1.SJC.gblx.net (206.132.150.93) 5.831 ms 5.573 ms 18.367 ms
5 pos4-0-622M.cr1.NUQ.gblx.net (206.132.254.2) 11.803 ms 7.780 ms 6.085 ms
6 pos4-0-0-155M.br1.NUQ.gblx.net (206.132.160.26) 10.821 ms 19.016 ms 8.883 ms
7 fe-globalcenter.quote.com (206.251.6.74) 8.894 ms 6.895 ms 6.741 ms
8 www.quote.com (204.71.196.2) 24.751 ms 7.410 ms 7.915 ms

An average of 4ms from Mainstreet to www.quote.com and 7ms from Walltech's T1. Once we have the IP address of the actual server you are connecting to at quote.com, from the NT prompt we'll just run a trace to www.server.com and watch the results to see where packets are dropping and what the round-trip times are.

We have always had a zero-percent packet loss policy and since we dropped the ISDN and Modem POPs and a few Frame Relay customers, we are sitting here with even more bandwidth than before. Heck, we had plenty before the dropping of those POPs...

Remember, it takes a village to pass a packet :-)

==========