AS203532
Thales Cloud Securise SAS — s3ns.io
Summary
| Country |
 France
|
| Organization | Thales Cloud Securise SAS |
| Domain | s3ns.io |
| Number of IPv4 | 16,128 |
| Number of IPv6 | 5.3108× 1027 |
| AS Type | Hosting |
| Registry | RIPE NCC |
| Allocated | July 29, 2022 (about 2 years ago) |
| Updated | September 12, 2024 (about 7 months ago) |
IP Ranges
AS203532 announces 12 IPv4 ranges and 13 IPv6 ranges.
That's a total of 16,128 IPv4 addresses and 5.3108× 1027 IPv6 addresses.
| Prefix | Organization | Size | Registry | Status |
|---|---|---|---|---|
| 31.43.174.0/24 |
Thales Cloud Securise SAS
|
256 | RIPE NCC | ALLOCATED PA |
| 31.43.175.0/24 |
Thales Cloud Securise SAS
|
256 | RIPE NCC | ALLOCATED PA |
| 177.222.64.0/19 |
Thales Cloud Securise SAS
|
8,192 | RIPE NCC | ALLOCATED PA |
| 177.222.64.0/21 |
Thales Cloud Securise SAS
|
2,048 | RIPE NCC | ALLOCATED PA |
| 177.222.72.0/21 |
Thales Cloud Securise SAS
|
2,048 | RIPE NCC | ALLOCATED PA |
| 177.222.80.0/22 |
Thales Cloud Securise SAS
|
1,024 | RIPE NCC | ALLOCATED PA |
| 177.222.84.0/22 |
Thales Cloud Securise SAS
|
1,024 | RIPE NCC | ALLOCATED PA |
| 177.222.88.0/24 |
Thales Cloud Securise SAS
|
256 | RIPE NCC | ALLOCATED PA |
| 177.222.89.0/24 |
Thales Cloud Securise SAS
|
256 | RIPE NCC | ALLOCATED PA |
| 177.222.90.0/24 |
Thales Cloud Securise SAS
|
256 | RIPE NCC | ALLOCATED PA |
| 177.222.91.0/24 |
Thales Cloud Securise SAS
|
256 | RIPE NCC | ALLOCATED PA |
| 177.222.92.0/24 |
Thales Cloud Securise SAS
|
256 | RIPE NCC | ALLOCATED PA |
| Prefix | Organization | Size | Registry | Status |
|---|---|---|---|---|
| 2a13:7500::/48 |
Thales Cloud Securise SAS
|
1.2089× 1024 | RIPE NCC | ALLOCATED-BY-RIR |
| 2a13:7500::/36 |
Thales Cloud Securise SAS
|
4.9518× 1027 | RIPE NCC | ALLOCATED-BY-RIR |
| 2a13:7500:200::/40 |
Thales Cloud Securise SAS
|
3.0949× 1026 | RIPE NCC | ALLOCATED-BY-RIR |
| 2a13:7500:241::/48 |
Thales Cloud Securise SAS
|
1.2089× 1024 | RIPE NCC | ALLOCATED-BY-RIR |
| 2a13:7500:242::/48 |
Thales Cloud Securise SAS
|
1.2089× 1024 | RIPE NCC | ALLOCATED-BY-RIR |
| 2a13:7500:248::/48 |
Thales Cloud Securise SAS
|
1.2089× 1024 | RIPE NCC | ALLOCATED-BY-RIR |
| 2a13:7500:320::/44 |
Thales Cloud Securise SAS
|
1.9343× 1025 | RIPE NCC | ALLOCATED-BY-RIR |
| 2a13:7500:8100::/44 |
Thales Cloud Securise SAS
|
1.9343× 1025 | RIPE NCC | ALLOCATED-BY-RIR |
| 2a13:7500:8100::/48 |
Thales Cloud Securise SAS
|
1.2089× 1024 | RIPE NCC | ALLOCATED-BY-RIR |
| 2a13:7500:8101::/48 |
Thales Cloud Securise SAS
|
1.2089× 1024 | RIPE NCC | ALLOCATED-BY-RIR |
| 2a13:7500:8102::/48 |
Thales Cloud Securise SAS
|
1.2089× 1024 | RIPE NCC | ALLOCATED-BY-RIR |
| 2a13:7500:8103::/48 |
Thales Cloud Securise SAS
|
1.2089× 1024 | RIPE NCC | ALLOCATED-BY-RIR |
| 2a13:7500:81fe::/48 |
Thales Cloud Securise SAS
|
1.2089× 1024 | RIPE NCC | ALLOCATED-BY-RIR |
Peers
AS203532 does not have any direct peering agreements. Instead, its global connectivity is achieved through transit providers. While this setup ensures comprehensive reach, future peering could reduce latency and optimize route efficiency.
Upstreams
AS203532 connects to the global Internet via at least 2 upstream providers. In this setup, AS203532 acts as a customer, subscribing to these transit services to obtain full BGP routing information and ensure reliable, redundant access to external networks.
Downstreams
AS203532 currently has no downstream networks, meaning it does not serve as a transit provider to customer networks.