RECKITTBENCKISER

BGP inherited
Cluster stats
Netblocks8
Registered in Australia (6) · KZ (1) · Turkey (1)
All fragments 14 blocks across 5 clusters
Cluster ID209207954
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 22 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
59.100.188.108/30 RECKITTBENCKISER APNIC ASSIGNED NON-PORTABLE ● high
59.100.188.120/30 RECKITTBENCKISER APNIC ASSIGNED NON-PORTABLE ● high
60.241.71.0/30 RECKITTBENCKISER APNIC ASSIGNED NON-PORTABLE ● high
60.241.207.252/30 RECKITTBENCKISER APNIC ASSIGNED NON-PORTABLE ● high
202.168.51.88/29 RECKITTBENCKISER APNIC ASSIGNED NON-PORTABLE ● high
59.154.221.8/29 RECKITTBENCKISER APNIC ASSIGNED NON-PORTABLE ● low
87.247.18.48/30 RECKITTBENCKISER-NET RIPE ASSIGNED PA ● low
176.236.52.224/29 RECKITTBENCKISER-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “RECKITTBENCKISER” — 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: D how networks compare →
25.0% of checked blocks have valid RPKI ROA coverage (2 of 8)
No discrepancies found among checked blocks.

NIC Handles

AA1416-AP DUMY-RIPE DUMY-RIPE MAINT-AU-AAPT MAINT-OPTUSCOM-AP MNT-TELETEK MNT-TELLCOM OA3-AP OA3-AP SATELCOM-MNT SOL-NET SR1005-AP +10 more