STADT-WETZLAR-NET

BGP inherited
Cluster stats
Netblocks7
Cluster ID210847321
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.7.151.112/29 STADT-WETZLAR-NET RIPE ASSIGNED PA ● low
5.7.151.120/29 STADT-WETZLAR-NET RIPE ASSIGNED PA ● low
5.7.151.136/29 STADT-WETZLAR-NET RIPE ASSIGNED PA ● low
5.7.151.144/29 STADT-WETZLAR-NET RIPE ASSIGNED PA ● low
62.55.192.128/29 STADT-WETZLAR-NET RIPE ASSIGNED PA ● low
87.191.48.136/29 STADT-WETZLAR-NET RIPE ASSIGNED PA ● low
2003:df:581c::/48 STADT-WETZLAR-NET RIPE ASSIGNED ● low

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 STADT-WETZLAR-NET 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.

2003:df:581c::/48 /48 authorized for AS3320 — Deutsche Telekom AG

NIC Handles

DTAG-NIC DUMY-RIPE DUMY-RIPE MDA-Z