Data as of Nov 10, 2026

188.2.78.0/24

19 residential-proxy exits · 30 days

Yettel d.o.o.

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

Residential-proxy exits

Proxy exits
19
7.4% of its addresses · 30 days
Always-on exits
2
11% of its exits
Providers
47
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

1.6K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • Kookey
  • LemonBright
  • LemonLabs
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
188.2.0.0/1665,536RS-SBB-NET-20090212Yettel d.o.o. (ORG-SKMS1-RIPE) · RSALLOCATED PAFeb 12, 2009abuse@yettel.rs
└ 188.2.0.0/1732,768SBBNETSerbia BroadBandASSIGNED PAOct 22, 2009abuse@yettel.rs
via RS-SBB-NET-20090212

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

Who has announced 188.2.0.0/16

188.2.0.0/16

Routing history

Pattern
Stable
First seen
Feb 2009
Current origin since
Feb 2009 · 18 yr
Origin networks
1