| 2a00::/11 | WHOIS (RIPE_NCC) | RIPE Network Coordination Center | EU |
| 2a10:24c0::/29 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0::/29 | WHOIS (RIPE_NCC) | FIBER TELECOM s.r.o. | CZ |
| 2a10:24c0::/29 | RIPE_NCC assigned | — | CZ |
| 2a10:24c0:d220::/44 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:fb0::/44 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:1e30::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:2c0::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:6d28::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:7b08::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:8a0::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:21d0::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:22e8::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:25f0::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:28::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:40f8::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:42d0::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:43c0::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:43f0::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:63c0::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:64a0::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:80b0::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:80f8::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:228::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:268::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:330::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:2008::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:2030::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:2068::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:2210::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:2240::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:2280::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:2488::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:2560::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:4060::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:4120::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:4150::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:4210::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:4318::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:4418::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:4440::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:6190::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:6208::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:6268::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:6510::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:6610::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:6870::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:7350::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:8088::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:8098::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:8100::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:b8::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0:e8::/45 | BGP route | AS50833 FIBER TELECOM s.r.o. | — |
| 2a10:24c0::/48 | WHOIS (RIPE_NCC) | FIBERTELECOM-VPS | CZ |
| 2a10:24c0:2a::/48 | WHOIS (RIPE_NCC) | ASTANA-103-GPON | KZ |
| 2a10:24c0:2b::/48 | WHOIS (RIPE_NCC) | Home office and residential DSL - Karagandy | KZ |
| 2a10:24c0:2c::/48 | WHOIS (RIPE_NCC) | Neighbourhood fibre rollout - Shymkent | KZ |
| 2a10:24c0:2c0::/48 | WHOIS (RIPE_NCC) | Residential FTTH customers - Mariehamn | AX |
| 2a10:24c0:2c1::/48 | WHOIS (RIPE_NCC) | Home office and residential DSL - Vaduz | LI |
| 2a10:24c0:2c2::/48 | WHOIS (RIPE_NCC) | MONACO-104-DSL | MC |
| 2a10:24c0:2c3::/48 | WHOIS (RIPE_NCC) | DSL customer pool - Monte-Carlo | MC |
| 2a10:24c0:2c4::/48 | WHOIS (RIPE_NCC) | LONGYEARBYEN-65-FTTH | SJ |
| 2a10:24c0:2c5::/48 | WHOIS (RIPE_NCC) | RES-SAN-MARINO-42 | SM |
| 2a10:24c0:2c6::/48 | WHOIS (RIPE_NCC) | Residential broadband allocation - Vatican City | VA |
| 2a10:24c0:2d::/48 | WHOIS (RIPE_NCC) | Residential FTTH customers - Taraz | KZ |
| 2a10:24c0:22a::/48 | WHOIS (RIPE_NCC) | GPON residential subscribers - Manaus | BR |
| 2a10:24c0:22b::/48 | WHOIS (RIPE_NCC) | BR-HOME-27 | BR |
| 2a10:24c0:22c::/48 | WHOIS (RIPE_NCC) | DSL customer pool - Salvador | BR |
| 2a10:24c0:22d::/48 | WHOIS (RIPE_NCC) | DSL customer pool - Sao Paulo | BR |
| 2a10:24c0:26a::/48 | WHOIS (RIPE_NCC) | Residential broadband allocation - Kharkiv | UA |
| 2a10:24c0:26b::/48 | WHOIS (RIPE_NCC) | KYIV-POOL-106 | UA |
| 2a10:24c0:26c::/48 | WHOIS (RIPE_NCC) | RES-LVIV-89 | UA |
| 2a10:24c0:26d::/48 | WHOIS (RIPE_NCC) | Home office and residential DSL - Odesa | UA |
| 2a10:24c0:28::/48 | WHOIS (RIPE_NCC) | KZ-HOME-183 | KZ |
| 2a10:24c0:29::/48 | WHOIS (RIPE_NCC) | RES-ALMATY-12 | KZ |
| 2a10:24c0:38c::/48 | WHOIS (RIPE_NCC) | Residential FTTH customers - Durres | AL |
| 2a10:24c0:38d::/48 | WHOIS (RIPE_NCC) | Residential FTTH customers - Tirana | AL |
| 2a10:24c0:38e::/48 | WHOIS (RIPE_NCC) | Home office and residential DSL - Vlore | AL |
| 2a10:24c0:228::/48 | WHOIS (RIPE_NCC) | GPON residential subscribers - Belo Horizonte | BR |
| 2a10:24c0:229::/48 | WHOIS (RIPE_NCC) | RES-FORTALEZA-195 | BR |
| 2a10:24c0:268::/48 | WHOIS (RIPE_NCC) | Residential FTTH customers - Dnipro | UA |
| 2a10:24c0:269::/48 | WHOIS (RIPE_NCC) | RES-DONETSK-90 | UA |
| 2a10:24c0:272::/48 | WHOIS (RIPE_NCC) | FIBTEL-NET | CZ |
| 2a10:24c0:330::/48 | WHOIS (RIPE_NCC) | PAGO-PAGO-63-FTTH | AS |
| 2a10:24c0:331::/48 | WHOIS (RIPE_NCC) | Home office and residential DSL - Avarua | CK |
| 2a10:24c0:332::/48 | WHOIS (RIPE_NCC) | ALOFI-POOL-39 | NU |
| 2a10:24c0:333::/48 | WHOIS (RIPE_NCC) | NUKU-ALOFA-117-FTTH | TO |
| 2a10:24c0:334::/48 | WHOIS (RIPE_NCC) | Residential FTTH customers - Mata-Utu | WF |
| 2a10:24c0:335::/48 | WHOIS (RIPE_NCC) | Neighbourhood fibre rollout - Apia | WS |
| 2a10:24c0:b8::/48 | WHOIS (RIPE_NCC) | BUDTA-91-FTTH | PH |
| 2a10:24c0:b9::/48 | WHOIS (RIPE_NCC) | CALOOCAN-31-DSL | PH |
| 2a10:24c0:ba::/48 | WHOIS (RIPE_NCC) | RES-DAVAO-56 | PH |
| 2a10:24c0:bb::/48 | WHOIS (RIPE_NCC) | MANILA-DSL-96 | PH |
| 2a10:24c0:bc::/48 | WHOIS (RIPE_NCC) | DSL customer pool - Quezon City | PH |
| 2a10:24c0:bd::/48 | WHOIS (RIPE_NCC) | GPON residential subscribers - Taguig | PH |
| 2a10:24c0:e8::/48 | WHOIS (RIPE_NCC) | RU-HOME-19 | RU |
| 2a10:24c0:e9::/48 | WHOIS (RIPE_NCC) | GPON residential subscribers - Moscow | RU |
| 2a10:24c0:ea::/48 | WHOIS (RIPE_NCC) | NIZHNIY-CABLE-123 | RU |
| 2a10:24c0:eb::/48 | WHOIS (RIPE_NCC) | Home office and residential DSL - Novosibirsk | RU |
| 2a10:24c0:ec::/48 | WHOIS (RIPE_NCC) | SAINT-POOL-176 | RU |
| 2a10:24c0:ed::/48 | WHOIS (RIPE_NCC) | RU-HOME-147 | RU |