Data as of Nov 14, 2026

176.12.0.0/18

654 residential-proxy exits · 30 days

A1 Bulgaria EAD

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
654
4.0% of its addresses · 30 days
Always-on exits
47
7.2% of its exits
Spread
64 of 64
/24s with at least one exit
Providers
132
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

120K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • APROXY
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CROXY
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYON
  • PROXYSALE
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PROXY_CC
  • PSBProxy
  • PrivateByte
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SpyderProxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TalorData
  • Thordata
  • ThunderProxy
  • TrueProxies
  • TrustProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

Arrived
PrefixOriginTypeProxy exitsHolderRPKI
176.12.0.0/22
since Jan 2021
AS29580Residential39
3 always on
A1 Bulgaria EAD
176.12.4.0/22
since Jul 2019
AS29580Residential23
1 always on
A1 Bulgaria EAD
176.12.8.0/24
since Jul 2019
AS29580Residential7
1 always on
A1 Bulgaria EAD
176.12.9.0/24
since Mar 2021
AS29580Residential10A1 Bulgaria EAD
176.12.10.0/24
since Apr 2019
AS29580Residential17A1 Bulgaria EAD
176.12.11.0/24
since Jan 2021
AS29580Residential14
1 always on
A1 Bulgaria EAD
176.12.12.0/24
since Aug 2021
AS29580Residential16A1 Bulgaria EAD
176.12.13.0/24
since May 2019
AS29580Residential11
2 always on
A1 Bulgaria EAD
176.12.14.0/24
since Jul 2019
AS29580Residential10
1 always on
A1 Bulgaria EAD
176.12.16.0/20
since Jul 2019
AS29580Residential200
17 always on
A1 Bulgaria EAD
176.12.32.0/23
since Jan 2020
AS29580Residential33
5 always on
A1 Bulgaria EAD
176.12.34.0/23
since Aug 2020
AS29580Residential34
5 always on
A1 Bulgaria EAD
176.12.36.0/22
since Jan 2021
AS29580Residential40
2 always on
A1 Bulgaria EAD
176.12.40.0/21
since Jan 2021
AS29580Residential75
5 always on
A1 Bulgaria EAD
176.12.48.0/21
since Jan 2021
AS29580Residential66
2 always on
A1 Bulgaria EAD
176.12.56.0/22
since Mar 2021
AS29580Residential37
1 always on
A1 Bulgaria EAD
176.12.60.0/22
since Mar 2021
AS29580Residential19
1 always on
A1 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
176.12.0.0/1816,384BG-MTELNET-20110518A1 Bulgaria EAD (ORG-MN1-RIPE) · BGALLOCATED PAMay 18, 2011RIPE.Abuse@a1.bg
└ 176.12.0.0/221,024GPON-BurgasGPON BurgasASSIGNED PAOct 29, 2015RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.4.0/221,024GPON-SofiaGPON SofiaASSIGNED PAOct 29, 2015RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.8.0/24256GPON_Services_SKK_9unknownASSIGNED PAMar 12, 2019RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.9.0/24256A1_Net_26032019unknownASSIGNED PAMar 26, 2019RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.10.0/24256GPON_OLT_Plovdiv_12unknownASSIGNED PAApr 8, 2019RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.11.0/24256GPON_OLT_Varna_14unknownASSIGNED PAApr 8, 2019RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.12.0/24256GPON_SFN_11GPON Sofia NDK 11ASSIGNED PAApr 9, 2019RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.13.0/24256GPON_SND_8unknownASSIGNED PAApr 12, 2019RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.14.0/24256GPON_Sofia_SFL_8GPON Sofia SFL 8ASSIGNED PAApr 12, 2019RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.15.0/24256A1_ITS_12042019unknownASSIGNED PAApr 12, 2019RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.16.0/212,048GPONBurgas-EastGPON ServicesASSIGNED PADec 13, 2011RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.24.0/212,048GPONBurgas-NorthGPON ServicesASSIGNED PADec 13, 2011RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.32.0/23512Sofia_GPONSofia GPONASSIGNED PAAug 19, 2015RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.34.0/23512A1-ClA1 ClientsASSIGNED PAAug 19, 2015RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.36.0/221,024GPON_BurgasGPON BurgasASSIGNED PAAug 19, 2015RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.40.0/212,048GPONPlovdiv-NET2GPON ServicesASSIGNED PADec 13, 2011RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.48.0/212,048GPONPlovdiv-NET3GPON ServicesASSIGNED PADec 13, 2011RIPE.Abuse@a1.bg
via BG-MTELNET-20110518
└ 176.12.56.0/212,048GPONPlovdiv-NET4GPON ServicesASSIGNED PADec 13, 2011RIPE.Abuse@a1.bg
via BG-MTELNET-20110518

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
Stable
First seen
Oct 2011
Current origin since
Oct 2011 · 15 yr
Origin networks
1