bgpreport

Network · data from 2026-11-12

AS972 Cofractal (3)

Registry name: CF3 - Cofractal, Inc., US · PeeringDB

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

Announced routes

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

2600:ec02:105::/48 No ROA None 634 100% 69
2600:ec02:107::/48 No ROA None 634 100% 69
2600:ec02:1016::/48 No ROA None 633 100% 68

AS-SET

AS972'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 6 are in fix.csv.

  • ROA: none3
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none2600:ec02:105::/48No ROA covers it. Add a ROA for AS972, maxLength 48.634 of 636
Route object: none2600:ec02:105::/48No route object for it. Add a route object with origin AS972 in the RIR database for the space.634 of 636
ROA: none2600:ec02:107::/48No ROA covers it. Add a ROA for AS972, maxLength 48.634 of 636
Route object: none2600:ec02:107::/48No route object for it. Add a route object with origin AS972 in the RIR database for the space.634 of 636
ROA: none2600:ec02:1016::/48No ROA covers it. Add a ROA for AS972, maxLength 48.633 of 636
Route object: none2600:ec02:1016::/48No route object for it. Add a route object with origin AS972 in the RIR database for the space.633 of 636

Route objects not announced

Every route object with origin AS972 is announced.

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.