Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ucbvax!RSCH.WISC.EDU!dave
From: dave@RSCH.WISC.EDU (Dave Cohrs)
Newsgroups: mod.protocols.tcp-ip
Subject: Re: Why is the ARPANet in such bad shape these days?
Message-ID: <8609272345.AA07129@rsch.wisc.edu>
Date: Sat, 27-Sep-86 22:54:41 EDT
Article-I.D.: rsch.8609272345.AA07129
Posted: Sat Sep 27 22:54:41 1986
Date-Received: Sun, 28-Sep-86 00:43:27 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 19
Approved: tcp-ip@sri-nic.arpa

I don't know why it's so bad, but no, it is *not* a localized problem.

Hosts at UW-Madison are also having problems reaching hosts farther
away than our local PSN.  The worst problems (of course) are reaching
hosts on the east coast, especially Rutgers and CSS.GOV sites.

The problem seems to be time/day-of-the-week related, so I assume it's
a congestion problem (response time seems pretty good right now), but
I'm not a net-watcher, so don't take that as gospel.  There also seem
to be some severe routing problems.  On one occation this past week, the
packet turnaround time from our gateway to the CSS gateway (10.0.0.25)
was about 1sec, while one hop farther, from a host on our Pronet to
10.0.0.25 was about 8sec with peaks of over 20sec and many packets were lost.

Actually, one site in the Bay Area has started setting up new UUCP
links (using good ol' dialup connections) to make sure that their mail
will get through.

dave