THOMAS-PHILIPPS-BISSENDORF-NET
BGP inherited
Cluster stats
Netblocks6
All fragments 20 blocks across 5 clusters
Cluster ID192936015
RegistryRIPE
Customersfind 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

2 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-06

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.159.202.88/29 THOMAS-PHILIPPS-BISSENDORF-NET RIPE ASSIGNED PA ● low
80.156.29.160/28 THOMAS-PHILIPPS-BISSENDORF-NET RIPE ASSIGNED PA ● low
91.25.98.168/29 THOMAS-PHILIPPS-BISSENDORF-NET RIPE ASSIGNED PA ● low
91.26.202.24/29 THOMAS-PHILIPPS-BISSENDORF-NET RIPE ASSIGNED PA ● low
2003:64:c9::/48 THOMAS-PHILIPPS-BISSENDORF-NET RIPE ASSIGNED ● low
2003:c0:a83f::/48 THOMAS-PHILIPPS-BISSENDORF-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 (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

DTAG-NIC DUMY-RIPE DUMY-RIPE