TPR

BGP inherited
Cluster stats
Netblocks7
Registered in Russia (3) · India (2) · Netherlands (2)
All fragments 10 blocks across 4 clusters
Cluster ID209861562
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 12 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
210.212.173.192 – 210.212.173.239 tpr APNIC ASSIGNED NON-PORTABLE ● high
210.212.179.192/28 TPR-NET APNIC ASSIGNED NON-PORTABLE ● high
81.95.130.176/30 TPR RIPE ASSIGNED PA ● low
81.95.140.8/29 TPR RIPE ASSIGNED PA ● low
92.242.53.48/28 TPR RIPE ASSIGNED PA ● low
93.117.247.160/29 TPR RIPE ASSIGNED PA ● low
93.117.247.184/29 TPR RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “TPR” — 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.

Network trust

what's this?
RPKI hygiene: C how networks compare →
71.4% of checked blocks have valid RPKI ROA coverage (5 of 7)
No discrepancies found among checked blocks.

NIC Handles

CDN1-AP DS719-AP DUMY-RIPE DUMY-RIPE MAINT-IN-DOT MBG3-AP MBG4-AP MBG6-AP NC83-AP NIP13-AP RU-MATRIXTELECOM-MNT TNF-MNT