bgpreport

Network · data from 2026-11-12

AS14935 MONTICELLO - Monticello Networks, Inc.

Registry name: MONTICELLO - Monticello Networks, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS14935, 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.

2605:da00:2424::/48 No ROA Nonecovered by 2605:da00::/32 634 100% 67
2605:da00:8738::/48 No ROA Nonecovered by 2605:da00::/32 634 100% 67
199.47.123.0/24 No ROA Other IRR onlyRADB 670 100% 67
2605:da00:1111::/48 No ROA Other IRR onlyRADB 634 100% 67
2605:da00:5222::/48 No ROA Other IRR onlyRADB 634 100% 67
2605:da00:d161::/48 No ROA Other IRR onlyRADB 634 100% 67
208.68.160.0/21 No ROA RIR databaseARIN, RADB 672 100% 67
199.102.44.0/22 No ROA RIR databaseARIN, RADB 670 100% 67

AS-SET

AS14935 isn't in PeeringDB, where networks name their 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 21 are in fix.csv.

  • ROA: none8
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none2605:da00:2424::/48No ROA covers it. Add a ROA for AS14935, maxLength 48.634 of 636
Route object: none2605:da00:2424::/48No route object for it. A route object for 2605:da00::/32 with origin AS14935 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14935 in the RIR database for the space.634 of 636
ROA: none2605:da00:8738::/48No ROA covers it. Add a ROA for AS14935, maxLength 48.634 of 636
Route object: none2605:da00:8738::/48No route object for it. A route object for 2605:da00::/32 with origin AS14935 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14935 in the RIR database for the space.634 of 636
ROA: none199.47.123.0/24No ROA covers it. Add a ROA for AS14935, maxLength 24.670 of 673
Route object: RIR199.47.123.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2605:da00:1111::/48No ROA covers it. Add a ROA for AS14935, maxLength 48.634 of 636
Route object: RIR2605:da00:1111::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2605:da00:5222::/48No ROA covers it. Add a ROA for AS14935, maxLength 48.634 of 636
Route object: RIR2605:da00:5222::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none2605:da00:d161::/48No ROA covers it. Add a ROA for AS14935, maxLength 48.634 of 636
Route object: RIR2605:da00:d161::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none208.68.160.0/21No ROA covers it. Add a ROA for AS14935, maxLength 21.672 of 673
ROA: none199.102.44.0/22No ROA covers it. Add a ROA for AS14935, maxLength 22.670 of 673

Route objects not announced

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

66.235.171.0/24RADBNo ROA
108.165.184.0/22RADBNo ROA
191.96.30.0/24RADB, RIPEValid
198.37.112.0/20ARIN, RADBValid
199.47.120.0/22ARIN, RADBNo ROA
199.83.208.0/21ARINNo ROA
2605:da00::/32ARINNo ROA

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.