bgpreport

Network · data from 2026-11-12

AS218500 Krottisrv-Wartenstein

Registry name: Krottisrv-Wartenstein David Trolp, AT · PeeringDB

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

Announced routes

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

5.83.158.0/24 Invalid: origin RIR databaseRIPE 0 0%low visibility 1
2a0b:4e07:290::/44 Valid RIR databaseRIPE 3 0%low visibility 3

AS-SET

AS218500's PeeringDB record names no 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 1 are in fix.csv.

  • ROA: origin1
ChangePrefix or setDetailFull-table peers
ROA: origin5.83.158.0/24ROAs covering it name AS12586, not AS218500. If AS218500 should announce it, add a ROA for AS218500.0 of 673

Route objects not announced

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