Data as of Nov 6, 2026
212.12.4.0/24
48 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
48
19% of its addresses · 30 days
Providers
39
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
1.7K observations
Proxy providers listing exits
- 2Captcha
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CliProxy
- EnigmaProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- GonzoProxy
- IPFly
- IPOasis
- IPPeak
- Infatica
- LemonLabs
- LightningProxies
- MangoProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyHat
- ProxyWing
- Proxyma
- PuraRoute
- RainProxy
- Shifter
- Thordata
- ThunderProxy
- VantageProxies
- VitalData
- VitalExclusive
- VitalProxy
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 212.12.0.0/19 since May 2005 | AS8675 | Residential | 284 27 always on | 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.4.0/24 | 256 | TULATEL-ACCSS3-NET | Dialup network for NAS-2 | ASSIGNED PA | Dec 20, 2024 | 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
IPv4 market
Holder
- Organization
- PJSC Rostelecom
- Handle
- ORG-JR8-RIPE
- Range
- 212.
12. 0. 0/ 19 - Registration type
- ALLOCATED PA
- Record created
- Jul 11, 2002
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
Covering aggregate above, the prefix's own history below
Summary
Routing history
- Pattern
- Stable
- First seen
- Aug 2005
- Current origin since
- Nov 2016 · 10.0 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 212.12.4.0/24 | AS8675 | /24 | RIPE | RPKI valid |
| 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 dialup clients | ROSTELECOM-MNT | Dec 23, 2024 |
Whois
Registration for this announcement
- Range
- 212.
12. 4. 0/ 24 - Netname
- TULATEL-ACCSS3-NET
- Registrant
- Dialup network for NAS-2
- Registrant country
- RU
- Organization
- Dialup network for NAS-2
- Org country
- RU
- Type
- ASSIGNED PA
- Created
- Dec 20, 2024
- Updated
- Dec 20, 2024
- Maintainer
- ROSTELECOM-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