bgpreport

Network · data from 2026-11-12

AS275007 AS275007 - CAP189

Registry name: AS275007 - CAP189, CO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS275007, 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:d330:1000::/48 Invalid: origin Other origin only 23 4%low visibility 11
2803:d330::/32 No ROA None 634 100% 67

AS-SET

AS275007 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 4 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin2803:d330:1000::/48ROAs covering it name AS267823, not AS275007. If AS275007 should announce it, add a ROA for AS275007.23 of 636
Route object: none2803:d330:1000::/48Route objects for it name AS267823. Add a route object with origin AS275007 in the RIR database for the space.23 of 636
ROA: none2803:d330::/32No ROA covers it. Add a ROA for AS275007, maxLength 32.634 of 636
Route object: none2803:d330::/32No route object for it. Add a route object with origin AS275007 in the RIR database for the space.634 of 636

Route objects not announced

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