Ilm-Provider UG

Ilm-Provider
Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks10 · 2,053 IPv4 addresses
IPv6 3 prefixes (largest 2001:7f8:19:1:0:3:168:1/128)
All fragments 33 blocks across 12 clusters
Cluster ID214586661
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

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

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.81.192.210/32 Ilm-Provider PEERINGDB ASSIGNED ● high
185.1.170.240/32 Ilm-Provider PEERINGDB ASSIGNED ● high
185.1.208.216/32 Ilm-Provider PEERINGDB ASSIGNED ● high
185.1.210.209/32 Ilm-Provider PEERINGDB ASSIGNED ● high
193.178.185.136/32 Ilm-Provider PEERINGDB ASSIGNED ● high
2001:7f8::3:168:0:1/128 Ilm-Provider PEERINGDB ASSIGNED ● high
2001:7f8:19:1:0:3:168:1/128 Ilm-Provider PEERINGDB ASSIGNED ● high
2001:7f8:9e:0:3:168:0:1/128 Ilm-Provider PEERINGDB ASSIGNED ● high
178.21.0.0/22 ILM-PROVIDER-NET RIPE ASSIGNED PA ● low
178.21.4.0/22 ILM-PROVIDER RIPE ASSIGNED PA ● low

IPv6 ranges (3)

Network trust

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

NIC Handles

AS196968 DUMY-RIPE DUMY-RIPE MNT-ILMPCK