ASYMPTOTE NETWORK
Cluster stats
Netblocks11
All fragments 13 blocks across 3 clusters
Cluster ID191605743
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
36.255.57.180/32 ASYMPTOTE NETWORK PEERINGDB ASSIGNED ● high
149.112.26.102/32 ASYMPTOTE NETWORK PEERINGDB ASSIGNED ● high
160.22.49.217/32 ASYMPTOTE NETWORK PEERINGDB ASSIGNED ● high
163.61.161.21/32 ASYMPTOTE NETWORK PEERINGDB ASSIGNED ● high
204.235.243.0/24 ASYMPTOTE NETWORK, LLC BGP ANNOUNCED ● high
206.80.238.159/32 ASYMPTOTE NETWORK PEERINGDB ASSIGNED ● high
217.217.32.0/22 ASYMPTOTE NETWORK, LLC BGP ANNOUNCED ● high
2001:504:91::159/128 ASYMPTOTE NETWORK PEERINGDB ASSIGNED ● high
2001:de8:7::5:3616:1/128 ASYMPTOTE NETWORK PEERINGDB ASSIGNED ● high
2401:f460:210::5:3616:1/128 ASYMPTOTE NETWORK PEERINGDB ASSIGNED ● high
2404:c140:101e::5:3616/128 ASYMPTOTE NETWORK PEERINGDB ASSIGNED ● high

Network trust

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

These blocks are registered to ASYMPTOTE NETWORK 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.

217.217.32.0/22 /22 authorized for AS49304 — SAKURA LINK LIMITED

NIC Handles

AS53616 AS53616 netutils-mnt