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

85.30.0.0/18

18 residential-proxy exits · 30 days

Bredband2 AB

Announcement
this exact prefix
RPKI valid
Announced by
AS29518
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
18
0.11% of its addresses · 30 days
Always-on exits
2
11% of its exits
Spread
14 of 64
/24s with at least one exit
Providers
45
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

6.2K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
85.30.8.0/2411
85.30.54.0/2411
85.30.40.0/2403
85.30.24.0/2402
85.30.45.0/2402
85.30.26.0/2401
85.30.27.0/2401
85.30.28.0/2401
85.30.30.0/2401
85.30.34.0/2401
85.30.7.0/2401
85.30.44.0/2401
85.30.16.0/2401
85.30.55.0/2401

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • IPOasis
  • IPRoyal
  • Infatica
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • Q2IP
  • SPYDERPROXY_PREMIUM
  • Shifter
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_LITE

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
85.30.0.0/1816,384SE-BREDBAND2-20101019Bredband2 AB (ORG-LA21-RIPE) · SEALLOCATED PAFeb 18, 2022abuse@bredband2.se
└ 85.30.0.0/212,048BREDBAND2-NET-SEBredband2 CustomerASSIGNED PAJan 23, 2020abuse@bredband2.se
via SE-BREDBAND2-20101019
└ 85.30.8.0/212,048BREDBAND2-NET-SEBredband2 CustomerASSIGNED PAJan 23, 2020abuse@bredband2.se
via SE-BREDBAND2-20101019
└ 85.30.16.0/212,048BREDBAND2-NET-SEBredband2 CustomerASSIGNED PAJan 23, 2020abuse@bredband2.se
via SE-BREDBAND2-20101019
└ 85.30.24.0/212,048BREDBAND2-NET-SEBredband2 CustomerASSIGNED PAJan 23, 2020abuse@bredband2.se
via SE-BREDBAND2-20101019
└ 85.30.32.0/212,048BREDBAND2-NET-SEBredband2 CustomerASSIGNED PAJan 23, 2020abuse@bredband2.se
via SE-BREDBAND2-20101019
└ 85.30.40.0/212,048BREDBAND2-NET-SEBredband2 CustomerASSIGNED PAJan 23, 2020abuse@bredband2.se
via SE-BREDBAND2-20101019
└ 85.30.48.0/212,048BREDBAND2-NET-SEBredband2 CustomerASSIGNED PAJan 23, 2020abuse@bredband2.se
via SE-BREDBAND2-20101019
└ 85.30.56.0/212,048BREDBAND2-NET-SEBredband2 CustomerASSIGNED PAJan 23, 2020abuse@bredband2.se
via SE-BREDBAND2-20101019

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Jun 2005
Current origin since
Apr 2023 · 3.5 yr
Origin networks
4
Last change of origin
Apr 2023
Recorded history

History

Handoffs
3