Data as of Nov 20, 2026

109.121.192.0/18

2 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Recent change
New origin Jul 2026
from AS43205 Vivacom Bulgaria EAD

Residential-proxy exits

Proxy exits
2
0.01% of its addresses · 30 days
Spread
2 of 64
/24s with at least one exit
Providers
8
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

27 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
109.121.224.0/2401
109.121.226.0/2401

Proxy providers listing exits

  • Decodo
  • GEEKPROXY_FLEX
  • GoProxies
  • Infatica
  • Oxylabs
  • PROXYLANE
  • Shifter
  • Thordata

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
109.121.192.0/24
since Nov 2009
AS21415ResidentialVivacom Bulgaria EAD
109.121.202.0/24
since Nov 2009
AS21415ResidentialVivacom Bulgaria EAD
109.121.203.0/24
since Nov 2009
AS21415ResidentialVivacom Bulgaria EAD
109.121.224.0/20
since Nov 14, 2026
AS8866Residential2Vivacom Bulgaria EAD
109.121.254.0/24
since Oct 2009
AS21415ResidentialVivacom Bulgaria EAD
109.121.255.0/24
since Oct 2009
AS21415ResidentialVivacom Bulgaria EAD

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
109.121.192.0/1816,384BG-BTC-20090924Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PASep 24, 2009abuse-ip@vivacom.bg
└ 109.121.192.0/24256INETG-STZ-BGInterNet Group LtdASSIGNED PAJul 18, 2016abuse-ip@vivacom.bg
via BG-BTC-20090924
└ 109.121.193.0/24256BULSATCOMBulsatcom EADASSIGNED PADec 11, 2017abuse-ip@vivacom.bg
via BG-BTC-20090924
└ 109.121.196.0/24256BULSATCOMBulsatcom EADASSIGNED PAFeb 24, 2016abuse-ip@vivacom.bg
via BG-BTC-20090924
└ 109.121.198.0/23512BULSATCOM-CUSTOMERSBulsatcom EOODASSIGNED PAFeb 24, 2016abuse-ip@vivacom.bg
via BG-BTC-20090924
└ 109.121.200.0/24256BULSATCOM-CUSTOMERSBulsatcom EADASSIGNED PAJul 25, 2017abuse-ip@vivacom.bg
via BG-BTC-20090924
└ 109.121.201.0/24256BULSATCOMBulsatcom EADASSIGNED PANov 14, 2017abuse-ip@vivacom.bg
via BG-BTC-20090924
└ 109.121.204.0/24256BULSATCOM-CUSTOMERSBulsatcom EADASSIGNED PAMay 4, 2020abuse-ip@vivacom.bg
via BG-BTC-20090924
└ 109.121.205.0/24256BULSATCOM-CUSTOMERSBulsatcom EADASSIGNED PAMar 28, 2017abuse-ip@vivacom.bg
via BG-BTC-20090924
└ 109.121.206.0/23512BULSATCOM-CUSTOMERSBulsatcom EADASSIGNED PAMar 28, 2017abuse-ip@vivacom.bg
via BG-BTC-20090924
└ 109.121.208.0/212,048BULSATCOMBulsatcom EADASSIGNED PAAug 22, 2016abuse-ip@vivacom.bg
via BG-BTC-20090924
└ 109.121.216.0/212,048BULSATCOMBulsatcom EADASSIGNED PAJul 27, 2016abuse-ip@vivacom.bg
via BG-BTC-20090924
└ 109.121.240.0/212,048BULSATCOMBulsatcom EADASSIGNED PAJul 20, 2016abuse-ip@vivacom.bg
via BG-BTC-20090924
└ 109.121.248.0/221,024BULSATCOMBulsatcom EADASSIGNED PADec 28, 2016abuse-ip@vivacom.bg
via BG-BTC-20090924
└ 109.121.252.0/23512BULSATCOM-CUSTOMERSBulsatcom EOODASSIGNED PAApr 3, 2019abuse-ip@vivacom.bg
via BG-BTC-20090924
└ 109.121.254.0/23512INETG-STZ-BGInterNet Group LtdASSIGNED PAAug 2, 2016abuse-ip@vivacom.bg
via BG-BTC-20090924

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 this prefix

Summary

Routing history

Pattern
Rotating
First seen
Oct 2009
Current origin since
Jul 2026 · 5 mo
Origin networks
3
Last change of origin
Jul 2026
Recorded history

History

Handoffs
2