Data as of Nov 4, 2026
5.228.83.0/24
243 residential-proxy exits · 30 daysPJSC Rostelecom
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby
Residential-proxy exits
Proxy exits
243
95% of its addresses · 30 days
Always-on exits
23
9.5% of its exits
Providers
92
selling exits here
Oct 5, 2026 – Nov 3, 2026
Exits seen per day
31K observations
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GeekProxy
- Geonode
- GhostConnect
- GloryCloud
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonBright
- LemonPrime
- LudaxProxy
- MangoProxy
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PSBProxy
- PrivateByte
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 5.228.0.0/16 since Sep 2012 | AS42610 | Residential | 4,396 401 always on | 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 |
|---|---|---|---|---|---|---|
| 5.228.0.0/16 | 65,536 | RU-RTK-20120907 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Sep 7, 2012 | abuse@ |
| └ 5.228.0.0/17 | 32,768 | NCN-BBCUST | unknown | SUB-ALLOCATED PA | Mar 4, 2025 | abuse@ via RU-RTK-20120907 |
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 5.228.82.0/23
- Prefix
- 5.228.82.0/23
- Announced by
- AS42610 PJSC Rostelecom
- Type
- Residential
- Proxy exits
- 494
- Always-on exits
- 49
- RPKI
- RPKI valid
- Netname
- NCN-BBCUST
- RIR
- RIPE NCC
IPv4 market
Holder
- Organization
- PJSC Rostelecom
- Handle
- ORG-JR8-RIPE
- Range
- 5.
228. 0. 0/ 16 - Registration type
- ALLOCATED PA
- Record created
- Sep 7, 2012
- Reallocated to
- Not named in the registry
- Reallocated range
- 5.
228. 0. 0/ 17 - Reallocation type
- SUB-ALLOCATED PA
- Reallocated
- Mar 4, 2025
Origin network
AS42610
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Mar 22, 2007
- Domain
- rt.ru
- Website
- moscow.rt.ru
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Covering aggregate above, the prefix's own history below
5.228.82.0/23
Routing history
- Pattern
- Stable
- First seen
- Dec 2023
- Current origin since
- Dec 2023 · 2.9 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 5.228.82.0/23 | AS42610 | /23 | RIPE | RPKI valid |
| 5.228.0.0/16 | AS42610 | /16 | RIPE | Too specific |
IRR
Route objects on 5.228.82.0/23
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS42610 | RIPE | ROSTELECOM-MNT | Mar 6, 2025 |
Whois
Registration for this announcement
- Range
- 5.
228. 0. 0/ 17 - Netname
- NCN-BBCUST
- Registrant country
- RU
- Organization
- Not stated by the registry
- Type
- SUB-ALLOCATED PA
- Created
- Mar 4, 2025
- Updated
- Mar 4, 2025
- Maintainer
- ROSTELECOM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Sep 7, 2012
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE