Investigation service unavailable
ResolvedWorkbench, Evidence processing, Evidence uploads, Reports and exports
Workaround: Public synthetic demo cases and sample reports remain accessible. Do not submit customer incident evidence through the pilot inquiry.
- 11 Oct 2026, 02:14 UTCIdentifiedThe hosting provider recorded the application API, analysis worker, report renderer and scheduled services as suspended. This timestamp reflects the earliest verified suspension record, not a proven outage start.
- 13 Oct 2026, 01:11 UTCIdentifiedA production readiness check returned HTTP 503, and service suspension remained confirmed. Customer investigations, uploads and new report generation are unavailable while the runtime is suspended. A recovery time has not been verified.
- 13 Oct 2026, 21:32 UTCMonitoringThe application API, analysis worker, report renderer and scheduled services were redeployed and are running, and the production readiness check passes for the API and its database. The job-queue Redis instance was still suspended, so workers picked up analysis jobs by polling and request rate limiting was degraded.
- 13 Oct 2026, 21:41 UTCResolvedThe Redis instance was resumed and the analysis worker reconnected to the job queue. The production readiness check reports the API, database and Redis available. This resolution is based on readiness checks and service logs; a full customer investigation was not re-run on production for this update.