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

46.250.192.0/19

1 residential-proxy exit · 30 days

EMP Secure AS

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

Residential-proxy exits

Proxy exits
1
0.01% of its addresses · 30 days
Spread
1 of 32
/24s with at least one exit
Providers
1
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2 observations

Proxy providers listing exits

  • 2Extract

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
46.250.192.0/198,192NO-HATTELAND-20110202EMP Secure AS (ORG-HA11-RIPE) · NOALLOCATED PAFeb 2, 2011soc@hatteland.com
└ 46.250.192.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.193.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.194.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.195.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.196.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.197.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.198.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.199.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.200.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.201.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.202.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.203.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.204.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.205.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.206.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.207.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.208.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.209.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.210.0/24256NO-PROISPPro ISP AS (ORG-PIA38-RIPE)ASSIGNED PAFeb 25, 2015support@proisp.no
└ 46.250.211.0/24256NO-PROISPPro ISP AS (ORG-PIA38-RIPE)ASSIGNED PASep 1, 2019support@proisp.no
└ 46.250.212.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.213.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.214.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.215.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.216.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.217.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.218.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.219.0/24256NO-HATTELAND-CUSTOMERSunknownASSIGNED PASep 1, 2019soc@hatteland.com
via NO-HATTELAND-20110202
└ 46.250.220.0/221,024NO-PROISPPro ISP AS (ORG-PIA38-RIPE)ASSIGNED PAJan 6, 2020support@proisp.no

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
Stable
First seen
Feb 2011
Current origin since
Feb 2011 · 16 yr
Origin networks
1