AS197761 hostslim-as Elkin Semyon Yuryevich
🇷🇺Org handle: ORG-ES713-RIPE
-----BEGIN TOKEN-----283ba1186e4b4ce3cdf28b02367646b266fae8787022571874e64d43cefe195c39346b94e3d5d25475277923d18804d112a650f9cc8b6cecaf2314bddff18e12-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
4total
2 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)2.4×10²⁴
Routing hygiene
Score 15/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
2
0 announced against others' ROAs, 2 own announced by others
Upstreams
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
- 2 prefixes of this ASN announced by another network against its ROAs
Based on 4 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
204.10.195.0/24MOAS | Valid | ARIN | 2026-10-26 |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
All 4 announced prefixes of AS197761 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS197761 hands its own prefixes to: transit providers, or peers at an exchange.
- AS203446AS203446 SMARTNET Germany4
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 AS197761 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/197761Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/197761" | jq