bgpreport

Network · data from 2026-11-12

AS8292 CAMDATA CamData GmbH

Registry name: CAMDATA CamData GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8292, 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.
188.65.200.0/21 No ROA RIR databaseRIPE 673 100% 66
2a12:a940::/29 No ROA RIR databaseRIPE 632 99% 67

AS-SET

AS8292 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: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none188.65.200.0/21No ROA covers it. Add a ROA for AS8292, maxLength 21.673 of 673
ROA: none2a12:a940::/29No ROA covers it. Add a ROA for AS8292, maxLength 29.632 of 636

Route objects not announced

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

188.65.200.0/22RIPENo ROA
188.65.204.0/22RIPENo 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.