Data as of Nov 4, 2026
178.234.216.0/21
314 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
314
15% of its addresses · 30 days
Spread
8 of 8
/24s with at least one exit
Providers
63
selling exits here
Oct 5, 2026 – Nov 3, 2026
Exits seen per day
11K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 178.234.219.0/24 | 0 | 56 | |
| 178.234.216.0/24 | 0 | 41 | |
| 178.234.222.0/24 | 0 | 40 | |
| 178.234.223.0/24 | 0 | 38 | |
| 178.234.217.0/24 | 0 | 37 | |
| 178.234.221.0/24 | 0 | 36 | |
| 178.234.218.0/24 | 0 | 34 | |
| 178.234.220.0/24 | 0 | 32 |
Proxy providers listing exits
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlexyProxies
- FloppyData
- Geonode
- GhostConnect
- GloryCloud
- HideProxy
- IPFly
- IPPeak
- InfiniteProxies
- KindProxy
- Kookey
- LemonPrime
- LudaxProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyRack
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- ResiProxies
- RolaProxy
- Shifter
- Smartproxy
- StrikeProxy
- TalorData
- TrueProxies
- VantageProxies
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 178.234.128.0/17 since Jun 2010 | AS8570 | Residential | 6,568 | PJSC Rostelecom | |
| 178.234.0.0/16 since Jun 2010 | AS8570 | Residential | 13,474 31 always on | PJSC Rostelecom |
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 178.234.216.0/22 since Nov 2017 | AS12389 | Residential | 168 | PJSC Rostelecom | |
| 178.234.220.0/22 since Nov 2017 | AS12389 | Residential | 146 | PJSC Rostelecom |
Registrations in this block
The registry's network records over this block, widest first, each under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 178.234.0.0/16 | 65,536 | RU-RTK-20100510 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | May 10, 2010 | [email protected] |
| └ 178.234.216.0/21 | 2,048 | LES-BBN-6-NET | Broadband Connections Addresses Pool # 5 | ASSIGNED PA | Jun 7, 2010 | [email protected] via RU-RTK-20100510 |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Network & registry
Announced by
Covering announcement 178.234.192.0/18
- Prefix
- 178.234.192.0/18
- Announced by
- AS8570 PJSC Rostelecom
- Type
- Residential
- Proxy exits
- 2,468
- RPKI
- RPKI valid
- Netname
- RU-RTK-20100510
- Registrant
- PJSC Rostelecom
- RIR
- RIPE NCC
Origin network
AS8570
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Dec 4, 1997
- Domain
- lipetsk.ru
- Industry
- Computer and Information Technology
- Spamhaus ASN-DROP
- not listed
Routing timeline
Covering aggregate above, the prefix's own history below
178.234.192.0/18
Routing history
- Pattern
- Stable
- First seen
- Jun 2010
- Current origin since
- Jun 2010 · 16 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 178.234.0.0/16 | AS8570 | /18 | RIPE | RPKI valid |
IRR
Route objects on 178.234.192.0/18
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS8570 | RIPE | Address block for point-to-point Lipetsk Regional Public Network Route BBN-3/2/2 General | ROSTELECOM-MNT | Dec 23, 2024 |
Whois
Registration for this announcement
- Range
- 178.234.0.0/16
- Netname
- RU-RTK-20100510
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- May 10, 2010
- Updated
- May 22, 2026
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- May 10, 2010
- Status
- assigned
Report abuse
Abuse contact
- [email protected]
- Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE