Data as of Nov 16, 2026

41.190.233.0/24

4 residential-proxy exits · 30 days

Orioncom SPRL

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
25
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

359 observations

Proxy providers listing exits

  • AETHYN_BASIC
  • AnyIP
  • BlurPath
  • BottingTools
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • FloppyData
  • GloryCloud
  • INSTANTSOCKS_BASIC
  • IPFly
  • IPMUSK
  • IPRoyal
  • KindProxy
  • NextProxy
  • NiuProxy
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SwiftProxy
  • TORCHPROXIES_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
41.190.232.0/23
since Feb 2024
AS37638Residential25
1 always on
Orioncom SPRL

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
41.190.232.0/221,024Orioncom-SPRLOrioncom SPRL (ORG-OS3-AFRINIC) · CDALLOCATED PA——
└ 41.190.233.0/25128ORIONCOMConfigured on our router under a VLAN and are issued to clients on their special requirement to configure on their Firewall, mail Server, etc.ASSIGNED PA——
└ 41.190.233.128/2664ORIONCOMUsed to do Natting for our Private IP client.ASSIGNED PA——
└ 41.190.233.192/298ORIONCOMIssued to a client for their IP-Sec Tunnel and configuration to routers & server.ASSIGNED PA——
└ 41.190.233.200/298ORIONCOMIssued to a client for their IP-Sec tunnel and configuration on their router & server.ASSIGNED PA——
└ 41.190.233.240/304ORIONCOMUsed for creating a PTP with client router and then routed a block.ASSIGNED PA——
└ 41.190.233.244/304ORIONCOMUsed for creating a PTP with client router and then routed a block.ASSIGNED PA——
└ 41.190.233.248/298ORIONCOMOrioncomASSIGNED PA——

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
May 2013
Current origin since
Feb 2014 · 13 yr
Origin networks
3
Last change of origin
Feb 2018
Recorded history

History

Handoffs
2