AS211352 OBSIDIAN-CORE Tom MARQUAILLE trading as OBSIDIAN CORE
🇫🇷Org handle: ORG-TMTA6-RIPE
VULTR
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)2×10²⁵
Announced (BGP)1.2×10²⁴
Routing hygiene
Score 25/100 · Medium riskRPKI ROA coverage
50%
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
1
diversity 0/100
- 50% of announced prefixes (1 of 2) have no valid ROA
- Only one upstream seen in the AS paths of its routes
Based on 2 announced prefixes, updated daily (2026-10-18). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| No ROA | RIPE | 2026-10-26 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 217.147.12.0/24 | 🇫🇷 FR | RIPE | assigned |
| 2a10:4646:4c0::/44 | 🇫🇷 FR | RIPE | assigned |
| 2a10:4646:4c0::/48 | 🇫🇷 FR | RIPE | assigned |
All 2 announced prefixes of AS211352 →
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS207745 | 🇫🇷MVINC-CORE Vincent Morvan |
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS211352 hands its own prefixes to: transit providers, or peers at an exchange.
- AS39421SAPINET SAS2
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/211352Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/211352" | jq