Data as of Nov 5, 2026
46.61.138.0/24
3 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
32
selling exits here
Oct 6, 2026 – Nov 4, 2026
Exits seen per day
1.2K observations
- Residential
- Business
Proxy providers listing exits
- 711Proxy
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- DataImpulse
- Decodo
- Evomi
- FlashProxy
- GSocks
- Geonix
- GonzoProxy
- IPFly
- IPRoyal
- Infatica
- Kookey
- LemonLabs
- LemonPrime
- MangoProxy
- NodeProxy
- NovaProxy
- Oxylabs
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyRack
- PuraRoute
- RainProxy
- Shifter
- StrikeProxy
- ThunderProxy
- VitalExclusive
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 46.61.0.0/16 since Sep 2018 | AS12389 | Residential | 13,397 121 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 |
|---|---|---|---|---|---|---|
| 46.61.0.0/16 | 65,536 | RU-RTK-20101022 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Nov 30, 2011 | abuse@ |
| └ 46.61.138.0/30 | 4 | Daichi_ | Ticket 09-24788 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.4/30 | 4 | ONeryungrinskiy_ | Ticket 10-36002 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.8/29 | 8 | Tandem | Ticket 10-36704 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.16/28 | 16 | DDG-2 | Ticket 10-19309 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.32/28 | 16 | Informatsionnyy_ | Ticket 10-35421 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.48/29 | 8 | Amurskiy_ | Ticket 10-23611 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.56/30 | 4 | Sokolov | Ticket 10-35602 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.60/30 | 4 | Yakutskiy_ | Ticket 10-07713 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.64/28 | 16 | DDG-2 | Ticket 10-20442 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.80/28 | 16 | Rynok_ | Ticket 10-28235 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.96/29 | 8 | Chudesnaya_ | Ticket 10-36543 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.104/29 | 8 | RodStor_ | Ticket 10-36114 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.112/28 | 16 | Royal_ | Ticket 10-38567 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.128/28 | 16 | Gorodok_ | Ticket 10-35195 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.144/29 | 8 | Novaya_ | Ticket 10-13367 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.152/29 | 8 | DDG-2 | Ticket 10-39584 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.160/28 | 16 | Regionalnye_ | Ticket 10-39110 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.176/29 | 8 | UFNS_ | Ticket 10-37782 | ASSIGNED PA | Jan 18, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.184/30 | 4 | Progress-88 | Ticket 10-39021 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.188/30 | 4 | Kontrolnoe_ | Ticket 10-29031 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.192/28 | 16 | Pravitelstvo_ | Ticket 10-24901 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46. | 12 | Vostok-Media | Ticket 10-39096 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.224/28 | 16 | Russkaya_ | Ticket 10-39631 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
| └ 46.61.138.240/28 | 16 | Upravlenie_ | Ticket 11-00653 | ASSIGNED PA | Jan 19, 2011 | abuse@ via RU-RTK-20101022 |
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
256 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Business | 252 | 98% | 24 | |
| Residential | 4 | 1.6% | 1 |
Network & registry
Announced by
Covering announcement 46.61.128.0/17
- Prefix
- 46.61.128.0/17
- Announced by
- AS12389 PJSC Rostelecom
- Type
- Residential
- Proxy exits
- 662
- Always-on exits
- 121
- RPKI
- RPKI valid
- Netname
- RU-RTK-20101022
- Registrant
- PJSC Rostelecom
- RIR
- RIPE NCC
Origin network
AS12389
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Jul 1, 2005
- Domain
- rt.ru
- Website
- www.company.rt.ru/en/
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Covering aggregate above, the prefix's own history below
46.61.128.0/17
Routing history
- Pattern
- Stable
- First seen
- Dec 2010
- Current origin since
- Dec 2010 · 16 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 46.61.128.0/17 | AS12389 | /24 | RIPE | RPKI valid |
| 46.61.0.0/16 | AS12389 | /24 | RIPE | RPKI valid |
IRR
Route objects on 46.61.128.0/17
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12389 | RIPE | ROSTELECOM NETS | ROSTELECOM-MNT | Oct 27, 2010 |
Whois
Registration for this announcement
- Range
- 46.
61. 0. 0/ 16 - Netname
- RU-RTK-20101022
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Nov 30, 2011
- Updated
- Jun 5, 2024
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Oct 27, 2010
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE