🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.internet.services
Article #4702

Re: IDT-connect problems

#4702
From: Dale Botkin
Date: Fri, 15 Mar 1996 00:00
33 lines
2720 bytes
John McGarry <jmcgarry@onramp.net> seems to have written:

>David Chapman wrote:
>> 
>> BIG D wrote:
>> 
>> >
>> > You are not alone in your frustration with IDT.
>> 
>> I had IDT for 3months and and could never get on so I switched to
>> compassnet (776-0022) it's been great any time of day and their local!

>IDT owns their own POP's in two or three locations. They sell "franchises" to local ISP's 
>for a percentage of the signup fee and monthly recurring.  IDT in Houston is more than
>likely through a local Houston ISP who has provided a dialin number for their service.

Yup.  They wanted us to provide dialup for them in our area.  We get
$10/mo per customer and give their customers a ***15:1*** ratio of
users to modems.  Fifteen to one!  We know from experience that
anyting above 10:1 is asking for trouble.

We decided to pass.  We didn't need our name dragged through the mud
by being associated with this kind of service, and also figured out
we'd probably go broke at ten bucks a user.  We don't run metered
residential lines in somebody's basement for dialups.


		Dale

------------------------------------------------------------
Dale Botkin    (N0XAS/qrp)         | 
Probe Technology Internet Services | (402) 593-9800 Voice
Omaha, NE                          | (402) 593-8748 FAX
Technical Details
Message-ID: <4idqoe$k2h@jake.probe.net>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <3137658D.35E5@valleynet.com> <4h80df$rok@spectator.cris.com> <nts.430.00769538@nortech.com> <3138C537.2849@gramercy.ios.com> <4hip8i$eji@news.ios.com> <314159DF.672B@compassnet.com> <314420FD.41C67EA6@onramp.net>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f9628,92c42a8507ea1486
X-Google-Attributes: gidf9628,public
X-Google-Thread: 105c4d,92c42a8507ea1486
X-Google-Attributes: gid105c4d,public
X-Google-Thread: 12ec63,92c42a8507ea1486
X-Google-Attributes: gid12ec63,public
X-Google-Thread: 10f21d,92c42a8507ea1486
X-Google-Attributes: gid10f21d,public
X-Google-Thread: fc7b2,92c42a8507ea1486
X-Google-Attributes: gidfc7b2,public
X-Google-Thread: ffd79,92c42a8507ea1486
X-Google-Attributes: gidffd79,public
X-Google-Thread: 10bd82,92c42a8507ea1486
X-Google-Attributes: gid10bd82,public
X-Google-Thread: 1550f9,92c42a8507ea1486
X-Google-Attributes: gid1550f9,public
From: dbotkin@probe.net (Dale Botkin)
Subject: Re: IDT-connect problems
Date: 1996/03/15
Message-ID: <4idqoe$k2h@jake.probe.net>
X-Deja-AN: 143190706
references: <3137658D.35E5@valleynet.com> <4h80df$rok@spectator.cris.com> <nts.430.00769538@nortech.com> <3138C537.2849@gramercy.ios.com> <4hip8i$eji@news.ios.com> <314159DF.672B@compassnet.com> <314420FD.41C67EA6@onramp.net>
organization: Probe Technology
reply-to: dbotkin@probe.net
newsgroups: alt.internet.services,houston.internet.providers,ne.internet.services,sacramento.internet,necus.internet.news,necus.internet.announce,necus.internet.commerce,misc.news.internet.discuss,alt.internet.access,backbone.general,comp.dcom.telecom.tec