Traffic Manager
Cluster stats
Netblocks14
All fragments 537 blocks across 44 clusters
Cluster ID192656059
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 11 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
14 0 netblocks since 2026-07-05
2026-07-05 peak 14 2026-07-06

IP Ranges (14)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.39.23.24/29 Traffic Manager RIPE ASSIGNED PA ● high
5.196.45.224/28 Traffic Manager RIPE ASSIGNED PA ● high
5.196.166.128/29 Traffic Manager RIPE ASSIGNED PA ● high
51.75.225.128/27 Traffic Manager RIPE LEGACY ● high
51.77.8.32/29 Traffic Manager RIPE LEGACY ● high
54.36.1.240/29 Traffic Manager RIPE LEGACY ● high
61.164.146.176/28 TRAFFIC-FTP APNIC ASSIGNED NON-PORTABLE ● high
92.222.98.224/28 Traffic Manager RIPE ASSIGNED PA ● high
92.222.252.224/27 Traffic Manager RIPE ASSIGNED PA ● high
137.74.247.32/29 Traffic Manager RIPE ASSIGNED PA ● high
146.59.135.0/27 Traffic Manager RIPE LEGACY ● high
147.135.166.156/30 Traffic Manager RIPE ASSIGNED PA ● high
147.135.166.176/30 Traffic Manager RIPE ASSIGNED PA ● high
58.181.216.224/28 TRAFFIC-TH APNIC ASSIGNED NON-PORTABLE ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (14 of 14)
No discrepancies found among checked blocks.

NIC Handles

AK1137-AP CW27-AP DUMY-RIPE DUMY-RIPE KSC-ADMIN MAINT-CN-CHINANET-ZJ-WZ ORG-TM109-RIPE OVH-MNT TOC1-AP TOC1-AP XC605-AP