- To: David Zortea <dave@megapop.net>
- Subject: Re: Seattle 56k - READ THIS IT IS IMPORTANT
- From: Robert Dinse <nanook@eskimo.com>
- Date: Mon, 7 Aug 2000 18:23:21 -0700 (PDT)
- cc: eskimo-announce@eskimo.com, malecki@megapop.net, eric@megapop.net, scottg@starnetusa.net, malonzo@megapop.net, tomv@megapop.net, sue@megapop.net, support@megapop.net, noc@megapop.net
- In-Reply-To: <v04210104b5b46d0bd30a@[209.224.139.62]>
- Resent-Date: Mon, 7 Aug 2000 18:23:30 -0700
- Resent-From: eskimo-announce@eskimo.com
- Resent-Message-ID: <"bSkPT.0.oU1.I4sZv"@mx1>
- Resent-Sender: eskimo-announce-request@eskimo.com
- Prev by Date: Seattle 56k - READ THIS IT IS IMPORTANT
- Next by Date: Seattle 56k, and Western WA...
- Prev by thread: Seattle 56k - READ THIS IT IS IMPORTANT
- Next by thread: Mail SMTP Problems
- Index(es):
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Seattle 56k - READ THIS IT IS IMPORTANT
On Mon, 7 Aug 2000, David Zortea wrote:
>
> At 10:09 PM -0700 8/4/00, Robert Dinse wrote:
> > After telling is that the old seattle 56k number 206-812-1399
> >would NOT be
> >disconnected in the forseeable future, MegaPOP today notified me that it would
> >be disconnected soon.
>
> You need to read more carefully Robert. We stressed that it WOULD NOT
> BE DISCONNECTED.
>
> "...we are keeping both live and active for the time being. "
The message accompanying the old Phoenix disconnect also said that the
old Seattle would go about the same time, which was 8/31/2000.
Even if it's delayed somewhat we need these problems resolved before hand
and I'm personally not convinced that with the Cisco's they can be. Every
location that has had Cisco put in we've lost customers due to cutoffs, poor
connections, failure of ISDN to connect at all, etc.