Data as of Nov 14, 2026

80.254.0.0/20

98 residential-proxy exits · 30 days

TOV BF Express Ltd

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

Residential-proxy exits

Proxy exits
98
2.4% of its addresses · 30 days
Spread
11 of 16
/24s with at least one exit
Providers
81
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

5.3K observations
  • Residential
  • Business

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FROXY
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • HPROXY
  • HideProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateByte
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • Smartproxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • Webshare
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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
80.254.0.0/204,096UA-EXPRESS-20011217TOV BF Express Ltd (ORG-ERN1-RIPE) · UAALLOCATED PAJun 7, 2002abuse@express.net.ua
└ 80.254.0.0/24256EXPRESSEXPRESS Radio NetworkASSIGNED PAMay 28, 2002abuse@express.net.ua
via UA-EXPRESS-20011217
└ 80.254.1.0/24256EXPRESSEXPRESS Radio NetworkASSIGNED PAApr 18, 2005abuse@express.net.ua
via UA-EXPRESS-20011217
└ 80.254.2.0/24256EXPRESSEXPRESS Radio NetworkASSIGNED PAMay 28, 2002abuse@express.net.ua
via UA-EXPRESS-20011217
└ 80.254.3.0/24256EXPRESSEXPRESS Radio NetworkASSIGNED PANov 20, 2003abuse@express.net.ua
via UA-EXPRESS-20011217
└ 80.254.4.0/24256EXPRESSZaporizhzhiaASSIGNED PAMay 28, 2002abuse@express.net.ua
via UA-EXPRESS-20011217
└ 80.254.5.0/24256EXPRESSEXPRESS Radio NetworkASSIGNED PANov 20, 2003abuse@express.net.ua
via UA-EXPRESS-20011217
└ 80.254.6.0/24256EXPRESSEXPRESS Radio NetworkASSIGNED PAFeb 17, 2004abuse@express.net.ua
via UA-EXPRESS-20011217
└ 80.254.7.192/2664LINOZAunknownASSIGNED PAJul 26, 2016abuse@express.net.ua
via UA-EXPRESS-20011217
└ 80.254.8.0/24256EXPRESSEXPRESS Radio NetworkASSIGNED PANov 20, 2003abuse@express.net.ua
via UA-EXPRESS-20011217
└ 80.254.9.0/24256EXPRESSEXPRESS Radio NetworkASSIGNED PAFeb 17, 2004abuse@express.net.ua
via UA-EXPRESS-20011217
└ 80.254.10.0/24256EXPRESSEXPRESS KievASSIGNED PAJun 8, 2004abuse@express.net.ua
via UA-EXPRESS-20011217
└ 80.254.11.0/24256EXPRESSEXPRESS Radio NetworkASSIGNED PAFeb 17, 2004abuse@express.net.ua
via UA-EXPRESS-20011217
└ 80.254.12.0/24256EXPRESSEXPRESS Radio NetworkASSIGNED PAMay 27, 2011abuse@express.net.ua
via UA-EXPRESS-20011217
└ 80.254.13.0/24256EXPRESSEXPRESS Radio NetworkASSIGNED PAApr 18, 2005abuse@express.net.ua
via UA-EXPRESS-20011217
└ 80.254.14.0/24256EXPRESSEXPRESS Radio NetworkASSIGNED PAApr 18, 2005abuse@express.net.ua
via UA-EXPRESS-20011217
└ 80.254.15.0/24256EXPRESSExpress LtdASSIGNED PAApr 18, 2005abuse@express.net.ua
via UA-EXPRESS-20011217

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

4,096 addresses
TypeAddressesShareRanges
Residential4,03298%2
Business641.6%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1