bgpreport

Network · data from 2026-11-12

AS43002 KTV-GARS-Klipso-GmbH-AS43002 Klipso GmbH

Registry name: KTV-GARS-Klipso-GmbH-AS43002 Klipso GmbH, AT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43002, 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.
195.62.85.0/24 No ROA Nonecovered by 195.62.84.0/23 670 100% 68
195.62.84.0/23 No ROA RIR databaseRIPE 670 100% 68
62.93.116.0/22 Valid RIR databaseRIPE 670 100% 68

AS-SET

AS43002 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 3 are in fix.csv.

  • ROA: none2
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none195.62.85.0/24No ROA covers it. Add a ROA for AS43002, maxLength 24.670 of 673
Route object: none195.62.85.0/24No route object for it. A route object for 195.62.84.0/23 with origin AS43002 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43002 in the RIR database for the space.670 of 673
ROA: none195.62.84.0/23No ROA covers it. Add a ROA for AS43002, maxLength 23.670 of 673

Route objects not announced

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