TARMAC

BGP inherited
Cluster stats
Netblocks8 · 326 IPv4 addresses
Registered in United Kingdom (5) · China (1)
All fragments 11 blocks across 4 clusters
Cluster ID209108232
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
192.189.160.0/24 TARMAC RIPE LEGACY ● high
218.80.205.168/30 TARMAC-CO APNIC ASSIGNED NON-PORTABLE ● high
86.188.176.80/28 TARMAC RIPE ASSIGNED PA ● low
86.188.176.96/28 TARMAC RIPE ASSIGNED PA ● low
213.122.162.192/27 TARMAC RIPE ASSIGNED PA ● low
217.33.247.160/29 TARMAC RIPE ASSIGNED PA ● low
2a00:2381:edb::/56 TARMAC RIPE ASSIGNED ● low
2a00:2381:133a::/48 TARMAC RIPE AGGREGATED-BY-LIR ● low

Possibly related to this organisation

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

Network trust

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

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE LBS10-AP LBS10-AP LT7675-MNT MAINT-CHINANET-SH