Previous incidents

We have identified the issue which was due to a Linux verison upgrade on our nodes. We've reverted this, but some runs may be stuck or failed. You can retrigger a new one by pushing a new commit or merging main into your PR.

We have identified the cause of the issue which is excessive load and scaled up our backend accordingly.

Stage 2 of annual scheduled maintenance completed successfully. Meticulous is back up.

This is now resolved, the issue was a misconfigured network policy. Some test runs have been automatically restarted. If your run was not restarted you can restart it by pushing a new commit to your PR.