LOGISTIC

BGP inherited
Cluster stats
Netblocks6
Registered in Poland (2) · Germany (1) · Hong Kong (1) · KZ (1) · Russia (1)
All fragments 28 blocks across 20 clusters
Cluster ID209229442
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 10 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
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
78.11.84.0/30 LOGISTIC RIPE ASSIGNED PA ● low
78.11.110.196/30 LOGISTIC RIPE ASSIGNED PA ● low
88.204.226.84/30 LOGISTIC RIPE ASSIGNED PA ● low
151.189.106.144/28 LOGISTIC-NET RIPE ASSIGNED PA ● low
210.6.244.200/29 LOGISTIC APNIC ASSIGNED NON-PORTABLE ● low
217.26.5.32/28 LOGISTIC-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “LOGISTIC” — 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.
Combined view of all 20 name-family clusters →
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 →
83.3% of checked blocks have valid RPKI ROA coverage (5 of 6)
No discrepancies found among checked blocks.

NIC Handles

AC2009-AP ARCOR-MNT CH134-AP CH134-AP DUMY-RIPE DUMY-RIPE KNIC-MNT MAINT-HK-CTI NETIA-MNT TASCOM-MNT-RIPE