SEAKING

BGP inherited
Cluster stats
Netblocks8
Registered in United Kingdom (4) · Finland (3) · Hong Kong (1)
All fragments 12 blocks across 4 clusters
Cluster ID209520225
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 11 shared RIR contact/maintainer handles
Registry names 4 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 (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.11.208.144/28 SEAKING-NET RIPE ASSIGNED PA ● low
192.194.211.16/29 SEAKING-NET RIPE ASSIGNED PA ● low
194.100.92.112/28 SEAKING_OY RIPE ASSIGNED PA ● low
195.89.165.136/29 SEAKING RIPE ASSIGNED PA ● low
195.89.177.72/29 SEAKING RIPE ASSIGNED PA ● low
195.89.192.164/30 SEAKING RIPE ASSIGNED PA ● low
195.89.237.224/29 SEAKING RIPE ASSIGNED PA ● low
203.186.66.48/30 SEAKING APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

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

NIC Handles

AC2009-AP CH134-AP CH134-AP DATANET-NOC DUMY-RIPE DUMY-RIPE FI2G-MNT MAINT-HK-CTI S1-MNT VODAFONE-UK-MNTNER VODAFONE-WORLDWIDE-MNTNER