Network · data from 2026-11-12

AS31213 MF-NWGSM-AS PJSC MegaFon

Registry name: MF-NWGSM-AS PJSC MegaFon, RU · not in PeeringDB

37IPv4 routes 100.0% RPKI valid · 100.0% with a route object

11IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

25Route objects not announced registered with origin AS31213, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS31213, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


37.28.160.0/21	Valid	RIR databaseRIPE	673 100%	66
37.28.168.0/21	Valid	RIR databaseRIPE	673 100%	66
37.29.48.0/21	Valid	RIR databaseRIPE	673 100%	66
37.29.56.0/21	Valid	RIR databaseRIPE	673 100%	66
37.29.64.0/22	Valid	RIR databaseRIPE	673 100%	66
37.29.68.0/23	Valid	RIR databaseRIPE	673 100%	66
78.25.96.0/21	Valid	RIR databaseRIPE	673 100%	66
78.25.104.0/22	Valid	RIR databaseRIPE	673 100%	66
78.25.108.0/22	Valid	RIR databaseRIPE	673 100%	66
78.25.120.0/22	Valid	RIR databaseRIPE	673 100%	66
83.149.0.0/21	Valid	RIR databaseRIPE	673 100%	66
85.26.128.0/20	Valid	RIR databaseRIPE	673 100%	66
85.26.208.0/22	Valid	RIR databaseRIPE	673 100%	66
85.26.212.0/22	Valid	RIR databaseRIPE	673 100%	66
85.26.216.0/22	Valid	RIR databaseRIPE	673 100%	66
85.26.220.0/22	Valid	RIR databaseRIPE	673 100%	66
85.26.248.0/22	Valid	RIR databaseRIPE	673 100%	66
85.26.252.0/22	Valid	RIR databaseRIPE	673 100%	66
94.25.208.0/22	Valid	RIR databaseRIPE	673 100%	66
94.25.216.0/21	Valid	RIR databaseRIPE	673 100%	66
94.25.224.0/21	Valid	RIR databaseRIPE	673 100%	66
94.25.228.0/23	Valid	RIR databaseRIPE	673 100%	66
94.25.232.0/21	Valid	RIR databaseRIPE	673 100%	66
109.188.128.0/17	Valid	RIR databaseRIPE	673 100%	66
128.204.74.0/24	Valid	RIR databaseRIPE	673 100%	66
128.204.75.0/24	Valid	RIR databaseRIPE	673 100%	66
178.178.244.0/22	Valid	RIR databaseRIPE	673 100%	66
178.178.248.0/23	Valid	RIR databaseRIPE	673 100%	66
188.162.64.0/23	Valid	RIR databaseRIPE	673 100%	66
188.170.64.0/24	Valid	RIR databaseRIPE	673 100%	66
188.170.66.0/24	Valid	RIR databaseRIPE	673 100%	66
188.170.67.0/24	Valid	RIR databaseRIPE	673 100%	66
188.170.72.0/21	Valid	RIR databaseRIPE	673 100%	66
188.170.80.0/21	Valid	RIR databaseRIPE	673 100%	66
188.170.92.0/22	Valid	RIR databaseRIPE	673 100%	66
37.29.70.0/24	Valid	RIR databaseRIPE	672 100%	66
37.29.71.0/24	Valid	RIR databaseRIPE	672 100%	66
2a03:d000::/40	Valid	RIR databaseRIPE	636 100%	69
2a03:d000::/41	Valid	RIR databaseRIPE	636 100%	69
2a03:d000:80::/41	Valid	RIR databaseRIPE	636 100%	69
2a03:d000:100::/40	Valid	RIR databaseRIPE	636 100%	69
2a03:d000:100::/41	Valid	RIR databaseRIPE	636 100%	69
2a03:d000:180::/41	Valid	RIR databaseRIPE	636 100%	69
2a03:d000:200::/41	Valid	RIR databaseRIPE	636 100%	69
2a03:d000:280::/41	Valid	RIR databaseRIPE	636 100%	69
2a03:d000:301::/48	Valid	RIR databaseRIPE	636 100%	69
2a03:d000:302::/48	Valid	RIR databaseRIPE	636 100%	69
2a03:d000:400::/40	Valid	RIR databaseRIPE	636 100%	69

AS-SET

AS31213 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 25 are in fix.csv.

Route object: not announced25

Route objects not announced

Route objects with origin AS31213 whose prefix no peer sees AS31213 announce. Many are kept on purpose (backup routes, space announced only in some places).


83.149.4.0/22	RIPE	Invalid: maxLength
94.25.212.0/22	RIPE	Invalid: origin
94.25.248.0/21	RIPE	Invalid: origin
176.106.130.0/23	RIPE	Invalid: origin
176.106.130.0/24	RIPE	Valid
176.106.131.0/24	RIPE	Valid
178.178.224.0/24	RIPE	Valid
178.178.225.0/24	RIPE	Valid
178.178.226.0/24	RIPE	Valid
178.178.227.0/24	RIPE	Valid
188.170.64.0/21	RIPE	Invalid: origin
188.170.65.0/24	RIPE	Valid
188.170.68.0/24	RIPE	Valid
188.170.72.0/22	RIPE	Invalid: maxLength
188.170.76.0/22	RIPE	Invalid: maxLength
188.170.80.0/22	RIPE	Invalid: maxLength
188.170.80.0/23	RIPE	Invalid: maxLength
188.170.82.0/23	RIPE	Invalid: maxLength
188.170.84.0/22	RIPE	Invalid: maxLength
188.170.88.0/22	RIPE	Invalid: origin
2a03:d000:70::/45	RIPE	Invalid: maxLength
2a03:d000:170::/46	RIPE	Invalid: maxLength
2a03:d000:1f8::/46	RIPE	Invalid: maxLength
2a03:d000:270::/45	RIPE	Invalid: maxLength
2a03:d000:2f8::/46	RIPE	Invalid: maxLength

83.149.4.0/22

RIPE

Invalid: maxLength

94.25.212.0/22

RIPE

Invalid: origin

94.25.248.0/21

RIPE

Invalid: origin

176.106.130.0/23

RIPE

Invalid: origin

176.106.130.0/24

RIPE

Valid

176.106.131.0/24

RIPE

Valid

178.178.224.0/24

RIPE

Valid

178.178.225.0/24

RIPE

Valid

178.178.226.0/24

RIPE

Valid

178.178.227.0/24

RIPE

Valid

188.170.64.0/21

RIPE

Invalid: origin

188.170.65.0/24

RIPE

Valid

188.170.68.0/24

RIPE

Valid

188.170.72.0/22

RIPE

Invalid: maxLength

188.170.76.0/22

RIPE

Invalid: maxLength

188.170.80.0/22

RIPE

Invalid: maxLength

188.170.80.0/23

RIPE

Invalid: maxLength

188.170.82.0/23

RIPE

Invalid: maxLength

188.170.84.0/22

RIPE

Invalid: maxLength

188.170.88.0/22

RIPE

Invalid: origin

2a03:d000:70::/45

RIPE

Invalid: maxLength

2a03:d000:170::/46

RIPE

Invalid: maxLength

2a03:d000:1f8::/46

RIPE

Invalid: maxLength

2a03:d000:270::/45

RIPE

Invalid: maxLength

2a03:d000:2f8::/46

RIPE

Invalid: maxLength

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.