Saint-Petersburg Computer Networks
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 10 · 3,079 IPv4 addresses |
| IPv6 | 1 prefix (largest 2a00:6f60::/32) |
| All fragments | 38 blocks across 3 clusters |
| Cluster ID | 214410569 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
6 weekly snapshots · JSON
13
0 netblocks since 2026-07-05
2026-07-05
peak 13
2026-07-26
IP Ranges (10)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 31.44.186.146/32 | Saint-Petersburg Computer Networks | PEERINGDB | ASSIGNED | ● high |
| 37.9.49.179/32 | Saint-Petersburg Computer Networks | PEERINGDB | ASSIGNED | ● high |
| 93.92.200.0/21 | Saint-Petersburg Computer Networks Ltd. | BGP | ANNOUNCED | ● high |
| 185.0.13.114/32 | Saint-Petersburg Computer Networks | PEERINGDB | ASSIGNED | ● high |
| 185.1.152.29/32 | Saint-Petersburg Computer Networks | PEERINGDB | ASSIGNED | ● high |
| 185.1.153.249/32 | Saint-Petersburg Computer Networks | PEERINGDB | ASSIGNED | ● high |
| 185.24.52.0/22 | Saint-Petersburg Computer Networks Ltd. | BGP | ANNOUNCED | ● high |
| 193.27.38.41/32 | Saint-Petersburg Computer Networks | PEERINGDB | ASSIGNED | ● high |
| 193.27.39.155/32 | Saint-Petersburg Computer Networks | PEERINGDB | ASSIGNED | ● high |
| 2a00:6f60::/32 | Saint-Petersburg Computer Networks Ltd. | BGP | ANNOUNCED | ● high |
IPv6 ranges (1)
| CIDR |
|---|
| 2a00:6f60::/32 |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
46.2%
of checked blocks have valid RPKI ROA coverage
(6 of 13)
No discrepancies found among checked blocks.
NIC Handles
AS44923
AS44923
DUMY-RIPE
DUMY-RIPE
MNT-SPBKS
MNT-SPBKS
ORG-SCNL3-RIPE
RIPE-NCC-HM-MNT