Data as of Nov 13, 2026

158.58.168.0/21

14 anonymizer addresses · 0.68% · VPN11 residential-proxy exits · 30 days

Seflow s.r.l.

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
>99% of it

Residential-proxy exits

Proxy exits
11
0.54% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
26
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

63 observations

Proxy providers listing exits

  • 711Proxy
  • ASHBURNPROXIES
  • B2Proxy
  • Byteful
  • EnigmaProxy
  • FastProxy
  • GSocks
  • IPFly
  • IPPeak
  • Infatica
  • LightningProxies
  • LudaxProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • VantageProxies
  • YumiProxy
  • ZENPROXY_LITE
IPv4 market

Path

1 · Holder
record created Nov 10, 2011
2 · Leased from
not leased
3 · Announced by
AS49367 Seflow s.r.l.
since Dec 2023 · 3.0 yr ago
4 · Use
VPN servicesnamed TunnelBear
Hosting

Operators, sellers and brokers

VPN services

NameParentIn 158.58.168.0/21/24s
TunnelBearMcAfee
140.68%
1

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

158.58.168.0/21

From the registry to its use

  1. Nov 10, 2011
    Registry record
    Seflow s.r.l.
    ALLOCATED PA
    158.58.168.0/21
  2. Nov 10, 2011
    Route object
    AS49367 Seflow s.r.l.
    RIPE route object for AS49367 Seflow s.r.l., maintainer MNT-SEFLOW
  3. Nov 15, 2011– Aug 16, 2018
    Announced
    AS49367 Seflow s.r.l.
    Hosting
  4. Dec 3, 2019
    Route object
    AS49367 Seflow s.r.l.
    RIPE route object for AS49367 Seflow s.r.l., maintainer SEFLOW-MNT MNT-SEFLOW
    158.58.168.0/24
  5. Dec 3, 2019
    Route object
    AS49367 Seflow s.r.l.
    RIPE route object for AS49367 Seflow s.r.l., maintainer SEFLOW-MNT MNT-SEFLOW
    158.58.169.0/24
  6. Dec 3, 2019
    Route object
    AS49367 Seflow s.r.l.
    RIPE route object for AS49367 Seflow s.r.l., maintainer SEFLOW-MNT MNT-SEFLOW
    158.58.170.0/24
  7. Dec 3, 2019
    Route object
    AS49367 Seflow s.r.l.
    RIPE route object for AS49367 Seflow s.r.l., maintainer SEFLOW-MNT MNT-SEFLOW
    158.58.171.0/24
  8. Dec 3, 2019
    Route object
    AS49367 Seflow s.r.l.
    RIPE route object for AS49367 Seflow s.r.l., maintainer SEFLOW-MNT MNT-SEFLOW
    158.58.172.0/24
  9. Dec 3, 2019
    Route object
    AS49367 Seflow s.r.l.
    RIPE route object for AS49367 Seflow s.r.l., maintainer SEFLOW-MNT MNT-SEFLOW
    158.58.173.0/24
  10. Dec 3, 2019
    Route object
    AS49367 Seflow s.r.l.
    RIPE route object for AS49367 Seflow s.r.l., maintainer SEFLOW-MNT MNT-SEFLOW
    158.58.174.0/24
  11. Dec 3, 2019
    Route object
    AS49367 Seflow s.r.l.
    RIPE route object for AS49367 Seflow s.r.l., maintainer SEFLOW-MNT MNT-SEFLOW
    158.58.175.0/24
  12. May 15, 2023
    Route object
    AS49367 Seflow s.r.l.
    RIPE route object for AS49367 Seflow s.r.l., maintainer SEFLOW-MNT MNT-SEFLOW
    158.58.172.0/23
  13. Dec 1, 2023– today
    Announced
    AS49367 Seflow s.r.l.
    Hosting
  14. today
    Used
    TunnelBear
    VPN

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
158.58.168.0/212,048IT-SEFLOW-20111110Seflow s.r.l. (ORG-SS112-RIPE) · ITALLOCATED PANov 10, 2011abuse@seflow.net
└ 158.58.168.0/221,024SEFLOW-CLOUD-NETCloudFlow Virtual DatacenterASSIGNED PAOct 29, 2012abuse@seflow.net
via IT-SEFLOW-20111110
└ 158.58.172.0/23512SEFLOW-MGMTDedicated ServersASSIGNED PAOct 29, 2012abuse@seflow.net
via IT-SEFLOW-20111110
└ 158.58.174.0/24256SEFLOW-DEDICATED-NETDedicated ServersASSIGNED PANov 1, 2012abuse@seflow.net
via IT-SEFLOW-20111110
└ 158.58.175.0/25128SEFLOW-VPS-NETVPS Services - DC2 MilanASSIGNED PAOct 31, 2012abuse@seflow.net
via IT-SEFLOW-20111110
└ 158.58.175.128/25128SEFLOW-MGMTSeFlow Dedicated ServersASSIGNED PAJul 9, 2017abuse@seflow.net
via IT-SEFLOW-20111110

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

2,048 addresses
TypeAddressesShareRanges
Hosting2,034>99%17
VPNanonymizer140.68%14

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2011
Current origin since
Dec 2023 · 3.0 yr
Origin networks
1