CAR SYSTEMS BV

CAR-SYSTEMS_BV
Registry
Cluster stats
Netblocks4
All fragments 8 blocks across 3 clusters
Cluster ID204909852
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (4)

⬇ export CSV
CIDR Org name Registry Status Confidence
77.158.34.80/28 CAR-SYSTEMS RIPE ASSIGNED PA ● low
109.3.194.36/30 CAR-SYSTEMS RIPE ASSIGNED PA ● low
213.125.43.80/29 CAR-SYSTEMS_BV RIPE ASSIGNED PA ● low
2001:41f0:31f8::/48 CAR-SYSTEMS_BV RIPE ASSIGNED ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “CAR SYSTEMS” — 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 (4 of 4)
Possible discrepancies (1)

These blocks are registered to CAR-SYSTEMS_BV but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2001:41f0:31f8::/48 /48 authorized for AS33915 — Vodafone Libertel B.V.

NIC Handles

DUMY-RIPE DUMY-RIPE LDCOM-MNT LDCOM-PRO-MNT ZIGGO-AUTOREG1