Cron run statuses have tbh always felt a bit flaky, but have unfortunately been completely broken since the outage. See the pictures for some examples.

This one has one execution allegedly running for 5 hours (it's not), yet the card shows no current execution: https://railway.com/project/56cafcfa-394c-46c9-a811-dc3207bad3dc/service/1b0c2bc3-2e9a-4d3b-9852-c9b3468a3022/schedule?groupId=be2427f6-4308-48fd-b5a2-991a2eb8cf18&environmentId=ec032274-ccb3-4372-907d-acc4f1ca967f

This one has two currently running ones according to the UI, one of them for over 5 hours, even though both only ran for a few minutes and finished hours ago: https://railway.com/project/56cafcfa-394c-46c9-a811-dc3207bad3dc/service/29f1876c-1230-4779-8d8b-265f7b71aaff/schedule?groupId=be2427f6-4308-48fd-b5a2-991a2eb8cf18&environmentId=ec032274-ccb3-4372-907d-acc4f1ca967f

It seems the system is still reliably triggering runs - as far as I can tell it's purely a representational issue.