Data as of Nov 15, 2026
188.162.0.0/16
18,417 residential-proxy exits · 30 daysPJSC MegaFon
Residential-proxy exits
Proxy exits
18,417
28% of its addresses · 30 days
Always-on exits
6
0.03% of its exits
Spread
114 of 256
/24s with at least one exit
Providers
148
selling exits here
Oct 16, 2026 – Nov 14, 2026
Exits seen per day
992K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 188.162.248.0/24 | 3 | 172 | |
| 188.162.5.0/24 | 1 | 255 | |
| 188.162.74.0/24 | 1 | 226 | |
| 188.162.13.0/24 | 1 | 192 | |
| 188.162.64.0/24 | 0 | 255 | |
| 188.162.65.0/24 | 0 | 255 | |
| 188.162.249.0/24 | 0 | 255 | |
| 188.162.239.0/24 | 0 | 253 | |
| 188.162.238.0/24 | 0 | 253 | |
| 188.162.161.0/24 | 0 | 252 | |
| 188.162.241.0/24 | 0 | 244 | |
| 188.162.156.0/24 | 0 | 242 | |
| 188.162.173.0/24 | 0 | 242 | |
| 188.162.10.0/24 | 0 | 241 | |
| 188.162.255.0/24 | 0 | 240 | |
| 188.162.174.0/24 | 0 | 240 | |
| 188.162.49.0/24 | 0 | 235 | |
| 188.162.15.0/24 | 0 | 233 | |
| 188.162.242.0/24 | 0 | 231 | |
| 188.162.245.0/24 | 0 | 231 | |
| 188.162.36.0/24 | 0 | 229 | |
| 188.162.75.0/24 | 0 | 227 | |
| 188.162.128.0/24 | 0 | 226 | |
| 188.162.51.0/24 | 0 | 222 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- 9Proxy
- APROXY
- ASHBURNPROXIES
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CROXY
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EVOPROXY
- EZProxies
- EnigmaProxy
- Evomi
- FLEETPROXY
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- FuseProxy
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HELODATA
- HPROXY
- HideProxy
- HydraProxy
- INSTANTSOCKS_BASIC
- INSTANTSOCKS_PREMIUM
- IP2WORLD
- IPCola
- IPFly
- IPMUSK
- IPOasis
- IPPeak
- IPROCKET_BASIC
- IPROCKET_PREMIUM
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- KocerRoxy
- Kookey
- LOKIPROXY
- LUMIPROXY
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MagneticProxy
- MangoProxy
- MarsProxies
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYFALL
- PROXYLANE
- PROXYON
- PROXYSALE
- PROXYSAVER
- PROXYSCRAPE
- PROXYWING_BASIC
- PROXY_CC
- PSBProxy
- PYPROXY
- PacketStream
- PrivateByte
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Cheap
- Proxy-Seller
- Proxy302
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RH7Proxy
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SIMPLYNODE
- SPYDERPROXY_BASIC
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- SwiftProxy
- TORCHPROXIES_BASIC
- TORCHPROXIES_PREMIUM
- TORCHPROXIES_X
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- TrustProxy
- VProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- Webshare
- YumiProxy
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
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 | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 188.162.0.0/24 since Apr 2020 | AS31205 | Mobile | 210 | PJSC MegaFon | |
| 188.162.1.0/24 since Dec 2020 | AS31205 | Mobile | 204 | PJSC MegaFon | |
| 188.162.2.0/23 since Aug 2016 | AS31205 | Mobile | PJSC MegaFon | ||
| 188.162.4.0/22 since Apr 2020 | AS31205 | Mobile | 852 1 always on | PJSC MegaFon | |
| 188.162.8.0/23 since Aug 2016 | AS31205 | Mobile | PJSC MegaFon | ||
| 188.162.10.0/23 since Apr 2020 | AS31205 | Mobile | 440 | PJSC MegaFon | |
| 188.162.12.0/23 since Apr 2020 | AS31205 | Mobile | 392 1 always on | PJSC MegaFon | |
| 188.162.14.0/23 since Jan 2024 | AS31133 | Mobile | 430 | PJSC MegaFon | |
| 188.162.32.0/22 since May 2026 | AS31133 | Mobile | PJSC MegaFon | ||
| 188.162.36.0/23 since May 2026 | AS31133 | Mobile | 427 | PJSC MegaFon | |
| 188.162.38.0/23 since May 2026 | AS31133 | Mobile | 390 | PJSC MegaFon | |
| 188.162.40.0/21 since May 2026 | AS31133 | Mobile | 782 | PJSC MegaFon | |
| 188.162.48.0/20 since May 2026 | AS31133 | Mobile | 1,403 | PJSC MegaFon | |
| 188.162.55.0/24 since Aug 2021 | AS31133 | Mobile | PJSC MegaFon | ||
| 188.162.61.0/24 since Nov 2022 | AS31133 | Mobile | PJSC MegaFon | ||
| 188.162.62.0/23 since Aug 2023 | AS31133 | Mobile | PJSC MegaFon | ||
| 188.162.64.0/23 since Dec 2017 | AS31213 | Mobile | 510 | PJSC MegaFon | |
| 188.162.72.0/22 since Jan 2024 | AS31133 | Mobile | 849 1 always on | PJSC MegaFon | |
| 188.162.76.0/23 since Jan 2024 | AS31133 | Mobile | 438 | PJSC MegaFon | |
| 188.162.78.0/24 since Aug 2017 | AS31205 | Mobile | 111 | PJSC MegaFon | |
| 188.162.79.0/24 since Jul 2021 | AS31205 | Mobile | PJSC MegaFon | ||
| 188.162.80.0/24 since Jan 2024 | AS31133 | Mobile | 196 | PJSC MegaFon | |
| 188.162.81.0/24 since Sep 2019 | AS31205 | Mobile | PJSC MegaFon | ||
| 188.162.82.0/24 since Apr 2023 | AS31205 | Mobile | PJSC MegaFon | ||
| 188.162.83.0/24 since Mar 2020 | AS31205 | Mobile | PJSC MegaFon | ||
| 188.162.84.0/24 since Jan 2024 | AS31133 | Mobile | 87 | PJSC MegaFon | |
| 188.162.85.0/24 since Dec 2020 | AS31205 | Mobile | PJSC MegaFon | ||
| 188.162.87.0/24 since May 2022 | AS31205 | Mobile | PJSC MegaFon | ||
| 188.162.88.0/24 since Apr 2023 | AS31205 | Mobile | 1 | PJSC MegaFon | |
| 188.162.89.0/24 since May 2021 | AS31205 | Mobile | 2 | PJSC MegaFon | |
| 188.162.90.0/23 since Apr 2023 | AS31205 | Mobile | PJSC MegaFon | ||
| 188.162.92.0/22 since Sep 2022 | AS31205 | Mobile | PJSC MegaFon | ||
| 188.162.128.0/24 since Mar 2024 | AS31163 | Mobile | 226 | PJSC MegaFon | |
| 188.162.129.0/24 since Mar 2024 | AS31163 | Mobile | PJSC MegaFon | ||
| 188.162.130.0/23 since Oct 2016 | AS31163 | Mobile | PJSC MegaFon | ||
| 188.162.132.0/24 since Dec 2016 | AS31163 | Mobile | 147 | PJSC MegaFon | |
| 188.162.133.0/24 since Nov 2023 | AS31163 | Mobile | PJSC MegaFon | ||
| 188.162.134.0/23 since Nov 2023 | AS31163 | Mobile | PJSC MegaFon | ||
| 188.162.136.0/23 since Nov 2023 | AS31163 | Mobile | PJSC MegaFon | ||
| 188.162.138.0/24 since Oct 2016 | AS31163 | Mobile | PJSC MegaFon | ||
| 188.162.139.0/24 since Oct 2016 | AS31163 | Mobile | PJSC MegaFon | ||
| 188.162.140.0/24 since Dec 2018 | AS31163 | Mobile | 152 | PJSC MegaFon | |
| 188.162.141.0/24 since Dec 2018 | AS31163 | Mobile | 47 | PJSC MegaFon | |
| 188.162.142.0/24 since Dec 2018 | AS31163 | Mobile | 168 | PJSC MegaFon | |
| 188.162.143.0/24 since May 2018 | AS31163 | Mobile | 177 | PJSC MegaFon | |
| 188.162.144.0/24 since May 2018 | AS31163 | Mobile | 83 | PJSC MegaFon | |
| 188.162.145.0/24 since May 2018 | AS31163 | Mobile | 197 | PJSC MegaFon | |
| 188.162.146.0/23 since Nov 2023 | AS31163 | Mobile | PJSC MegaFon | ||
| 188.162.148.0/22 since Nov 2023 | AS31163 | Mobile | PJSC MegaFon | ||
| 188.162.152.0/22 since Nov 2023 | AS31163 | Mobile | PJSC MegaFon | ||
| 188.162.156.0/24 since Nov 2023 | AS31163 | Mobile | 242 | PJSC MegaFon | |
| 188.162.161.0/24 since Aug 2022 | AS31163 | Mobile | 252 | PJSC MegaFon | |
| 188.162.162.0/24 since Aug 2022 | AS31163 | Mobile | 135 | PJSC MegaFon | |
| 188.162.163.0/24 since Aug 2022 | AS31163 | Mobile | 177 | PJSC MegaFon | |
| 188.162.164.0/23 since Oct 2016 | AS31163 | Mobile | PJSC MegaFon | ||
| 188.162.166.0/24 since Dec 2016 | AS31163 | Mobile | 48 | PJSC MegaFon | |
| 188.162.167.0/24 since Dec 2016 | AS31163 | Mobile | 82 | PJSC MegaFon | |
| 188.162.168.0/23 since Oct 2016 | AS31163 | Mobile | 1 | PJSC MegaFon | |
| 188.162.170.0/23 since Oct 2016 | AS31163 | Mobile | 1 | PJSC MegaFon | |
| 188.162.172.0/22 since Dec 2016 | AS31163 | Mobile | 838 | PJSC MegaFon | |
| 188.162.176.0/22 since Dec 2016 | AS31163 | Mobile | 595 | PJSC MegaFon | |
| 188.162.180.0/22 since Dec 2016 | AS31163 | Mobile | 704 | PJSC MegaFon | |
| 188.162.184.0/22 since Dec 2016 | AS31163 | Mobile | 433 | PJSC MegaFon | |
| 188.162.188.0/24 since Aug 2022 | AS31163 | Mobile | 124 | PJSC MegaFon | |
| 188.162.191.0/24 since Dec 2016 | AS31163 | Mobile | 169 | PJSC MegaFon | |
| 188.162.192.0/23 since May 2026 | AS31133 | Mobile | 321 | PJSC MegaFon | |
| 188.162.194.0/23 since May 2026 | AS31133 | Mobile | 234 | PJSC MegaFon | |
| 188.162.196.0/22 since May 2026 | AS31133 | Mobile | 440 | PJSC MegaFon | |
| 188.162.200.0/21 since May 2026 | AS31133 | Mobile | 1,124 | PJSC MegaFon | |
| 188.162.207.0/24 since May 2022 | AS31133 | Mobile | PJSC MegaFon | ||
| 188.162.220.0/22 since Feb 2019 | AS31133 | Mobile | 1 | PJSC MegaFon via infrastructure in Ufa | |
| 188.162.224.0/24 since Apr 2021 | AS31133 | Internet provider | PJSC MegaFon via Far East PLSC Megafon | ||
| 188.162.225.0/24 since Nov 2020 | AS31133 | Mobile | PJSC MegaFon via Far East PLSC Megafon | ||
| 188.162.226.0/23 since Dec 2020 | AS31133 | Mobile | 2 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.228.0/24 since Nov 2020 | AS31133 | Mobile | 190 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.229.0/24 since Nov 2020 | AS31133 | Mobile | 142 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.230.0/23 since Dec 2020 | AS31133 | Mobile | PJSC MegaFon via Far East PLSC Megafon | ||
| 188.162.231.0/24 since Nov 2020 | AS31133 | Mobile | PJSC MegaFon via Far East PLSC Megafon | ||
| 188.162.232.0/24 since Dec 2020 | AS31133 | Mobile | 1 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.233.0/24 since Oct 2020 | AS31133 | Mobile | PJSC MegaFon via Far East PLSC Megafon | ||
| 188.162.234.0/23 since Dec 2020 | AS31133 | Mobile | 2 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.236.0/24 since Nov 2020 | AS31133 | Mobile | 216 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.237.0/24 since Nov 2020 | AS31133 | Mobile | 191 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.238.0/24 since Nov 2020 | AS31133 | Mobile | 253 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.239.0/24 since Nov 2020 | AS31133 | Mobile | 253 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.240.0/24 since Nov 2020 | AS31133 | Mobile | 209 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.241.0/24 since Nov 2020 | AS31133 | Mobile | 244 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.242.0/24 since Nov 2020 | AS31133 | Mobile | 231 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.243.0/24 since Nov 2020 | AS31133 | Mobile | 145 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.244.0/24 since Nov 2020 | AS31133 | Mobile | 103 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.245.0/24 since Nov 2020 | AS31133 | Mobile | 231 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.246.0/23 since Dec 2020 | AS31133 | Mobile | 2 | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.248.0/22 since Dec 2020 | AS31133 | Mobile | 823 3 always on | PJSC MegaFon via Far East PLSC Megafon | |
| 188.162.252.0/22 since Dec 2020 | AS31133 | Mobile | 337 | PJSC MegaFon via Far East PLSC Megafon |
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 |
|---|---|---|---|---|---|---|
| 188.162.0.0/16 | 65,536 | RU-MEGAFON-20090520 | PJSC MegaFon (ORG-OM1-RIPE) · RU | ALLOCATED PA | May 20, 2009 | abuse-mailbox@ |
| └ 188.162.0.0/20 | 4,096 | MF-GDC-Yota-09112022 | unknown | LIR-PARTITIONED PA | Nov 9, 2022 | abuse-mailbox@ via RU-MEGAFON-20090520 |
| └ 188.162.0.0/23 | 512 | SF-PS-Import-from-Yota-mobile-CGNAT-TOLM | unknown | ASSIGNED PA | Jan 25, 2023 | abuse-mailbox@ via MF-GDC-Yota-09112022 |
| └ 188.162.2.0/23 | 512 | SF-PS-Import-from-Yota-mobile-CGNAT-TOLM | unknown | ASSIGNED PA | Jan 25, 2023 | abuse-mailbox@ via MF-GDC-Yota-09112022 |
| └ 188.162.4.0/22 | 1,024 | SF-PS-Import-from-Yota-mobile-CGNAT-TOLM | unknown | ASSIGNED PA | Jan 25, 2023 | abuse-mailbox@ via MF-GDC-Yota-09112022 |
| └ 188.162.8.0/23 | 512 | SF-PS-Import-from-Yota-mobile-CGNAT-TOLM | unknown | ASSIGNED PA | Jan 25, 2023 | abuse-mailbox@ via MF-GDC-Yota-09112022 |
| └ 188.162.10.0/23 | 512 | SF-PS-Import-from-Yota-mobile-CGNAT-TOLM | unknown | ASSIGNED PA | Jan 25, 2023 | abuse-mailbox@ via MF-GDC-Yota-09112022 |
| └ 188.162.12.0/23 | 512 | SF-PS-Import-from-Yota-mobile-CGNAT-TOLM | unknown | ASSIGNED PA | Jan 25, 2023 | abuse-mailbox@ via MF-GDC-Yota-09112022 |
| └ 188.162.14.0/23 | 512 | SF-PS-Import-from-Yota-mobile-CGNAT-TOLM | unknown | ASSIGNED PA | Jan 25, 2023 | abuse-mailbox@ via MF-GDC-Yota-09112022 |
| └ 188.162.32.0/19 | 8,192 | MF-GDC | unknown | LIR-PARTITIONED PA | Aug 25, 2021 | abuse-mailbox@ via RU-MEGAFON-20090520 |
| └ 188.162.32.0/22 | 1,024 | SCARTEL | infrastructure in Samara | ASSIGNED PA | May 5, 2022 | abuse-mailbox@ via MF-GDC |
| └ 188.162.36.0/23 | 512 | SCARTEL | unknown | ASSIGNED PA | Jun 1, 2026 | abuse-mailbox@ via MF-GDC |
| └ 188.162.38.0/23 | 512 | PF-NAT | unknown | ASSIGNED PA | Jun 1, 2026 | abuse-mailbox@ via MF-GDC |
| └ 188.162.40.0/21 | 2,048 | SCARTEL | infrastructure in Msk | ASSIGNED PA | Aug 25, 2009 | abuse-mailbox@ via MF-GDC |
| └ 188.162.48.0/21 | 2,048 | SCARTEL | infrastructure in Msk | ASSIGNED PA | Aug 7, 2009 | abuse-mailbox@ via MF-GDC |
| └ 188.162.56.0/21 | 2,048 | SCARTEL | unknown | ASSIGNED PA | Jul 16, 2009 | abuse-mailbox@ via MF-GDC |
| └ 188.162.64.0/19 | 8,192 | MF-GDC-17072023 | unknown | LIR-PARTITIONED PA | Jul 17, 2023 | abuse-mailbox@ via RU-MEGAFON-20090520 |
| └ 188.162.64.0/21 | 2,048 | SCARTEL | infrastructure in SPb | ASSIGNED PA | Sep 23, 2009 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.72.0/22 | 1,024 | SibF_ | unknown | ASSIGNED PA | Jul 15, 2021 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.76.0/23 | 512 | SibF_ | unknown | ASSIGNED PA | Jul 15, 2021 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.78.0/24 | 256 | SibF_ | unknown | ASSIGNED PA | Jul 15, 2021 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.79.0/24 | 256 | SibF_ | unknown | ASSIGNED PA | Jul 15, 2021 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.80.0/24 | 256 | SCARTEL | Krasnoyarsk Clients | ASSIGNED PA | Sep 2, 2013 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.81.0/24 | 256 | SCARTEL | Krasnoyarsk Clients | ASSIGNED PA | Sep 2, 2013 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.82.0/24 | 256 | APN-public-sib | unknown | ASSIGNED PA | Mar 22, 2023 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.83.0/24 | 256 | SCARTEL | SCARTEL Network | ASSIGNED PA | Jul 8, 2022 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.84.0/24 | 256 | SCARTEL | Tomsk Clients | ASSIGNED PA | Sep 2, 2013 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.85.0/24 | 256 | SCARTEL | Tomsk Clients | ASSIGNED PA | Sep 2, 2013 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.86.0/24 | 256 | MF-SF-MOB | MF-DV-09072021- T3686966 | ASSIGNED PA | Jul 9, 2021 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.87.0/24 | 256 | SCARTEL | SCARTEL Network | ASSIGNED PA | Jul 8, 2022 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.88.0/24 | 256 | APN-public-sib | unknown | ASSIGNED PA | Mar 22, 2023 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.89.0/24 | 256 | NSK-Yota-clients | unknown | ASSIGNED PA | Apr 17, 2025 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.90.0/23 | 512 | APN-public-sib | unknown | ASSIGNED PA | Mar 22, 2023 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.92.0/22 | 1,024 | APN-public-sib | unknown | ASSIGNED PA | Apr 17, 2025 | abuse-mailbox@ via MF-GDC-17072023 |
| └ 188.162.96.0/19 | 8,192 | SCARTEL | infrastructure in Msk | ASSIGNED PA | Sep 15, 2009 | abuse-mailbox@ via RU-MEGAFON-20090520 |
| └ 188.162.128.0/18 | 16,384 | MF-MB-20220825-T4172950 | unknown | LIR-PARTITIONED PA | Aug 25, 2022 | abuse-mailbox@ via RU-MEGAFON-20090520 |
| └ 188.162.128.0/20 | 4,096 | MF-GDC-KF-20220826 | Mobile Subscribers | ASSIGNED PA | Aug 26, 2022 | abuse-mailbox@ via MF-MB-20220825-T4172950 |
| └ 188.162.144.0/24 | 256 | MF-GDC-20220826 | unknown | ASSIGNED PA | Nov 23, 2023 | abuse-mailbox@ via MF-MB-20220825-T4172950 |
| └ 188.162.145.0/24 | 256 | MF-GDC-20220826 | unknown | ASSIGNED PA | Nov 23, 2023 | abuse-mailbox@ via MF-MB-20220825-T4172950 |
| └ 188.162.146.0/24 | 256 | MF-GDC-20220826 | unknown | ASSIGNED PA | Nov 23, 2023 | abuse-mailbox@ via MF-MB-20220825-T4172950 |
| └ 188.162.147.0/24 | 256 | MF-GDC-20220826 | unknown | ASSIGNED PA | Nov 23, 2023 | abuse-mailbox@ via MF-MB-20220825-T4172950 |
| └ 188. | 1,023 | MF-GDC-20220826 | unknown | ASSIGNED PA | Nov 23, 2023 | abuse-mailbox@ via MF-MB-20220825-T4172950 |
| └ 188. | 1,023 | MF-GDC-20220826 | unknown | ASSIGNED PA | Nov 23, 2023 | abuse-mailbox@ via MF-MB-20220825-T4172950 |
| └ 188.162.156.0/24 | 256 | MF-GDC-20220826 | unknown | ASSIGNED PA | Nov 23, 2023 | abuse-mailbox@ via MF-MB-20220825-T4172950 |
| └ 188.162.157.0/24 | 256 | MF-GDC-20220826 | unknown | ASSIGNED PA | Nov 23, 2023 | abuse-mailbox@ via MF-MB-20220825-T4172950 |
| └ 188.162.158.0/24 | 256 | MF-GDC-20220826 | unknown | ASSIGNED PA | Nov 23, 2023 | abuse-mailbox@ via MF-MB-20220825-T4172950 |
| └ 188.162.159.0/24 | 256 | MF-GDC-20220826 | unknown | ASSIGNED PA | Nov 23, 2023 | abuse-mailbox@ via MF-MB-20220825-T4172950 |
| └ 188.162.160.0/20 | 4,096 | MF-GDC-KF-20220826 | Mobile Subscribers | ASSIGNED PA | Aug 26, 2022 | abuse-mailbox@ via MF-MB-20220825-T4172950 |
| └ 188.162.176.0/20 | 4,096 | MF-GDC-KF-20220826 | Mobile Subscribers | ASSIGNED PA | Aug 26, 2022 | abuse-mailbox@ via MF-MB-20220825-T4172950 |
| └ 188.162.192.0/20 | 4,096 | MF-GDC | unknown | LIR-PARTITIONED PA | Aug 20, 2021 | abuse-mailbox@ via RU-MEGAFON-20090520 |
| └ 188.162.192.0/21 | 2,048 | MF-MGSM | infrastructure in Ufa | ASSIGNED PA | Sep 14, 2009 | abuse-mailbox@ via MF-GDC |
| └ 188.162.200.0/21 | 2,048 | SCARTEL | infrastructure in Ufa | ASSIGNED PA | Dec 29, 2009 | abuse-mailbox@ via MF-GDC |
| └ 188.162.208.0/21 | 2,048 | SCARTEL | infrastructure in Ufa | ASSIGNED PA | Jul 20, 2009 | abuse-mailbox@ via RU-MEGAFON-20090520 |
| └ 188.162.216.0/21 | 2,048 | SCARTEL | infrastructure in Ufa | LIR-PARTITIONED PA | Aug 25, 2021 | abuse-mailbox@ via RU-MEGAFON-20090520 |
| └ 188.162.216.0/22 | 1,024 | SCARTEL | infrastructure in Ufa | ASSIGNED PA | May 5, 2022 | abuse-mailbox@ via SCARTEL |
| └ 188.162.220.0/22 | 1,024 | SCARTEL | infrastructure in Ufa | ASSIGNED PA | May 5, 2022 | abuse-mailbox@ via SCARTEL |
| └ 188.162.224.0/19 | 8,192 | MF-DVF-T3306070 | Far East PLSC Megafon | SUB-ALLOCATED PA | Aug 14, 2020 | abuse-mailbox@ via RU-MEGAFON-20090520 |
| └ 188.162.224.0/24 | 256 | MF-DvF-IT-INFRASTRUCTURE | IT-Infrastructure Khabarovsk | ASSIGNED PA | Oct 30, 2013 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.225.0/24 | 256 | SCARTEL | Vladivostok Yota Clients | ASSIGNED PA | Oct 30, 2013 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.226.0/23 | 512 | SCARTEL | Vladivostok Yota Clients | ASSIGNED PA | Oct 30, 2013 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.228.0/24 | 256 | SCARTEL | Vladivostok Yota PAT Clients | ASSIGNED PA | Oct 30, 2013 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.229.0/24 | 256 | SCARTEL | Khabarovsk Yota PAT Clients | ASSIGNED PA | Oct 30, 2013 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.230.0/23 | 512 | DVF_ | unknown | ASSIGNED PA | Nov 25, 2020 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.232.0/24 | 256 | SCARTEL | Khabarovsk Static IP | ASSIGNED PA | Oct 30, 2013 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.233.0/24 | 256 | DVF_ | unknown | ASSIGNED PA | Oct 30, 2013 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.234.0/23 | 512 | DVF_ | unknown | ASSIGNED PA | Nov 25, 2020 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.236.0/24 | 256 | DVF_ | unknown | ASSIGNED PA | Nov 25, 2020 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.237.0/24 | 256 | DVF_ | unknown | ASSIGNED PA | Nov 25, 2020 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.238.0/24 | 256 | DVF_ | unknown | ASSIGNED PA | Nov 25, 2020 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.239.0/24 | 256 | DVF_ | unknown | ASSIGNED PA | Nov 25, 2020 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.240.0/24 | 256 | DVF_ | unknown | ASSIGNED PA | Nov 25, 2020 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.241.0/24 | 256 | DVF_ | unknown | ASSIGNED PA | Nov 25, 2020 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.242.0/24 | 256 | DVF_ | unknown | ASSIGNED PA | Nov 25, 2020 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.243.0/24 | 256 | DVF_ | unknown | ASSIGNED PA | Nov 25, 2020 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.244.0/24 | 256 | DVF_ | unknown | ASSIGNED PA | Nov 25, 2020 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.245.0/24 | 256 | DVF_ | unknown | ASSIGNED PA | Nov 25, 2020 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.246.0/23 | 512 | DVF_ | DVF Khabarovsk YOTA-mobile | ASSIGNED PA | Mar 5, 2015 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.248.0/22 | 1,024 | DVF_ | unknown | ASSIGNED PA | Nov 6, 2020 | abuse-mailbox@ via MF-DVF-T3306070 |
| └ 188.162.252.0/22 | 1,024 | DVF_ | unknown | ASSIGNED PA | Nov 25, 2020 | abuse-mailbox@ via MF-DVF-T3306070 |
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
65,536 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Mobile | 65,280 | >99% | 101 | |
| Internet provider | 256 | 0.39% | 1 |
Network & registry
Origin network
AS31133
RU
- Name
- PJSC MegaFon
- Type
- Internet provider
- Registered
- Mar 5, 2004
- Domain
- megafon.ru
- Website
- www.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
- Mar 2020
- Current origin since
- Mar 2020 · 6.7 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 188.162.0.0/16 | AS31133 | /16 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS31133 | RIPE | MEGAFON-RIPE-MNT | Mar 4, 2020 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 188.162.0.0/19 | AS47395 | RIPE | NSK SCARTEL network | MEGAFON-RIPE-MNT | Apr 7, 2020 |
| 188.162.32.0/19 | AS31133 | RIPE | Samara SCARTEL network | GDC-TR-COREIP | Jul 30, 2021 |
| 188.162.64.0/18 | AS47395 | RIPE | SPb SCARTEL network | SCARTEL-SPB-MNT | Oct 26, 2009 |
| 188.162.64.0/20 | AS47395 | RIPE | SCARTEL Novosibirsk | GDC-TR-COREIP | Nov 23, 2022 |
| 188.162.66.0/23 | AS47395 | RIPE | SPb Yota PAT Clients | SCARTEL-SPB-MNT | Oct 25, 2013 |
| 188.162.68.0/22 | AS47395 | RIPE | SPb SCARTEL network | SCARTEL-SPB-MNT | Sep 23, 2009 |
| 188.162.72.0/21 | AS47395 | RIPE | SPb SCARTEL network | GDC-TR-COREIP | Jul 9, 2021 |
| 188.162.80.0/20 | AS31133 | RIPE | MEGAFON-RIPE-MNT GDC-TR-COREIP | Apr 6, 2023 | |
| 188.162.86.0/24 | AS31133 | RIPE | GDC-TR-COREIP MEGAFON-AUTO-MNT | Nov 14, 2023 | |
| 188.162.96.0/19 | AS47395 | RIPE | MSK SCARTEL network | SCARTEL-MSK-MNT | Sep 18, 2009 |
| 188.162.128.0/18 | AS31133 | RIPE | MEGAFON-RIPE-MNT GDC-TR-COREIP | Nov 23, 2023 | |
| 188.162.158.0/24 | AS25159 | RIPE | MF-MSK-APN | GDC-TR-COREIP | Nov 23, 2023 |
| 188.162.192.0/20 | AS31133 | RIPE | GDC-TR-COREIP | Jul 30, 2021 | |
| 188.162.208.0/21 | AS47395 | RIPE | Ufa SCARTEL network | SCARTEL-SPB-MNT | Jul 20, 2009 |
Whois
Registration for this announcement
- Range
- 188.
162. 0. 0/ 16 - Netname
- RU-MEGAFON-20090520
- Registrant
- PJSC MegaFon
- Registrant country
- RU
- Organization
- PJSC MegaFon (ORG-OM1-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- May 20, 2009
- Updated
- Jul 3, 2023
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- May 20, 2009
- Status
- assigned
Report abuse
Abuse contact
- abuse-mailbox@
megafon. ru - Name
- MegaFon PJSC - Internet Service Network Operation Center
- Handle
- MFON-RIPE