We have RPKI setup to filter BGP routes received from providers, however they do not seem to be getting filtered.

We have inbound filters setup
rpki-verify RPKI
if (rpki invalid) { reject } else { accept }
under the same chain name as other working inbound filters and are on the latest OS.

to check to see if the router is working and able to connect to the Validator

/routing/rpki> /routing/rpki/ rpki-check group=RPKI prefix=70.132.18.0/24 origin-as=16509
valid

/routing/rpki> /routing/rpki/ rpki-check group=RPKI prefix=2a05:dfc7:/48 origin-as=205531
invalid

rpki-verify just adds the RPKI status to the prefix, you can see whether status have been addd by looking at parameters in /routing/route/print detail

To actually reject or accept prefix you have to match the rpki status and add apropriate action, see example here:
https://help.mikrotik.com/docs/display/ROS/RPKI

the issue is, none of the routes are getting marked

rpki-verify RPKI is not working and must be a bug in the firmware. Can someone please check?

rpki-verify RPKI is not working and must be a bug in the firmware. Can someone please check?

https://mikrotik.com/support

I already done this but no response

I'm using RPKI since ROS 7.xx. Never had a problem with that. One session is pointing to Routinator and the second one to Fort validator. Pay attention to the filtering order: for example you should filter first rfc5735 then RPKI with reject only, then all other filters with accept rules. Avoid using "if else accept" unless in the last filter rule.

In your example you are using "else" in the RPKI validation. This means that all the filter that follows are useless. If you have another "if else accept" before the RPKI validation the RPKI filtering is useless, because the routes are being accepted before the validation.