SECW TELECOM
BGP inherited
Cluster stats
| Netblocks | 6 |
| All fragments | 8 blocks across 2 clusters |
| Cluster ID | 207724829 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
4 weekly snapshots · JSON
6
-42 netblocks since 2026-07-05
2026-07-05
peak 48
2026-07-13
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.184.144.125/32 | SECW TELECOM | PEERINGDB | ASSIGNED | ● high |
| 64.191.233.217/32 | SECW TELECOM | PEERINGDB | ASSIGNED | ● high |
| 187.16.221.6/32 | SECW TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:7:0:26:6409:1/128 | SECW TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8::221:6/128 | SECW TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:13::125/128 | SECW TELECOM | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(4 of 6)
No discrepancies found among checked blocks.
NIC Handles
AS266409