Data as of Nov 12, 2026

95.169.92.0/22

5 residential-proxy exits · 30 days

HelloTel Telecomunicazioni srl

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

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
24
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

666 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.169.93.0/2404
95.169.95.0/2401

Proxy providers listing exits

  • 2Extract
  • AnyIP
  • BlurPath
  • Byteful
  • CliProxy
  • FastProxy
  • FloppyData
  • GSocks
  • Geonix
  • GonzoProxy
  • IPCola
  • IPPeak
  • Infatica
  • LemonBright
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • RainProxy
  • Shifter
  • VitalExclusive

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
95.169.64.0/198,192IT-HELLOTEL-20090120HelloTel Telecomunicazioni srl (ORG-HTS3-RIPE) · ITALLOCATED PAJan 20, 2009abuse@hellotelwifi.it
└ 95.169.88.0/212,048HELLOTEL-WLNETHelloTel SubnetsLIR-PARTITIONED PAJan 12, 2017abuse@hellotelwifi.it
via IT-HELLOTEL-20090120
└ 95.169.92.0/221,024HELLOTEL-WLNETHelloTel SubnetsLIR-PARTITIONED PAJan 12, 2017abuse@hellotelwifi.it
via HELLOTEL-WLNET
└ 95.169.92.0/24256HELLOTEL-WLNETHelloTel Telecomunicazioni srl (ORG-HTS3-RIPE) · ITASSIGNED PAJan 12, 2017abuse@hellotelwifi.it
└ 95.169.93.0/24256HELLOTEL-WLNETHelloTel Telecomunicazioni srl (ORG-HTS3-RIPE) · ITASSIGNED PAJan 12, 2017abuse@hellotelwifi.it
└ 95.169.94.0/24256HELLOTEL-WLNETHelloTel Telecomunicazioni srl (ORG-HTS3-RIPE) · ITASSIGNED PAJan 12, 2017abuse@hellotelwifi.it
└ 95.169.95.0/24256HELLOTEL-WLNETHelloTel Telecomunicazioni srl (ORG-HTS3-RIPE) · ITASSIGNED PAJan 12, 2017abuse@hellotelwifi.it

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
Feb 2017
Current origin since
Feb 2017 · 9.7 yr
Origin networks
1