FEEDBACK-NET-AS12611

Data as of 2026-10-25
BGP inherited
This organisation
Netblocks7
IPv6 1 prefix (largest 2001:16e0:10f::/48)
Record ID254841659
RegistryRIPE
Customerssee who runs inside 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 · report an issue

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.27.170.128/25 FEEDBACK-NET-AS12611 RIPE ASSIGNED PA ● low
91.106.122.16/28 FEEDBACK-NET-AS12611 RIPE ASSIGNED PA ● low
212.77.167.208/28 FEEDBACK-NET-AS12611 RIPE ASSIGNED PA ● low
212.77.178.160/28 FEEDBACK-NET-AS12611 RIPE ASSIGNED PA ● low
212.77.189.32/29 FEEDBACK-NET-AS12611 RIPE ASSIGNED PA ● low
212.77.190.160/28 FEEDBACK-NET-AS12611 RIPE ASSIGNED PA ● low
2001:16e0:10f::/48 FEEDBACK-NET-AS12611 RIPE ASSIGNED ● low

IPv6 ranges (1)

Footprint over time

18 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-10-25

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
Possible discrepancies (1)

These blocks are registered to FEEDBACK-NET-AS12611 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.

2001:16e0:10f::/48 /48 authorized for AS12611 — R-KOM Regensburger Telekommunikationsgesellschaft mbH

NIC Handles

DUMY-RIPE DUMY-RIPE RKOM-MNT