WIRCOM S.P.A.
BGP inherited
Cluster stats
Netblocks11
All fragments 19 blocks across 6 clusters
Cluster ID191595657
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 9 shared RIR contact/maintainer handles
Registry names 5 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
11 +1 netblocks since 2026-07-05
2026-07-05 peak 11 2026-07-12

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
170.247.204.0/22 AS264827 BGP ANNOUNCED ● high
176.101.176.0/21 Wircom s.r.o. RIPE ASSIGNED PI ● high
176.101.176.0/21 Wircom s.r.o. BGP ANNOUNCED ● high
187.102.192.0/23 AS264827 BGP ANNOUNCED ● high
187.102.195.0/24 AS264827 BGP ANNOUNCED ● high
2803:36c0::/32 AS264827 BGP ANNOUNCED ● high
2803:36c0::/32 UNKNOWN LACNIC allocated ● high
2803:36c0:e807::/48 AS264827 BGP ANNOUNCED ● high
87.204.157.160/28 Wircom RIPE ASSIGNED PA ● low
87.204.157.176/29 Wircom RIPE ASSIGNED PA ● low
212.106.1.200/29 Wircom RIPE ASSIGNED PA ● low

Network trust

what's this?
RPKI hygiene: B how networks compare →
81.8% of checked blocks have valid RPKI ROA coverage (9 of 11)
Possible discrepancies (6)

These blocks are registered to WIRCOM S.P.A. 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.

2803:36c0::/32 /32 authorized for AS264827 — AS264827
2803:36c0::/32 /32 authorized for AS264827 — AS264827
2803:36c0:e807::/48 /48 authorized for AS264827 — AS264827
170.247.204.0/22 /22 authorized for AS264827 — AS264827
187.102.192.0/23 /23 authorized for AS264827 — AS264827
187.102.195.0/24 /24 authorized for AS264827 — AS264827

NIC Handles

AS264827 AS57566 DUMY-RIPE DUMY-RIPE NETIA-MNT ORG-WIRC1-RIPE RIPE-NCC-END-MNT WIRCOM-MNT WIRCOM-MNT