Data as of Nov 6, 2026
212.12.0.0/19
284 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
284
3.5% of its addresses · 30 days
Always-on exits
27
9.5% of its exits
Spread
22 of 32
/24s with at least one exit
Providers
91
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
62K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 212.12.31.0/24 | 3 | 21 | |
| 212.12.28.0/24 | 3 | 19 | |
| 212.12.19.0/24 | 3 | 19 | |
| 212.12.27.0/24 | 3 | 14 | |
| 212.12.18.0/24 | 2 | 20 | |
| 212.12.15.0/24 | 2 | 19 | |
| 212.12.24.0/24 | 2 | 17 | |
| 212.12.29.0/24 | 2 | 17 | |
| 212.12.20.0/24 | 2 | 15 | |
| 212.12.25.0/24 | 2 | 11 | |
| 212.12.17.0/24 | 1 | 12 | |
| 212.12.14.0/24 | 1 | 8 | |
| 212.12.1.0/24 | 1 | 5 | |
| 212.12.4.0/24 | 0 | 48 | |
| 212.12.30.0/24 | 0 | 12 | |
| 212.12.21.0/24 | 0 | 9 | |
| 212.12.8.0/24 | 0 | 9 | |
| 212.12.7.0/24 | 0 | 3 | |
| 212.12.6.0/24 | 0 | 3 | |
| 212.12.23.0/24 | 0 | 1 | |
| 212.12.9.0/24 | 0 | 1 | |
| 212.12.13.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GloryCloud
- GoProxies
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- MoMoProxy
- NSocks
- NextProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PrivateByte
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxy-Cheap
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxyma
- PuraRoute
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
Announcements
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 212.12.4.0/24 since Nov 2016 | AS8675 | Residential | 48 | PJSC Rostelecom | |
| 212.12.21.0/24 since Sep 2016 | AS8675 | Residential | 9 | PJSC Rostelecom |
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 |
|---|---|---|---|---|---|---|
| 212.12.0.0/19 | 8,192 | RU-RTK-980220 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Jul 11, 2002 | abuse@ |
| └ 212.12.1.0/24 | 256 | TULATEL-ACCSS1-NET | OJSC TULATELECOM Access Network 1 | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.2.0/24 | 256 | TULATEL-CLIENT-2-NET | Broadband clients leased adresses | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.3.0/24 | 256 | TULATEL-CLIENT-3-NET | Broadband clients leased adresses | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.4.0/24 | 256 | TULATEL-ACCSS3-NET | Dialup network for NAS-2 | ASSIGNED PA | Dec 20, 2024 | abuse@ via RU-RTK-980220 |
| └ 212.12.6.0/24 | 256 | TULATEL-LEASEDLINKS-NET | Client leased link network | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.7.0/24 | 256 | TULATEL-CLIENT-7-NET | Broadband clients leased adresses | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.8.0/24 | 256 | TULATEL-CLIENT-8-NET | Broadband clients leased adresses | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.9.0/24 | 256 | TULATEL-IOLA-NET | Client leased link network (IOLA) | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.10.0/24 | 256 | TULATEL-IOLA-NET | Client leased link network (IOLA) | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.12.0/24 | 256 | TULATEL-IOLA-NET | Client leased link network (IOLA) | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.13.0/24 | 256 | TULATEL-IOLA-NET | Client leased link network (IOLA) | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.14.0/24 | 256 | TULATEL-IOLA-NET | Client leased link network (IOLA) | ASSIGNED PA | Dec 20, 2024 | abuse@ via RU-RTK-980220 |
| └ 212.12.15.0/24 | 256 | TULATEL-IOLA-NET | Client leased link network (IOLA) | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.16.0/24 | 256 | TULATEL-IOLA-NET | Client leased link network (IOLA) | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.17.0/24 | 256 | TULATEL-IOLA-NET | Client leased link network (IOLA) | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.18.0/24 | 256 | TULATEL-IOLA-NET | Client leased link network (IOLA) | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.19.0/24 | 256 | TULATEL-MCC-NET | Client leased link network (MCC) | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.20.0/24 | 256 | TULATEL-ACCSS22-NET | OJSC TULATELECOM Access Network (dialup 2nd pool) | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.21.0/24 | 256 | TULATEL-ACCSS21-NET | OJSC TULATELECOM Access Network (STK 2nd pool) | ASSIGNED PA | Dec 20, 2024 | abuse@ via RU-RTK-980220 |
| └ 212.12.23.0/24 | 256 | TULATEL-CLIENT-NET | Client leased link network | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.24.0/24 | 256 | TULATEL-MCC-NET | Client leased link network (MCC) | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.25.0/24 | 256 | TULATEL-MCC-NET | Client leased link network (MCC) | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.26.0/24 | 256 | TULATEL-MCC-NET | Client leased link network (MCC) | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.27.0/24 | 256 | TULATEL-MCC-NET | Client leased link network (MCC) | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.28.0/24 | 256 | TULATEL-ACCSS28-NET | OJSC TULATELECOM NAT network for MCC | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.29.0/24 | 256 | TULATEL-ACCSS29-NET | OJSC TULATELECOM NAT network for MCC | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.30.0/24 | 256 | TULATEL-ACCSS30-NET | OJSC TULATELECOM NAT network for MCC | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
| └ 212.12.31.0/24 | 256 | TULATEL-MCC-NET | OJSC TULATELECOM Client leased link network (MCC) | ASSIGNED PA | Mar 3, 2026 | abuse@ via RU-RTK-980220 |
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
Origin network
AS8675
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Feb 18, 1998
- Domain
- rostelecom.ru
- Industry
- Computer and Information Technology
- 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 · 21 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 212.12.0.0/19 | AS8675 | /24 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS8675 | RIPE | Specific route for AS 8675 | ROSTELECOM-MNT | Dec 23, 2024 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 212.12.0.0/24 | AS8675 | RIPE | Specific route for Tulatelecom corporate networks | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.1.0/24 | AS8675 | RIPE | Specific route for dialup clients | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.2.0/24 | AS8675 | RIPE | Specific route for client`s leased links | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.3.0/24 | AS8675 | RIPE | Specific route for client`s leased links | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.5.0/24 | AS8675 | RIPE | Specific route for load balansing | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.6.0/24 | AS8675 | RIPE | Specific route for client`s leased links | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.7.0/24 | AS8675 | RIPE | Specific route for Tulanews Ltd | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.8.0/24 | AS8675 | RIPE | Specific route for load balansing | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.9.0/24 | AS8675 | RIPE | Address space for IOLA users | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.10.0/24 | AS8675 | RIPE | Address space for IOLA users | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.11.0/24 | AS8675 | RIPE | Address space for IOLA users | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.12.0/24 | AS8675 | RIPE | Specific route for IOLA users | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.13.0/24 | AS8675 | RIPE | Address space for IOLA users | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.14.0/24 | AS8675 | RIPE | Specific route for IOLA users | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.15.0/24 | AS8675 | RIPE | Specific route for IOLA users | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.16.0/24 | AS8675 | RIPE | Specific route for IOLA users | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.17.0/24 | AS8675 | RIPE | Specific route for IOLA users | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.18.0/24 | AS8675 | RIPE | Specific route for IOLA users | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.19.0/24 | AS8675 | RIPE | Specific route for load balansing | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.20.0/24 | AS8675 | RIPE | Specific route for ADSL users | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.22.0/24 | AS8675 | RIPE | Specific route for load balansing | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.23.0/24 | AS8675 | RIPE | Specific route for load balansing | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.24.0/24 | AS8675 | RIPE | Specific route for load balansing | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.25.0/24 | AS8675 | RIPE | Specific route for load balansing | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.26.0/24 | AS8675 | RIPE | Specific route for load balansing | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.27.0/24 | AS8675 | RIPE | Specific route for load balansing | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.28.0/24 | AS8675 | RIPE | Specific route for load balansing | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.29.0/24 | AS8675 | RIPE | Specific route for load balansing | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.30.0/24 | AS8675 | RIPE | Specific route for load balansing | ROSTELECOM-MNT | Aug 21, 2026 |
| 212.12.31.0/24 | AS8675 | RIPE | Specific route for load balansing | ROSTELECOM-MNT | Aug 21, 2026 |
Whois
Registration for this announcement
- Range
- 212.
12. 0. 0/ 19 - Netname
- RU-RTK-980220
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Jul 11, 2002
- Updated
- Jun 23, 2026
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Feb 20, 1998
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE