bgpreport

Network · data from 2026-11-12

AS40379 PIO-1846 - Carroll College

Registry name: PIO-1846 - Carroll College, US · not in PeeringDB

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

Announced routes

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

140.104.0.0/22 No ROA Nonecovered by 140.104.0.0/18 668 99% 68
140.104.0.0/16 No ROA Other IRR onlyRADB 670 100% 68

AS-SET

AS40379 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 24 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
ROA: none140.104.0.0/22No ROA covers it. Add a ROA for AS40379, maxLength 22.668 of 673
Route object: none140.104.0.0/22No route object for it. A route object for 140.104.0.0/18 with origin AS40379 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40379 in the RIR database for the space.668 of 673
ROA: none140.104.0.0/16No ROA covers it. Add a ROA for AS40379, maxLength 16.670 of 673
Route object: RIR140.104.0.0/16Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

140.104.0.0/18RADBNo ROA
140.104.64.0/21RADBNo ROA
140.104.72.0/22RADBNo ROA
140.104.74.0/23RADBNo ROA
140.104.76.0/22RADBNo ROA
140.104.80.0/20RADBNo ROA
140.104.96.0/19RADBNo ROA
140.104.128.0/17RADBNo ROA
140.104.128.0/20RADBNo ROA
140.104.144.0/21RADBNo ROA
140.104.157.0/24RADBNo ROA
140.104.159.0/24RADBNo ROA
140.104.160.0/20RADBNo ROA
140.104.160.0/24RADBNo ROA
140.104.161.0/24RADBNo ROA
140.104.162.0/23RADBNo ROA
140.104.166.0/23RADBNo ROA
140.104.168.0/21RADBNo ROA
140.104.224.0/22RADBNo ROA
140.104.240.0/20RADBNo 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.