AS213873 OUIDO-Hosting MOJI SAS
๐ซ๐ทOrg handle: ORG-MS374-RIPE
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)3ร10ยฒโถ
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
๐ซ๐ท FRRIR
RIPE NCCStatus
allocated
Allocated
2024-11-12
Routing hygiene
Score 20/100 ยท Low riskRPKI ROA coverage
66.7%
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
- 33% of announced prefixes (1 of 3) have no valid ROA
- Only one upstream seen in the AS paths of its routes
Based on 3 announced prefixes, updated daily (2026-10-20). How the score works ยท RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | Other IRR | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 203.55.81.0/24 | ๐ซ๐ท FR | RIPENCC | allocated |
All 3 announced prefixes of AS213873 โ
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS213873 hands its own prefixes to: transit providers, or peers at an exchange.
- AS47160MOJI SAS3
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/213873Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/213873" | jq