INTINFORM-NET

BGP inherited
Cluster stats
Netblocks6 · 1,034 IPv4 addresses
All fragments 7 blocks across 2 clusters
Cluster ID208934667
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names 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
89.17.48.0/24 INTINFORM-NET RIPE ASSIGNED PA ● low
217.15.48.0/24 INTINFORM RIPE ASSIGNED PA ● low
217.15.49.0 – 217.15.49.175 INTINFORM RIPE ASSIGNED PA ● low
217.15.52.0/24 INTINFORM-NET RIPE ASSIGNED PA ● low
217.15.54.128/26 INTINFORM-NET RIPE ASSIGNED PA ● low
217.15.54.224/27 INTINFORM-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “INTINFORM” — 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: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (5 of 6)
Possible discrepancies (2)

These blocks are registered to INTINFORM-NET but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

217.15.48.0/24 /24 authorized for AS25531 — PJSC Rostelecom
217.15.52.0/24 /24 authorized for AS25531 — PJSC Rostelecom

NIC Handles

DUMY-RIPE DUMY-RIPE INTFRM-RIPE-MNT