Re: NAPNET issues

[Robert Dinse <nanook@eskimo.com>]

On Tue, 21 Sep 1999, AMY L SPIES wrote:

> Date: Tue, 21 Sep 1999 11:17:14 -0700
> From: AMY L SPIES <AMY.L.SPIES@mail.sprint.com>
> To: nanook@eskimo.com
> Cc: toni.w@openmail.mail.sprint.com
> Subject: NAPNET issues
> 
> BOB and team, 
> I have called the ISC and they gave me the details to validate the
> problem with Napnet. Since NApnet is not a Sprint customer, the
> complaints to Napnet needs to come from Eskimo North, as their customer.
> Here are the details you can send along to Napnet, along with your own
> router 
> statistics.

     Maybe you folks are missing something here.

     I don't pay sprint $6k a month for connectivity just to other SprintLink
customers, I pay $6k/month for INTERnet connectivity.  Frankly, $6k/month is
way above the going rate here for two T1's but it is worth it IF I can get good
connectivity to the rest of the net and problems are resolved promptly.  But if
I am going to get garbage peering and nothing but finger pointing at the other
guy when I have a problem then there is no good incentive for me not to go with
some of these outfits offering T1's for $600/month. 

     This expectation on the part of Sprint that other backbone networks are
all supposed to be CUSTOMERS rather than PEERS needs to end, else I will need
to find another carrier to provide INTERnet connectivity for our hosts.  I have
avoided going to UUNET for this reason, and if Sprint is going to adopt this
same policy of trying to force all of the other backbones to be their customer
rather than their peer, then I will go elsewhere.

     I can't reach hosts in NapNet, or in this case Comm Servers that belong
to StarNet Inc, as part of their MegaPOP service, without 20% packet loss.
We use MegaPOP for dial access in many areas and this is making it impossible
for our customers to reliably reach our servers connected to the INTERnet in
theory, by Sprint.

     If Sprint can not provide INTERnet connectivity that works, that is, where
20% of the packets don't get lost in the peering with other networks, then I
will be forced to go elsewhere for INTERnet connectivity.

> -CUST PROVIDED DEST IP ADDRESS 207.227.230.5.                     
> -WHEN TRACING TO THIS DESTINATION FROM THE SL-GW2-SEA I DID NOT   
>  NOTICE ANY ABORNOMAL LATENCY WITHIN SPRINT NETWORK.              
> -I ALSO WENT TO SL-W1-MAE AND PINGED MAE-WEST.NAP.NET(198.32.136.1
>  THIS PING CAME BACK WITH ONLY 76 PERCENT SUCCESS-RATE INDICATING 
>  THAT SOMEHOW, THE LINK IS NOT GOOD EITHER FROM SPRINT SIDE OR FRO
>  NAPNET SIDE.                                                     
> -THIS APPEARS TO BE A PROBLEM AT THE GIGASWITCH LEVEL TOWARD NAPNET
> I ADVISED THE CUST TO CONTACT HIS ACCOUNT TEAM TO PUSH THE ISSU
> WITH NAPNET AND THE PUBLIC PEERING POINT (MAE WEST).           
> The account team has validated the problem. 
> 
> Amy Spies
> se.seattle