Mailing List Archive: NANOG: users

Route to 208.71.177.15, 208.71.179.10

Index | Next | Previous | View Threaded

hiersd at gmail

Oct 2, 2009, 12:50 PM

Post #1 of 3 (267 views)
Permalink

Route to 208.71.177.15, 208.71.179.10

Is anyone having trouble routing to 208.71.177.15 or 208.71.179.10?

Can't get there from 65.59.112.0/24 in Chicago.

David

hiersd at gmail

Oct 2, 2009, 1:03 PM

Post #2 of 3 (239 views)
Permalink

Re: Route to 208.71.177.15, 208.71.179.10 [In reply to]

Something seems to be flapping at the IP layer. BGP is steady, but
IP reachablity is intermittent, irrespective of using L3 or VZN for
out outbound path.

David

On Fri, Oct 2, 2009 at 12:58 PM, Tatsuya Kawasaki <tkawasaki [at] fbr> wrote:
> We are in DC area, we lost connection to several site including to
> India.
>
> Tatsuya
>
>
> Tatsuya Kawasaki
> 703.469.1311 (24x7)
>
> -----Original Message-----
> From: David Hiers [mailto:hiersd [at] gmail]
> Sent: Friday, October 02, 2009 3:51 PM
> To: nanog [at] nanog
> Subject: Route to 208.71.177.15, 208.71.179.10
>
> Is anyone having trouble routing to 208.71.177.15 or 208.71.179.10?
>
> Can't get there from 65.59.112.0/24 in Chicago.
>
> David
>
> This electronic message and all attachments transmitted with it may contain confidential and legally privileged information belonging to the sender. Please visit http://www.fbrcapitalmarkets.com/disclosures2.asp for important related disclosures, by either following the attached hyperlink or copying and pasting the URL into your internet browser.
>
>

peter at peter-dambier

Oct 2, 2009, 1:29 PM

Post #3 of 3 (237 views)
Permalink

Re: Route to 208.71.177.15, 208.71.179.10 [In reply to]

Seen from a dtag.de customer

traceroute to 208.71.179.10 (208.71.179.10), 64 hops max, 40 byte packets
1 yttrium.anul.nsa (7.19.30.39) 3 ms 0 ms 0 ms
2 217.0.116.228 (217.0.116.228) 45 ms 47 ms 48 ms
3 217.0.78.58 (217.0.78.58) 46 ms 45 ms 46 ms
4 217.239.40.70 (217.239.40.70) 139 ms 135 ms 136 ms
5 62.156.128.110 (62.156.128.110) 140 ms 137 ms 138 ms
6 sl-crs2-dc-0-1-0-0.sprintlink.net (144.232.19.231) 139 ms sl-crs2-dc-0-13-0-0.sprintlink.net (144.232.25.14) 142 ms 138 ms
7 sl-crs1-atl-0-9-2-0.sprintlink.net (144.232.24.54) 161 ms 160 ms sl-crs2-atl-0-8-0-1.sprintlink.net (144.232.8.160) 160 ms
8 sl-st21-atl-1-0-0.sprintlink.net (144.232.18.135) 157 ms 158 ms sl-st21-atl-0-0-0.sprintlink.net (144.232.20.117) 163 ms
9 sl-xocomm-190550-0.sprintlink.net (144.223.7.110) 156 ms 158 ms 157 ms
10 te-4-1-0.rar3.atlanta-ga.us.xo.net (207.88.12.129) 152 ms 152 ms 153 ms
11 te-11-0-0.rar3.washington-dc.us.xo.net (207.88.12.10) [MPLS: Label 25315 Exp 0] 161 ms 164 ms 159 ms
12 te-3-0-0.rar3.nyc-ny.us.xo.net (207.88.12.73) [MPLS: Label 28026 Exp 0] 165 ms 163 ms 165 ms
13 65.106.1.93.ptr.us.xo.net (65.106.1.93) 161 ms 160 ms 158 ms
14 p0-0-0.MAR2.NYC-NY.us.xo.net (65.106.3.50) 164 ms 163 ms 162 ms
15 p15-0.chr1.nyc-ny.us.xo.net (207.88.86.170) 158 ms 158 ms 163 ms
16 ip65-46-73-34.z73-46-65.customer.algx.net (65.46.73.34) 163 ms 163 ms 160 ms
17 * * *
18 * * *

traceroute to 208.71.177.15 (208.71.177.15), 64 hops max, 40 byte packets
1 yttrium.anul.nsa (7.19.30.39) 1 ms 0 ms 0 ms
2 217.0.116.228 (217.0.116.228) 48 ms 46 ms 53 ms
3 217.0.78.54 (217.0.78.54) 47 ms 47 ms 47 ms
4 * f-ea5-i.F.DE.NET.DTAG.DE (62.154.16.161) 49 ms 47 ms
5 te-4-4.car2.Frankfurt1.Level3.net (4.68.110.253) 168 ms 55 ms 56 ms
6 vlan89.csw3.Frankfurt1.Level3.net (4.68.23.190) 56 ms 56 ms 58 ms
7 ae-82-82.ebr2.Frankfurt1.Level3.net (4.69.140.25) 58 ms 57 ms 58 ms
8 ae-44-44.ebr2.Washington1.Level3.net (4.69.137.62) 139 ms ae-41-41.ebr2.Washington1.Level3.net (4.69.137.50) 138 ms ae-42-42.ebr2.Washington1.Level3.net (4.69.137.54) 137 ms
9 ae-72-72.csw2.Washington1.Level3.net (4.69.134.150) 136 ms 144 ms ae-62-62.csw1.Washington1.Level3.net (4.69.134.146) 144 ms
10 ae-84-84.ebr4.Washington1.Level3.net (4.69.134.185) 145 ms ae-94-94.ebr4.Washington1.Level3.net (4.69.134.189) 146 ms ae-64-64.ebr4.Washington1.Level3.net (4.69.134.177) 145 ms
11 ae-3-3.ebr1.NewYork1.Level3.net (4.69.132.94) 138 ms 136 ms 138 ms
12 ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66) 146 ms ae-91-91.csw4.NewYork1.Level3.net (4.69.134.78) 139 ms ae-71-71.csw2.NewYork1.Level3.net (4.69.134.70) 147 ms
13 ae-2-79.edge1.NewYork1.Level3.net (4.68.16.78) 137 ms ae-1-69.edge1.NewYork1.Level3.net (4.68.16.14) 202 ms ae-4-99.edge1.NewYork1.Level3.net (4.68.16.206) 140 ms
14 PEER-1-NETW.edge1.NewYork1.Level3.net (4.78.132.66) 139 ms 138 ms 138 ms
15 gig4-0.nyc-gsr-d.peer1.net (216.187.123.6) 138 ms 136 ms 136 ms
16 10ge.xe-0-0-0.nyc-telx-dis-1.peer1.net (216.187.115.165) 139 ms 138 ms 138 ms
17 64.34.62.4 (64.34.62.4) 139 ms 146 ms 140 ms
18 * * *
19 * * *

No, I cannot see them either.
Peter

David Hiers wrote:
> Is anyone having trouble routing to 208.71.177.15 or 208.71.179.10?
>
> Can't get there from 65.59.112.0/24 in Chicago.
>
> David

--
Peter and Karin Dambier
Cesidian Root - Radice Cesidiana
Rimbacher Strasse 16
D-69509 Moerlenbach-Bonsweiher
+49(6209)795-816 (Telekom)
+49(6252)750-308 (VoIP: sipgate.de)
mail: peter [at] peter-dambier
http://www.peter-dambier.de/
http://iason.site.voila.fr/
https://sourceforge.net/projects/iason/
ULA= fd80:4ce1:c66a::/48

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads