AS198621 KLAUS-ONL Bernd Klaus
🇦🇹Org handle: ORG-BK197-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
1 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)2.4×10²⁴
Announced (BGP)2.4×10²⁴
Routing hygiene
Score 30/100 · Medium riskRPKI ROA coverage
66.7%
1 prefix RPKI invalid
IRR route objects
66.7%
1 prefix registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 33% of announced prefixes (1 of 3) have no valid ROA, 1 of them RPKI invalid
- Only one upstream seen in the AS paths of its routes
- 33% of announced prefixes (1 of 3) have no IRR route object for this ASN
Based on 3 announced prefixes, updated daily (2026-10-22). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
195.58.128.0/24MOAS | Invalid | - | - |
| Valid | RIPE | - | |
| Valid | RIPE | - |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 195.58.128.0/24 | 🇪🇪 EE | RIPE | assigned |
| 2a06:9801:281::/48 | 🇦🇹 AT | RIPE | assigned |
| 2a06:9801:2bc::/48 | 🇦🇹 AT | RIPE | assigned |
All 3 announced prefixes of AS198621 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS198621 hands its own prefixes to: transit providers, or peers at an exchange.
- AS35661VIRTUASYS EU VIRTUA SYSTEMS SAS3
ASPA
No ASPA
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS198621 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/198621Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/198621" | jq