NET-NL-Tesla-Netherlands

BGP inherited
Cluster stats
Netblocks11
All fragments 14 blocks across 2 clusters
Cluster ID210184528
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
10 +2 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
212.78.172.56/29 NET-NL-Tesla-Netherlands RIPE ASSIGNED PA ● low
212.78.173.248/29 NET-NL-Tesla-Netherlands RIPE ASSIGNED PA ● low
212.78.187.48/29 NET-NL-Tesla-Netherlands RIPE ASSIGNED PA ● low
212.123.196.160/29 NET-NL-Tesla-Netherlands RIPE ASSIGNED PA ● low
212.123.199.48/29 NET-NL-Tesla-Netherlands RIPE ASSIGNED PA ● low
212.123.199.208/29 NET-NL-Tesla-Netherlands RIPE ASSIGNED PA ● low
212.123.202.24/29 NET-NL-Tesla-Netherlands RIPE ASSIGNED PA ● low
212.123.250.16/29 NET-NL-Tesla-Netherlands RIPE ASSIGNED PA ● low
212.123.253.32/29 NET-NL-Tesla-Netherlands RIPE ASSIGNED PA ● low
213.208.227.192/29 NET-NL-Tesla-Netherlands RIPE ASSIGNED PA ● low
213.208.230.16/29 NET-NL-Tesla-Netherlands RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “NET NL Tesla” — 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 (11 of 11)
No discrepancies found among checked blocks.

NIC Handles

COLT-NL-MNT DUMY-RIPE DUMY-RIPE