Data as of Nov 14, 2026

84.253.103.0/24

3 residential-proxy exits · 30 days

Moscow Center of New Telecommunication Technologies JSC · space held by PJSC Rostelecom

Announcement
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
25
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

495 observations

Proxy providers listing exits

  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • Geonix
  • IPFly
  • Infatica
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
84.253.64.0/18
since Feb 2014
AS42610Residential23
1 always on
PJSC Rostelecom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
84.253.64.0/1816,384RU-RTK-20040916PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PASep 16, 2004abuse@rt.ru
└ 84.253.103.0/2732MCNTT103-1MCNTT Moscow Center of New Telecommunication TechnologiesASSIGNED PAJul 27, 2026abuse@rt.ru
via RU-RTK-20040916
└ 84.253.103.32/2732iqmen2-msk-netJSC "Aikumen IBS"ASSIGNED PAJul 28, 2026abuse@rt.ru
via RU-RTK-20040916
└ 84.253.103.64/2664iqmen3-msk-netJSC "Aikumen IBS"ASSIGNED PAJul 28, 2026abuse@rt.ru
via RU-RTK-20040916
└ 84.253.103.128/298iqmen-msk-netJSC "Aikumen IBS"ASSIGNED PAJul 27, 2026abuse@rt.ru
via RU-RTK-20040916
└ 84.253.103.136 - 84.253.103.22388MCNTT103-2MCNTT Moscow Center of New Telecommunication TechnologiesASSIGNED PAJul 27, 2026abuse@rt.ru
via RU-RTK-20040916
└ 84.253.103.224/2816LOKOS-1LOKOSASSIGNED PAJul 27, 2026abuse@rt.ru
via RU-RTK-20040916
└ 84.253.103.240/2816MCNTT103-3MCNTT Moscow Center of New Telecommunication TechnologiesASSIGNED PAJul 27, 2026abuse@rt.ru
via RU-RTK-20040916

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

Routing timeline

Covering aggregate above, the prefix's own history below

84.253.96.0/19

Routing history

Pattern
Stable
First seen
Aug 2018
Current origin since
Aug 2018 · 8.3 yr
Origin networks
1