| 91.0.0.0/8 | WHOIS (RIPE_NCC) | RIPE-NCC-MANAGED-ADDRESS-BLOCK | — |
| 91.108.0.0/18 | WHOIS (RIPE_NCC) | Global Network Management Inc | RU |
| 91.108.0.0/18 | RIPE_NCC assigned | — | AG |
| 91.108.24.0/21 | BGP route | AS42065 Global Network Management Inc | — |
| 91.108.0.0/22 | BGP route | AS42065 Global Network Management Inc | — |
| 91.108.0.0/22 | WHOIS (RIPE_NCC) | AO ElectronTelecom | RU |
| 91.108.4.0/22 | BGP route | AS62041 Telegram Messenger Inc | — |
| 91.108.4.0/22 | WHOIS (RIPE_NCC) | Telegram Messenger Network | NL |
| 91.108.8.0/22 | BGP route | AS62041 Telegram Messenger Inc | — |
| 91.108.8.0/22 | WHOIS (RIPE_NCC) | Telegram_Messenger_Network | NL |
| 91.108.12.0/22 | BGP route | AS59930 Telegram Messenger Inc | — |
| 91.108.12.0/22 | WHOIS (RIPE_NCC) | Telegram_Messenger_Network | US |
| 91.108.16.0/22 | BGP route | AS62014 Telegram Messenger Inc | — |
| 91.108.16.0/22 | WHOIS (RIPE_NCC) | Telegram_Messenger_Network | SG |
| 91.108.20.0/22 | BGP route | AS44907 Telegram Messenger Inc | — |
| 91.108.20.0/22 | WHOIS (RIPE_NCC) | Telegram_CDN_Network | AZ |
| 91.108.28.0/22 | WHOIS (RIPE_NCC) | AO ElectronTelecom | RU |
| 91.108.44.0/22 | BGP route | AS43106 Nevacom Ltd | — |
| 91.108.44.0/22 | WHOIS (RIPE_NCC) | Nevacom_Network | RU |
| 91.108.48.0/22 | WHOIS (RIPE_NCC) | RU-GlobalNet-Routing | RU |
| 91.108.56.0/22 | BGP route | AS62041 Telegram Messenger Inc | — |
| 91.108.56.0/22 | WHOIS (RIPE_NCC) | Telegram Messenger Network | NL |
| 91.108.60.0/22 | WHOIS (RIPE_NCC) | AT-Home | RU |
| 91.108.4.0/23 | BGP route | AS62041 Telegram Messenger Inc | — |
| 91.108.6.0/23 | BGP route | AS62041 Telegram Messenger Inc | — |
| 91.108.8.0/23 | BGP route | AS62041 Telegram Messenger Inc | — |
| 91.108.10.0/23 | BGP route | AS62041 Telegram Messenger Inc | — |
| 91.108.16.0/23 | BGP route | AS62014 Telegram Messenger Inc | — |
| 91.108.18.0/23 | BGP route | AS62014 Telegram Messenger Inc | — |
| 91.108.20.0/23 | BGP route | AS44907 Telegram Messenger Inc | — |
| 91.108.24.0/23 | WHOIS (RIPE_NCC) | AO ElectronTelecom | RU |
| 91.108.26.0/23 | WHOIS (RIPE_NCC) | AO ElectronTelecom | RU |
| 91.108.32.0/23 | BGP route | AS42065 Global Network Management Inc | — |
| 91.108.32.0/23 | WHOIS (RIPE_NCC) | AO ElectronTelecom | RU |
| 91.108.36.0/23 | WHOIS (RIPE_NCC) | Telegram_CDN | TR |
| 91.108.38.0/23 | WHOIS (RIPE_NCC) | Telegram_CDN | ID |
| 91.108.56.0/23 | BGP route | AS62014 Telegram Messenger Inc | — |
| 91.108.31.0/24 | BGP route | AS42065 Global Network Management Inc | — |
| 91.108.34.0/24 | BGP route | AS204941 LLC "Tsentralnaya Gorodskaya Set" | — |
| 91.108.34.0/24 | WHOIS (RIPE_NCC) | CGNET_NETWORK | RU |
| 91.108.35.0/24 | WHOIS (RIPE_NCC) | AS47133_temp_NAT | RU |
| 91.108.40.0/24 | BGP route | AS31500 Global Network Management Inc | — |
| 91.108.40.0/24 | WHOIS (RIPE_NCC) | Antigua_Users | AG |
| 91.108.41.0/24 | BGP route | AS57246 WellTelecom LLC | — |
| 91.108.41.0/24 | WHOIS (RIPE_NCC) | WellTelecom_Network | RU |
| 91.108.42.0/24 | WHOIS (RIPE_NCC) | CentrGorNet | RU |
| 91.108.43.0/24 | BGP route | AS24739 JSC "Severen-Telecom" | — |
| 91.108.43.0/24 | WHOIS (RIPE_NCC) | SEVEREN-TELECOM | RU |
| 91.108.50.0/24 | BGP route | AS31500 Global Network Management Inc | — |
| 91.108.52.0/24 | BGP route | AS42065 Global Network Management Inc | — |
| 91.108.52.0/24 | WHOIS (RIPE_NCC) | AO ElectronTelecom | RU |
| 91.108.53.0/24 | BGP route | AS204941 LLC "Tsentralnaya Gorodskaya Set" | — |
| 91.108.53.0/24 | WHOIS (RIPE_NCC) | CGNET_NETWORK | RU |
| 91.108.54.0/24 | BGP route | AS57512 OOO "Sportmaster" | — |
| 91.108.54.0/24 | WHOIS (RIPE_NCC) | OOO "Sportmaster" | RU |
| 91.108.56.0/24 | BGP route | AS62014 Telegram Messenger Inc | — |
| 91.108.57.0/24 | BGP route | AS62014 Telegram Messenger Inc | — |