bgpreport

Network · data from 2026-11-12

AS275022 AS275022 - CRG67

Registry name: AS275022 - CRG67, CO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS275022, 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.
2803:db30::/32 Valid None 634 100% 67
2803:db30:9::/48 Valid None 633 100% 67
2803:db30:a::/48 Valid None 633 100% 67
2803:db30:b::/48 Valid None 633 100% 67
2803:db30:c::/48 Valid None 633 100% 67

AS-SET

AS275022 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 5 are in fix.csv.

  • Route object: none5
ChangePrefix or setDetailFull-table peers
Route object: none2803:db30::/32No route object for it. Add a route object with origin AS275022 in the RIR database for the space.634 of 636
Route object: none2803:db30:9::/48No route object for it. Add a route object with origin AS275022 in the RIR database for the space.633 of 636
Route object: none2803:db30:a::/48No route object for it. Add a route object with origin AS275022 in the RIR database for the space.633 of 636
Route object: none2803:db30:b::/48No route object for it. Add a route object with origin AS275022 in the RIR database for the space.633 of 636
Route object: none2803:db30:c::/48No route object for it. Add a route object with origin AS275022 in the RIR database for the space.633 of 636

Route objects not announced

Every route object with origin AS275022 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.