BlueOptima Outage History

BlueOptima degraded View live status →

BlueOptima had 7 outages in the last 2 years totaling 384h 54m of downtime — averaging 0.3 incidents per month.

There were 7 BlueOptima outages since October 15, 2025 totaling 384h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.blueoptima.com

Major July 8, 2026

Frequent automatic logout issue

Detected by Pingoru
Jul 08, 2026, 09:40 AM UTC
Resolved
Jul 13, 2026, 10:45 AM UTC
Duration
5d 1h
Affected: UIX
Timeline · 5 updates
  1. investigating Jul 08, 2026, 09:40 AM UTC

    We are currently investigating an issue where users are getting automatically logged out frequently while using the application. We apologise for the inconvenience.

  2. investigating Jul 08, 2026, 11:11 AM UTC

    We are continuing to investigate this issue. The token refresh is failing which results in users getting logged out automatically in 10 minutes and being forced to log in again. We will provide an update as soon as we identify the root cause

  3. monitoring Jul 08, 2026, 12:27 PM UTC

    A fix has been implemented and we are monitoring the application. The refresh token API had a regression issue due to a release done earlier in the day that has now been fixed. We will provide more details shortly.

  4. monitoring Jul 09, 2026, 01:08 PM UTC

    Some users are have been facing issues with refresh token due to cookie size exceeding the limit of 8KB. In such cases the api is failing and causing the users to get logged out. A fix has been implemented for that and we are continuing to monitor the application.

  5. resolved Jul 13, 2026, 10:45 AM UTC

    This incident has been resolved and we have not noticed any automatic logout issues in the last 24 hours

Read the full incident report →

Major June 26, 2026

Data Processing Delays - Reporting Tools Affected

Detected by Pingoru
Jun 26, 2026, 09:00 AM UTC
Resolved
Jun 26, 2026, 09:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Jun 26, 2026, 12:28 PM UTC

    We experienced delays in request processing due to a backend issue that affected synchronization between the application cache and the database. As a result, request statuses were not being updated correctly, leading to processing delays. The root cause was identified as an application error, which has now been fixed. The affected requests are currently being processed, and the system has resumed normal operation for new requests. In addition to implementing the fix, we have introduced additional validation and monitoring checks to ensure cache and database synchronization remains consistent and to help prevent this issue from recurring.

Read the full incident report →

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 →