🚀 go-pugleaf

Stephen P. Potter (spp@beach.cis.ufl.edu) wrote:
: In article <D39y3A.9Kn@emi.net> stymie@emi.net (Mike Wertheimer) writes:
:    Thanks for the welcome.  We are currently using a 56k sprintlink connection.

: I'm sorry for you.  The one complaint that I have about our service
: provider is that they use sprintlink also.  It has got to be the most
: overloaded, unreliable network around.  I've had to redownload so many
: large files because one of the routers went down in the middle and had
: my system lock up on me for minutes at a time because of downed
: routers/overloaded bandwidth.

I've been downloading lots of big files and have been doing alot of net-surfing
and have had very reliable service via eminets link with Sprint.  There have
been occasional disruptions in service, but I've found that to be typical
of most carriers that I've used.

Most of the disruptions that I've been seeing with Sprint are usually in the
9am - 2pm time frame and we're gathering statistics to give to Sprint to
show them which links are going down at what times.  Most of the links
are back up within 3-4 minutes, so setting a higher timeout value on 
network accesses will help prevent having to re-download files.

I've seen alot of service providers claim that the problem with their
internet access is caused by Sprint.  I believe that its more likely to
be the service providers fault 75% of the time, and Sprint's problem about
25% of the time.  There are far too many name server and routing problems
which are the service providers fault that are getting blamed on Sprint.
Most service providers are just using Sprint as an easy scapegoat.  

mike