Data as of Nov 8, 2026
213.171.32.0/19
70 residential-proxy exits · 30 daysJSC Comcor
Residential-proxy exits
Proxy exits
70
0.85% of its addresses · 30 days
Always-on exits
8
11% of its exits
Spread
24 of 32
/24s with at least one exit
Providers
64
selling exits here
Oct 9, 2026 – Nov 7, 2026
Exits seen per day
20K observations
- Residential
- Business
/24s with the most always-on exits
Proxy providers listing exits
- 2Captcha
- 711Proxy
- Ake.net
- B2Proxy
- BartProxies
- BirdProxies
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CliProxy
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GloryCloud
- GonzoProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- Infatica
- InfiniteProxies
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- NSocks
- NodeMaven
- NodeProxy
- NovaProxy
- Novada
- PROXYWING_BASIC
- PrivateProxy
- Proxies.fo
- Proxio
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyWing
- Proxyma
- PuraRoute
- RainProxy
- ResiProxies
- Shifter
- Smartproxy
- Thordata
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- ZENPROXY_PREMIUM
Announcements
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 213.171.41.0/24 since Jan 2024 | AS203093 | Business | 1 | JSC Comcor |
Registrations in this block
The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 213.171.32.0/19 | 8,192 | RU-COMCOR-20001219 | JSC Comcor (ORG-CA35-RIPE) · RU | ALLOCATED PA | Dec 14, 2001 | netadm@ |
| └ 213.171.32.4/30 | 4 | COMCOR-B2C-Clients | Network for COMCOR-B2C-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.8/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Apr 26, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.12/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Apr 18, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.16/30 | 4 | COMCOR-B2C-Clients | Network for COMCOR-B2C-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.20/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.24/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Feb 10, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.28/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.32/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 1, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.36/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.40/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 16, 2022 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.44/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Feb 20, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.48/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Jul 28, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.56/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.64/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 20, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.72/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Feb 10, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.76/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.80/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Oct 11, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.84/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.88/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.92/30 | 4 | COMCOR-B2C-Clients | Network for COMCOR-B2C-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.96/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 26, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.100/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | May 22, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.104/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.112/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 13, 2022 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.116/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Jan 31, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.120/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Oct 30, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.124/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 16, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.128/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.136/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Jan 26, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.144/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.152/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Aug 3, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.156/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 16, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.160/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.164/30 | 4 | COMCOR-B2C-Clients | Network for COMCOR-B2C-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.168/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.176/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.180/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 19, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.184/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.188/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 16, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.192/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.196/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.200/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 26, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.204/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Dec 26, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.208/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Jul 21, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.212/30 | 4 | COMCOR-B2C-Clients | Network for COMCOR-B2C-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.216/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.224/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Aug 24, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.228/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Aug 26, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.232/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.240/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Apr 23, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.244/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.248/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.32.252/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 20, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.33.0/24 | 256 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Oct 29, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.34.0/24 | 256 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.0/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.8/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Dec 11, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.16/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.24/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Jan 27, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.32/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 16, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.40/29 | 8 | COMCOR-B2C-Clients | Network for COMCOR-B2C-Clients | ASSIGNED PA | Nov 12, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.48/29 | 8 | COMCOR-B2C-Clients | Network for COMCOR-B2C-Clients | ASSIGNED PA | Nov 12, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.56/29 | 8 | COMCOR-B2C-Clients | Network for COMCOR-B2C-Clients | ASSIGNED PA | Nov 12, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.64/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.72/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 7, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.76/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 19, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.80/30 | 4 | COMCOR-B2C-Clients | Network for COMCOR-B2C-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.84/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 20, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.88/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.92/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.96/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Jan 9, 2025 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.100/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Dec 24, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.104/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Jan 18, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.120/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.128/28 | 16 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Aug 5, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.144/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Feb 22, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.148/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | May 26, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.152/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 17, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.156/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Jan 28, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.160/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Feb 3, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.164/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 25, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.168/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Aug 16, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.172/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 19, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.176/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Dec 17, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.180/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Oct 15, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.184/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Aug 19, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.188/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | May 23, 2022 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.192/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Feb 8, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.196/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 18, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.200/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Feb 22, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.204/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Aug 21, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.208/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Oct 11, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.216/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 18, 2022 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.220/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Aug 27, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.224/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 20, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.228/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Feb 20, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.232/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Aug 22, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.236/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Aug 24, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.240/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Dec 2, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.244/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Jul 23, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.248/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 23, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.35.252/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | May 14, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.8/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Feb 13, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.16/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Apr 21, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.20/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | May 17, 2022 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.24/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.32/30 | 4 | COMCOR-B2C-Clients | Network for COMCOR-B2C-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.36/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Apr 22, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.40/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | May 20, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.44/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | May 20, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.48/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.52/30 | 4 | COMCOR-B2C-Clients | Network for COMCOR-B2C-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.56/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.72/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.80/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.88/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.96/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 23, 2022 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.100/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Feb 10, 2022 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.104/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.112/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Oct 20, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.116/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Jun 29, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.120/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Jun 11, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.124/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 10, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.128/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Dec 5, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.140/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 7, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.144/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 1, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.148/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | May 20, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.152/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Dec 21, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.156/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Feb 13, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.160/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.168/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 15, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.176/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 20, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.192/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.200/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Jan 29, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.204/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Aug 18, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.208/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.216/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.224/28 | 16 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.240/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Jan 31, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.244/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 17, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.36.248/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.0/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.4/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.8/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | May 31, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.12/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 11, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.16/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 18, 2022 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.20/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Jul 21, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.24/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.32/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 15, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.36/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Oct 30, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.40/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Feb 9, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.48/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 3, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.56/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.64/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 30, 2022 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.68/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 25, 2022 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.72/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.80/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Apr 6, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.84/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Apr 6, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.92/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Apr 5, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.104/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.116/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 18, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.120/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.128/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 20, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.136/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 20, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.140/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 20, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.144/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 20, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.148/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 20, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.152/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 16, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.156/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Feb 20, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.160/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Apr 24, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.168/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Apr 10, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.176/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Aug 28, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.180/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Aug 21, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.192/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.208/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.216/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.220/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.224/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 22, 2022 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.228/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 19, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.232/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Aug 2, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.236/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Aug 2, 2023 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.240/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.248/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 8, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.37.252/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 4, 2020 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.0/28 | 16 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.16/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Oct 15, 2019 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.24/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.32/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.40/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.48/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.56/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.64/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.68/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 19, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.76/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 26, 2024 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.80/28 | 16 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.96/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Apr 22, 2021 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.104/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 27, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.112/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Sep 13, 2022 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.120/29 | 8 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Nov 9, 2018 | netadm@ via RU-COMCOR-20001219 |
| └ 213.171.38.128/30 | 4 | COMCOR-B2B-Clients | Network for COMCOR-B2B-Clients | ASSIGNED PA | Mar 11, 2024 | netadm@ via RU-COMCOR-20001219 |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Composition
The types across the prefix's announced space, by addresses.
Announced space
Address share
Announced space
Types across the prefix
8,192 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Business | 7,273 | 89% | 1,006 | |
| Residential | 919 | 11% | 111 |
Network & registry
Origin network
AS8732
RU
- Name
- JSC Comcor
- Type
- Internet provider
- Registered
- Mar 26, 1998
- Domain
- akado-telecom.ru
- Website
- www.akado-telecom.ru
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- May 2005
- Current origin since
- May 2005 · 22 yr
- Origin networks
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS8732 | RIPE | comcor.ru | AS8732-MNT | Sep 29, 2003 |
Whois
Registration for this announcement
- Range
- 213.
171. 32. 0/ 19 - Netname
- RU-COMCOR-20001219
- Registrant
- JSC Comcor
- Registrant country
- RU
- Organization
- JSC Comcor (ORG-CA35-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Dec 14, 2001
- Updated
- Nov 12, 2018
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Dec 19, 2000
- Status
- assigned
Report abuse
Abuse contact
- netadm@
comcor. ru - Name
- Abuse Contacts
- Handle
- AC23903-RIPE