Resolved after 22 minutes, affecting section-333593 (Juryo Platform (platform.juryo.ai)), on September 22, 2026.
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.
Affected components
Update timeline
- investigating Sep 22, 2026, 10:50 AM UTC
Juryo Platform (platform.juryo.ai) went down.
- resolved Sep 22, 2026, 11:13 AM UTC
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.
Your product runs on more than Juryo
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services