2a13:7500:1000::/36 - S3ns Thales Cloud Securise SAS (AS202045)
CIDR
2a13:7500:1000::/36
IP Version
IPv6
Addresses
4951.7Y
Mask
/36
Country
🇫🇷 France
City
Paris
RIR
RIPE NCC
Status
announced
Allocated
-
Announced BGP Routes
1 of 1 routeRPKI:
IRR:
Swipe sideways to see all columns →
| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 2a13:7500:1000::/36 | AS202045 s3ns Thales Cloud Securise SAS | Valid | RIPE | 2026-10-11 |
More-Specific Announcements
6 more-specific announcements| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 2a13:7500:1000::/48 | AS202045 s3ns Thales Cloud Securise SAS | Valid | - | 2026-10-11 |
| 2a13:7500:1200::/44 | AS202045 s3ns Thales Cloud Securise SAS | Valid | - | 2026-10-11 |
| 2a13:7500:1241::/48 | AS202045 s3ns Thales Cloud Securise SAS | Valid | - | 2026-10-11 |
| 2a13:7500:1242::/48 | AS202045 s3ns Thales Cloud Securise SAS | Valid | - | 2026-10-11 |
| 2a13:7500:1248::/48 | AS202045 s3ns Thales Cloud Securise SAS | Valid | - | 2026-10-11 |
| 2a13:7500:1320::/44 | AS202045 s3ns Thales Cloud Securise SAS | Valid | - | 2026-10-11 |
Origin ASN
AS202045
s3ns Thales Cloud Securise SAS
Related Prefixes
Geolocation
Abuse Contact
Learn more
- RPKI and ROAs explainedWhat RPKI valid, invalid and no ROA mean
- RPKI validatorCheck ROA coverage for any prefix or ASN
- What is BGP?How prefixes are announced and routed
- More-specific prefixesGlossary: covering and more-specific routes
- IPv4 transfers in the RIPE NCC regionWho bought and sold address space recently
API
Open https://api.ipctl.io/v1/prefix/2a13:7500:1000::/36Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/2a13:7500:1000::/36" | jq
External Links