SIDNET TELECOM
Cluster stats
Netblocks11
Cluster ID191607635
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.177.8.0/23 SIDNET TELECOM BGP ANNOUNCED ● high
45.177.8.0/22 SIDNET TELECOM BGP ANNOUNCED ● high
45.177.10.0/23 SIDNET TELECOM BGP ANNOUNCED ● high
2804:5d5c::/34 SIDNET TELECOM BGP ANNOUNCED ● high
2804:5d5c::/32 SIDNET TELECOM BGP ANNOUNCED ● high
2804:5d5c:4000::/34 SIDNET TELECOM BGP ANNOUNCED ● high
2804:5d5c:8000::/34 SIDNET TELECOM BGP ANNOUNCED ● high
2804:5d5c:c000::/34 SIDNET TELECOM BGP ANNOUNCED ● high
212.113.23.144/28 SIDNET-UK RIPE ASSIGNED PA ● low
212.187.210.0/27 SIDNET-UK RIPE ASSIGNED PA ● low
2001:df2:ffc0::/48 SIDNET-ID APNIC ASSIGNED PORTABLE ● low

Network trust

what's this?
RPKI hygiene: F how networks compare →
9.1% of checked blocks have valid RPKI ROA coverage (1 of 11)
Possible discrepancies (1)

These blocks are registered to SIDNET TELECOM 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.

2001:df2:ffc0::/48 /48 authorized for AS150923 — PT Sistem Interkoneksi Data

NIC Handles

AS268967 DUMY-RIPE DUMY-RIPE LEVEL3-MNT MARP1-AP MARP1-AP MNT-APJII-ID