Joint Stock Company TransTeleCom
VTT-PPPoE-Volgograd
BGP inherited
Cluster stats
| Netblocks | 3 |
| All fragments | 37 blocks across 8 clusters |
| Cluster ID | 204885772 |
| Registry | RIPE |
| Customers | find customers using 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 | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 213.80.132.0/24 | VTT-PPPoE-Volgograd | RIPE | ASSIGNED PA | ● low |
| 213.80.144.0/22 | VTT-PPPoE-Volgograd | RIPE | ASSIGNED PA | ● low |
| 213.80.148.0/22 | VTT-PPPoE-Volgograd | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “VTT PPPoE” — 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.
- VTT-PPPoE-Saratov 15 blocks
- VTT-PPPoE-IPv6-Saratov_Test 5 blocks
- VTT-PPPoE-Astrakhan 4 blocks
- VTT-PPPoE-IPv6-Saratov 3 blocks
- VTT-PPPoE-IPv6-Astrakhan 3 blocks
- VTT-PPPoE-IPv6-Volgograd 3 blocks
- VTT-PPPoE-IPv6-TEST 1 blocks
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.
- VYBORG-PPPOE-SYS via PJSC MegaFon sub-allocation
- 1811 Nikol Pervomaysk 2 Pppoe Sys via PJSC MegaFon sub-allocation
- D2801-KNG-GAKUNA-2-PPPOE-SYS via PJSC MegaFon sub-allocation
- D7206-PSK-OSTROV3-PPPOE-SYS via PJSC MegaFon sub-allocation
- 1841 Kovalevskaya Pppoe Sys via PJSC MegaFon sub-allocation
- PPPOE-NIKOL-OKTYABORG-9-SYS via PJSC MegaFon sub-allocation
- PPPOE-CITADELSKOE-43-SYS via PJSC MegaFon sub-allocation
- POL-PPPOE-USSK-UNLIM-3-NET via PJSC Rostelecom sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
RPKI-inferred operator
Joint Stock Company TransTeleCom
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