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

5.158.64.0/20

20 residential-proxy exits · 30 days

Orakom S.r.l.

Announcement
this exact prefix
RPKI valid
Announced by
AS199181
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
20
0.49% of its addresses · 30 days
Always-on exits
1
5.0% of its exits
Spread
5 of 16
/24s with at least one exit
Providers
33
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

996 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
5.158.77.0/2417
5.158.70.0/2407
5.158.68.0/2402
5.158.71.0/2402
5.158.72.0/2402

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPMUSK
  • Infatica
  • KindProxy
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • 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
5.158.64.0/204,096IT-ORAKOM-20120725Orakom S.r.l. (ORG-OS89-RIPE) · ITALLOCATED PAJul 25, 2012abuse@orakom.it
└ 5.158.64.0/24256ORAKOM-NOC-BAT01Orakom NOC BAT-01ASSIGNED PAJan 5, 2015abuse@orakom.it
via IT-ORAKOM-20120725
└ 5.158.65.0/24256ORAKOM-NOC-BAT01-VMOrakom NOC BAT-01 VMASSIGNED PAJan 5, 2015abuse@orakom.it
via IT-ORAKOM-20120725
└ 5.158.66.0/23512ORAKOM-CUST3Orakom NAS NAP-01ASSIGNED PAJan 5, 2015abuse@orakom.it
via IT-ORAKOM-20120725
└ 5.158.68.0/221,024ORAKOM-CUST2Orakom NAS BAT-02ASSIGNED PAJan 5, 2015abuse@orakom.it
via IT-ORAKOM-20120725
└ 5.158.72.0/212,048ORAKOM-CUST1unknownASSIGNED PAJan 5, 2015abuse@orakom.it
via IT-ORAKOM-20120725

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
Jul 2013
Current origin since
Feb 2020 · 6.8 yr
Origin networks
1