AS200063 ECUTuneFiles Tanguy DELMER
🇫🇷Org handle: ORG-TD177-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)3.8×10²⁵
Announced (BGP)1.9×10²⁵
Routing hygiene
Score 10/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
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
Based on 2 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)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 194.15.53.0/24 | 🇪🇺 EU | RIPE | assigned |
| 2a0c:b641:200::/44 | 🇫🇷 FR | RIPE | assigned |
| 2a10:4646:290::/44 | 🇫🇷 FR | RIPE | assigned |
All 2 announced prefixes of AS200063 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS200063 hands its own prefixes to: transit providers, or peers at an exchange.
- AS198831HOLYCLOUD GENIUSWEER SAS2
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 AS200063 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/200063Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/200063" | jq