#127669/C (1site) appl:A site in Germany reports routing proble...

The end of this issue - last post by me anyhow. Seems to be a
bandwidth issue on a segment of the BBN-Planet network.


Ticket Number: 127669 Ticket Status: closed
Ticket Type: unplanned/e2e Scope/Source: 1site/email
Ticket Closer: jhickey Problem Fixer: none
Ticket Opened: 07-15-1997 14:32 GMT Problem Started: 07-15-1997

14:32 GMT

Ticket Closed: 07-16-1997 01:14 GMT Problem Ended: 07-15-1997

14:32 GMT

Close Code: ucp

Svc/Site ID #: 178044
Svc/Site Name: appl


    A site in Germany reports routing problems resulting in


    reaching www.apple.com.

  Coming from either or and going to
  www.apple.com traces seem to be delayed around paloalto. Winfried

Haug from

  the source reports their AS is 5549 and the first Net is announces

as a /16

  from their former upstream, they have The

second block

  has no super-route, but is splitted between themselves and another

ISP, they

  have Traces attached.


  Per neteng this issue is directly related to the saturated T3 from


  to decwrl (PAIX). However (also per neteng) there is nothing to be

done at

  this time about offloading any of this traffic and thus no

resolution to the

The end of this issue - last post by me anyhow. Seems to be a
bandwidth issue on a segment of the BBN-Planet network.

I'm not sure if their theory is correct. Routing to www.apple.com
from EUnet/UUNET and from carpeNet/Nacamar both go through the
same Palo Alto link, but look at this ping -c 20 -q www.apple.com ..

* via EUnet/UUNET
    --- www.apple.com ping statistics ---
    20 packets transmitted, 13 packets received, 35% packet loss
    round-trip min/avg/max = 2645.188/2724.840/3156.298 ms

* via carpeNet/Nacamar
    --- www.apple.com ping statistics ---
    20 packets transmitted, 20 packets received, 0% packet loss
    round-trip min/avg/max = 155.404/180.195/249.367 ms

The above was yesterday after I saw the report. The guy at seicom.net
who posted the original problem is also going via UUNET in Frankfurt
(same as EUnet).


You are actually here talking about EUnet Germany, not EUnet as
such; see


for details about that issue. See


for information about EUnet (yes, I know it's confusing, one of
these historical things).

This is what things look like from here; Xlink in Germany will look
pretty much the same (yes, getting really peppered now).

jotun.EU.net% trc www.apple.com
traceroute to www.apple.com (, 30 hops max, 40 byte packets
1 Amsterdam7.NL.EU.net ( 4 ms 4 ms 3 ms
2 Amsterdam5.NL.EU.net ( 4 ms 3 ms 3 ms
3 Pennsauken1.NJ.US.EU.net ( 88 ms 88 ms 87 ms
4 Vienna2.VA.US.EU.net ( 92 ms 90 ms 95 ms
5 San-Jose1.CA.US.EU.net ( 147 ms 151 ms 148 ms
6 sanjose1-br1.bbnplanet.net ( 150 ms 150 ms 148 ms
7 paloalto-br2.bbnplanet.net ( 149 ms 153 ms 149 ms
8 paloalto-cr4.bbnplanet.net ( 154 ms 152 ms 149 ms
9 appl.bbnplanet.net ( 165 ms 157 ms 155 ms
10 ton.apple.com ( 161 ms 155 ms 159 ms
11 A17-254-3-35.apple.com ( 168 ms 151 ms 156 ms