AS198423 RESOLV-AS Resolv SARL
🇫🇷Org handle: ORG-RS50-RIPE
-----BEGIN TOKEN-----b59d848dbf9c127e6f2d5a38c97a6d6a7b72d8ae0ff8c477e6cd9d4f8c3d071c3e61937d94a2754f0335cbd6c066715e976be2a2d5c217a9c4a662606fa31ed3-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)0
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 192.41.216.0/24 | 🇫🇷 FR | RIPENCC | assigned |
| 2001:678:a64::/48 | 🇫🇷 FR | RIPENCC | assigned |
All 1 announced prefix of AS198423 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS198423 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16276OVH SAS1
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 AS198423 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/198423Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/198423" | jq