[NANOG] Comcast (AS 7922 -> 33491) issues?

Thu Apr 24 16:24:12 UTC 2008

I'm seeing tons of availability issues to networks with AS paths ending
in "7922 33491". A couple of the prefixes in question are 98.214.0.0/15,
69.137.240.0/20, 73.117.0.0/16, and 67.175.0.0/16. 

I spoke with Abovenet earlier this morning - they say its due to L3
suppressing those announcements to some of their peers. Initially I
thought they were just making things up, until I started seeing "%
Network not in table" responses to BGP lookups on the router where I
peer with Sprint:

#show ip bgp 98.214.184.18
% Network not in table

#show ip bgp 69.137.251.134
% Network not in table

And yet...

#show ip bgp 98.214.184.18
BGP routing table entry for 98.214.0.0/15, version 26493985
Paths: (2 available, best #1, table Default-IP-Routing-Table)
  Advertised to update-groups:
     3          4         
  3491 7922 33491
    63.218.31.1 from 63.218.31.1 (63.218.30.9)
      Origin IGP, localpref 100, valid, external, best
      Community: 228787176 228787177 228794098
  6395 3356 7922 33491
    216.140.65.73 from 216.140.65.73 (216.140.9.56)
      Origin IGP, metric 160, localpref 100, valid, external

#show ip bgp 69.137.251.134
BGP routing table entry for 69.137.240.0/20, version 26493909
Paths: (2 available, best #1, table Default-IP-Routing-Table)
  Advertised to update-groups:
     3          4         
  3491 7922 33491
    63.218.31.1 from 63.218.31.1 (63.218.30.9)
      Origin IGP, localpref 100, valid, external, best
      Community: 228787176 228787177 228794098
  6395 3356 7922 33491
    216.140.65.73 from 216.140.65.73 (216.140.9.56)
      Origin IGP, metric 160, localpref 100, valid, external

Based on what I'm seeing, someone out there has to be seeing similar
behavior. Anybody? Bueller? 

D.