Well, Mikrotik’s block “159.148.147.0/24” was hijacked yesterday by AS19429.
https://stat.ripe.net/special/bgplay#bgplay_fetch.resource=159.148.147.196
Despite Mikrotik’s signed ROAs for the blocks, they are no good if we can’t validate them externally and feed into ROS, or get ROS to validate the routes internally.
Which is, in and of itself, kind of ironic… can’t update routers / complain in the forum about the route hijack, cause the route is hijacked.