Data as of Nov 19, 2026

213.166.184.0/23

1 residential-proxy exit · 30 days

Bofiber AS · reallocated from IP-Only Networks AS

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

Residential-proxy exits

Proxy exits
1
0.20% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
10
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

533 observations

Proxy providers listing exits

  • BlurPath
  • BottingTools
  • CliProxy
  • GloryCloud
  • IPFly
  • IPPeak
  • MoMoProxy
  • NovProxy
  • PuraRoute
  • RainProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
213.166.160.0/19
since Dec 2020
AS12552Unknown3IP-Only Networks AS

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
213.166.160.0/198,192NO-FASTHOST-20090924IP-Only Networks AS (ORG-FA9-RIPE) · NOALLOCATED PASep 24, 2009abuse@ip-only.net
└ 213.166.184.0/23512NO-BOFIBERBofiber ASSUB-ALLOCATED PAApr 15, 2010abuse@ip-only.net
via NO-FASTHOST-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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Aug 2013
Current origin since
Aug 2013 · 13 yr
Origin networks
1