AS212012 Tours_DTC Thales DIS France SAS
🇫🇷Org handle: ORG-TDFS3-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)2,304
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)1.2×10²⁴
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)6Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.8.105.0/24 | 🇫🇷 FR | RIPENCC | allocated |
| 91.240.72.0/24 | 🇫🇷 FR | RIPENCC | assigned |
| 185.42.232.0/22 | 🇫🇷 FR | RIPENCC | allocated |
| 185.42.232.0/24 | 🇫🇷 FR | RIPE | assigned |
| 194.88.222.0/23 | 🇫🇷 FR | RIPENCC | assigned |
| 2a04:7040::/29 | 🇫🇷 FR | RIPENCC | allocated |
All 4 announced prefixes of AS212012 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS212012 hands its own prefixes to: transit providers, or peers at an exchange.
- AS19551Incapsula4
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 AS212012 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/212012Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/212012" | jq