Resolved. The Juryo platform is serving normally again.

Timeline (UTC): errors began at 10:21 when our database provider's connection layer stopped resolving the route to our database. That fault cleared at around 10:55, but application servers that had started during the window held on to the failed connection state and kept returning errors. We replaced those servers and service was restored at 11:11.

Your data was never at risk. The database itself stayed healthy and online for the entire incident, and there has been no data loss or corruption.

If you were signed out or saw an error page during this window, simply reload and sign in again. Background jobs and webhooks received during the window are retried automatically. Please contact support if you notice anything still missing.

We are sorry for the disruption. We are making two changes as a result: our application servers will no longer hold a failed database connection for their lifetime, and we are adding alerting on error rates so that partial outages like this one are detected immediately rather than only when the service is fully unreachable.

We are aware that users are seeing errors when loading the Juryo platform, beginning at 10:21 UTC.

The cause is a connectivity fault at our database provider's connection layer. That fault has now cleared, but a number of our application servers cached the failed connection state at startup and continue to return errors. We are recycling those servers now and expect full service to be restored shortly.

Your data is safe. The database itself remained healthy and online throughout, and no data has been lost or corrupted.

Some background jobs and incoming webhooks during this window may have been delayed or retried. We will confirm once service is fully restored.

Juryo Platform (platform.juryo.ai) went down.