| 2a00::/11 | WHOIS (RIPE_NCC) | RIPE Network Coordination Center | EU |
| 2a02:2698::/29 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" | RU |
| 2a02:2698::/29 | RIPE_NCC assigned | — | RU |
| 2a02:2698:b000::/36 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" | RU |
| 2a02:2698::/38 | BGP route | AS12768 JSC "ER-Telecom Holding" | — |
| 2a02:2698::/38 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" | RU |
| 2a02:2698:1c00::/38 | BGP route | AS34590 JSC "ER-Telecom Holding" | — |
| 2a02:2698:1c00::/38 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" Izhevsk branch | RU |
| 2a02:2698:2c00::/38 | BGP route | AS41727 JSC "ER-Telecom Holding" | — |
| 2a02:2698:3c00::/38 | BGP route | AS50498 JSC "ER-Telecom Holding" | — |
| 2a02:2698:4c00::/38 | BGP route | AS42682 JSC "ER-Telecom Holding" | — |
| 2a02:2698:4c00::/38 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" Nizhny Novgorod | RU |
| 2a02:2698:5c00::/38 | BGP route | AS41754 JSC "ER-Telecom Holding" | — |
| 2a02:2698:6c00::/38 | BGP route | AS51570 JSC "ER-Telecom Holding" | — |
| 2a02:2698:6c00::/38 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" Saint-Petersburg Branch | RU |
| 2a02:2698:7c00::/38 | BGP route | AS52207 JSC "ER-Telecom Holding" | — |
| 2a02:2698:8c00::/38 | BGP route | AS57026 JSC "ER-Telecom Holding" | — |
| 2a02:2698:9c00::/38 | BGP route | AS34150 JSC "ER-Telecom Holding" | — |
| 2a02:2698:400::/38 | BGP route | AS50512 JSC "ER-Telecom Holding" | — |
| 2a02:2698:400::/38 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" Barnaul Branch | RU |
| 2a02:2698:800::/38 | BGP route | AS57044 JSC "ER-Telecom Holding" | — |
| 2a02:2698:800::/38 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" Bryansk Branch | RU |
| 2a02:2698:1400::/38 | BGP route | AS50542 JSC "ER-Telecom Holding" | — |
| 2a02:2698:1400::/38 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" Voronezh Branch | RU |
| 2a02:2698:1800::/38 | BGP route | AS51604 JSC "ER-Telecom Holding" | — |
| 2a02:2698:1800::/38 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" Yekaterinburg Branch | RU |
| 2a02:2698:2000::/38 | BGP route | AS51645 JSC "ER-Telecom Holding" | — |
| 2a02:2698:2000::/38 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" Irkutsk Branch | RU |
| 2a02:2698:2400::/38 | BGP route | AS41786 JSC "ER-Telecom Holding" | — |
| 2a02:2698:2400::/38 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" Yoshkar-Ola Branch | RU |
| 2a02:2698:2800::/38 | BGP route | AS41668 JSC "ER-Telecom Holding" | — |
| 2a02:2698:3000::/38 | BGP route | AS50544 JSC "ER-Telecom Holding" | — |
| 2a02:2698:3400::/38 | BGP route | AS56330 JSC "ER-Telecom Holding" | — |
| 2a02:2698:3800::/38 | BGP route | AS59713 JSC "ER-Telecom Holding" | — |
| 2a02:2698:4000::/38 | BGP route | AS56377 JSC "ER-Telecom Holding" | — |
| 2a02:2698:4400::/38 | BGP route | AS42116 JSC "ER-Telecom Holding" | — |
| 2a02:2698:5000::/38 | BGP route | AS43478 JSC "ER-Telecom Holding" | — |
| 2a02:2698:5400::/38 | BGP route | AS41843 JSC "ER-Telecom Holding" | — |
| 2a02:2698:5800::/38 | BGP route | AS42683 JSC "ER-Telecom Holding" | — |
| 2a02:2698:6000::/38 | BGP route | AS57378 JSC "ER-Telecom Holding" | — |
| 2a02:2698:6400::/38 | BGP route | AS56420 JSC "ER-Telecom Holding" | — |
| 2a02:2698:6400::/38 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" Ryazan' Branch | RU |
| 2a02:2698:6800::/38 | BGP route | AS34533 JSC "ER-Telecom Holding" | — |
| 2a02:2698:7000::/38 | BGP route | AS50543 JSC "ER-Telecom Holding" | — |
| 2a02:2698:7400::/38 | BGP route | AS49048 JSC "ER-Telecom Holding" | — |
| 2a02:2698:8000::/38 | BGP route | AS41682 JSC "ER-Telecom Holding" | — |
| 2a02:2698:8400::/38 | BGP route | AS39028 JSC "ER-Telecom Holding" | — |
| 2a02:2698:8800::/38 | BGP route | AS51035 JSC "ER-Telecom Holding" | — |
| 2a02:2698:9000::/38 | BGP route | AS41661 JSC "ER-Telecom Holding" | — |
| 2a02:2698:9400::/38 | BGP route | AS51819 JSC "ER-Telecom Holding" | — |
| 2a02:2698:9800::/38 | BGP route | AS31363 JSC "ER-Telecom Holding" | — |
| 2a02:2698:9800::/38 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" | RU |
| 2a02:2698:c00::/38 | BGP route | AS39435 JSC "ER-Telecom Holding" | — |
| 2a02:2698:c00::/38 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" Volgograd Branch | RU |
| 2a02:2698:200::/39 | WHOIS (RIPE_NCC) | Corporate customers | RU |
| 2a02:2698:6600::/39 | WHOIS (RIPE_NCC) | Corporate customers | RU |
| 2a02:2698:100::/40 | WHOIS (RIPE_NCC) | Corporate customers | RU |
| 2a02:2698:6500::/40 | WHOIS (RIPE_NCC) | Corporate customers | RU |
| 2a02:2698:a100::/40 | BGP route | AS9049 JSC "ER-Telecom Holding" | — |
| 2a02:2698:a200::/40 | BGP route | AS9049 JSC "ER-Telecom Holding" | — |
| 2a02:2698:a004::/46 | BGP route | AS49874 JSC "ER-Telecom Holding" | — |
| 2a02:2698:2a::/47 | BGP route | AS12768 JSC "ER-Telecom Holding" | — |
| 2a02:2698:22::/47 | BGP route | AS12768 JSC "ER-Telecom Holding" | — |
| 2a02:2698:22::/47 | WHOIS (RIPE_NCC) | ERTH-PERM-PPPOE-1-NET | RU |
| 2a02:2698:24::/47 | BGP route | AS12768 JSC "ER-Telecom Holding" | — |
| 2a02:2698:24::/47 | WHOIS (RIPE_NCC) | ERTH-PERM-PPPOE-2-NET | RU |
| 2a02:2698:26::/47 | BGP route | AS12768 JSC "ER-Telecom Holding" | — |
| 2a02:2698:26::/47 | WHOIS (RIPE_NCC) | ERTH-PERM-PPPOE-3-NET | RU |
| 2a02:2698:202c::/47 | BGP route | AS51645 JSC "ER-Telecom Holding" | — |
| 2a02:2698:422::/47 | BGP route | AS50512 JSC "ER-Telecom Holding" | — |
| 2a02:2698:424::/47 | BGP route | AS50512 JSC "ER-Telecom Holding" | — |
| 2a02:2698:2022::/47 | BGP route | AS51645 JSC "ER-Telecom Holding" | — |
| 2a02:2698:2024::/47 | BGP route | AS51645 JSC "ER-Telecom Holding" | — |
| 2a02:2698:2422::/47 | BGP route | AS41786 JSC "ER-Telecom Holding" | — |
| 2a02:2698:6422::/47 | WHOIS (RIPE_NCC) | ERTH-RYAZAN-PPPOE-2-NET | RU |
| 2a02:2698:6424::/47 | WHOIS (RIPE_NCC) | ERTH-RYAZAN-PPPOE-3-NET | RU |
| 2a02:2698:7600::/48 | WHOIS (RIPE_NCC) | JSC StankoMachComplex | RU |
| 2a02:2698:a000:1000::/56 | WHOIS (RIPE_NCC) | JSC "ER-Telecom Holding" Nizhny Novgorod | RU |