This issue is now resolved and runs should be available again over the UI.

Update: we are rolling out a hotfix to get around the DNS resolution failures. Services are starting to recover.

We are seeing DNS issues with our upstream database provider which is preventing runs from loading in the UI or over the API. Core queueing operations are not impacted, but endpoints utilizing the REST API will fail to respond.