AS214838 osiomagency OSIOM AGENCY SAS
🇫🇷Org handle: ORG-OAS7-RIPE
-----BEGIN TOKEN-----d574f2b7b70db078106db4eb50cb4a3af3b9e6ed99c004bade99148ea8844b71faf69c71478e98452c5209651b1d3fdbf1381414ef6ed7c6c170a4575ff3f0c1-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)2×10²⁵
Announced (BGP)1.2×10²⁴
Routing hygiene
Score 6/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 44/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 3 announced prefixes, updated daily (2026-10-25). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRRRIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 141.11.155.0/24 | 🇫🇷 FR | RIPE | assigned |
| 200.102.93.0/24 | 🇫🇷 FR | RIPE | assigned |
| 2a0f:85c1:bb8::/48 | 🇫🇷 FR | RIPE | assigned |
| 2a10:4646:480::/44 | 🇫🇷 FR | RIPE | assigned |
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 AS214838 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/214838Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/214838" | jq