INFO-DATA-LIMBURG-NET

BGP inherited
Cluster stats
Netblocks7
All fragments 12 blocks across 2 clusters
Cluster ID205349381
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

4 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-13

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.153.169.0/24 INFO-DATA-LIMBURG-NET RIPE ASSIGNED PA ● low
87.130.11.248/29 INFO-DATA-LIMBURG-NET RIPE ASSIGNED PA ● low
93.240.172.128/29 INFO-DATA-LIMBURG-NET RIPE ASSIGNED PA ● low
194.25.14.0/24 INFO-DATA-LIMBURG-NET RIPE ASSIGNED PA ● low
2003:5e:13::/48 INFO-DATA-LIMBURG-NET RIPE ASSIGNED ● low
2003:f0:a816::/48 INFO-DATA-LIMBURG-NET RIPE ASSIGNED ● low
2003:f0:a81c::/48 INFO-DATA-LIMBURG-NET RIPE ASSIGNED ● low

Possibly related to this organisation

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

NIC Handles

DTAG-NIC DUMY-RIPE DUMY-RIPE