Data as of Nov 11, 2026

95.158.170.0/23

1 residential-proxy exit · 30 days

'Novatel' EOOD

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
1
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

7 observations

Proxy providers listing exits

  • Thordata

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.158.160.0/19
since Dec 2019
AS41313Residential214
21 always on
"Novatel" EOOD
95.158.128.0/18
since Apr 2009
AS41313Residential256
23 always on
"Novatel" EOOD

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.158.128.0/1816,384BG-NOVATEL-20090406"Novatel" EOOD (ORG-NA318-RIPE) · BGALLOCATED PAApr 6, 2009abuse@novatel.bg
└ 95.158.170.0/24256NOVATELBG-NETNovatel LtdASSIGNED PAFeb 16, 2016abuse@novatel.bg
via BG-NOVATEL-20090406
└ 95.158.171.0/24256NOVATELBG-NETunknownASSIGNED PAJan 25, 2021abuse@novatel.bg
via BG-NOVATEL-20090406

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
Jul 2025
Current origin since
Jul 2025 · 1.3 yr
Origin networks
1