AS206174 KKM-AS Kasperovich Konstantin Mikhailovich
🇷🇺Org handle: ORG-KKM3-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
14total
0 IPv414 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)7.9×10²⁹
Announced (BGP)1.1×10³⁰
Routing hygiene
Score 60/100 · High riskRPKI ROA coverage
50%
1 prefix RPKI invalid
IRR route objects
50%
no origin mismatches
Hijack signals
1
1 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- Announces 1 prefix that RPKI assigns to another network (possible hijack or misconfiguration)
- 50% of announced prefixes (7 of 14) have no valid ROA, 1 of them RPKI invalid
- Only one upstream seen in the AS paths of its routes
- 50% of announced prefixes (7 of 14) have no IRR route object for this ASN
Based on 14 announced prefixes, updated daily (2026-10-25). How the score works · RPKI explained
Announced Prefixes
(BGP)14|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-27 | |
| Invalid | - | 2026-10-27 | |
| No ROA | - | 2026-10-27 | |
| No ROA | - | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 | |
| No ROA | - | 2026-10-27 | |
| Valid | RIPE | 2026-10-27 |
1-10 of 14
1 / 2
Allocated Prefixes
(RIR)10Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a11:77c0::/32 | 🇷🇺 RU | RIPE | assigned |
| 2a11:7d07::/32 | 🇷🇺 RU | RIPE | assigned |
| 2a11:9041::/32 | 🇷🇺 RU | RIPE | assigned |
| 2a11:9642::/32 | 🇷🇺 RU | RIPE | assigned |
| 2a11:ab82::/32 | 🇷🇺 RU | RIPE | assigned |
| 2a11:bdc0::/32 | 🇷🇺 RU | RIPE | assigned |
| 2a12:e81::/32 | 🇷🇺 RU | RIPE | assigned |
| 2a12:6483::/32 | 🇷🇺 RU | RIPE | assigned |
| 2a12:bc81::/32 | 🇷🇺 RU | RIPE | assigned |
| 2a12:f983::/32 | 🇷🇺 RU | RIPE | assigned |
All 14 announced prefixes of AS206174 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS206174 hands its own prefixes to: transit providers, or peers at an exchange.
- AS35196IH TRANSIT FIRST SERVER LIMITED14
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 AS206174 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/206174Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/206174" | jq