🚀 go-pugleaf

>1. Since Digex found out about the bandwidth problem, what action(s) have 
>been taken?

Way, WAY too many to be detailed here.  Lines have been tested 3000 different
ways, equipment purchased, configured, tested, in-line loads installed on 
every single line here, long conferences had with BA, etc.  Many many many
hours of peoples time burned.  BA at last fessed up some weeks ago, and 
ever since we have changed the focus, based on the new information.

>2. Has Digex attempted to request BA replace the SLC, even at Digex's 
>cost, to improve service for Baltimore area users?

Yes - there is no alternative to them, and BA states that they are 
providing the telephone service as indicated in the tariff.  It is 
not their problem that they are not able to deliver 28.8k  That is 
the official BA policy and statement, and the tariffs back that up.

>3. Has Digex investigated locating equipment or telco interfaces at 
>another location,in order to improve service for Baltimore area users?

Yes we have, and we are investigating doing just that.  We will weigh
all of the factors in making a decision.

>4. What are Digex's short and long term plans (if any) for bringing 
>Baltimore service up to the level required by customers?

We are not going to detail all of those plans here in this space.

>Other ISPs should view this as an excellent opportunity to grab a chunk 
>of Digex's market. Work with BA, get a decent telco interface, and offer 
>users top notch service. 

If they grow to this point, then they are likely to have similar 
problems.  Certainly they are welcomed to try.

Doug