bgpreport

Network · data from 2026-11-12

AS25159 SONICDUO

Registry name: SONICDUO-AS PJSC MegaFon, RU · PeeringDB

69IPv4 routes 100.0% RPKI valid · 100.0% with a route object
19IPv6 routes 94.7% RPKI valid · 94.7% with a route object
1RPKI invalid 1 origin · 0 maxLength
0No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
41Route objects not announced registered with origin AS25159, seen from no peer

Announced routes

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

2a13:9f00::/29 Invalid: origin Other origin only 64 10% 33
31.173.32.0/19 Valid RIR databaseRIPE 673 100% 67
31.173.72.0/21 Valid RIR databaseRIPE 673 100% 67
31.173.88.0/21 Valid RIR databaseRIPE 673 100% 67
62.64.0.0/20 Valid RIR databaseRIPE 673 100% 67
62.64.16.0/20 Valid RIR databaseRIPE 673 100% 67
78.25.112.0/22 Valid RIR databaseRIPE 673 100% 67
78.25.118.0/24 Valid RIR databaseRIPE 673 100% 67
78.25.119.0/24 Valid RIR databaseRIPE 673 100% 67
83.222.212.0/22 Valid RIR databaseRIPE 673 100% 67
83.222.216.0/21 Valid RIR databaseRIPE 673 100% 67
83.229.211.0/24 Valid RIR databaseRIPE 673 100% 67
85.26.144.0/20 Valid RIR databaseRIPE 673 100% 67
91.205.168.0/23 Valid RIR databaseRIPE 673 100% 67
91.205.170.0/23 Valid RIR databaseRIPE 673 100% 67
94.25.131.0/24 Valid RIR databaseRIPE 673 100% 67
94.25.144.0/20 Valid RIR databaseRIPE 673 100% 67
109.188.64.0/19 Valid RIR databaseRIPE 673 100% 67
109.188.96.0/21 Valid RIR databaseRIPE 673 100% 67
109.188.112.0/23 Valid RIR databaseRIPE 673 100% 67
109.188.114.0/24 Valid RIR databaseRIPE 673 100% 67
128.204.76.0/22 Valid RIR databaseRIPE 673 100% 67
128.204.76.0/23 Valid RIR databaseRIPE 673 100% 67
128.204.78.0/23 Valid RIR databaseRIPE 673 100% 67
130.49.216.0/24 Valid RIR databaseRIPE 673 100% 67
178.176.0.0/19 Valid RIR databaseRIPE 673 100% 67
178.176.32.0/21 Valid RIR databaseRIPE 673 100% 67
178.177.0.0/18 Valid RIR databaseRIPE 673 100% 67
178.178.198.0/23 Valid RIR databaseRIPE 673 100% 67
188.170.0.0/19 Valid RIR databaseRIPE 673 100% 67
193.201.228.0/22 Valid RIR databaseRIPE 673 100% 67
195.16.96.0/19 Valid RIR databaseRIPE 673 100% 67
195.16.110.0/23 Valid RIR databaseRIPE 673 100% 67
195.230.70.0/23 Valid RIR databaseRIPE 673 100% 67
195.230.91.0/24 Valid RIR databaseRIPE 673 100% 67
195.230.92.0/24 Valid RIR databaseRIPE 673 100% 67
212.69.96.0/19 Valid RIR databaseRIPE 673 100% 67
212.69.106.0/24 Valid RIR databaseRIPE 673 100% 67
212.69.113.0/24 Valid RIR databaseRIPE 673 100% 67
212.69.114.0/24 Valid RIR databaseRIPE 673 100% 67
212.69.125.0/24 Valid RIR databaseRIPE 673 100% 67
213.243.109.0/24 Valid RIR databaseRIPE 673 100% 67
213.243.116.0/24 Valid RIR databaseRIPE 673 100% 67
31.173.0.0/21 Valid RIR databaseRIPE 672 100% 67
31.173.8.0/21 Valid RIR databaseRIPE 672 100% 67
31.173.16.0/21 Valid RIR databaseRIPE 672 100% 67
31.173.24.0/21 Valid RIR databaseRIPE 672 100% 67
31.173.64.0/21 Valid RIR databaseRIPE 672 100% 67
31.173.80.0/21 Valid RIR databaseRIPE 672 100% 67
37.28.176.0/21 Valid RIR databaseRIPE 672 100% 67
37.29.32.0/21 Valid RIR databaseRIPE 672 100% 67
46.229.128.0/22 Valid RIR databaseRIPE 672 100% 67
94.25.160.0/24 Valid RIR databaseRIPE 672 100% 67
94.25.164.0/24 Valid RIR databaseRIPE 672 100% 67
94.25.168.0/22 Valid RIR databaseRIPE 672 100% 67
94.25.172.0/22 Valid RIR databaseRIPE 672 100% 67
94.25.176.0/21 Valid RIR databaseRIPE 672 100% 67
94.25.184.0/21 Valid RIR databaseRIPE 672 100% 67
109.188.124.0/24 Valid RIR databaseRIPE 672 100% 67
109.188.125.0/24 Valid RIR databaseRIPE 672 100% 67
178.176.40.0/21 Valid RIR databaseRIPE 672 100% 67
178.176.52.0/22 Valid RIR databaseRIPE 672 100% 67
178.176.72.0/21 Valid RIR databaseRIPE 672 100% 67
178.176.92.0/22 Valid RIR databaseRIPE 672 100% 67
178.178.192.0/22 Valid RIR databaseRIPE 672 100% 67
178.178.216.0/21 Valid RIR databaseRIPE 672 100% 67
178.178.235.0/24 Valid RIR databaseRIPE 672 100% 67
178.178.236.0/24 Valid RIR databaseRIPE 672 100% 67
188.170.32.0/21 Valid RIR databaseRIPE 672 100% 67
188.170.40.0/21 Valid RIR databaseRIPE 672 100% 67
2a03:d000:4000::/36 Valid RIR databaseRIPE 636 100% 69
2a03:d000:4100::/40 Valid RIR databaseRIPE 636 100% 69
2a03:d000:4200::/40 Valid RIR databaseRIPE 636 100% 69
2a03:d000:4300::/40 Valid RIR databaseRIPE 636 100% 69
2a03:d000:4400::/40 Valid RIR databaseRIPE 636 100% 69
2a03:d004::/40 Valid RIR databaseRIPE 636 100% 69
2a09:17c0:1312::/48 Valid RIR databaseRIPE 636 100% 69
2a09:17c0:fbad::/48 Valid RIR databaseRIPE 636 100% 69
2a0e:f602::/32 Valid RIR databaseRIPE 636 100% 69
2a0f:1586::/32 Valid RIR databaseRIPE 636 100% 69
2a0f:2d83::/32 Valid RIR databaseRIPE 636 100% 69
2a0f:3d86:1::/48 Valid RIR databaseRIPE 636 100% 69
2a12:ecc5::/32 Valid RIR databaseRIPE 636 100% 69
2a13:18c0:100::/48 Valid RIR databaseRIPE 636 100% 69
2a13:93c1::/32 Valid RIR databaseRIPE 636 100% 69
2a07:7880::/29 Valid RIR databaseRIPE 635 100% 69
2a0e:1a86::/32 Valid RIR databaseRIPE 635 100% 69
2a12:5e00::/29 Valid RIR databaseRIPE 635 100% 69

AS-SET

AS25159's PeeringDB record names no 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 43 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced41
ChangePrefix or setDetailFull-table peers
ROA: origin2a13:9f00::/29ROAs covering it name AS41095, not AS25159. If AS25159 should announce it, add a ROA for AS25159.64 of 636
Route object: none2a13:9f00::/29Route objects for it name AS41095. Add a route object with origin AS25159 in the RIR database for the space.64 of 636

Route objects not announced

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

31.173.60.0/24RIPEValid
78.25.116.0/23RIPEValid
83.149.8.0/23RIPEInvalid: origin
83.149.11.0/24RIPEInvalid: origin
83.229.185.0/24RIPEInvalid: origin
83.229.248.0/22RIPEInvalid: origin
83.229.252.0/23RIPEInvalid: origin
91.205.171.0/24RIPEInvalid: maxLength
94.25.132.0/24RIPEInvalid: origin
94.25.133.0/24RIPEInvalid: origin
94.25.134.0/24RIPEInvalid: origin
94.25.144.0/21RIPEInvalid: maxLength
94.25.152.0/21RIPEInvalid: maxLength
94.25.168.0/21RIPEInvalid: origin
94.25.170.0/24RIPEInvalid: maxLength
94.25.171.0/24RIPEInvalid: maxLength
94.25.173.0/24RIPEInvalid: maxLength
94.25.174.0/24RIPEInvalid: maxLength
94.25.175.0/24RIPEInvalid: maxLength
94.25.176.0/20RIPEInvalid: origin
109.188.64.0/21RIPEInvalid: maxLength
109.188.72.0/21RIPEInvalid: maxLength
109.188.80.0/21RIPEInvalid: maxLength
109.188.88.0/21RIPEInvalid: maxLength
109.188.112.0/24RIPEInvalid: maxLength
109.188.113.0/24RIPEInvalid: maxLength
109.188.120.0/24RIPEInvalid: origin
109.188.124.0/22RIPEInvalid: origin
178.176.49.0/24RIPEInvalid: origin
178.176.64.0/19RIPEInvalid: origin
178.177.3.0/24RIPEValid
178.178.204.0/24RIPEValid
178.178.205.0/24RIPEValid
188.162.158.0/24RIPEInvalid: origin
188.170.24.0/22RIPEInvalid: maxLength
188.170.24.0/23RIPEValid
188.170.25.0/24RIPEValid
195.16.114.0/23RIPEValid
2a10:4702::/32RIPEValid
2a10:4703::/32RIPEValid
2a13:ac82::/32RIPEValid

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.