Bestinet

Registry

Cluster stats

Netblocks	7
All fragments	9 blocks across 3 clusters
Cluster ID	212708059
Registry	APNIC
Customers	find customers using this network →

Evidence & provenance ?

Attribution	Registry record
Shared handles	clustered on 9 shared RIR contact/maintainer handles
Registry names	3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON

7 0 netblocks since 2026-07-05

2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
43.254.82.102/32	Bestinet	PEERINGDB	ASSIGNED	● high
119.11.185.85/32	Bestinet	PEERINGDB	ASSIGNED	● high
123.108.11.49/32	Bestinet	PEERINGDB	ASSIGNED	● high
2001:c18:dc00:205a::/64	BESTINET	APNIC	ASSIGNED NON-PORTABLE	● low
2001:c18:dc00:206b::/64	BESTINET	APNIC	ASSIGNED NON-PORTABLE	● low
2402:1a80:dc00:2010::/64	Bestinet	APNIC	ALLOCATED NON-PORTABLE	● low
2402:1a80:dc00:2011::/64	Bestinet	APNIC	ALLOCATED NON-PORTABLE	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “Bestinet” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

BESTINET-2 1 blocks
BESTINET-1 1 blocks

Sub-allocations under carriers

IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

BESTINET-2 via NTT MSC SDN. BHD. sub-allocation
BESTINET-1 via NTT MSC SDN. BHD. sub-allocation

Network trust

what's this?

RPKI hygiene: B how networks compare →

85.7% of checked blocks have valid RPKI ROA coverage (6 of 7)

No discrepancies found among checked blocks.

NIC Handles

AN638-AP AN941-AP AS153085 MAINT-MY-NTT-MSC MAINT-NMSBM-MY NDEI2-AP NDEI2-AP NT202-AP NT204-AP