Data as of Nov 4, 2026
195.16.96.0/19
8 residential-proxy exits · 30 daysPJSC MegaFon
Residential-proxy exits
Proxy exits
8
0.10% of its addresses · 30 days
Spread
5 of 32
/24s with at least one exit
Providers
26
selling exits here
Oct 5, 2026 – Nov 3, 2026
Exits seen per day
132 observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 195.16.97.0/24 | 0 | 3 | |
| 195.16.110.0/24 | 0 | 2 | |
| 195.16.102.0/24 | 0 | 1 | |
| 195.16.107.0/24 | 0 | 1 | |
| 195.16.109.0/24 | 0 | 1 |
Proxy providers listing exits
- 711Proxy
- AnyIP
- BirdProxies
- BottingTools
- CatProxies
- EZProxies
- EnigmaProxy
- Evomi
- FloppyData
- Geonode
- HideProxy
- IPFly
- InfiniteProxies
- NSocks
- NextProxy
- NovaProxy
- Novada
- ProxiesVision
- ProxyEmpire
- ProxyGeo
- ProxyWing
- PuraRoute
- Smartproxy
- Thordata
- ThunderProxy
- VantageProxies
Announcements
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 195.16.110.0/23 since Sep 2016 | AS25159 | Mobile | 2 | PJSC MegaFon via Megafon-Moscow GPRS Pool 2 |
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 |
|---|---|---|---|---|---|---|
| 195.16.96.0/19 | 8,192 | RU-MEGAFON-970313 | PJSC MegaFon (ORG-OM1-RIPE) · RU | ALLOCATED PA | Dec 10, 2001 | abuse-mailbox@ |
| └ 195. | 3,584 | MF-STF-BBA-POOL | Megafon-Moscow Broadband clients pool | LIR-PARTITIONED PA | Jul 6, 2022 | abuse-mailbox@ via RU-MEGAFON-970313 |
| └ 195.16.96.0/21 | 2,048 | MF-MOSCOW-BBA-POOL-195-16-96 | Megafon-Moscow Broadband clients pool 195.16.96.0/21 | ASSIGNED PA | Mar 14, 2013 | abuse-mailbox@ via MF-STF-BBA-POOL |
| └ 195.16.104.0/22 | 1,024 | MF-MOSCOW-BBA-POOL-195-16-104-0 | unknown | LIR-PARTITIONED PA | Feb 21, 2022 | abuse-mailbox@ via MF-STF-BBA-POOL |
| └ 195.16.107.80/29 | 8 | T3939007_ | unknown | ASSIGNED PA | Feb 21, 2022 | abuse-mailbox@ via MF-MOSCOW-BBA-POOL-195-16-104-0 |
| └ 195.16.108.0/23 | 512 | MF-MOSCOW-BBA-POOL-195-16-108-0 | unknown | ASSIGNED PA | Sep 9, 2020 | abuse-mailbox@ via MF-STF-BBA-POOL |
| └ 195.16.110.0/23 | 512 | MF-STF-GPRS-POOL-2 | Megafon-Moscow GPRS Pool 2 | LIR-PARTITIONED PA | Jul 6, 2022 | abuse-mailbox@ via RU-MEGAFON-970313 |
| └ 195.16.110.0/24 | 256 | StF-KB-GPRS-POOL | unknown | ASSIGNED PA | Apr 17, 2025 | abuse-mailbox@ via MF-STF-GPRS-POOL-2 |
| └ 195.16.111.0/24 | 256 | StF-KB-GPRS-POOL | unknown | ASSIGNED PA | Apr 17, 2025 | abuse-mailbox@ via MF-STF-GPRS-POOL-2 |
| └ 195.16.112.0/23 | 512 | MF-MOSCOW-BBA-20220424-T4104128 | Megafon-Moscow Broadband clients pool | LIR-PARTITIONED PA | Jul 6, 2022 | abuse-mailbox@ via RU-MEGAFON-970313 |
| └ 195.16.114.0/23 | 512 | MF-MOSCOW-MBA-POOL | Megafon-Moscow Mobile | LIR-PARTITIONED PA | Jul 6, 2022 | abuse-mailbox@ via RU-MEGAFON-970313 |
| └ 195.16.114.0/24 | 256 | APN-public-msk | unknown | ASSIGNED PA | Apr 17, 2025 | abuse-mailbox@ via MF-MOSCOW-MBA-POOL |
| └ 195.16.115.0/24 | 256 | APN-public-msk | unknown | ASSIGNED PA | Apr 17, 2025 | abuse-mailbox@ via MF-MOSCOW-MBA-POOL |
| └ 195. | 3,072 | MF-STF-BBA | unknown | LIR-PARTITIONED PA | Jul 6, 2022 | abuse-mailbox@ via RU-MEGAFON-970313 |
| └ 195.16.116.0/22 | 1,024 | MF-MOSCOW-BBA-20220424-T4104128 | Megafon-Moscow Broadband pool | ASSIGNED PA | Sep 9, 2020 | abuse-mailbox@ via MF-STF-BBA |
| └ 195.16.120.0/21 | 2,048 | MF-MOSCOW-BBA-POOL-195-16-120 | Megafon-Moscow Broadband clients pool 195.16.120.0/21 | ASSIGNED PA | Mar 14, 2013 | abuse-mailbox@ via MF-STF-BBA |
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
8,192 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Mobile | 8,184 | >99% | 4 | |
| Business | 8 | 0.10% | 1 |
Network & registry
Origin network
AS25159
RU
- Name
- PJSC MegaFon
- Type
- Internet provider
- Registered
- Aug 13, 2002
- Domain
- megafon.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
- May 2005
- Current origin since
- Sep 2016 · 10 yr
- Origin networks
- 2
- Last change of origin
- Mar 2013
Recorded history
History
- Handoffs
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 195.16.96.0/19 | AS25159 | /19 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS25159 | RIPE | Megafon-Moscow | MEGAFON-RIPE-MNT | Mar 4, 2020 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 195.16.114.0/23 | AS25159 | RIPE | MF-MOSCOW-MBB-APN-PUBLIC-MSK-195-16-114-0 | MEGAFON-AUTO-MNT GDC-TR-COREIP MEGAFON-RIPE-MNT | May 30, 2022 |
Whois
Registration for this announcement
- Range
- 195.
16. 96. 0/ 19 - Netname
- RU-MEGAFON-970313
- Registrant
- PJSC MegaFon
- Registrant country
- RU
- Organization
- PJSC MegaFon (ORG-OM1-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Dec 10, 2001
- Updated
- Nov 29, 2019
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Mar 13, 1997
- Status
- assigned
Report abuse
Abuse contact
- abuse-mailbox@
megafon. ru - Name
- MegaFon PJSC - Internet Service Network Operation Center
- Handle
- MFON-RIPE