bgpreport

Network · data from 2026-11-12

AS11135 Cross Development/Montgomery LP

Registry name: CROSS-DEVELOPMENT-MONTGOMERY - Cross Development/Montgomery LP, US · PeeringDB

8IPv4 routes 50.0% RPKI valid · 50.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
4No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS11135, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS11135, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

209.163.230.0/24 No ROA Nonecovered by 209.163.230.0/23 672 100% 67
209.163.231.0/24 No ROA Nonecovered by 209.163.230.0/23 672 100% 67
173.219.13.0/24 No ROA Other IRR onlyRADB 672 100% 67
173.219.14.0/24 No ROA Other IRR onlyRADB 672 100% 67
65.59.246.0/24 Valid Nonecovered by 65.59.246.0/23 664 99% 67
65.59.247.0/24 Valid Nonecovered by 65.59.246.0/23 664 99% 67
66.193.115.0/24 Valid Other IRR onlyRADB 672 100% 67
199.102.136.0/21 Valid RIR databaseARIN, RADB 672 100% 67

AS-SET

AS11135's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 14 are in fix.csv.

  • ROA: none4
  • Route object: none4
  • Route object: RIR3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none209.163.230.0/24No ROA covers it. Add a ROA for AS11135, maxLength 24.672 of 673
Route object: none209.163.230.0/24No route object for it. A route object for 209.163.230.0/23 with origin AS11135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11135 in the RIR database for the space.672 of 673
ROA: none209.163.231.0/24No ROA covers it. Add a ROA for AS11135, maxLength 24.672 of 673
Route object: none209.163.231.0/24No route object for it. A route object for 209.163.230.0/23 with origin AS11135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11135 in the RIR database for the space.672 of 673
ROA: none173.219.13.0/24No ROA covers it. Add a ROA for AS11135, maxLength 24.672 of 673
Route object: RIR173.219.13.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none173.219.14.0/24No ROA covers it. Add a ROA for AS11135, maxLength 24.672 of 673
Route object: RIR173.219.14.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none65.59.246.0/24No route object for it. A route object for 65.59.246.0/23 with origin AS11135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11135 in the RIR database for the space.664 of 673
Route object: none65.59.247.0/24No route object for it. A route object for 65.59.246.0/23 with origin AS11135 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11135 in the RIR database for the space.664 of 673
Route object: RIR66.193.115.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS11135 whose prefix no peer sees AS11135 announce. Many are kept on purpose (backup routes, space announced only in some places).

65.59.246.0/23RADBNo ROA
209.163.230.0/23RADBNo ROA
2607:d9c0::/32ARINValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.