Hi, we see very high TTL to many US destinations. Beside asymetric routing it seems to be a uunet problem... can anybody confirm this ? TO nitrous.digex.net: 3 Stuttgart.seicom.NET (194.97.216.22) 29.801 ms 21.646 ms 20.728 ms 4 Frankfurt-s0.seicom.NET (194.97.193.10) 31.776 ms Frankfurt-s1.seicom.NET (194.97.193.14) 20.876 ms Frankfurt-s0.seicom.NET (194.97.193.10) 21.808 ms 5 us-gate.Frankfurt.seicom.NET (195.254.80.41) 47.943 ms 45.519 ms 25.216 ms 6 195.219.64.209 (195.219.64.209) 36.325 ms 30.744 ms 29.361 ms 7 195.219.64.209 (195.219.64.209) 59.212 ms 41.559 ms 32.213 ms 8 195.219.64.238 (195.219.64.238) 105.072 ms Teleglobe.net (207.45.215.2) 115.584 ms 104.231 ms 9 gin-nyy-ac1.Teleglobe.net (207.45.199.233) 170.581 ms 160.385 ms 124.512 ms 10 sl-gw16-pen-2-0.sprintlink.net (144.228.164.61) 135.087 ms 152.616 ms 142.091 ms 11 sl-bb10-pen-3-1.sprintlink.net (144.232.5.93) 1029.545 ms 929.967 ms 907.473 ms 12 144.232.5.62 (144.232.5.62) 957.565 ms 886.067 ms 925.234 ms 13 sprint-nap.digex.net (192.157.69.42) 348.060 ms 1306.569 ms * 14 phl1-core1-h1-0.atlas.digex.net (165.117.50.77) 209.121 ms sprint-nap.digex.net (192.157.69.42) 229.315 ms phl1-core1-h1-0.atlas.digex.net (165.117.50.77) 367.977 ms 15 dca3-core1-h1-0.atlas.digex.net (165.117.50.69) 523.725 ms 1728.589 ms 1486.675 ms 16 dca1-core4-h1-0.atlas.digex.net (165.117.50.65) 562.890 ms 1606.708 ms 1327.118 ms 17 dca1-core3-fa6-0-0.atlas.digex.net (165.117.16.3) 1214.027 ms * 1175.428 ms 18 * * * 19 * nitrous.digex.net (205.197.249.3) 1201.812 ms * FROM nitrous.digex.net: 1 iad1-core2-fa5-0-0.atlas.digex.net (165.117.129.2) 0 msec 0 msec 0 msec 2 dca5-core2-h8-0-0.atlas.digex.net (165.117.53.41) 0 msec 4 msec 4 msec 3 dca5-core1-fa1-0-0.atlas.digex.net (165.117.54.1) 4 msec 4 msec 4 msec 4 Hssi3-1-0.BR1.DCA1.ALTER.NET (209.116.159.98) 0 msec 4 msec 4 msec 5 101.ATM2-0.XR2.DCA1.ALTER.NET (146.188.160.238) [AS 701] 0 msec 0 msec 0 msec 6 294.ATM2-0.TR2.DCA1.ALTER.NET (146.188.161.154) [AS 701] 4 msec 0 msec 4 msec 7 101.ATM6-0.TR2.NYC1.ALTER.NET (146.188.136.218) [AS 701] 28 msec 32 msec 28 msec 8 * 298.ATM6-0.XR2.NYC1.ALTER.NET (146.188.178.201) [AS 701] 28 msec 36 msec 9 194.ATM8-0-0.GW2.NYC2.ALTER.NET (146.188.178.149) [AS 701] 32 msec 32 msec 32 msec 10 teleglobe.ny2-gw.customer.ALTER.NET (157.130.4.166) [AS 701] 588 msec 596 msec 604 msec 11 gin-nyy-ac1.Teleglobe.net (207.45.201.37) [AS 6453] 644 msec 588 msec 668 msec 12 gin-ppt-bb1.Teleglobe.net (207.45.199.234) [AS 6453] 600 msec 552 msec 672 msec 13 Teleglobe.net (207.45.215.1) [AS 6453] 700 msec 668 msec 672 msec 14 195.219.64.237 [AS 8297] 916 msec * 888 msec 15 * * 195.219.64.210 [AS 8297] 824 msec 16 * de-gate.Frankfurt.seicom.NET (195.254.80.11) [AS 5549] 1032 msec 928 msec 17 Stuttgart-s6.seicom.NET (194.97.193.13) [AS 5549] 908 msec de-gate.Frankfurt.seicom.NET (195.254.80.11) [AS 5549] 860 msec Stuttgart-s5.seicom.NET (194.97.193.9) [AS 5549] 1280 msec Winfried -- Winfried Haug | seicom.NET & SCHWABEN.DE | Tel. +49 7121 9770- 0 Laiblinsplatz 12 | Internet+ISDN access & consulting | Fax. +49 7121 9770-19 72793 Pfullingen | Access in STGT + RT + TUE + BB + LB | Rack +49 7433 1449-X haug@schwaben.net| 150*ISDN (64kb/X.75) / 100 * K56flex | Rack +49 711 9675-X haug@seicom.NET |SAP-OSS * FTP * TELNET * NETNEWS * IRC | Rack +49 7121 709-X 34 Mbit Teleglobe * 100 MBit DE-CIX * 2 MBit INXS * 2 Mbit Belwue * 34 Mbit WIN
There has been reports of a WCOM fiber outage caused by a train derailment somewhere in Washington state (approx 700 DS3's, 1900 DS1's down). Sorry, don't have a WCOM ticket # available from where I'm at right now. K | Kyle C. Bacon | kbacon@fnsi.net | Vice President - Operations | Fiber Network Solutions, Inc. On Fri, 10 Jul 1998, Winfried Haug wrote:
Hi,
we see very high TTL to many US destinations.
Beside asymetric routing it seems to be a uunet problem... can anybody confirm this ?
TO nitrous.digex.net:
3 Stuttgart.seicom.NET (194.97.216.22) 29.801 ms 21.646 ms 20.728 ms 4 Frankfurt-s0.seicom.NET (194.97.193.10) 31.776 ms Frankfurt-s1.seicom.NET (194.97.193.14) 20.876 ms Frankfurt-s0.seicom.NET (194.97.193.10) 21.808 ms 5 us-gate.Frankfurt.seicom.NET (195.254.80.41) 47.943 ms 45.519 ms 25.216 ms 6 195.219.64.209 (195.219.64.209) 36.325 ms 30.744 ms 29.361 ms 7 195.219.64.209 (195.219.64.209) 59.212 ms 41.559 ms 32.213 ms 8 195.219.64.238 (195.219.64.238) 105.072 ms Teleglobe.net (207.45.215.2) 115.584 ms 104.231 ms 9 gin-nyy-ac1.Teleglobe.net (207.45.199.233) 170.581 ms 160.385 ms 124.512 ms 10 sl-gw16-pen-2-0.sprintlink.net (144.228.164.61) 135.087 ms 152.616 ms 142.091 ms 11 sl-bb10-pen-3-1.sprintlink.net (144.232.5.93) 1029.545 ms 929.967 ms 907.473 ms 12 144.232.5.62 (144.232.5.62) 957.565 ms 886.067 ms 925.234 ms 13 sprint-nap.digex.net (192.157.69.42) 348.060 ms 1306.569 ms * 14 phl1-core1-h1-0.atlas.digex.net (165.117.50.77) 209.121 ms sprint-nap.digex.net (192.157.69.42) 229.315 ms phl1-core1-h1-0.atlas.digex.net (165.117.50.77) 367.977 ms 15 dca3-core1-h1-0.atlas.digex.net (165.117.50.69) 523.725 ms 1728.589 ms 1486.675 ms 16 dca1-core4-h1-0.atlas.digex.net (165.117.50.65) 562.890 ms 1606.708 ms 1327.118 ms 17 dca1-core3-fa6-0-0.atlas.digex.net (165.117.16.3) 1214.027 ms * 1175.428 ms 18 * * * 19 * nitrous.digex.net (205.197.249.3) 1201.812 ms *
FROM nitrous.digex.net:
1 iad1-core2-fa5-0-0.atlas.digex.net (165.117.129.2) 0 msec 0 msec 0 msec 2 dca5-core2-h8-0-0.atlas.digex.net (165.117.53.41) 0 msec 4 msec 4 msec 3 dca5-core1-fa1-0-0.atlas.digex.net (165.117.54.1) 4 msec 4 msec 4 msec 4 Hssi3-1-0.BR1.DCA1.ALTER.NET (209.116.159.98) 0 msec 4 msec 4 msec 5 101.ATM2-0.XR2.DCA1.ALTER.NET (146.188.160.238) [AS 701] 0 msec 0 msec 0 msec 6 294.ATM2-0.TR2.DCA1.ALTER.NET (146.188.161.154) [AS 701] 4 msec 0 msec 4 msec 7 101.ATM6-0.TR2.NYC1.ALTER.NET (146.188.136.218) [AS 701] 28 msec 32 msec 28 msec 8 * 298.ATM6-0.XR2.NYC1.ALTER.NET (146.188.178.201) [AS 701] 28 msec 36 msec 9 194.ATM8-0-0.GW2.NYC2.ALTER.NET (146.188.178.149) [AS 701] 32 msec 32 msec 32 msec 10 teleglobe.ny2-gw.customer.ALTER.NET (157.130.4.166) [AS 701] 588 msec 596 msec 604 msec 11 gin-nyy-ac1.Teleglobe.net (207.45.201.37) [AS 6453] 644 msec 588 msec 668 msec 12 gin-ppt-bb1.Teleglobe.net (207.45.199.234) [AS 6453] 600 msec 552 msec 672 msec 13 Teleglobe.net (207.45.215.1) [AS 6453] 700 msec 668 msec 672 msec 14 195.219.64.237 [AS 8297] 916 msec * 888 msec 15 * * 195.219.64.210 [AS 8297] 824 msec 16 * de-gate.Frankfurt.seicom.NET (195.254.80.11) [AS 5549] 1032 msec 928 msec 17 Stuttgart-s6.seicom.NET (194.97.193.13) [AS 5549] 908 msec de-gate.Frankfurt.seicom.NET (195.254.80.11) [AS 5549] 860 msec Stuttgart-s5.seicom.NET (194.97.193.9) [AS 5549] 1280 msec
Winfried --
Winfried Haug | seicom.NET & SCHWABEN.DE | Tel. +49 7121 9770- 0 Laiblinsplatz 12 | Internet+ISDN access & consulting | Fax. +49 7121 9770-19 72793 Pfullingen | Access in STGT + RT + TUE + BB + LB | Rack +49 7433 1449-X haug@schwaben.net| 150*ISDN (64kb/X.75) / 100 * K56flex | Rack +49 711 9675-X haug@seicom.NET |SAP-OSS * FTP * TELNET * NETNEWS * IRC | Rack +49 7121 709-X 34 Mbit Teleglobe * 100 MBit DE-CIX * 2 MBit INXS * 2 Mbit Belwue * 34 Mbit WIN
There is a fiber cut in Phil. PA right now, but nothing in WA State. UUNet confirms that the fiber cut on the East Coast is the only thing going on right now. Regards, - Bill On Fri, 10 Jul 1998, Kyle C. Bacon wrote:
Date: Fri, 10 Jul 1998 12:35:53 -0400 (EDT) From: "Kyle C. Bacon" <kbacon@kevlar.fnsi.net> To: haug@seicom.de Cc: nanog@merit.edu, Winfried Haug <haug@hq.seicom.net> Subject: Re: UUnet broken `?
There has been reports of a WCOM fiber outage caused by a train derailment somewhere in Washington state (approx 700 DS3's, 1900 DS1's down).
Sorry, don't have a WCOM ticket # available from where I'm at right now.
K
| Kyle C. Bacon | kbacon@fnsi.net | Vice President - Operations | Fiber Network Solutions, Inc.
On Fri, 10 Jul 1998, Winfried Haug wrote:
Hi,
we see very high TTL to many US destinations.
Beside asymetric routing it seems to be a uunet problem... can anybody confirm this ?
TO nitrous.digex.net:
3 Stuttgart.seicom.NET (194.97.216.22) 29.801 ms 21.646 ms 20.728 ms 4 Frankfurt-s0.seicom.NET (194.97.193.10) 31.776 ms Frankfurt-s1.seicom.NET (194.97.193.14) 20.876 ms Frankfurt-s0.seicom.NET (194.97.193.10) 21.808 ms 5 us-gate.Frankfurt.seicom.NET (195.254.80.41) 47.943 ms 45.519 ms 25.216 ms 6 195.219.64.209 (195.219.64.209) 36.325 ms 30.744 ms 29.361 ms 7 195.219.64.209 (195.219.64.209) 59.212 ms 41.559 ms 32.213 ms 8 195.219.64.238 (195.219.64.238) 105.072 ms Teleglobe.net (207.45.215.2) 115.584 ms 104.231 ms 9 gin-nyy-ac1.Teleglobe.net (207.45.199.233) 170.581 ms 160.385 ms 124.512 ms 10 sl-gw16-pen-2-0.sprintlink.net (144.228.164.61) 135.087 ms 152.616 ms 142.091 ms 11 sl-bb10-pen-3-1.sprintlink.net (144.232.5.93) 1029.545 ms 929.967 ms 907.473 ms 12 144.232.5.62 (144.232.5.62) 957.565 ms 886.067 ms 925.234 ms 13 sprint-nap.digex.net (192.157.69.42) 348.060 ms 1306.569 ms * 14 phl1-core1-h1-0.atlas.digex.net (165.117.50.77) 209.121 ms sprint-nap.digex.net (192.157.69.42) 229.315 ms phl1-core1-h1-0.atlas.digex.net (165.117.50.77) 367.977 ms 15 dca3-core1-h1-0.atlas.digex.net (165.117.50.69) 523.725 ms 1728.589 ms 1486.675 ms 16 dca1-core4-h1-0.atlas.digex.net (165.117.50.65) 562.890 ms 1606.708 ms 1327.118 ms 17 dca1-core3-fa6-0-0.atlas.digex.net (165.117.16.3) 1214.027 ms * 1175.428 ms 18 * * * 19 * nitrous.digex.net (205.197.249.3) 1201.812 ms *
FROM nitrous.digex.net:
1 iad1-core2-fa5-0-0.atlas.digex.net (165.117.129.2) 0 msec 0 msec 0 msec 2 dca5-core2-h8-0-0.atlas.digex.net (165.117.53.41) 0 msec 4 msec 4 msec 3 dca5-core1-fa1-0-0.atlas.digex.net (165.117.54.1) 4 msec 4 msec 4 msec 4 Hssi3-1-0.BR1.DCA1.ALTER.NET (209.116.159.98) 0 msec 4 msec 4 msec 5 101.ATM2-0.XR2.DCA1.ALTER.NET (146.188.160.238) [AS 701] 0 msec 0 msec 0 msec 6 294.ATM2-0.TR2.DCA1.ALTER.NET (146.188.161.154) [AS 701] 4 msec 0 msec 4 msec 7 101.ATM6-0.TR2.NYC1.ALTER.NET (146.188.136.218) [AS 701] 28 msec 32 msec 28 msec 8 * 298.ATM6-0.XR2.NYC1.ALTER.NET (146.188.178.201) [AS 701] 28 msec 36 msec 9 194.ATM8-0-0.GW2.NYC2.ALTER.NET (146.188.178.149) [AS 701] 32 msec 32 msec 32 msec 10 teleglobe.ny2-gw.customer.ALTER.NET (157.130.4.166) [AS 701] 588 msec 596 msec 604 msec 11 gin-nyy-ac1.Teleglobe.net (207.45.201.37) [AS 6453] 644 msec 588 msec 668 msec 12 gin-ppt-bb1.Teleglobe.net (207.45.199.234) [AS 6453] 600 msec 552 msec 672 msec 13 Teleglobe.net (207.45.215.1) [AS 6453] 700 msec 668 msec 672 msec 14 195.219.64.237 [AS 8297] 916 msec * 888 msec 15 * * 195.219.64.210 [AS 8297] 824 msec 16 * de-gate.Frankfurt.seicom.NET (195.254.80.11) [AS 5549] 1032 msec 928 msec 17 Stuttgart-s6.seicom.NET (194.97.193.13) [AS 5549] 908 msec de-gate.Frankfurt.seicom.NET (195.254.80.11) [AS 5549] 860 msec Stuttgart-s5.seicom.NET (194.97.193.9) [AS 5549] 1280 msec
Winfried --
Winfried Haug | seicom.NET & SCHWABEN.DE | Tel. +49 7121 9770- 0 Laiblinsplatz 12 | Internet+ISDN access & consulting | Fax. +49 7121 9770-19 72793 Pfullingen | Access in STGT + RT + TUE + BB + LB | Rack +49 7433 1449-X haug@schwaben.net| 150*ISDN (64kb/X.75) / 100 * K56flex | Rack +49 711 9675-X haug@seicom.NET |SAP-OSS * FTP * TELNET * NETNEWS * IRC | Rack +49 7121 709-X 34 Mbit Teleglobe * 100 MBit DE-CIX * 2 MBit INXS * 2 Mbit Belwue * 34 Mbit WIN
I live in Gig Harbor Washigton ( 50 miles south of seattle) and I used UUNet to dialup and they were terrably slow..... I know that they have over loaded routers.. and so on... maybe it is time for a NW upgrade. morex -. morex@narrows.com On Fri, 10 Jul 1998, Kyle C. Bacon wrote:
There has been reports of a WCOM fiber outage caused by a train derailment somewhere in Washington state (approx 700 DS3's, 1900 DS1's down).
Sorry, don't have a WCOM ticket # available from where I'm at right now.
K
| Kyle C. Bacon | kbacon@fnsi.net | Vice President - Operations | Fiber Network Solutions, Inc.
On Fri, 10 Jul 1998, Winfried Haug wrote:
Hi,
we see very high TTL to many US destinations.
Beside asymetric routing it seems to be a uunet problem... can anybody confirm this ?
TO nitrous.digex.net:
3 Stuttgart.seicom.NET (194.97.216.22) 29.801 ms 21.646 ms 20.728 ms 4 Frankfurt-s0.seicom.NET (194.97.193.10) 31.776 ms Frankfurt-s1.seicom.NET (194.97.193.14) 20.876 ms Frankfurt-s0.seicom.NET (194.97.193.10) 21.808 ms 5 us-gate.Frankfurt.seicom.NET (195.254.80.41) 47.943 ms 45.519 ms 25.216 ms 6 195.219.64.209 (195.219.64.209) 36.325 ms 30.744 ms 29.361 ms 7 195.219.64.209 (195.219.64.209) 59.212 ms 41.559 ms 32.213 ms 8 195.219.64.238 (195.219.64.238) 105.072 ms Teleglobe.net (207.45.215.2) 115.584 ms 104.231 ms 9 gin-nyy-ac1.Teleglobe.net (207.45.199.233) 170.581 ms 160.385 ms 124.512 ms 10 sl-gw16-pen-2-0.sprintlink.net (144.228.164.61) 135.087 ms 152.616 ms 142.091 ms 11 sl-bb10-pen-3-1.sprintlink.net (144.232.5.93) 1029.545 ms 929.967 ms 907.473 ms 12 144.232.5.62 (144.232.5.62) 957.565 ms 886.067 ms 925.234 ms 13 sprint-nap.digex.net (192.157.69.42) 348.060 ms 1306.569 ms * 14 phl1-core1-h1-0.atlas.digex.net (165.117.50.77) 209.121 ms sprint-nap.digex.net (192.157.69.42) 229.315 ms phl1-core1-h1-0.atlas.digex.net (165.117.50.77) 367.977 ms 15 dca3-core1-h1-0.atlas.digex.net (165.117.50.69) 523.725 ms 1728.589 ms 1486.675 ms 16 dca1-core4-h1-0.atlas.digex.net (165.117.50.65) 562.890 ms 1606.708 ms 1327.118 ms 17 dca1-core3-fa6-0-0.atlas.digex.net (165.117.16.3) 1214.027 ms * 1175.428 ms 18 * * * 19 * nitrous.digex.net (205.197.249.3) 1201.812 ms *
FROM nitrous.digex.net:
1 iad1-core2-fa5-0-0.atlas.digex.net (165.117.129.2) 0 msec 0 msec 0 msec 2 dca5-core2-h8-0-0.atlas.digex.net (165.117.53.41) 0 msec 4 msec 4 msec 3 dca5-core1-fa1-0-0.atlas.digex.net (165.117.54.1) 4 msec 4 msec 4 msec 4 Hssi3-1-0.BR1.DCA1.ALTER.NET (209.116.159.98) 0 msec 4 msec 4 msec 5 101.ATM2-0.XR2.DCA1.ALTER.NET (146.188.160.238) [AS 701] 0 msec 0 msec 0 msec 6 294.ATM2-0.TR2.DCA1.ALTER.NET (146.188.161.154) [AS 701] 4 msec 0 msec 4 msec 7 101.ATM6-0.TR2.NYC1.ALTER.NET (146.188.136.218) [AS 701] 28 msec 32 msec 28 msec 8 * 298.ATM6-0.XR2.NYC1.ALTER.NET (146.188.178.201) [AS 701] 28 msec 36 msec 9 194.ATM8-0-0.GW2.NYC2.ALTER.NET (146.188.178.149) [AS 701] 32 msec 32 msec 32 msec 10 teleglobe.ny2-gw.customer.ALTER.NET (157.130.4.166) [AS 701] 588 msec 596 msec 604 msec 11 gin-nyy-ac1.Teleglobe.net (207.45.201.37) [AS 6453] 644 msec 588 msec 668 msec 12 gin-ppt-bb1.Teleglobe.net (207.45.199.234) [AS 6453] 600 msec 552 msec 672 msec 13 Teleglobe.net (207.45.215.1) [AS 6453] 700 msec 668 msec 672 msec 14 195.219.64.237 [AS 8297] 916 msec * 888 msec 15 * * 195.219.64.210 [AS 8297] 824 msec 16 * de-gate.Frankfurt.seicom.NET (195.254.80.11) [AS 5549] 1032 msec 928 msec 17 Stuttgart-s6.seicom.NET (194.97.193.13) [AS 5549] 908 msec de-gate.Frankfurt.seicom.NET (195.254.80.11) [AS 5549] 860 msec Stuttgart-s5.seicom.NET (194.97.193.9) [AS 5549] 1280 msec
Winfried --
Winfried Haug | seicom.NET & SCHWABEN.DE | Tel. +49 7121 9770- 0 Laiblinsplatz 12 | Internet+ISDN access & consulting | Fax. +49 7121 9770-19 72793 Pfullingen | Access in STGT + RT + TUE + BB + LB | Rack +49 7433 1449-X haug@schwaben.net| 150*ISDN (64kb/X.75) / 100 * K56flex | Rack +49 711 9675-X haug@seicom.NET |SAP-OSS * FTP * TELNET * NETNEWS * IRC | Rack +49 7121 709-X 34 Mbit Teleglobe * 100 MBit DE-CIX * 2 MBit INXS * 2 Mbit Belwue * 34 Mbit WIN
On Fri, Jul 10, 1998 at 05:37:23PM +0200, Winfried Haug wrote:
Hi,
we see very high TTL to many US destinations.
Beside asymetric routing it seems to be a uunet problem... can anybody confirm this ?
I'm hearing mumblings about something of this sort: massive fiber cut between between Washington DC and Baltimore. This would affect the networks close to your entry point to the USA. - Jared
Guess I read the ticket wrong, It did say it was between Washington DC and Baltimore, MA...:) K | Kyle C. Bacon | kbacon@fnsi.net | Vice President - Operations | Fiber Network Solutions, Inc. On Fri, 10 Jul 1998, Jared Mauch wrote:
On Fri, Jul 10, 1998 at 05:37:23PM +0200, Winfried Haug wrote:
Hi,
we see very high TTL to many US destinations.
Beside asymetric routing it seems to be a uunet problem... can anybody confirm this ?
I'm hearing mumblings about something of this sort:
massive fiber cut between between Washington DC and Baltimore.
This would affect the networks close to your entry point to the USA.
- Jared
Unnamed Administration sources reported that Kyle C. Bacon said
Guess I read the ticket wrong, It did say it was between Washington DC and Baltimore, MA...:)
There is a significant fiber run up the ?Chessie? line; it goes through Laurel and Relay MD. -- A host is a host from coast to coast.................wb8foz@nrk.com & no one will talk to a host that's close........[v].(301) 56-LINUX Unless the host (that isn't close).........................pob 1433 is busy, hung or dead....................................20915-1433
participants (6)
-
Bill Barnes -
David Lesher -
Jared Mauch -
Kyle C. Bacon -
morex -
Winfried Haug