PRAXIS-PROJEKT-WEIDEN-NET

Data as of 2026-11-08
BGP inherited
This organisation
Netblocks7
IPv6 2 prefixes (largest 2003:dd:3020::/48)
Also registered under this name 9 netblocks across 2 separate records
Record ID266316066
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
91.24.99.208/29 PRAXIS-PROJEKT-WEIDEN-NET RIPE ASSIGNED PA ● low
91.24.159.224/27 PRAXIS-PROJEKT-WEIDEN-NET RIPE ASSIGNED PA ● low
91.24.174.32/27 PRAXIS-PROJEKT-WEIDEN-NET RIPE ASSIGNED PA ● low
91.24.182.64/26 PRAXIS-PROJEKT-WEIDEN-NET RIPE ASSIGNED PA ● low
217.239.250.184/29 PRAXIS-PROJEKT-WEIDEN-NET RIPE ASSIGNED PA ● low
2003:dd:3020::/48 PRAXIS-PROJEKT-WEIDEN-NET RIPE ASSIGNED ● low
2003:f1:b02b::/48 PRAXIS-PROJEKT-WEIDEN-NET RIPE ASSIGNED ● low

IPv6 ranges (2)

Footprint over time

7 weekly snapshots · JSON
7 +1 netblocks since 2026-09-27
2026-09-27 peak 7 2026-11-08

Network trust

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

NIC Handles

DTAG-NIC DUMY-RIPE DUMY-RIPE