MICROLINK-AS-AP

Data as of 2026-09-13
Handle
This organisation
Netblocks6
IPv6 2 prefixes (largest 2001:df3:d680::240/128)
Record ID243184688
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution RIR handle
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 · report an issue

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.151.196.240/32 MICROLINK-AS-AP PEERINGDB ASSIGNED ● high
103.161.216.172/32 MICROLINK-AS-AP PEERINGDB ASSIGNED ● high
160.191.82.88/32 MICROLINK-AS-AP PEERINGDB ASSIGNED ● high
163.61.160.85/32 MICROLINK-AS-AP PEERINGDB ASSIGNED ● high
2001:df3:d680::240/128 MICROLINK-AS-AP PEERINGDB ASSIGNED ● high
2407:840:1:800::a9/128 MICROLINK-AS-AP PEERINGDB ASSIGNED ● high

IPv6 ranges (2)

Footprint over time

3 weekly snapshots · JSON
6 0 netblocks since 2026-08-09
2026-08-09 peak 6 2026-09-06

Network trust

what's this?
RPKI hygiene: D how networks compare →
33.3% of checked blocks have valid RPKI ROA coverage (2 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS134601