BlueOptima Outage History
BlueOptima is up right nowPingoru has recorded 22 incidents for BlueOptima: 8 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 5 of 720 (1%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 1 | 23 of 720 (3%) |
| July 2026 | 3 | 158 of 744 (21%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 1 | 25 of 513 (5%) |
Incidents, newest first
Minor October 12, 2026 Data Processing Delays - Reporting Tools Affected 1d UIX
Started Oct 12, 2026, 11:09 AM UTC· resolved Oct 13, 2026, 11:49 AM UTC
- investigating Oct 12, 2026, 11:09 AM UTC
Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. No data has been lost and the system should be caught up shortly. Some customers may see delays before refreshed metrics and dashboards reflect their latest data. The data itself is not affected.
- investigating Oct 12, 2026, 11:10 AM UTC
We are continuing to investigate this issue.
- monitoring Oct 12, 2026, 03:27 PM UTC
A fix has been implemented and the system is catching up. We are monitoring the application.
- resolved Oct 13, 2026, 11:49 AM UTC
The issue is resolved. Data processing operations are functioning normally. An increase in incoming data, combined with an unforeseen change in the underlying database systems' behaviour, caused performance degradation at one stage of the data processing pipelines. We addressed the issue by implementing optimisations to the impacted stage, which brought the systems within the expected operating parameters.
Minor July 16, 2026 Intermittent login page issues 23h 17m UIX
Started Jul 16, 2026, 12:45 PM UTC· resolved Jul 17, 2026, 12:03 PM UTC
- investigating Jul 16, 2026, 12:45 PM UTC
We are investigating an issue where some users may experience intermittent login problems, including the SSO page failing to load or requiring a refresh. Additionally, some page navigations may be slower than expected. Our team is actively investigating the issue.
- monitoring Jul 16, 2026, 04:54 PM UTC
It was identified that degraded performance in one of the backend APIs caused this issue. Database optimizations have been implemented to mitigate the problem. The application has been operating normally for approximately the last four hours. We will continue to monitor the system closely to ensure ongoing stability.
- resolved Jul 17, 2026, 12:03 PM UTC
This incident has been resolved.
Minor July 13, 2026 Extraction Processing Degradation 13h 56m Central Server
Started Jul 13, 2026, 10:48 AM UTC· resolved Jul 14, 2026, 12:45 AM UTC
- resolved Jul 13, 2026, 10:48 AM UTC
Summary On 12 July, we experienced a service degradation that affected communication between integrators and the BlueOptima SaaS platform. The incident began at 19:20 UTC and service was restored by 13 July at 00:45 UTC. The issue was caused by an outage in a supporting infrastructure service, which temporarily impacted the availability of our application. Once the underlying infrastructure issue was resolved, all services recovered and processing resumed. Impact During the incident: Communication between integrators and the BlueOptima SaaS platform was disrupted. Daily extraction processing was not significantly affected. Processing of historical extractions was delayed by up to 5 hours in some cases. A backlog of processing requests accumulated and was processed following service restoration. Some integrators may have gone offline. Although automatic restart mechanisms are in place, a small number of integrators may not have restarted successfully. If you received a notification that your integrator is offline, please restart the affected integrator. Resolution The supporting infrastructure service was restored, allowing application availability to recover. Normal processing has resumed, and all queued requests have been processed. We apologize for the disruption and appreciate your patience while we worked to restore service.
Major July 8, 2026 Frequent automatic logout issue 5d 1h UIX
Started Jul 08, 2026, 09:40 AM UTC· resolved Jul 13, 2026, 10:45 AM UTC
- 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.
- 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
- 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.
- 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.
- 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
Notice April 18, 2026 Central Server downtime 5h
Started Apr 18, 2026, 06:00 AM UTC· resolved Apr 18, 2026, 11:00 AM UTC
- 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.
Minor February 4, 2026 Extraction Processing slowness 4d 19h Central Server
Started Feb 04, 2026, 01:36 PM UTC· resolved Feb 09, 2026, 08:56 AM UTC
- 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.
- investigating Feb 04, 2026, 01:37 PM UTC
We are continuing to investigate this issue.
- 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.
- resolved Feb 09, 2026, 08:56 AM UTC
The backlog of extractions has been processed and the issue has been resolved.
Notice February 3, 2026 Resolved – UIX Unavailability 19m UIX
Started Feb 03, 2026, 02:21 PM UTC· resolved Feb 03, 2026, 02:40 PM UTC
- 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.
Minor October 15, 2025 Integrator - SaaS server communication issue 6d 4h Central Server
Started Oct 15, 2025, 12:42 PM UTC· resolved Oct 21, 2025, 05:12 PM UTC
- 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.
- monitoring Oct 15, 2025, 12:42 PM UTC
We are continuing to monitor for any further issues.
- resolved Oct 21, 2025, 05:12 PM UTC
This incident has been resolved.
Notice April 20, 2025 Service Degradation: Extraction Failures and Delays 31d 18h
Started Apr 20, 2025, 10:44 AM UTC· resolved May 22, 2025, 04:54 AM UTC
- 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
- monitoring Apr 21, 2025, 06:08 PM UTC
A fix has been implemented and we are monitoring the results.
- 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
- 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.