Data as of Nov 3, 2026
5.45.112.0/20
2 anonymizer addresses · 0.05% · Datacenter proxy11 residential-proxy exits · 30 daysCLOUD.DOG OU
Residential-proxy exits
Proxy exits
11
0.27% of its addresses · 30 days
Spread
9 of 16
/24s with at least one exit
Providers
34
selling exits here
Oct 4, 2026 – Nov 2, 2026
Exits seen per day
585 observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 5.45.122.0/24 | 0 | 2 | |
| 5.45.126.0/24 | 0 | 2 | |
| 5.45.127.0/24 | 0 | 2 | |
| 5.45.112.0/24 | 0 | 1 | |
| 5.45.115.0/24 | 0 | 1 | |
| 5.45.116.0/24 | 0 | 1 | |
| 5.45.117.0/24 | 0 | 1 | |
| 5.45.118.0/24 | 0 | 1 | |
| 5.45.120.0/24 | 0 | 1 |
Proxy providers listing exits
- 2Captcha
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CliProxy
- Datarama
- EnigmaProxy
- Evomi
- FlexyProxies
- GSocks
- Geonix
- Geonode
- GonzoProxy
- HydraProxy
- IPFly
- Infatica
- InfiniteProxies
- LemonLabs
- MangoProxy
- NodeProxy
- NovaProxy
- Proxy-Seller
- ProxyEmpire
- ProxyGeo
- ProxyHat
- Proxyma
- RainProxy
- ResiProxies
- Shifter
- VantageProxies
- VitalData
- VitalExclusive
- VitalProxy
IPv4 market
Path
2 · Leased from
not leased
4 · Use
Hosting
anonymizer space, operator not named
Lineage
How this block came to its use, oldest first. The whole IPv4 market →
5.45.112.0/20
From the registry to its use
- Nov 20, 2015Route objectAS198068 CLOUD.DOG OURIPE route object for AS198068 CLOUD.DOG OU, maintainer PAGM-MNT5.45.114.0/23
- Nov 20, 2015Route objectAS198068 CLOUD.DOG OURIPE route object for AS198068 CLOUD.DOG OU, maintainer PAGM-MNT5.45.116.0/22
- Nov 20, 2015Route objectAS198068 CLOUD.DOG OURIPE route object for AS198068 CLOUD.DOG OU, maintainer PAGM-MNT5.45.120.0/21
- Dec 19, 2015
- Dec 22, 2015– Nov 2, 2026
- Mar 15, 2019Registry recordCLOUD.DOG OUALLOCATED PA5.45.112.0/20
Announcements
Nesting
More-specifics by size
Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific
Announcements inside
| Prefix | Origin | Type | Anonymizer addresses | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|---|
| 5.45.112.0/24 since Jul 2014 | AS198068 | Hosting | 1 | CLOUD.DOG OU | ||
| 5.45.113.0/24 since Dec 2015 | AS198068 | Hosting | CLOUD.DOG OU | |||
| 5.45.114.0/24 since Jul 2014 | AS198068 | Hosting | CLOUD.DOG OU | |||
| 5.45.115.0/24 since Jul 2014 | AS198068 | Hosting | 1 | CLOUD.DOG OU | ||
| 5.45.116.0/24 since Jul 2014 | AS198068 | Hosting | 1 | CLOUD.DOG OU | ||
| 5.45.117.0/24 since Jul 2014 | AS198068 | Hosting | 1 | CLOUD.DOG OU | ||
| 5.45.118.0/24 since Jul 2014 | AS198068 | Hosting | 1 | CLOUD.DOG OU | ||
| 5.45.119.0/24 since Jul 2014 | AS198068 | Hosting | 20.78%Datacenter proxy | CLOUD.DOG OU | ||
| 5.45.120.0/24 since Jul 2013 | AS198068 | Hosting | 1 | CLOUD.DOG OU | ||
| 5.45.121.0/24 since Jul 2013 | AS198068 | Hosting | CLOUD.DOG OU | |||
| 5.45.122.0/24 since Jul 2013 | AS198068 | Hosting | 2 | CLOUD.DOG OU | ||
| 5.45.123.0/24 since Jul 2013 | AS198068 | Hosting | CLOUD.DOG OU | |||
| 5.45.124.0/24 since Jul 2013 | AS198068 | Hosting | CLOUD.DOG OU | |||
| 5.45.125.0/24 since Jul 2013 | AS198068 | Hosting | CLOUD.DOG OU | |||
| 5.45.126.0/24 since Jul 2013 | AS198068 | Hosting | 2 | CLOUD.DOG OU | ||
| 5.45.127.0/24 since Jul 2013 | AS198068 | Hosting | 2 | CLOUD.DOG OU |
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 |
|---|---|---|---|---|---|---|
| 5.45.112.0/20 | 4,096 | EE-PAGMOU-20120524 | CLOUD.DOG OU (ORG-PO61-RIPE) · EE | ALLOCATED PA | Mar 15, 2019 | [email protected] |
| └ 5.45.112.0/24 | 256 | MANAGED_BY_FASTVPS_EESTI_OU | Fastvps Eesti OU (ORG-FEO3-RIPE) · EE | ASSIGNED PA | Jul 18, 2014 | [email protected] |
| └ 5.45.113.0/24 | 256 | PAGM-NET | Network for hosting services | ASSIGNED PA | Dec 20, 2013 | [email protected] via EE-PAGMOU-20120524 |
| └ 5.45.114.0/24 | 256 | PAGM-NET | Network for hosting services | ASSIGNED PA | Jul 18, 2014 | [email protected] via EE-PAGMOU-20120524 |
| └ 5.45.115.0/24 | 256 | PAGM-NET | Network for hosting services | ASSIGNED PA | Jul 18, 2014 | [email protected] via EE-PAGMOU-20120524 |
| └ 5.45.116.0/24 | 256 | PAGM-NET | Network for hosting services | ASSIGNED PA | Jul 18, 2014 | [email protected] via EE-PAGMOU-20120524 |
| └ 5.45.117.0/24 | 256 | PAGM-NET | Network for hosting services | ASSIGNED PA | Jul 18, 2014 | [email protected] via EE-PAGMOU-20120524 |
| └ 5.45.118.0/24 | 256 | PAGM-NET | Network for hosting services | ASSIGNED PA | Jul 18, 2014 | [email protected] via EE-PAGMOU-20120524 |
| └ 5.45.119.0/24 | 256 | PAGM-NET | Network for hosting services | ASSIGNED PA | Jul 18, 2014 | [email protected] via EE-PAGMOU-20120524 |
| └ 5.45.120.0/24 | 256 | PAGM-NET | Network for hosting services | ASSIGNED PA | Jul 5, 2013 | [email protected] via EE-PAGMOU-20120524 |
| └ 5.45.121.0/24 | 256 | PAGM-NET | Network for hosting services | ASSIGNED PA | Jul 5, 2013 | [email protected] via EE-PAGMOU-20120524 |
| └ 5.45.122.0/24 | 256 | PAGM-NET | Network for hosting services | ASSIGNED PA | Jul 5, 2013 | [email protected] via EE-PAGMOU-20120524 |
| └ 5.45.123.0/24 | 256 | PAGM-NET | Network for hosting services | ASSIGNED PA | Jul 5, 2013 | [email protected] via EE-PAGMOU-20120524 |
| └ 5.45.124.0/24 | 256 | PAGM-NET | Network for hosting services | ASSIGNED PA | Jul 5, 2013 | [email protected] via EE-PAGMOU-20120524 |
| └ 5.45.125.0/24 | 256 | PAGM-NET | Network for hosting services | ASSIGNED PA | Jul 5, 2013 | [email protected] via EE-PAGMOU-20120524 |
| └ 5.45.126.0/24 | 256 | PAGM-NET | Network for hosting services | ASSIGNED PA | Jul 5, 2013 | [email protected] via EE-PAGMOU-20120524 |
| └ 5.45.127.0/24 | 256 | PAGM-NET | Network for hosting services | ASSIGNED PA | Jul 5, 2013 | [email protected] via EE-PAGMOU-20120524 |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Composition
The types across the prefix's announced space, by addresses.
Announced space
Address share
Announced space
Types across the prefix
4,096 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Hosting | 4,094 | >99% | 18 | |
| Datacenter proxyanonymizer | 2 | 0.05% | 2 |
Network & registry
Origin network
AS198068
EE
- Name
- CLOUD.DOG OU
- Type
- Hosting
- Registered
- Sep 22, 2011
- Domain
- fastvps.ee
- Industry
- Hosting and Cloud Provider
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Dec 2015
- Current origin since
- Dec 2015 · 11 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 5.45.112.0/20 | AS198068 | /32 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS198068 | RIPE | PAGM routed network | PAGM-MNT | Mar 19, 2019 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 5.45.114.0/23 | AS198068 | RIPE | PAGM routed network | PAGM-MNT | Mar 19, 2019 |
| 5.45.116.0/22 | AS198068 | RIPE | PAGM routed network | PAGM-MNT | Mar 19, 2019 |
| 5.45.120.0/21 | AS198068 | RIPE | PAGM routed network | PAGM-MNT | Mar 19, 2019 |
Whois
Registration for this announcement
- Range
- 5.45.112.0/20
- Netname
- EE-PAGMOU-20120524
- Registrant
- CLOUD.DOG OU
- Registrant country
- EE
- Organization
- CLOUD.DOG OU (ORG-PO61-RIPE)
- Org country
- EE
- Type
- ALLOCATED PA
- Created
- Mar 15, 2019
- Updated
- Jun 9, 2023
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- EE
- Delegated
- May 24, 2012
- Status
- assigned
Report abuse
Abuse contact
- [email protected]
- Name
- Abuse-C Role
- Handle
- AR50855-RIPE