Data as of Nov 5, 2026
80.254.16.0/20
17 residential-proxy exits · 30 daysPiter-telecom Ltd.
Residential-proxy exits
Proxy exits
17
0.42% of its addresses · 30 days
Spread
8 of 16
/24s with at least one exit
Providers
47
selling exits here
Oct 6, 2026 – Nov 4, 2026
Exits seen per day
321 observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 80.254.21.0/24 | 0 | 4 | |
| 80.254.26.0/24 | 0 | 3 | |
| 80.254.16.0/24 | 0 | 2 | |
| 80.254.17.0/24 | 0 | 2 | |
| 80.254.18.0/24 | 0 | 2 | |
| 80.254.22.0/24 | 0 | 2 | |
| 80.254.25.0/24 | 0 | 1 | |
| 80.254.27.0/24 | 0 | 1 |
Proxy providers listing exits
- 711Proxy
- Ake.net
- B2Proxy
- BestProxy
- BirdProxies
- BottingTools
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- EZProxies
- EnigmaProxy
- Evomi
- Geonode
- GloryCloud
- IPFly
- IPPeak
- IPRoyal
- InfiniteProxies
- KindProxy
- Kookey
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NovaProxy
- Novada
- ProxiesVision
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyRack
- ProxyWing
- PuraRoute
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- VantageProxies
Announcements
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 80.254.16.0/21 since Mar 2011 | AS39101 | Internet provider | 12 | Piter-telecom Ltd. | |
| 80.254.17.0/24 since Feb 2020 | AS39101 | Internet provider | 2 | Piter-telecom Ltd. | |
| 80.254.19.0/24 since Feb 2019 | AS39101 | Internet provider | Piter-telecom Ltd. | ||
| 80.254.23.0/24 since Mar 2018 | AS39101 | Internet provider | Piter-telecom Ltd. |
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 |
|---|---|---|---|---|---|---|
| 80.254.16.0/20 | 4,096 | RU-PITEL-20051202 | Piter-telecom Ltd. (ORG-PA118-RIPE) · RU | ALLOCATED PA | Dec 2, 2005 | noc@ |
| └ 80.254.16.0/23 | 512 | PITEL-NET | Piter-telecom Ltd. (ORG-PA118-RIPE) · RU | ASSIGNED PA | Dec 9, 2005 | noc@ |
| └ 80.254.18.0/24 | 256 | TIPANOVA-NET | Piter-telecom Ltd. (ORG-PA118-RIPE) · RU | ASSIGNED PA | Mar 12, 2007 | noc@ |
| └ 80.254.19.0/24 | 256 | BOLSHOY-NET | Piter-telecom subnet #3 | ASSIGNED PA | Apr 5, 2007 | noc@ via RU-PITEL-20051202 |
| └ 80.254.20.0/27 | 32 | SENNAYA-NET-P2P | Piter-telecom subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.20.32/29 | 8 | ASFGROUP-NET | Customer subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80. | 208 | SENNAYA-NET-P2P | Piter-telecom subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.20.248/29 | 8 | F_ | Customer subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.21.0/24 | 256 | SENNAYA-NET-P2P | Piter-telecom subnet # 4 | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80. | 168 | PITEL-II-NET-P2P | Piter-telecom subnet # 5 | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.22.168/29 | 8 | F_ | Customer subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80. | 80 | PITEL-II-NET-P2P | Piter-telecom subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.23.0/29 | 8 | SAKURA-NET | Customer subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.23.8/29 | 8 | TORGGROUP-NET | Customer subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.23.16/28 | 16 | PITEL-II-NET-P2P | Piter-telecom subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.23.32/29 | 8 | AUGUST-NET | Customer subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80. | 56 | PITEL-II-NET-P2P | Piter-telecom subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.23.96/29 | 8 | RAPORTAL-NET | Customer subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80. | 72 | PITEL-II-NET-P2P | Piter-telecom subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.23.176/29 | 8 | RECONGROUP-NET | Customer subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80. | 72 | PITEL-II-NET-P2P | Piter-telecom subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.24.0/24 | 256 | PITEL-II-NET-P2P | Piter-telecom subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80. | 120 | PITEL-II-NET-P2P | Piter-telecom subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.25.120/29 | 8 | LOXITAN_ | Customer subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.25.128/25 | 128 | PITEL-II-NET-P2P | Piter-telecom subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.26.0/24 | 256 | GALLERY-NET-P2P | Piter-telecom subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.27.0/28 | 16 | GALLERY-NET-P2P | Piter-telecom subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.27.16/29 | 8 | AKSATK-NET | Customer subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80. | 136 | GALLERY-NET-P2P | Piter-telecom subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.27.160/29 | 8 | VOSXODTK-NET | Customer subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80. | 88 | GALLERY-NET-P2P | Piter-telecom subnet | ASSIGNED PA | Mar 19, 2018 | noc@ via RU-PITEL-20051202 |
| └ 80.254.28.0/23 | 512 | MMORSKAYA-NET | Piter-telecom subnet #7 | ASSIGNED PA | Dec 4, 2012 | noc@ via RU-PITEL-20051202 |
| └ 80.254.30.0/23 | 512 | PITEL-III-NET | Piter-telecom subnet # 8 | ASSIGNED PA | Apr 24, 2014 | noc@ via RU-PITEL-20051202 |
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 | |
|---|---|---|---|---|
| Internet provider | 3,872 | 95% | 15 | |
| Business | 224 | 5.5% | 14 |
Network & registry
Origin network
AS39101
RU
- Name
- Piter-telecom Ltd.
- Type
- Internet provider
- Registered
- Dec 14, 2005
- Domain
- piter-telecom.ru
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Feb 2006
- Current origin since
- Jul 2017 · 9.3 yr
- Origin networks
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS39101 | RIPE | Piter-telecom main route | PITEL-MNT | Feb 16, 2011 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 80.254.24.0/21 | AS39101 | RIPE | Piter-telecom route | PITEL-MNT | Feb 16, 2011 |
Whois
Registration for this announcement
- Range
- 80.
254. 16. 0/ 20 - Netname
- RU-PITEL-20051202
- Registrant
- Piter-telecom Ltd.
- Registrant country
- RU
- Organization
- Piter-telecom Ltd. (ORG-PA118-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Dec 2, 2005
- Updated
- Mar 13, 2018
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Dec 2, 2005
- Status
- assigned
Report abuse
Abuse contact
- noc@
piter-telecom. ru - Name
- Abuse-C Role
- Handle
- AR13618-RIPE