bgpreport

Network · data from 2026-11-12

AS31224 MF-UGSM-AS PJSC MegaFon

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

34IPv4 routes 100.0% RPKI valid · 100.0% with a route object
6IPv6 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
11Route objects not announced registered with origin AS31224, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS31224, 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.
31.173.96.0/24 Valid RIR databaseRIPE 673 100% 66
31.173.99.0/24 Valid RIR databaseRIPE 673 100% 66
31.173.100.0/24 Valid RIR databaseRIPE 673 100% 66
31.173.101.0/24 Valid RIR databaseRIPE 673 100% 66
31.173.103.0/24 Valid RIR databaseRIPE 673 100% 66
31.173.120.0/24 Valid RIR databaseRIPE 673 100% 66
31.173.121.0/24 Valid RIR databaseRIPE 673 100% 66
83.149.32.0/22 Valid RIR databaseRIPE 673 100% 66
83.149.34.0/24 Valid RIR databaseRIPE 673 100% 66
83.149.36.0/22 Valid RIR databaseRIPE 673 100% 66
83.149.37.0/24 Valid RIR databaseRIPE 673 100% 66
83.149.39.0/24 Valid RIR databaseRIPE 673 100% 66
83.169.216.0/24 Valid RIR databaseRIPE 673 100% 66
128.204.68.0/24 Valid RIR databaseRIPE 673 100% 66
128.204.69.0/24 Valid RIR databaseRIPE 673 100% 66
178.176.112.0/24 Valid RIR databaseRIPE 673 100% 66
178.176.113.0/24 Valid RIR databaseRIPE 673 100% 66
178.178.88.0/22 Valid RIR databaseRIPE 673 100% 66
178.178.92.0/22 Valid RIR databaseRIPE 673 100% 66
31.173.97.0/24 Valid RIR databaseRIPE 671 100% 66
31.173.102.0/24 Valid RIR databaseRIPE 671 100% 66
31.173.122.0/24 Valid RIR databaseRIPE 671 100% 66
31.173.123.0/24 Valid RIR databaseRIPE 671 100% 66
31.173.124.0/24 Valid RIR databaseRIPE 671 100% 66
31.173.125.0/24 Valid RIR databaseRIPE 671 100% 66
31.173.126.0/24 Valid RIR databaseRIPE 671 100% 66
31.173.127.0/24 Valid RIR databaseRIPE 671 100% 66
37.29.44.0/22 Valid RIR databaseRIPE 671 100% 66
46.229.132.0/22 Valid RIR databaseRIPE 671 100% 66
78.25.88.0/22 Valid RIR databaseRIPE 671 100% 66
80.253.8.0/24 Valid RIR databaseRIPE 671 100% 66
80.253.9.0/24 Valid RIR databaseRIPE 671 100% 66
85.26.192.0/22 Valid RIR databaseRIPE 671 100% 66
178.176.104.0/21 Valid RIR databaseRIPE 671 100% 66
2a03:d000:5000::/41 Valid RIR databaseRIPE 636 100% 69
2a03:d000:5080::/41 Valid RIR databaseRIPE 636 100% 69
2a03:d000:5100::/41 Valid RIR databaseRIPE 636 100% 69
2a03:d000:5180::/41 Valid RIR databaseRIPE 636 100% 69
2a03:d000:5301::/48 Valid RIR databaseRIPE 636 100% 69
2a03:d000:5302::/48 Valid RIR databaseRIPE 636 100% 69

AS-SET

AS31224 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 11 are in fix.csv.

  • Route object: not announced11

Route objects not announced

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

31.173.100.0/23RIPEValid
37.29.47.0/24RIPEInvalid: maxLength
178.178.229.0/24RIPEValid
178.178.230.0/24RIPEValid
212.48.147.0/24RIPEInvalid: origin
2a03:d000:5000::/40RIPEValid
2a03:d000:5100::/40RIPEValid
2a03:d000:5200::/41RIPEValid
2a03:d000:5270::/44RIPEValid
2a03:d000:5280::/41RIPEValid
2a03:d000:52f0::/44RIPEValid

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.