DCNET TELECOM
Cluster stats
| Netblocks | 63 |
| Cluster ID | 191351808 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 24 shared RIR contact/maintainer handles |
| Registry names | 6 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
63
0 netblocks since 2026-07-05
2026-07-05
peak 63
2026-07-06
IP Ranges (63)
showing 50 of 63 — see all — ⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 37.49.237.254/32 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 80.81.194.61/32 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 80.249.211.149/32 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 101.203.74.125/32 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 101.203.90.189/32 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 103.16.103.47/32 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 103.26.68.48/32 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 103.41.12.32/32 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 103.51.120.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 103.51.121.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 103.203.158.87/32 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 103.216.72.0/22 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 103.216.72.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 103.216.73.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 103.216.74.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 103.216.75.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 103.245.244.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 103.245.245.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 103.245.246.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 103.245.247.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 103.247.139.13/32 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 123.255.90.78/32 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 139.150.100.87/32 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 163.227.120.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 163.227.121.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 163.227.228.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 163.227.229.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 195.66.228.55/32 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 203.167.8.0/22 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 203.167.8.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 203.167.9.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 203.167.10.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 203.167.11.0/24 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 206.82.105.25/32 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:504:36::f8fd:0:1/128 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::f8fd:0:1/128 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a506:3741:1/128 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:4::f8fd:1/128 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:54::1:254/128 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:0:1::ca28:a04e/128 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:8::87/128 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:c::6:3741:1/128 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:12:100::103:47/128 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:dea:0:10::30/128 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:ded::20/128 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:296::a506:3741:1/128 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:df5:66c0::/48 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 2001:df5:7c40::/48 | DCNET TELECOM | BGP | ANNOUNCED | ● high |
| 2403:c780:7200:b074:0:6:3741:1/128 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2403:c780:b800:bb00:0:6:3741:1/128 | DCNET TELECOM | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
85.7%
of checked blocks have valid RPKI ROA coverage
(54 of 63)
Possible discrepancies (1)
These blocks are registered to DCNET 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.
| 211.153.35.0 – 211.153.36.255 /23 | authorized for AS4847 — China Networks Inter-Exchange |
NIC Handles
AR1082-AP
AS142211
AS63741
AS63741
DTH13-AP
DUMY-RIPE
DUMY-RIPE
DZ6-AP
DZ6-AP
HM66-AP
INNOVANTI-MNT
KF31-AP
+12 more