ROCOM-GROUP

BGP inherited
Cluster stats
Netblocks8 · 348 IPv4 addresses
Registered in United Kingdom (4) · Sweden (3) · Hong Kong (1)
All fragments 12 blocks across 5 clusters
Cluster ID208840641
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-12

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
193.12.157.248/29 SE-ROCOM RIPE ASSIGNED PA ● low
193.82.112.80/28 ROCOM-GROUP-LIMITED RIPE ASSIGNED PA ● low
193.132.233.144/28 ROCOM-GROUP RIPE ASSIGNED PA ● low
193.133.113.160 – 193.133.113.255 ROCOM-GROUP RIPE ASSIGNED PA ● low
194.131.194.64 – 194.131.194.255 ROCOM-GROUP RIPE ASSIGNED PA ● low
212.247.87.48/28 SE-ROCOM RIPE ASSIGNED PA ● low
212.247.219.88/29 SE-ROCOM RIPE ASSIGNED PA ● low
213.104.1.128/30 ROCOM-GROUP-LTD RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

AS1849-MNT AS5089-MNT DUMY-RIPE DUMY-RIPE PSINET-UK-SYSADMIN SWIPNET-LIR-MNT