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

46.10.160.0/23

17 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
this exact prefix
RPKI valid
Announced by
AS8866
Type
Residential
79% of it

Residential-proxy exits

Proxy exits
17
3.3% of its addresses · 30 days
Always-on exits
2
12% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
35
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

1.8K observations
  • Residential
  • Business

/24s with the most always-on exits

/24Always-on exitsProxy exits
46.10.161.0/24215
46.10.160.0/2402

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • IPFly
  • IPPeak
  • IPRoyal
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • Novada
  • PrivateProxy
  • Proxiware
  • Proxy302
  • Proxy4U
  • ProxyWing
  • RainProxy
  • RapidProxy
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
46.10.161.0/24
since Oct 2019
AS8866Residential15
2 always on
Vivacom 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
46.10.0.0/1665,536BG-BTC-20100913Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PASep 13, 2010abuse-ip@vivacom.bg
└ 46.10.160.0/298Burgas-Track-Service-BurgasunknownASSIGNED PAJan 30, 2018abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.8/298Promet_SafeunknownASSIGNED PAAug 31, 2017abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.16/298SmartSoftHealthcare-VarnaunknownASSIGNED PASep 29, 2022abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.24/298ObshtSevlievo-WIFI4EU-Dan-KolovunknownASSIGNED PASep 17, 2019abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.48/298Easypay_AsenovgradunknownASSIGNED PANov 29, 2019abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.72/298Employment-Agency-BregovounknownASSIGNED PAJan 19, 2022abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.80/304Municipal-Silistra_Pristanistna_2unknownASSIGNED PADec 22, 2021abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.88/304Equant-Maham-CharkovounknownASSIGNED PAFeb 13, 2019abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.120/298BG-Federadion-Basketball-Sf-3unknownASSIGNED PAAug 7, 2017abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.160/304Gebr_Heinemann_Bulgaria_OOD_Ruse_Kanla_DereunknownASSIGNED PAOct 3, 2022abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.164/304Photo_Synthesis-Sofia-1unknownASSIGNED PAOct 24, 2022abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.192/298Ottobock_Manufacturin_Bbulgaria_SofiaunknownASSIGNED PAOct 31, 2022abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.208/298Bolid-Sofia-Suhodolska175unknownASSIGNED PANov 30, 2021abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.216/298Bulgarian-Burger-SofiaunknownASSIGNED PAJul 14, 2017abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.224/304Equant_Jacobs_Douwe_Egberts_SofiaunknownASSIGNED PAJan 13, 2021abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.244/304VIK_Lovech_LukovitunknownASSIGNED PANov 12, 2021abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.160.248/298SIS_Industriis-SofiaunknownASSIGNED PADec 7, 2017abuse-ip@vivacom.bg
via BG-BTC-20100913
└ 46.10.161.0/24256VIVACOM-BroadbandunknownASSIGNED PAJan 4, 2022abuse-ip@vivacom.bg
via BG-BTC-20100913

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

512 addresses
TypeAddressesShareRanges
Residential40479%9
Business10821%16

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Apr 2016
Current origin since
Apr 2016 · 11 yr
Origin networks
1