FRAKO-TENINGEN-NET

BGP inherited
Cluster stats
Netblocks6
Cluster ID208808145
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
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.153.97.248/29 FRAKO-TENINGEN-NET RIPE ASSIGNED PA ● low
62.154.158.80/29 FRAKO-TENINGEN-NET RIPE ASSIGNED PA ● low
87.130.53.224/29 FRAKO-TENINGEN-NET RIPE ASSIGNED PA ● low
217.7.162.16/29 FRAKO-TENINGEN-NET RIPE ASSIGNED PA ● low
2003:53:15::/48 FRAKO-TENINGEN-NET RIPE ASSIGNED ● low
2003:e2:401a::/48 FRAKO-TENINGEN-NET 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.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

DTAG-NIC DUMY-RIPE DUMY-RIPE