TEK-SPb-LAN
BGP inherited
Cluster stats
| Netblocks | 3 |
| All fragments | 53 blocks across 32 clusters |
| Cluster ID | 204922634 |
| Registry | RIPE |
| Customers | find 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 | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 84.204.33.176/29 | TEK-SPb-LAN | RIPE | ASSIGNED PA | ● low |
| 84.204.33.184/29 | TEK-SPb-LAN | RIPE | ASSIGNED PA | ● low |
| 84.204.226.0/24 | TEK-SPb-LAN | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (1)
These blocks are registered to TEK-SPb-LAN 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.
| 84.204.226.0/24 /24 | authorized for AS20632 — PJSC MegaFon |
NIC Handles
DUMY-RIPE
DUMY-RIPE
MNT-MF-NWGSM
PSTAR-MNT