SAINT

BGP inherited
Cluster stats
Netblocks6
Registered in South Africa (4) · Germany (1) · United Kingdom (1)
All fragments 695 blocks across 145 clusters
Cluster ID210751737
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
195.66.225.235/32 SAINT PEERINGDB ASSIGNED ● high
196.10.141.38/32 SAINT PEERINGDB ASSIGNED ● high
196.60.9.41/32 SAINT PEERINGDB ASSIGNED ● high
196.60.96.132/32 SAINT PEERINGDB ASSIGNED ● high
196.223.30.132/32 SAINT PEERINGDB ASSIGNED ● high
176.95.155.184/29 SAINT-NET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “SAINT” — 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.
Combined view of all 145 name-family clusters →
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.

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

ARCOR-MNT AS328146 DUMY-RIPE DUMY-RIPE