bgpreport

Network · data from 2026-11-12

AS57487 MIXTELECOM-AS Advanced Solutions LLC

Registry name: MIXTELECOM-AS Advanced Solutions LLC, RU · not in PeeringDB

8IPv4 routes 0.0% RPKI valid · 100.0% with a route object
5IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
13No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS57487, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS57487, 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.90.212.0/22 No ROA RIR databaseRIPE 673 100% 66
91.228.238.0/23 No ROA RIR databaseRIPE 673 100% 66
91.232.132.0/22 No ROA RIR databaseRIPE 673 100% 66
92.62.112.0/22 No ROA RIR databaseRIPE 673 100% 66
93.88.76.0/22 No ROA RIR databaseRIPE 673 100% 66
185.30.96.0/23 No ROA RIR databaseRIPE 673 100% 66
185.30.98.0/23 No ROA RIR databaseRIPE 673 100% 66
185.48.16.0/22 No ROA RIR databaseRIPE 673 100% 66
2a04:3600::/29 No ROA RIR databaseRIPE 634 100% 69
2a11:6505::/32 No ROA RIR databaseRIPE 633 100% 67
2a11:8445::/32 No ROA RIR databaseRIPE 633 100% 67
2a11:cd05::/32 No ROA RIR databaseRIPE 633 100% 67
2a12:1243::/32 No ROA RIR databaseRIPE 633 100% 67

AS-SET

AS57487 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: none13
ChangePrefix or setDetailFull-table peers
ROA: none91.90.212.0/22No ROA covers it. Add a ROA for AS57487, maxLength 22.673 of 673
ROA: none91.228.238.0/23No ROA covers it. Add a ROA for AS57487, maxLength 23.673 of 673
ROA: none91.232.132.0/22No ROA covers it. Add a ROA for AS57487, maxLength 22.673 of 673
ROA: none92.62.112.0/22No ROA covers it. Add a ROA for AS57487, maxLength 22.673 of 673
ROA: none93.88.76.0/22No ROA covers it. Add a ROA for AS57487, maxLength 22.673 of 673
ROA: none185.30.96.0/23No ROA covers it. Add a ROA for AS57487, maxLength 23.673 of 673
ROA: none185.30.98.0/23No ROA covers it. Add a ROA for AS57487, maxLength 23.673 of 673
ROA: none185.48.16.0/22No ROA covers it. Add a ROA for AS57487, maxLength 22.673 of 673
ROA: none2a04:3600::/29No ROA covers it. Add a ROA for AS57487, maxLength 29.634 of 636
ROA: none2a11:6505::/32No ROA covers it. Add a ROA for AS57487, maxLength 32.633 of 636
ROA: none2a11:8445::/32No ROA covers it. Add a ROA for AS57487, maxLength 32.633 of 636
ROA: none2a11:cd05::/32No ROA covers it. Add a ROA for AS57487, maxLength 32.633 of 636
ROA: none2a12:1243::/32No ROA covers it. Add a ROA for AS57487, maxLength 32.633 of 636

Route objects not announced

Every route object with origin AS57487 is announced.

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.