bgpreport

Network · data from 2026-11-12

AS40191 Openface (AS40191)

Registry name: AS-PRE2POST-1 - Beanfield Technologies Inc., CA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS40191, 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.
2607:5e00::/32 No ROA Other IRR onlyRADB, RIPE-NONAUTH 636 100% 67
74.114.100.0/22 No ROA RIR databaseARIN, RADB, RIPE-NONAUTH 673 100% 67
74.123.92.0/22 No ROA RIR databaseARIN, RADB 673 100% 67
173.243.192.0/21 No ROA RIR databaseARIN 673 100% 67
173.243.200.0/23 No ROA RIR databaseARIN 673 100% 67
173.243.202.0/24 No ROA RIR databaseARIN 673 100% 67
173.246.64.0/19 No ROA RIR databaseARIN, RADB, RIPE-NONAUTH 673 100% 67
208.71.8.0/22 No ROA RIR databaseARIN, RADB, RIPE-NONAUTH 673 100% 67
208.85.112.0/22 No ROA RIR databaseARIN, RADB, RIPE-NONAUTH 673 100% 67

AS-SET

AS40191'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 18 are in fix.csv.

  • ROA: none9
  • Route object: RIR1
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none2607:5e00::/32No ROA covers it. Add a ROA for AS40191, maxLength 32.636 of 636
Route object: RIR2607:5e00::/32Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.636 of 636
ROA: none74.114.100.0/22No ROA covers it. Add a ROA for AS40191, maxLength 22.673 of 673
ROA: none74.123.92.0/22No ROA covers it. Add a ROA for AS40191, maxLength 22.673 of 673
ROA: none173.243.192.0/21No ROA covers it. Add a ROA for AS40191, maxLength 21.673 of 673
ROA: none173.243.200.0/23No ROA covers it. Add a ROA for AS40191, maxLength 23.673 of 673
ROA: none173.243.202.0/24No ROA covers it. Add a ROA for AS40191, maxLength 24.673 of 673
ROA: none173.246.64.0/19No ROA covers it. Add a ROA for AS40191, maxLength 19.673 of 673
ROA: none208.71.8.0/22No ROA covers it. Add a ROA for AS40191, maxLength 22.673 of 673
ROA: none208.85.112.0/22No ROA covers it. Add a ROA for AS40191, maxLength 22.673 of 673

Route objects not announced

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

74.123.92.0/23RIPE-NONAUTHNo ROA
74.123.94.0/24RIPE-NONAUTHNo ROA
74.123.95.0/24RIPE-NONAUTHNo ROA
173.243.192.0/20ARIN, RADB, RIPE-NONAUTHNo ROA
199.84.182.0/24RIPE-NONAUTHNo ROA
199.84.183.0/24RIPE-NONAUTHNo ROA
205.237.250.0/24RADBNo ROA
205.237.253.0/24RADBNo 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.