Data as of Nov 7, 2026
213.178.48.0/20
157 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
157
3.8% of its addresses · 30 days
Always-on exits
2
1.3% of its exits
Spread
14 of 16
/24s with at least one exit
Providers
74
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
13K observations
- Residential
- Business
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 213.178.59.0/24 | 1 | 6 | |
| 213.178.54.0/24 | 1 | 2 | |
| 213.178.53.0/24 | 0 | 31 | |
| 213.178.52.0/24 | 0 | 25 | |
| 213.178.60.0/24 | 0 | 24 | |
| 213.178.61.0/24 | 0 | 24 | |
| 213.178.55.0/24 | 0 | 12 | |
| 213.178.49.0/24 | 0 | 11 | |
| 213.178.63.0/24 | 0 | 8 | |
| 213.178.56.0/24 | 0 | 6 | |
| 213.178.48.0/24 | 0 | 5 | |
| 213.178.57.0/24 | 0 | 1 | |
| 213.178.58.0/24 | 0 | 1 | |
| 213.178.62.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- B2Proxy
- BartProxies
- BirdProxies
- BlurPath
- BottingTools
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- Maskify
- NSocks
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PrivateByte
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyWing
- Proxyma
- PuraRoute
- RainProxy
- RapidProxy
- Shifter
- Thordata
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- ZENPROXY_LITE
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.178.32.0/19 | 8,192 | RU-RTK-20080117 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Nov 14, 2022 | abuse@ |
| └ 213.178.48.0/27 | 32 | AISTNET | AIST ISP, Cores | ASSIGNED PA | Nov 21, 2011 | abuse@ via RU-RTK-20080117 |
| └ 213.178.49.32/27 | 32 | AISTNET | AIST ISP, Clients | ASSIGNED PA | Nov 21, 2011 | abuse@ via RU-RTK-20080117 |
| └ 213.178.51.0/24 | 256 | AISTNET | AIST ISP, NAT (physical persons) | ASSIGNED PA | Jan 23, 2009 | abuse@ via RU-RTK-20080117 |
| └ 213.178.52.0/24 | 256 | AISTNET | AIST ISP, PPTP (physical persons) | ASSIGNED PA | Jan 20, 2010 | abuse@ via RU-RTK-20080117 |
| └ 213.178.53.0/24 | 256 | AISTNET | AIST ISP, PPTP (physical persons) | ASSIGNED PA | Jan 20, 2010 | abuse@ via RU-RTK-20080117 |
| └ 213.178.56.192/26 | 64 | AISTNET | AIST ISP, PPTP (physical persons) | ASSIGNED PA | Jan 20, 2010 | abuse@ via RU-RTK-20080117 |
| └ 213.178.57.176/28 | 16 | AIST-AVIAOTEL | AIST ISP, Client AviaOtel | ASSIGNED PA | Dec 9, 2011 | abuse@ via RU-RTK-20080117 |
| └ 213.178.57.208/28 | 16 | AISTNET | AIST ISP, Clients | ASSIGNED PA | Jan 20, 2010 | abuse@ via RU-RTK-20080117 |
| └ 213.178.58.32/27 | 32 | AISTNET | AIST ISP, Clients. Core 005, TA 008 | ASSIGNED PA | Jan 23, 2009 | abuse@ via RU-RTK-20080117 |
| └ 213.178.59.0/25 | 128 | AISTNET | AIST ISP, PPTP (physical persons) | ASSIGNED PA | Apr 11, 2012 | abuse@ via RU-RTK-20080117 |
| └ 213.178.59.192/26 | 64 | AISTNET | AIST ISP, Clients. Core 005, TA 008 | ASSIGNED PA | Jan 20, 2010 | abuse@ via RU-RTK-20080117 |
| └ 213.178.62.0/27 | 32 | AISTNET | AIST ISP, Core 5, Aggregation | ASSIGNED PA | Feb 9, 2011 | abuse@ via RU-RTK-20080117 |
| └ 213.178.62.32/27 | 32 | AISTNET | AIST ISP, Core 4, Aggregation | ASSIGNED PA | Jan 23, 2009 | abuse@ via RU-RTK-20080117 |
| └ 213.178.62.64/28 | 16 | AISTNET | AIST ISP, Core 1, Aggregation | ASSIGNED PA | Jan 23, 2009 | abuse@ via RU-RTK-20080117 |
| └ 213.178.62.128/26 | 64 | AISTNET | AIST ISP, Clients. Core 001, TA 020 | ASSIGNED PA | Jan 23, 2009 | abuse@ via RU-RTK-20080117 |
| └ 213.178.63.224/27 | 32 | AISTNET | AIST ISP, Clients | ASSIGNED PA | Jan 20, 2010 | abuse@ via RU-RTK-20080117 |
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
4,096 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 3,552 | 87% | 9 | |
| Business | 544 | 13% | 12 |
Network & registry
Origin network
AS8439
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Aug 25, 1997
- Domain
- rt.ru
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Sep 2010
- Current origin since
- Sep 2010 · 16 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 213.178.48.0/20 | AS8439 | /20 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS8439 | RIPE | AIST Networks | ROSTELECOM-MNT | Dec 18, 2024 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 213.178.48.0/21 | AS8439 | RIPE | AIST Networks | AIST-MNT | Jan 17, 2008 |
| 213.178.56.0/21 | AS8439 | RIPE | AIST Networks | AIST-MNT | Jan 17, 2008 |
Whois
Registration for this announcement
- Range
- 213.
178. 32. 0/ 19 - Netname
- RU-RTK-20080117
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Nov 14, 2022
- Updated
- Jun 4, 2024
- Maintainer
- ROSTELECOM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Jan 17, 2008
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE