Data as of Nov 10, 2026
5.22.136.0/21
3 residential-proxy exits · 30 daysAspire Technology Solutions Ltd
Residential-proxy exits
Proxy exits
3
0.15% of its addresses · 30 days
Spread
3 of 8
/24s with at least one exit
Providers
14
selling exits here
Oct 11, 2026 – Nov 9, 2026
Exits seen per day
166 observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 5.22.137.0/24 | 0 | 1 | |
| 5.22.138.0/24 | 0 | 1 | |
| 5.22.142.0/24 | 0 | 1 |
Proxy providers listing exits
- BottingTools
- Byteful
- GloryCloud
- KindProxy
- Kookey
- Maskify
- MoMoProxy
- NovaProxy
- Novada
- PuraRoute
- RapidProxy
- RoamProxy
- SwiftProxy
- VantageProxies
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.22.136.0/21 | 2,048 | UK-ASPIRE-20120503 | Aspire Technology Solutions Ltd (ORG-ATSL4-RIPE) · GB | ALLOCATED PA | May 3, 2012 | abuse@ |
| └ 5.22.136.0/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.2/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.8/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Jul 1, 2026 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.16/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.20/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.22/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.24/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.26/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.27/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.28/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.30/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.32/27 | 32 | NN_ | unknown | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.64/28 | 16 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.80/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.88/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.90/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.92/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.94/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.95/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.96/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.98/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.104/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.105/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.106/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.107/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.108/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.110/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.112/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.114/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.116/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.120/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.128/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.130/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.132/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.134/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.136/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.138/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.140/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.142/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.144/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.146/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.148/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.150/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.152/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.154/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.160/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.162/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.164/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.168/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.172/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.174/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.176/28 | 16 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.192/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.200/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.202/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.203/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.204/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.206/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.208/28 | 16 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.224/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.228/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.230/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.231/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.232/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.240/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.244/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.246/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.247/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.136.248/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.0/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.8/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Dec 1, 2022 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.16/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.24/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.32/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.40/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.44/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.48/28 | 16 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.64/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.68/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.72/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.80/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.84/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.88/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.96/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.104/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.112/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.116/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.120/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.128/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.136/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.144/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.148/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.152/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.156/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.160/28 | 16 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.176/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.180/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.184/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.192/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.196/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.200/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.208/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.209/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.210/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.212/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.216/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.224/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.232/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.240/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.241/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.242/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.244/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.248/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.137.252/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.0/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.8/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.12/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.16/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.24/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.32/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.44/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.48/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.56/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.64/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.68/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.76/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.80/28 | 16 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.96/27 | 32 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.128/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.132/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.136/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.144/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.148/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.152/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.153/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.154/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.156/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.160/27 | 32 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.200/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.208/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.212/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.216/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.224/28 | 16 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.240/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.244/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.248/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.138.252/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.0/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.8/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.16/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.20/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.24/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.32/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.48/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.52/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.60/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.64/27 | 32 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.96/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.100/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.104/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.108/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.109/32 | 1 | NN_ | DNS Cache | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.110/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.111/32 | 1 | NN_ | DNS Cache | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.112/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.120/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.124/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.132/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.136/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.140/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.144/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.152/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.156/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.160/28 | 16 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.176/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.180/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.184/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.188/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.192/28 | 16 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.208/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.212/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.220/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.224/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.228/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.232/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.236/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.240/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.244/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.248/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.139.252/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.140.0/31 | 2 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.140.2/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.140.3/32 | 1 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.140.4/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.140.8/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.140.16/29 | 8 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.140.24/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.140.28/30 | 4 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.140.32/27 | 32 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
| └ 5.22.140.64/26 | 64 | NN_ | ISP Customer Connection | ASSIGNED PA | Apr 3, 2023 | abuse@ via UK-ASPIRE-20120503 |
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
2,048 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Business | 1,876 | 92% | 320 | |
| Internet provider | 172 | 8.4% | 32 |
Network & registry
Origin network
AS51043
GB
- Name
- Aspire Technology Solutions Ltd
- Type
- Internet provider
- Registered
- May 21, 2010
- Domain
- aspirets.com
- Website
- www.aspirets.com/
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Sep 2012
- Current origin since
- Aug 2016 · 10 yr
- Origin networks
- 1
Whois
Registration for this announcement
- Range
- 5.
22. 136. 0/ 21 - Netname
- UK-ASPIRE-20120503
- Registrant
- Aspire Technology Solutions Ltd
- Registrant country
- GB
- Organization
- Aspire Technology Solutions Ltd (ORG-ATSL4-RIPE)
- Org country
- GB
- Type
- ALLOCATED PA
- Created
- May 3, 2012
- Updated
- Aug 12, 2026
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- GB
- Delegated
- May 3, 2012
- Status
- assigned
Report abuse
Abuse contact
- abuse@
aspirets. com - Name
- ASPIRETS Abuse
- Handle
- AS2007