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.
SI - Site Forums : Silicon Investor - Welcome New SI Members!
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: justaninvestor who wrote (3151)11/2/1998 8:47:00 PM
From: SI Brad  Read Replies (2) of 32871
 
This is a response I got from our ISP regarding your @home slowness. It sound's like @home could be doing more to circumvent the public access points by working directly with Sprint. In any case, it's beyond our control to do anything to improve the situation.

- Brad

===================
Brad,

We recently had a similar issue to this with another customer. The
problem that you describe is similar to the problem that another customer was having. I have enclosed the information that a sprint engineer provided to us. If you have any more questions or concerns please let us know.

Thanks,
Andrew

from sprint:

Subject: trace route to 209.125.179.0/24

There are really 2 issues with this.

First is that the the public peering points, Mae-west and east, are
congested and Sprintlink cannot guarantee through put to peers.

Second is that at some point in Home.net, home.net doesn't send the
return icmp echoes back through Mae-east to Sprintlink. Probably after
it reaches w1-fe0-0-100bt.rdc1.nj.home.net, which is physically
located in New Jersey, this router routes traffic destined for
Sprintlink through Mae-East. A trace route from the 209.125.179.0/24
network will confirm this. You would also see the trace route times
degrade once you left Home.net and transitted over Mae-East and it
would appear that Sprintlink was the culprit for the latency. In
reality, it is the public peering points that are over loaded and
Sprintlink and Home.net networks are clean.
The only real fix for this type of problem is to have private
peering set up between Sprint and Home networks. That is an issue for
the legal departments of both networks.

Thank you,
Orin Reams
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  

HomeMailHotSubjectMarksPeopleMarksKeepersSettings
Terms Of UseContact UsCopyright/IP PolicyPrivacy PolicyAbout UsFAQAdvertise on SI
© 2025 Knight Sac Media.  Data provided by Twelve Data, Alpha Vantage, and CityFALCON News