R-COLLARD

BGP inherited
Cluster stats
Netblocks8
Cluster ID210462163
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 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
81.145.39.224/28 R-COLLARD RIPE ASSIGNED PA ● low
81.145.58.240/29 R-COLLARD-LTD RIPE ASSIGNED PA ● low
213.121.165.240/28 R-COLLARD RIPE ASSIGNED PA ● low
2a00:2381:e667::/48 R-COLLARD RIPE AGGREGATED-BY-LIR ● low
2a00:2381:e667::/56 R-COLLARD RIPE ASSIGNED ● low
2a00:2381:f370::/56 R-COLLARD RIPE ASSIGNED ● low
2a00:2381:f370::/48 R-COLLARD RIPE AGGREGATED-BY-LIR ● low
2a00:2381:f370:100::/56 R-COLLARD-LTD RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
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.
  • Collard via Orange S.A. sub-allocation
  • Collard via Orange S.A. sub-allocation

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

BTNET-MNT DUMY-RIPE DUMY-RIPE