bgpreport

Network · data from 2026-11-12

AS154132 MUI-AS-AP - M/S UMARA INTERNATIONAL

Registry name: MUI-AS-AP - M/S UMARA INTERNATIONAL, BD · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS154132, 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.57.167.0/24 Invalid: origin Other origin only 2 0%low visibility 2
68.164.24.0/24 Invalid: origin None 2 0%low visibility 1
68.164.68.0/24 Invalid: origin Other origin only 2 0%low visibility 1
82.29.45.0/24 Invalid: origin None 2 0%low visibility 2
162.141.152.0/24 Invalid: origin Other origin only 2 0%low visibility 2
31.57.0.0/24 Invalid: origin Other origin only 1 0%low visibility 1
109.66.14.0/24 Invalid: origin Other origin only 1 0%low visibility 1
167.148.81.0/24 Invalid: origin Other origin only 1 0%low visibility 1
169.128.137.0/24 Valid None 125 19% 39
68.166.199.0/24 Valid RIR databaseARIN, RADB 672 100% 67
177.201.202.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
187.55.8.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
187.55.38.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
187.55.46.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
187.55.51.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
94.118.212.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
94.118.232.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
162.141.24.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
162.141.168.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
179.253.52.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
179.253.56.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
187.55.39.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
189.30.104.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
189.31.18.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
162.141.144.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
179.69.109.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
167.148.64.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
189.12.180.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
200.141.58.0/24 Valid RIR databaseRADB, RIPE 666 99% 67
94.118.200.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1
200.180.172.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 1

AS-SET

AS154132 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 26 are in fix.csv.

  • ROA: origin8
  • Route object: none9
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: origin31.57.167.0/24ROAs covering it name AS834, not AS154132. If AS154132 should announce it, add a ROA for AS154132.2 of 673
Route object: none31.57.167.0/24Route objects for it name AS834. Add a route object with origin AS154132 in the RIR database for the space.2 of 673
ROA: origin68.164.24.0/24ROAs covering it name AS834, not AS154132. If AS154132 should announce it, add a ROA for AS154132.2 of 673
Route object: none68.164.24.0/24No route object for it. Add a route object with origin AS154132 in the RIR database for the space.2 of 673
ROA: origin68.164.68.0/24ROAs covering it name AS834, not AS154132. If AS154132 should announce it, add a ROA for AS154132.2 of 673
Route object: none68.164.68.0/24Route objects for it name AS834. Add a route object with origin AS154132 in the RIR database for the space.2 of 673
ROA: origin82.29.45.0/24ROAs covering it name AS834, not AS154132. If AS154132 should announce it, add a ROA for AS154132.2 of 673
Route object: none82.29.45.0/24No route object for it. Add a route object with origin AS154132 in the RIR database for the space.2 of 673
ROA: origin162.141.152.0/24ROAs covering it name AS834, not AS154132. If AS154132 should announce it, add a ROA for AS154132.2 of 673
Route object: none162.141.152.0/24Route objects for it name AS834. Add a route object with origin AS154132 in the RIR database for the space.2 of 673
ROA: origin31.57.0.0/24ROAs covering it name AS213516, not AS154132. If AS154132 should announce it, add a ROA for AS154132.1 of 673
Route object: none31.57.0.0/24Route objects for it name AS213516. Add a route object with origin AS154132 in the RIR database for the space.1 of 673
ROA: origin109.66.14.0/24ROAs covering it name AS834, not AS154132. If AS154132 should announce it, add a ROA for AS154132.1 of 673
Route object: none109.66.14.0/24Route objects for it name AS834. Add a route object with origin AS154132 in the RIR database for the space.1 of 673
ROA: origin167.148.81.0/24ROAs covering it name AS834, not AS154132. If AS154132 should announce it, add a ROA for AS154132.1 of 673
Route object: none167.148.81.0/24Route objects for it name AS834. Add a route object with origin AS154132 in the RIR database for the space.1 of 673
Route object: none169.128.137.0/24No route object for it. Add a route object with origin AS154132 in the RIR database for the space.125 of 673

Route objects not announced

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

13.141.12.0/24RADB, RIPEValid
13.141.14.0/24RADB, RIPEValid
90.96.125.0/24RADB, RIPEValid
90.96.126.0/24RADB, RIPEValid
179.253.44.0/24RADB, RIPEValid
179.254.212.0/24RADB, RIPEValid
187.55.9.0/24RADB, RIPEValid
189.30.126.0/24RADB, RIPEValid
200.180.168.0/24RADB, RIPEValid

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.