bgpreport

Network · data from 2026-11-12

AS402642 CRLML - Classic

Registry name: CRLML - Classic, US · not in PeeringDB

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

Announced routes

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

2a03:fbc0::/29 Valid Other origin only 634 100% 67
2a0a:7a00::/29 Valid Other origin only 634 100% 67
2a0a:a600::/29 Valid Other origin only 634 100% 67
2a0a:9200::/29 Valid Other origin only 633 100% 67
2a0f:5f00::/29 Valid RIR databaseRIPE 635 100% 67
2a0f:3240::/29 Valid RIR databaseRIPE 634 100% 67
2a0f:8300::/29 Valid RIR databaseRIPE 634 100% 67
2a10:7900::/29 Valid RIR databaseRIPE 632 99% 67
2a11:99c0::/29 Valid RIR databaseRIPE 632 99% 67
2a11:a640::/29 Valid RIR databaseRIPE 631 99% 67
2a11:4600::/29 Valid RIR databaseRIPE 629 99% 67
2a11:5a00::/29 Valid RIR databaseRIPE 629 99% 67
2a11:a4c0::/29 Valid RIR databaseRIPE 629 99% 67

AS-SET

AS402642 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 9 are in fix.csv.

  • Route object: none4
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none2a03:fbc0::/29Route objects for it name AS213618. Add a route object with origin AS402642 in the RIR database for the space.634 of 636
Route object: none2a0a:7a00::/29Route objects for it name AS215152. Add a route object with origin AS402642 in the RIR database for the space.634 of 636
Route object: none2a0a:a600::/29Route objects for it name AS215152. Add a route object with origin AS402642 in the RIR database for the space.634 of 636
Route object: none2a0a:9200::/29Route objects for it name AS215152. Add a route object with origin AS402642 in the RIR database for the space.633 of 636

Route objects not announced

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

92.50.1.0/24RADB, RIPEValid
2a0e:a280::/29RIPEValid
2a0e:a3c0::/29RIPEValid
2a11:b300::/29RIPEValid
2a12:2900::/29RIPEValid

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.