NETROPOLYS S.A.
Data as of 2026-08-23
BGP inherited
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 · 1,025 IPv4 addresses |
| IPv6 | 1 prefix (largest 2801:168:1::5/128) |
| Cluster ID | 229143487 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
3 weekly snapshots · JSON
12
0 netblocks since 2026-07-05
2026-07-05
peak 12
2026-07-12
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 138.204.255.5/32 | NETROPOLYS S.A. | PEERINGDB | ASSIGNED | ● high |
| 2801:168:1::5/128 | NETROPOLYS S.A. | PEERINGDB | ASSIGNED | ● high |
| 192.141.92.0/22 | NETROPOLYS S.A. | LACNIC | ALLOCATED | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2801:168:1::5/128 |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (1)
These blocks are registered to NETROPOLYS S.A. but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 192.141.92.0/22 /22 | authorized for AS265823 — AS265823 |
NIC Handles
AR-NESA50-LACNIC
AS265823
SEA49
SEA49
SEA49