Data as of Nov 7, 2026
213.5.16.0/22
60 residential-proxy exits · 30 daysOctopusnet LTD
Residential-proxy exits
Proxy exits
60
5.9% of its addresses · 30 days
Always-on exits
13
22% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
61
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
17K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 213.5.19.0/24 | 5 | 17 | |
| 213.5.17.0/24 | 3 | 16 | |
| 213.5.18.0/24 | 3 | 12 | |
| 213.5.16.0/24 | 2 | 16 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- Ake.net
- BartProxies
- BirdProxies
- BlurPath
- BottingTools
- ByteProxies
- Byteful
- CliProxy
- DataImpulse
- Decodo
- EnigmaProxy
- Evomi
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GloryCloud
- GonzoProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonLabs
- LightningProxies
- MangoProxy
- MoMoProxy
- NextProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- Proxiware
- Proxmint
- Proxy-Seller
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- Shifter
- TalorData
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
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.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 213.5.16.0/22 | 1,024 | RU-OCTOPUSNET-20091001 | Octopusnet LTD (ORG-OL46-RIPE) · RU | ALLOCATED PA | Mar 4, 2015 | support@ |
| └ 213.5.16.0/24 | 256 | USSURIYSK-OCTOPUSNET-NAT-POOL | Octopusnet LTD | ASSIGNED PA | Mar 5, 2015 | support@ via RU-OCTOPUSNET-20091001 |
| └ 213.5.17.0/24 | 256 | USSURIYSK-OCTOPUSNET-RESERVED-NET | Octopusnet LTD | ASSIGNED PA | Mar 5, 2015 | support@ via RU-OCTOPUSNET-20091001 |
| └ 213.5.18.0/24 | 256 | USSURIYSK-OCTOPUSNET-JURIDICAL-POOL | Octopusnet LTD | ASSIGNED PA | Mar 5, 2015 | support@ via RU-OCTOPUSNET-20091001 |
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
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Apr 2013
- Current origin since
- Feb 2021 · 5.7 yr
- Origin networks
- 2
- Last change of origin
- Mar 2015
Recorded history
History
- Handoffs
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS44724 | RIPE | USSURIYSK-OCTOPUSNET-NET | OCTOPUSNET-MNT | Feb 20, 2015 |
Whois
Registration for this announcement
- Range
- 213.
5. 16. 0/ 22 - Netname
- RU-OCTOPUSNET-20091001
- Registrant
- Octopusnet LTD
- Registrant country
- RU
- Organization
- Octopusnet LTD (ORG-OL46-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Mar 4, 2015
- Updated
- Feb 27, 2017
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Oct 1, 2009
- Status
- assigned
Report abuse
Abuse contact
- support@
inetvl. ru - Name
- Octopusnet crew
- Handle
- OC954-RIPE