Ocrolus incident

Detect Degraded Performance

Resolved after 3 hours 46 minutes, affecting Detect, on October 14, 2025.

resolved Oct 14, 2025, 09:11 PM UTC

The system has fully recovered, and all Detect services are now running smoothly.

Started
Oct 14, 2025, 05:24 PM UTC
Resolved
Oct 14, 2025, 09:11 PM UTC
Duration
3h 46m
Detected by Pingoru
Oct 14, 2025, 05:24 PM UTC

Affected components

Detect

Update timeline

  1. investigating Oct 14, 2025, 05:24 PM UTC

    We are currently experiencing a delay in our Detect, and you may notice an increase in turnaround time (TAT). Our team is actively investigating the issue, and we’ll keep you updated as we make progress.

  2. investigating Oct 14, 2025, 06:08 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 14, 2025, 06:38 PM UTC

    We identified the root cause and have applied the necessary fix.

  4. monitoring Oct 14, 2025, 08:01 PM UTC

    We are currently processing the backlog of messages and are approximately one hour behind. This delay is limited in scope — only a subset of books are affected, while the majority are processing as expected. Our teams continue to monitor the situation closely to ensure full recovery and system stability.

  5. resolved Oct 14, 2025, 09:11 PM UTC

    The system has fully recovered, and all Detect services are now running smoothly.

Your product runs on more than Ocrolus

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →