Network · data from 2026-11-12

AS31208 MF-CENTER-AS PJSC MegaFon

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

52IPv4 routes 98.1% RPKI valid · 98.1% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

1No ROA 1 with no route object for this origin

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

11Route objects not announced registered with origin AS31208, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS31208, 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.


91.236.10.0/23	No ROA	RIR databaseRIPE	673 100%	66
46.229.136.0/22	Valid	None	673 100%	66
83.149.40.0/24	Valid	RIR databaseRIPE	673 100%	66
83.149.42.0/23	Valid	RIR databaseRIPE	673 100%	66
83.169.208.0/24	Valid	RIR databaseRIPE	673 100%	66
83.169.211.0/24	Valid	RIR databaseRIPE	673 100%	66
83.169.212.0/24	Valid	RIR databaseRIPE	673 100%	66
83.169.213.0/24	Valid	RIR databaseRIPE	673 100%	66
83.169.214.0/24	Valid	RIR databaseRIPE	673 100%	66
178.176.56.0/24	Valid	RIR databaseRIPE	673 100%	66
178.176.57.0/24	Valid	RIR databaseRIPE	673 100%	66
178.176.58.0/24	Valid	RIR databaseRIPE	673 100%	66
178.176.59.0/24	Valid	RIR databaseRIPE	673 100%	66
178.176.60.0/24	Valid	RIR databaseRIPE	673 100%	66
178.176.61.0/24	Valid	RIR databaseRIPE	673 100%	66
178.176.62.0/24	Valid	RIR databaseRIPE	673 100%	66
178.176.63.0/24	Valid	RIR databaseRIPE	673 100%	66
178.178.128.0/24	Valid	RIR databaseRIPE	673 100%	66
178.178.129.0/24	Valid	RIR databaseRIPE	673 100%	66
178.178.130.0/24	Valid	RIR databaseRIPE	673 100%	66
178.178.131.0/24	Valid	RIR databaseRIPE	673 100%	66
178.178.132.0/24	Valid	RIR databaseRIPE	673 100%	66
178.178.133.0/24	Valid	RIR databaseRIPE	673 100%	66
178.178.134.0/24	Valid	RIR databaseRIPE	673 100%	66
178.178.135.0/24	Valid	RIR databaseRIPE	673 100%	66
178.178.136.0/24	Valid	RIR databaseRIPE	673 100%	66
178.178.137.0/24	Valid	RIR databaseRIPE	673 100%	66
178.178.142.0/24	Valid	RIR databaseRIPE	673 100%	66
178.178.143.0/24	Valid	RIR databaseRIPE	673 100%	66
178.178.144.0/24	Valid	RIR databaseRIPE	673 100%	66
178.178.145.0/24	Valid	RIR databaseRIPE	673 100%	66
188.170.48.0/24	Valid	RIR databaseRIPE	673 100%	66
188.170.49.0/24	Valid	RIR databaseRIPE	673 100%	66
188.170.50.0/24	Valid	RIR databaseRIPE	673 100%	66
188.170.52.0/24	Valid	RIR databaseRIPE	673 100%	66
188.170.53.0/24	Valid	RIR databaseRIPE	673 100%	66
188.170.56.0/24	Valid	RIR databaseRIPE	673 100%	66
188.170.57.0/24	Valid	RIR databaseRIPE	673 100%	66
188.170.59.0/24	Valid	RIR databaseRIPE	673 100%	66
188.170.60.0/24	Valid	RIR databaseRIPE	673 100%	66
188.170.61.0/24	Valid	RIR databaseRIPE	673 100%	66
188.170.62.0/24	Valid	RIR databaseRIPE	673 100%	66
188.170.63.0/24	Valid	RIR databaseRIPE	673 100%	66
37.28.184.0/24	Valid	RIR databaseRIPE	672 100%	66
37.28.186.0/24	Valid	RIR databaseRIPE	672 100%	66
37.29.72.0/24	Valid	RIR databaseRIPE	672 100%	66
37.29.74.0/24	Valid	RIR databaseRIPE	672 100%	66
37.29.75.0/24	Valid	RIR databaseRIPE	672 100%	66
46.229.140.0/24	Valid	RIR databaseRIPE	672 100%	66
46.229.141.0/24	Valid	RIR databaseRIPE	672 100%	66
46.229.142.0/24	Valid	RIR databaseRIPE	672 100%	66
46.229.143.0/24	Valid	RIR databaseRIPE	672 100%	66
2a03:d000:3000::/36	Valid	RIR databaseRIPE	636 100%	69

AS-SET

AS31208 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 13 are in fix.csv.

ROA: none1
Route object: none1
Route object: not announced11

Change	Prefix or set	Detail	Full-table peers
ROA: none	91.236.10.0/23	No ROA covers it. Add a ROA for AS31208, maxLength 23.	673 of 673
Route object: none	46.229.136.0/22	No route object for it. Add a route object with origin AS31208 in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

91.236.10.0/23

No ROA covers it. Add a ROA for AS31208, maxLength 23.

673 of 673

Route object: none

46.229.136.0/22

No route object for it. Add a route object with origin AS31208 in the RIR database for the space.

673 of 673

Route objects not announced

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


37.28.184.0/22	RIPE	Invalid: origin
37.29.72.0/22	RIPE	Invalid: origin
83.149.40.0/22	RIPE	Invalid: origin
83.149.42.0/24	RIPE	Invalid: maxLength
83.149.43.0/24	RIPE	Invalid: maxLength
83.149.44.0/22	RIPE	Invalid: origin
83.149.46.0/23	RIPE	Invalid: origin
91.205.170.0/24	RIPE	Invalid: origin
178.176.230.0/23	RIPE	Invalid: origin
178.178.84.0/22	RIPE	Invalid: origin
2a03:d000:3301::/48	RIPE	Invalid: maxLength

37.28.184.0/22

RIPE

Invalid: origin

37.29.72.0/22

RIPE

Invalid: origin

83.149.40.0/22

RIPE

Invalid: origin

83.149.42.0/24

RIPE

Invalid: maxLength

83.149.43.0/24

RIPE

Invalid: maxLength

83.149.44.0/22

RIPE

Invalid: origin

83.149.46.0/23

RIPE

Invalid: origin

91.205.170.0/24

RIPE

Invalid: origin

178.176.230.0/23

RIPE

Invalid: origin

178.178.84.0/22

RIPE

Invalid: origin

2a03:d000:3301::/48

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.