REMMERS-LOENINGEN-NET

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks7
IPv6 1 prefix (largest 2003:67:4021::/48)
Cluster ID213288213
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 · report an issue

Footprint over time

6 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-26

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.153.93.32/28 REMMERS-LOENINGEN-NET RIPE ASSIGNED PA ● low
62.153.168.224/29 REMMERS-LOENINGEN-NET RIPE ASSIGNED PA ● low
62.156.164.136/29 REMMERS-LOENINGEN-NET RIPE ASSIGNED PA ● low
62.159.153.216/29 REMMERS-LOENINGEN-NET RIPE ASSIGNED PA ● low
80.152.50.48/29 REMMERS-LOENINGEN-NET RIPE ASSIGNED PA ● low
217.6.130.56/29 REMMERS-LOENINGEN-NET RIPE ASSIGNED PA ● low
2003:67:4021::/48 REMMERS-LOENINGEN-NET RIPE ASSIGNED ● low

IPv6 ranges (1)

Network trust

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

NIC Handles

DTAG-NIC DUMY-RIPE DUMY-RIPE