Data as of Nov 13, 2026

82.209.218.136/30

1 residential-proxy exit · 30 days

Republican Unitary Telecommunication Enterprise Beltelecom

Announcement
RPKI valid
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
25% of its addresses · 30 days
Providers
36
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

7 observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • BestProxy
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • Infatica
  • LemonLabs
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
82.209.192.0/18
since May 2005
AS6697Residential432
26 always on
Republican Unitary Telecommunication Enterprise Beltelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
82.209.192.0/1816,384BY-BELPAK-20031001Republican Unitary Telecommunication Enterprise Beltelecom (ORG-RAB1-RIPE) · BYALLOCATED PAOct 1, 2003lir@belpak.by
└ 82.209.218.0/24256BYFLY-MGTSBELTELECOMLIR-PARTITIONED PAApr 5, 2013abuse@mgts.by
└ 82.209.218.136/304PIESEJ-MINSKTsentr Razrabotki Pi Es EjASSIGNED PAMar 21, 2017abuse@mgts.by
via BYFLY-MGTS

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

82.209.218.0/24

Routing history

Pattern
Stable
First seen
Jan 2014
Current origin since
Aug 2016 · 10 yr
Origin networks
1