Riepert Informationstechnologie GmbH
RIEPERT-CUST-30
BGP inherited
Cluster stats
| Netblocks | 10 |
| All fragments | 39 blocks across 26 clusters |
| Cluster ID | 210739996 |
| Registry | RIPE |
| Customers | find customers using 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 | |
Footprint over time
5 weekly snapshots · JSON
10
0 netblocks since 2026-07-05
2026-07-05
peak 10
2026-07-19
IP Ranges (10)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.89.162.76/30 | RIEPERT-CUST-30 | RIPE | ASSIGNED PA | ● low |
| 185.89.162.88/30 | RIEPERT-CUST-30 | RIPE | ASSIGNED PA | ● low |
| 185.89.162.92/30 | RIEPERT-CUST-30 | RIPE | ASSIGNED PA | ● low |
| 185.89.162.192/30 | RIEPERT-CUST-30 | RIPE | ASSIGNED PA | ● low |
| 185.89.162.196/30 | RIEPERT-CUST-30 | RIPE | ASSIGNED PA | ● low |
| 185.89.162.208/30 | RIEPERT-CUST-30 | RIPE | ASSIGNED PA | ● low |
| 185.89.162.212/30 | RIEPERT-CUST-30 | RIPE | ASSIGNED PA | ● low |
| 185.89.162.216/30 | RIEPERT-CUST-30 | RIPE | ASSIGNED PA | ● low |
| 185.89.162.220/30 | RIEPERT-CUST-30 | RIPE | ASSIGNED PA | ● low |
| 185.89.162.224/30 | RIEPERT-CUST-30 | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “RIEPERT CUST” — 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.
- RIEPERT-CUST 2 blocks
- RIEPERT-CUST-32 2 blocks
- RIEPERT-CUST-DYN 2 blocks
- RIEPERT-CUST-29 2 blocks
- RIEPERT-CUST-FORSTENLECHNER-1 1 blocks
- RIEPERT-CUST-MEISL-1 1 blocks
- RIEPERT-CUST-PETSCHL-1 1 blocks
- RIEPERT-CUST-STADTAMT-PERG-1 1 blocks
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.
- Cust Altzinger 1 via Riepert Informationstechnologie GmbH sub-allocation
- Cust Petschl 1 via Riepert Informationstechnologie GmbH sub-allocation
- Cust Habau 1 via Riepert Informationstechnologie GmbH sub-allocation
- Cust Stadtamt Perg 1 via Riepert Informationstechnologie GmbH sub-allocation
- Cust Forstenlechner 1 via Riepert Informationstechnologie GmbH sub-allocation
- Cust Meisl 1 via Riepert Informationstechnologie GmbH sub-allocation
- Cust Bulmor 1 via Riepert Informationstechnologie GmbH sub-allocation
- Cust Ebner 1 via Riepert Informationstechnologie GmbH sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(10 of 10)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
RIEPERT-MNT