PILLAR-NET

BGP inherited
Cluster stats
Netblocks6
Registered in Serbia (5) · Ukraine (1)
All fragments 8 blocks across 3 clusters
Cluster ID209483160
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
89.216.36.48/28 PILLAR-NET RIPE ASSIGNED PA ● low
178.254.129.40/30 PILLAR-NET RIPE ASSIGNED PA ● low
178.254.131.240/28 PILLAR-NET RIPE ASSIGNED PA ● low
213.186.197.72/29 PILLAR RIPE ASSIGNED PA ● low
217.169.211.248/29 PILLAR-NET RIPE ASSIGNED PA ● low
217.169.221.144/29 PILLAR-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

DUMY-RIPE DUMY-RIPE FARLEP-MNT ORIONTELEKOM-MNT SBB-MNT