BlueOptima Outage History

BlueOptima is up right now

BlueOptima had 9 outages in the last 2 years totaling 1408h 35m of downtime — averaging 0.4 incidents per month.

There were 9 BlueOptima outages since June 27, 2024 totaling 1408h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.blueoptima.com

Notice April 20, 2026

Central Server downtime

Detected by Pingoru
Apr 20, 2026, 09:35 AM UTC
Resolved
Apr 18, 2026, 06:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Apr 20, 2026, 09:35 AM UTC

    Due to a DB changes and application deployment, the central server was not available for around 5 hours. There was no major impact on integrators due to this as the Integrator Management Service was up, although there was some delays in processing of requests in the SaaS server. The backlog was cleared in a few hours after the release and normal service restored.

Read the full incident report →

Minor February 4, 2026

Extraction Processing slowness

Detected by Pingoru
Feb 04, 2026, 01:36 PM UTC
Resolved
Feb 09, 2026, 08:56 AM UTC
Duration
4d 19h
Affected: Central Server
Timeline · 4 updates
  1. investigating Feb 04, 2026, 01:36 PM UTC

    We are observing slowness in completing extraction processing in the backend servers and as a result the backlog is increasing. This is due to a DB issue and it may cause some random slowness in certain UI pages like Analyse ACE/Maintainability .We are currently investigating the issue.

  2. investigating Feb 04, 2026, 01:37 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Feb 05, 2026, 12:39 PM UTC

    The systems are back to normal and have been processing for the last couple of hours. We restored the data processing pipelines in a phased manner starting 8:30 AM UTC and all stages were restored by 10:30 AM UTC. The extractions are being processed as usual. We will continue to monitor the applications to ensure that the backlog is cleared in the next 24-36 hours. We identified the root cause was a data storage limitation in one of our backend tables that required an urgent fix. To safely perform this correction, data processing was temporarily paused and migration was performed.

  4. resolved Feb 09, 2026, 08:56 AM UTC

    The backlog of extractions has been processed and the issue has been resolved.

Read the full incident report →

Notice February 3, 2026

Resolved – UIX Unavailability

Detected by Pingoru
Feb 03, 2026, 03:11 PM UTC
Resolved
Feb 03, 2026, 03:11 PM UTC
Duration
Affected: UIX
Timeline · 1 update
  1. resolved Feb 03, 2026, 03:11 PM UTC

    The application UI was inaccessible due to a database-related issue between 14:21 GMT and 14:40 GMT. The issue has been resolved and all services are operating normally. The root cause analysis is currently in progress, and we will share more details once it is completed.

Read the full incident report →

Minor October 15, 2025

Integrator - SaaS server communication issue

Detected by Pingoru
Oct 15, 2025, 12:42 PM UTC
Resolved
Oct 21, 2025, 05:12 PM UTC
Duration
6d 4h
Affected: Central Server
Timeline · 3 updates
  1. monitoring Oct 15, 2025, 12:42 PM UTC

    We identified an issue with API communication between integrators and the backend server caused by intermittent database connectivity problems. The issue started around 9th October 2025, approximately 6:30 PM UTC. Impact: Due to this issue, some integrators may have experienced communication failures and, in certain cases, automatic restarts, and a slight delay in extraction completion due to failures and retries. Resolution: Our team has stabilized the connections and verified that API communication has returned to normal. We continue to monitor the system closely to ensure stability. Next Steps: We are investigating the root cause of the database instability and will implement preventive measures to avoid recurrence.

  2. monitoring Oct 15, 2025, 12:42 PM UTC

    We are continuing to monitor for any further issues.

  3. resolved Oct 21, 2025, 05:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 20, 2025

Service Degradation: Extraction Failures and Delays

Detected by Pingoru
Apr 20, 2025, 10:44 AM UTC
Resolved
May 22, 2025, 04:54 AM UTC
Duration
31d 18h
Timeline · 4 updates
  1. investigating Apr 20, 2025, 10:44 AM UTC

    We have identified a couple of issues affecting the processing of data extraction requests on the server. You will see extractions failing randomly with error code EE0005 error code. And this will affect data collection from last 2 days and any new onboarding initiated in this period. The second problem is related to an internal request management service and message queue failure that has caused a backlog in the extraction processing pipeline. Team is working on resolution of these issues. Once resolved all errors will be retried by the system and no action will be required from users The issue impacts only extraction processing. The UI remains fully functional and is not affected. Our team is actively working on resolving these issues and clearing the backlog as quickly as possible. We appreciate your patience and understanding while we work towards a resolution. Please follow this status page for regular updates on the issue

  2. monitoring Apr 21, 2025, 06:08 PM UTC

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

  3. investigating Apr 22, 2025, 09:27 AM UTC

    We have been monitoring the progress for the last 8 hours and the system is should be able to process the backlog in the next 12 hours. The extractions that failed when the issue first happened last week have also been queued for retry and will be processed soon

  4. resolved May 22, 2025, 04:54 AM UTC

    the issue has not re-surfaced and all failures from the time of the original incident have been retried.

Read the full incident report →

Minor September 25, 2024

Service degradation

Detected by Pingoru
Sep 25, 2024, 03:25 PM UTC
Resolved
Oct 11, 2024, 02:01 PM UTC
Duration
15d 22h
Affected: Central Server
Timeline · 3 updates
  1. investigating Sep 25, 2024, 03:25 PM UTC

    Service degradation: We have identified service interruptions affecting the integrators this evening. We have identified this as an issue with degraded performance of an API used for communication between Integrator & BlueOptima SaaS service. We are actively implementing mitigating controls to reduce the frequency of these shutdowns while we work on a resolution. We are committed to resolving it by early next week. We apologise for the inconvenience caused and appreciate your patience and understanding during this time. We will keep you updated on our progress and notify you as soon as we have a resolution.

  2. investigating Sep 26, 2024, 05:32 AM UTC

    We are continuing to investigate this issue.

  3. resolved Oct 11, 2024, 02:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 1, 2024

Central Server : Service Disruption Notification: Temporary Disruption Resolved - 01/08/2024

Detected by Pingoru
Aug 01, 2024, 02:00 AM UTC
Resolved
Aug 01, 2024, 02:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Aug 01, 2024, 05:03 AM UTC

    We encountered a brief service disruption in the Central Server from 02:35:00 to 02:51:00 UTC on 01/08/2024. The issue was resolved at 02:51:00 UTC systems are operating healthy. We are investigating the issue currently.

Read the full incident report →

Notice July 16, 2024

UIX - Login Issue

Detected by Pingoru
Jul 16, 2024, 02:15 AM UTC
Resolved
Jul 16, 2024, 02:15 AM UTC
Duration
Timeline · 1 update
  1. resolved Jul 16, 2024, 03:30 PM UTC

    Some users experienced intermittent login difficulties between 2:15 PM and 3:25 PM UTC. The issue has since been resolved, and normal service has resumed. We apologize for any inconvenience caused.

Read the full incident report →

Notice June 27, 2024

Service Outage-UIX: Login failure to the application

Detected by Pingoru
Jun 27, 2024, 07:30 AM UTC
Resolved
Jun 27, 2024, 07:30 AM UTC
Duration
Timeline · 1 update
  1. resolved Jun 27, 2024, 09:24 AM UTC

    Application users saw login failure between 7:43 UTC to 8:34 UTC. We have identified this as an outcome of a update to a database, which was not reflected in the cache. This issue has been resolved and no further impact is seen.

Read the full incident report →