LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

212.12.4.0/24

58 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
AS8675
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
58
23% of its addresses · 30 days
Providers
43
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2.3K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.12.0.0/19
since May 2005
AS8675Residential289
26 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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.12.0.0/198,192RU-RTK-980220PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJul 11, 2002abuse@rt.ru
└ 212.12.4.0/24256TULATEL-ACCSS3-NETDialup network for NAS-2ASSIGNED PADec 20, 2024abuse@rt.ru
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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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