- To: outages-list@eskimo.com
- Subject: 56k Service Seattle/Everett
- From: Robert Dinse <nanook@eskimo.com>
- Date: Sun, 16 May 1999 02:55:05 -0700 (PDT)
- Resent-Date: Sun, 16 May 1999 02:55:17 -0700
- Resent-From: outages-list@eskimo.com
- Resent-Message-ID: <"5j9Xk.0.vk4.4OfFt"@mx1>
- Resent-Sender: outages-list-request@eskimo.com
- Prev by Date: www / ftp
- Next by Date: Problems with 56k/Megapop connections.
- Prev by thread: Problems with 56k/Megapop connections.
- Next by thread: www / ftp
- Index(es):
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
56k Service Seattle/Everett
The 56k service had a work around installed May 10th, and it seemed to be
working largely OK until today. Yesterday and earlier today we had a small
number of complaints but not really above the background level that I've gotten
with respect to modem connections since we started with a single line and 300
baud modem in 1982.
However, this afternoon and evening things definitely got worse. I got
the tech support people involved, and they in turn got the vendor involved and
they did find several more software bugs. One involved modem firmware, and the
other has to do with busy/idle status on the box.
They were going to try to get a firmware fix in place tonight (which
unfortunately probably will involve some reboots and cutoffs) and the other
software fix should be ready by around tuesday/wednesday of this week.
The work-around seems to have changed it from a situation were all the
modems get marked busy when they are not in one night to where it takes about
four days, so with any luck the reboot tonight might hold until the real fix is
in place.