AS31213
PJSC MegaFon
AS31213 is PJSC MegaFon (megafon.ru). It announces 76,032 IPv4 addresses in 37 prefixes, and 11 IPv6 prefixes.
Russia· RIPE· allocated 2004-03-23· isp
76,032
IPv4 addresses announced
37
IPv4 prefixes
11
IPv6 prefixes
100.00%
of its routes RPKI-valid
76,032
of its IPv4 geolocated
1
country
Where its space is
The IPv4 it announces that IP Geolocation places, by country. A /24 counts for the AS announcing most of it.
- Russia76,032 · 100.00%
Registry record
Its ASN Whois record, as the registry publishes it.
- handle
- MF-NWGSM-AS
- name
- PJSC MegaFon
- org
- ORG-OM1-RIPE
- org name
- PJSC MegaFon
- org address
- 41, Oruzheyniy lane, 127006, Moscow, RUSSIAN FEDERATION
- org country
- RU
- country
- RU
- source
- ripe
- status
- ASSIGNED
- created
- 2004-03-23
- updated
- 2018-09-04
- remarks
- North-West Branch of PJSC MegaFon Network / ------------- Uplinks ---------------------------------------- / Name: MCS-Povolzhie / Name: Peterstar / ------------- Private Peering ---------------------------------
- maintainer
- RIPE-NCC-END-MNT|MEGAFON-RIPE-MNT|MEGAFON-GNOC-MNT|MEGAFON-WEST-MNT|MNT-MF-NWGSM
- abuse name
- MegaFon PJSC - Internet Service Network Operation Center
- abuse email
- abuse-mailbox@megafon.ru
- abuse kind
- role
What the databases see
Addresses each address-keyed database holds in the IPv4 it announces, as a share of that space, with its largest providers. Counts overlap.
- VPN IP3470.46%
- Residential Proxy IP8,785geonode, onesproxy, geonix11.55%
- None here
- dataimpulse, floppydata, vibeproxies1.07%
- None here
- None here
- Hosting IP12,28816.16%
- None here
- Carrier IP63,744MegaFon83.84%
- None here
- SSH IP4880.64%
- SMTP IP200.03%
- 0.13%
IPv4 prefixes
Every IPv4 prefix BGP Route saw it announce. A prefix another AS also announces says so.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 37.28.160.0/21 | Russia | valid | 17 | 2026-10-02 |
| 37.28.168.0/21 | Russia | valid | 17 | 2026-10-02 |
| 37.29.48.0/21 | Russia | valid | 17 | 2026-10-02 |
| 37.29.56.0/21 | Russia | valid | 17 | 2026-10-02 |
| 37.29.64.0/22 | Russia | valid | 17 | 2026-10-02 |
| 37.29.68.0/23 | Russia | valid | 17 | 2026-10-02 |
| 37.29.70.0/24 | Russia | valid | 17 | 2026-10-02 |
| 37.29.71.0/24 | Russia | valid | 17 | 2026-10-02 |
| 78.25.96.0/21 | Russia | valid | 17 | 2026-10-02 |
| 78.25.104.0/22 | Russia | valid | 17 | 2026-10-02 |
| 78.25.108.0/22 | Russia | valid | 17 | 2026-10-02 |
| 78.25.120.0/22 | Russia | valid | 17 | 2026-10-02 |
| 83.149.0.0/21 | Russia | valid | 17 | 2026-10-02 |
| 85.26.128.0/20 | Russia | valid | 17 | 2026-10-02 |
| 85.26.208.0/22 | Russia | valid | 17 | 2026-10-02 |
| 85.26.212.0/22 | Russia | valid | 17 | 2026-10-02 |
| 85.26.216.0/22 | Russia | valid | 17 | 2026-10-02 |
| 85.26.220.0/22 | Russia | valid | 17 | 2026-10-02 |
| 85.26.248.0/22 | Russia | valid | 17 | 2026-10-02 |
| 85.26.252.0/22 | Russia | valid | 17 | 2026-10-02 |
| 94.25.208.0/22 | Russia | valid | 17 | 2026-10-02 |
| 94.25.216.0/21 | Russia | valid | 17 | 2026-10-02 |
| 94.25.224.0/21 | Russia | valid | 17 | 2026-10-02 |
| 94.25.228.0/23 | Russia | valid | 17 | 2026-10-02 |
| 94.25.232.0/21 | Russia | valid | 17 | 2026-10-02 |
| 109.188.128.0/17 | Russia | valid | 17 | 2026-10-02 |
| 128.204.74.0/24 | Russia | valid | 17 | 2026-10-02 |
| 128.204.75.0/24 | Russia | valid | 17 | 2026-10-02 |
| 178.178.244.0/22 | Russia | valid | 17 | 2026-10-02 |
| 178.178.248.0/23 | Russia | valid | 17 | 2026-10-02 |
| 188.162.64.0/23 | Russia | valid | 17 | 2026-10-02 |
| 188.170.64.0/24 | Russia | valid | 17 | 2026-10-02 |
| 188.170.66.0/24 | Russia | valid | 17 | 2026-10-02 |
| 188.170.67.0/24 | Russia | valid | 17 | 2026-10-02 |
| 188.170.72.0/21 | Russia | valid | 17 | 2026-10-02 |
| 188.170.80.0/21 | Russia | valid | 17 | 2026-10-02 |
| 188.170.92.0/22 | Russia | valid | 17 | 2026-10-02 |
IPv6 prefixes
Every IPv6 prefix BGP Route saw it announce.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 2a03:d000::/40 | Russia | valid | 20 | 2026-10-02 |
| 2a03:d000::/41 | Russia | valid | 20 | 2026-10-02 |
| 2a03:d000:80::/41 | Russia | valid | 20 | 2026-10-02 |
| 2a03:d000:100::/40 | Russia | valid | 20 | 2026-10-02 |
| 2a03:d000:100::/41 | Russia | valid | 20 | 2026-10-02 |
| 2a03:d000:180::/41 | Russia | valid | 20 | 2026-10-02 |
| 2a03:d000:200::/41 | Russia | valid | 20 | 2026-10-02 |
| 2a03:d000:280::/41 | Russia | valid | 20 | 2026-10-02 |
| 2a03:d000:301::/48 | Russia | valid | 20 | 2026-10-02 |
| 2a03:d000:302::/48 | Russia | valid | 20 | 2026-10-02 |
| 2a03:d000:400::/40 | Russia | valid | 20 | 2026-10-02 |
00 · Evaluate
Test the real build first.
An evaluation license puts a full current build in your hands — every row, every column, no sampling — so you can measure it against your own traffic before anyone talks about terms.
01 · License
Then license what you use.
Standard, for detection and decisions inside your own product and operations.
Redistribution, when the data ships onward inside what you sell — priced by scope, not by seat.
Annual terms, a named contact, and flexible payment terms — monthly, quarterly or yearly.