IXDNS Sankt-Peterburg
Cluster stats
Netblocks12
All fragments 54 blocks across 8 clusters
Cluster ID193386853
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
194.226.100.38/32 IXDNS Sankt-Peterburg PEERINGDB ASSIGNED ● high
194.226.100.85/32 IXDNS Sankt-Peterburg PEERINGDB ASSIGNED ● high
194.226.100.112/32 IXDNS Sankt-Peterburg PEERINGDB ASSIGNED ● high
194.226.102.38/32 IXDNS Sankt-Peterburg PEERINGDB ASSIGNED ● high
194.226.102.85/32 IXDNS Sankt-Peterburg PEERINGDB ASSIGNED ● high
194.226.102.112/32 IXDNS Sankt-Peterburg PEERINGDB ASSIGNED ● high
2001:7f8:20:201::100:38/128 IXDNS Sankt-Peterburg PEERINGDB ASSIGNED ● high
2001:7f8:20:201::100:85/128 IXDNS Sankt-Peterburg PEERINGDB ASSIGNED ● high
2001:7f8:20:201::100:112/128 IXDNS Sankt-Peterburg PEERINGDB ASSIGNED ● high
2001:7f8:20:202::102:38/128 IXDNS Sankt-Peterburg PEERINGDB ASSIGNED ● high
2001:7f8:20:202::102:85/128 IXDNS Sankt-Peterburg PEERINGDB ASSIGNED ● high
2001:7f8:20:202::102:112/128 IXDNS Sankt-Peterburg PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS45029