Ocrolus Outage History

Ocrolus is up right now

Ocrolus had 10 outages in the last 2 years totaling 45h 20m of downtime — averaging 0.4 incidents per month.

There were 10 Ocrolus outages since June 3, 2025 totaling 45h 20m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.ocrolus.com

Minor April 29, 2026

Delays in Updating Custom Fields

Detected by Pingoru
Apr 29, 2026, 02:51 PM UTC
Resolved
Apr 29, 2026, 05:04 PM UTC
Duration
2h 12m
Affected: Income
Timeline · 4 updates
  1. investigating Apr 29, 2026, 02:51 PM UTC

    We are noticing delays with Encompass interactions, causing delay in custom field updates. We are actively looking into this.

  2. identified Apr 29, 2026, 03:33 PM UTC

    We identified the root cause and are applying the necessary fix.

  3. monitoring Apr 29, 2026, 04:05 PM UTC

    Services are stabilizing following the fix, and we will continue to closely monitor performance.

  4. resolved Apr 29, 2026, 05:04 PM UTC

    The issue has been successfully resolved, and impacted services are now fully operational.

Read the full incident report →

Minor April 22, 2026

Delays in Document Processing and Detect Completion

Detected by Pingoru
Apr 22, 2026, 10:59 PM UTC
Resolved
Apr 23, 2026, 05:08 AM UTC
Duration
6h 9m
Affected: Document ProcessingDetect
Timeline · 4 updates
  1. investigating Apr 22, 2026, 10:59 PM UTC

    Some customers are currently experiencing delays in document processing and Detect services, which may result in increased turnaround times (TAT) and slower Detect completion for documents. Our team is actively working through the backlog and monitoring the situation closely. We will continue to provide updates as progress is made.

  2. monitoring Apr 22, 2026, 11:47 PM UTC

    We are continuing to clear the backlog and are actively monitoring the situation.

  3. monitoring Apr 23, 2026, 01:45 AM UTC

    We have identified the issue impacting the Detect service and are actively monitoring the implemented fix. Our team is working to fully restore normal performance and is currently assessing the timeline for complete recovery. The issue affecting Document Processing has been resolved, and all related backlogs have been successfully cleared.

  4. resolved Apr 23, 2026, 05:08 AM UTC

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

Read the full incident report →

Minor March 17, 2026

Delays in Document Processing Services

Detected by Pingoru
Mar 17, 2026, 05:30 PM UTC
Resolved
Mar 17, 2026, 09:17 PM UTC
Duration
3h 47m
Affected: Document Processing
Timeline · 3 updates
  1. investigating Mar 17, 2026, 05:30 PM UTC

    Some customers are experiencing a delay in our document processing services. As a result, you may notice an increase in turnaround time (TAT). Our team is actively working through our backlogs, and we’ll keep you updated as we make progress.

  2. monitoring Mar 17, 2026, 07:44 PM UTC

    We are continuing to clear the backlog and are actively monitoring the situation.

  3. resolved Mar 17, 2026, 09:17 PM UTC

    The backlog has returned to normal levels, and turnaround time (TAT) has been steadily improving. We continue to actively monitor TAT and overall system health.

Read the full incident report →

Major January 29, 2026

Authentication and Login errors

Detected by Pingoru
Jan 29, 2026, 07:03 PM UTC
Resolved
Jan 29, 2026, 07:26 PM UTC
Duration
23m
Affected: Dashboard
Timeline · 3 updates
  1. investigating Jan 29, 2026, 07:03 PM UTC

    We are currently experiencing degraded performance with our authentication service that is causing some auth token refresh and Dashboard login requests to fail. API calls with valid non-expired tokens and document processing are unaffected.

  2. monitoring Jan 29, 2026, 07:11 PM UTC

    The performance of our authentication service has improved after we released a configuration change.

  3. resolved Jan 29, 2026, 07:26 PM UTC

    Our authentication service has returned to normal performance.

Read the full incident report →

Notice October 20, 2025

Expected outage due to Cloud provider

Detected by Pingoru
Oct 20, 2025, 12:57 PM UTC
Resolved
Oct 20, 2025, 08:44 PM UTC
Duration
7h 46m
Affected: Document Processing
Timeline · 4 updates
  1. identified Oct 20, 2025, 12:57 PM UTC

    Document processing may be delayed this morning due to ongoing recovery from a cloud provider outage.

  2. monitoring Oct 20, 2025, 02:57 PM UTC

    We are continuing to monitor the situation as our cloud provider's outage persists. At this time, we are observing only minor, intermittent failures. Our team is actively mitigating any resulting slowness, and document processing remains fully operational and stable.

  3. monitoring Oct 20, 2025, 05:08 PM UTC

    Our cloud provider's outage is ongoing, but current impact remains limited. We're continuing to apply mitigations and monitor system performance closely. Document processing remains stable, and we’ll provide further updates if conditions change.

  4. resolved Oct 20, 2025, 08:44 PM UTC

    Ocrolus remains fully operational as we continue to monitor the situation and await full service restoration from our cloud provider

Read the full incident report →

Minor October 14, 2025

Detect Degraded Performance

Detected by Pingoru
Oct 14, 2025, 05:24 PM UTC
Resolved
Oct 14, 2025, 09:11 PM UTC
Duration
3h 46m
Affected: Detect
Timeline · 5 updates
  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.

Read the full incident report →

Minor October 10, 2025

Document Processing Delays

Detected by Pingoru
Oct 10, 2025, 03:36 PM UTC
Resolved
Oct 10, 2025, 05:52 PM UTC
Duration
2h 16m
Affected: Document Processing
Timeline · 3 updates
  1. investigating Oct 10, 2025, 03:36 PM UTC

    We are currently experiencing a delay in our document processing services. As a result, 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. monitoring Oct 10, 2025, 04:37 PM UTC

    We have restored system operation, and we are working through the backlog of documents.

  3. resolved Oct 10, 2025, 05:52 PM UTC

    Our document processing system has fully returned to normal operations. Some documents may still experience delays as we work through the remaining backlog.

Read the full incident report →

Major September 3, 2025

Delays with Encompass interactions causing degraded performance

Detected by Pingoru
Sep 03, 2025, 04:38 PM UTC
Resolved
Sep 03, 2025, 05:17 PM UTC
Duration
39m
Affected: DashboardIncome
Timeline · 4 updates
  1. investigating Sep 03, 2025, 04:38 PM UTC

    We are noticing delays with Encompass interactions, causing degraded performance. We are actively looking into this.

  2. identified Sep 03, 2025, 04:47 PM UTC

    We identified the root cause and have applied the necessary fix. Services are stabilizing and we continue to monitor performance.

  3. monitoring Sep 03, 2025, 04:52 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Sep 03, 2025, 05:17 PM UTC

    The system has fully recovered, and encompass interactions are now functioning as expected.

Read the full incident report →

Major August 21, 2025

API Upload Delays

Detected by Pingoru
Aug 21, 2025, 07:59 PM UTC
Resolved
Aug 21, 2025, 08:53 PM UTC
Duration
53m
Affected: Ocrolus API
Timeline · 4 updates
  1. investigating Aug 21, 2025, 07:48 PM UTC

    We are currently experiencing a delay in our API upload services. We are actively investigating the issue.

  2. identified Aug 21, 2025, 07:59 PM UTC

    The problem seems to be related to our intake router. We’ve restarted it and are looking into it further.

  3. monitoring Aug 21, 2025, 08:22 PM UTC

    We haven’t observed any latency in the upload service since it was restarted. We are now monitoring the situation.

  4. resolved Aug 21, 2025, 08:53 PM UTC

    The system has fully recovered and upload API endpoints are now functioning as expected.

Read the full incident report →

Minor June 3, 2025

Duplicate Attachments In EFolder

Detected by Pingoru
Jun 03, 2025, 05:21 PM UTC
Resolved
Jun 04, 2025, 10:46 AM UTC
Duration
17h 24m
Affected: Dashboard
Timeline · 8 updates
  1. investigating Jun 03, 2025, 05:21 PM UTC

    We’re currently experiencing an issue where duplicate document files are being placed in the eFolder unexpectedly. The concerned team is already investigating and working on a fix to restore normal functionality as soon as possible

  2. investigating Jun 03, 2025, 05:24 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 03, 2025, 05:40 PM UTC

    We are continuing to investigate this issue.

  4. identified Jun 03, 2025, 05:42 PM UTC

    The issue has been identified and we are working on the fix.

  5. monitoring Jun 03, 2025, 05:59 PM UTC

    The fix has been released, and we're currently monitoring the system to ensure everything is stable.

  6. monitoring Jun 03, 2025, 06:34 PM UTC

    While keeping an eye on things, we noticed a few more irregularities. The team is already on it and working to sort them out.

  7. monitoring Jun 03, 2025, 11:15 PM UTC

    We are actively monitoring the system and have started to observe a reduction in duplicate instances. The team continues to work on resolving the issue and restoring the system to normal operations.

  8. resolved Jun 04, 2025, 10:46 AM UTC

    The system has fully recovered and is now functioning as expected.

Read the full incident report →