Limited Liability Company TTK-Svyaz
TTK-PPPoE-IPv6-Izhevsk
Data as of 2026-09-13
BGP inherited
This organisation
| Netblocks | 4 |
| IPv6 | 4 prefixes (largest 2a03:3700:5600::/40) |
| Also registered under this name | 40 netblocks across 11 separate records |
| Record ID | 243522918 |
| Registry | RIPE |
| Customers | see who runs inside 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 · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a03:3700:5000::/48 | TTK-PPPoE-IPv6-Izhevsk | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a03:3700:5001::/48 | TTK-PPPoE-IPv6-Izhevsk | RIPE | ASSIGNED | ● low |
| 2a03:3700:5003::/48 | TTK-PPPoE-IPv6-Izhevsk | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a03:3700:5600::/40 | TTK-PPPoE-IPv6-Izhevsk | RIPE | AGGREGATED-BY-LIR | ● low |
IPv6 ranges (4)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
RPKI-inferred operator
Limited Liability Company "TTK-Svyaz"
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
VTT-MNT