Data as of Nov 5, 2026
212.6.44.0/24
6 residential-proxy exits · 30 daysSIA Veesp
Residential-proxy exits
Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
1
17% of its exits
Providers
22
selling exits here
Oct 6, 2026 – Nov 4, 2026
Exits seen per day
445 observations
Proxy providers listing exits
- 2Captcha
- BartProxies
- BirdProxies
- ByteProxies
- Byteful
- CliProxy
- FlexyProxies
- GSocks
- Geonix
- GonzoProxy
- IPFly
- Infatica
- MangoProxy
- NodeProxy
- NovaProxy
- Proxy-Seller
- ProxyEmpire
- Proxyma
- RainProxy
- Shifter
- VitalData
- 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.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 212.6.44.0/24 | 256 | LV-VEESP-20200123 | SIA Veesp (ORG-VS198-RIPE) · LV | ALLOCATED PA | Apr 7, 2022 | abuse@ |
| └ 212. | 255 | Veesp | Veesp datacenter clients | ASSIGNED PA | Jun 16, 2020 | abuse@ via LV-VEESP-20200123 |
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
- May 2006
- Current origin since
- Sep 2021 · 5.1 yr
- Origin networks
- 3
- Last change of origin
- Sep 2021
Recorded history
History
- Handoffs
- 2
Whois
Registration for this announcement
- Range
- 212.
6. 44. 0/ 24 - Netname
- LV-VEESP-20200123
- Registrant
- SIA Veesp
- Registrant country
- LV
- Organization
- SIA Veesp (ORG-VS198-RIPE)
- Org country
- LV
- Type
- ALLOCATED PA
- Created
- Apr 7, 2022
- Updated
- Apr 7, 2022
- Maintainer
- FISHNET-MNT
- RIR
- RIPE NCC
- Country
- LV
- Delegated
- Jan 23, 2020
- Status
- assigned
Report abuse
Abuse contact
- abuse@
veesp. com - Name
- Abuse-C Role
- Handle
- AR43810-RIPE