bgpreport

Network · data from 2026-11-12

AS8339 Kabelplus GmbH

Registry name: KABSI-AS kabelplus GmbH, AT · PeeringDB

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

Announced routes

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

185.199.152.0/22 No ROA RIR databaseRIPE 673 100% 66
91.219.68.0/22 No ROA RIR databaseRIPE 672 100% 66
185.182.178.0/23 No ROA RIR databaseRIPE 672 100% 66
195.60.162.0/23 No ROA RIR databaseRIPE 672 100% 66
195.222.120.0/22 No ROA RIR databaseRIPE 672 100% 66
2001:678:1d8::/48 No ROA RIR databaseRIPE 634 100% 69
62.40.128.0/24 Valid RIR databaseRIPE 673 100% 66
195.202.128.0/24 Valid RIR databaseRIPE 673 100% 66
195.202.138.0/24 Valid RIR databaseRIPE 673 100% 66
62.40.128.0/17 Valid RIR databaseRIPE 672 100% 66
81.217.0.0/16 Valid RIR databaseRIPE 672 100% 66
82.149.96.0/19 Valid RIR databaseRIPE 672 100% 66
82.218.0.0/16 Valid RIR databaseRIPE 672 100% 66
89.104.0.0/19 Valid RIR databaseRIPE 672 100% 66
92.62.16.0/20 Valid RIR databaseRIPE 672 100% 66
92.62.30.0/24 Valid RIR databaseRIPE 672 100% 66
94.16.32.0/19 Valid RIR databaseRIPE 672 100% 66
95.143.224.0/20 Valid RIR databaseRIPE 672 100% 66
176.120.160.0/21 Valid RIR databaseRIPE 672 100% 66
178.18.160.0/20 Valid RIR databaseRIPE 672 100% 66
185.100.96.0/22 Valid RIR databaseRIPE 672 100% 66
194.106.224.0/19 Valid RIR databaseRIPE 672 100% 66
195.202.128.0/19 Valid RIR databaseRIPE 672 100% 66
195.202.160.0/19 Valid RIR databaseRIPE 672 100% 66
195.202.160.0/24 Valid RIR databaseRIPE 672 100% 66
195.230.160.0/19 Valid RIR databaseRIPE 672 100% 66
195.230.160.0/24 Valid RIR databaseRIPE 672 100% 66
202.170.80.0/21 Valid RIR databaseRIPE 672 100% 66
2a00:1b38::/32 Valid RIR databaseRIPE 634 100% 69
2a02:e200::/30 Valid RIR databaseRIPE 633 100% 69

AS-SET

PeeringDB's irr_as_set for AS8339: RIPE::AS-KABS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS8339 isn't in the set, or no route object for AS8339 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS8339 in itNot covered
RIPE::AS-KABS RIPE 12159 Yes 0

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

  • ROA: none6
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none185.199.152.0/22No ROA covers it. Add a ROA for AS8339, maxLength 22.673 of 673
ROA: none91.219.68.0/22No ROA covers it. Add a ROA for AS8339, maxLength 22.672 of 673
ROA: none185.182.178.0/23No ROA covers it. Add a ROA for AS8339, maxLength 23.672 of 673
ROA: none195.60.162.0/23No ROA covers it. Add a ROA for AS8339, maxLength 23.672 of 673
ROA: none195.222.120.0/22No ROA covers it. Add a ROA for AS8339, maxLength 22.672 of 673
ROA: none2001:678:1d8::/48No ROA covers it. Add a ROA for AS8339, maxLength 48.634 of 636

Route objects not announced

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

82.218.140.0/22RIPEValid
82.218.191.0/24RIPEValid
185.93.8.0/22RIPENo ROA
194.106.246.0/24RIPEValid
195.202.168.0/24RIPEValid

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.