AS59881 DC Kevin Buehl
🇩🇪Org handle: ORG-KB90-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Routing hygiene
Score 60/100 · High riskRPKI ROA coverage
0%
1 prefix RPKI invalid
IRR route objects
0%
2 prefixes registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 100% of announced prefixes (2 of 2) have no valid ROA, 1 of them RPKI invalid
- 100% of announced prefixes (2 of 2) have no IRR route object for this ASN
- Only one upstream seen in the AS paths of its routes
Based on 2 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
193.58.239.0/24MOAS | Invalid | - | 2026-10-24 |
| No ROA | - | 2026-10-24 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 193.58.239.0/24 | 🇨🇭 CH | RIPENCC | allocated |
| 2a01:e507::/32 | 🇺🇸 US | RIPE | assigned |
All 2 announced prefixes of AS59881 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS59881 hands its own prefixes to: transit providers, or peers at an exchange.
- AS58057SECUREBIT2
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 AS59881 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/59881Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/59881" | jq