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

91.147.80.0/22

1 residential-proxy exit · 30 days

NAT Kazakhstan JSC

Announcement
this exact prefix
RPKI valid
Announced by
AS202461
Type
Hosting

Residential-proxy exits

Proxy exits
1
0.10% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
20
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • BottingTools
  • BuyingProxy
  • DataImpulse
  • Evomi
  • FlashProxy
  • GeekProxy
  • Geonode
  • IPOasis
  • IPPeak
  • InfiniteProxies
  • PSBProxy
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • Proxy4U
  • ProxyRack
  • Shifter
  • VProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
91.147.80.0/24
since Feb 2026
AS202461HostingNAT Kazakhstan JSC
91.147.81.0/24
since Feb 2026
AS202461Hosting1NAT Kazakhstan JSC
91.147.82.0/24
since Feb 2026
AS202461HostingNAT Kazakhstan JSC
91.147.83.0/24
since Feb 2026
AS202461HostingNAT Kazakhstan JSC

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
91.147.80.0/221,024KZ-NATKAZAKHSTAN-20061027NAT Kazakhstan JSC (ORG-NKJ3-RIPE) · KZALLOCATED PAJan 27, 2026ripe-ncc@nat.kz
└ 91.147.80.0/24256NAT_KazakhstanunknownLIR-PARTITIONED PANov 5, 2026ripe-ncc@nat.kz
via KZ-NATKAZAKHSTAN-20061027
└ 91.147.80.128/25128NAT-KZ-CLOUD-PUBLICunknownASSIGNED PANov 5, 2026ripe-ncc@nat.kz
via NAT_Kazakhstan
└ 91.147.81.0/24256NAT_KazakhstanunknownLIR-PARTITIONED PANov 5, 2026ripe-ncc@nat.kz
via KZ-NATKAZAKHSTAN-20061027
└ 91.147.82.0/24256NAT_KazakhstanunknownLIR-PARTITIONED PANov 5, 2026ripe-ncc@nat.kz
via KZ-NATKAZAKHSTAN-20061027
└ 91.147.83.0/24256NAT_KazakhstanunknownLIR-PARTITIONED PANov 5, 2026ripe-ncc@nat.kz
via KZ-NATKAZAKHSTAN-20061027

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
Rotating
First seen
Apr 2012
Current origin since
Feb 2026 · 9 mo
Origin networks
3
Last change of origin
Feb 2026
Recorded history

History

Handoffs
2