Time: June 27, 2024, 9:24 a.m.

Status: Resolved

Update: 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.

Time: Feb. 20, 2024, 2:15 p.m.

Status: Resolved

Update: We encountered a brief service disruption in the Central Server from 03:20:00 to 03:36:00 UTC on 20/02/2024. During this period Integrators would have been unable to communicate with the Central Server, and hence unable to complete extractions or start new extractions. By design the Integrators continued to progress their existing extractions and completed them once the service was available again The issue was caused by transaction locks interfering with the module update, and a managed downtime of the service was required, resulting in the service disruption The issue was resolved at 03:36:00 UTC, and systems are operating healthy. No disruption to Integrators or ongoing extractions is seen The issue was caused by a planned system update that included changes to our database. Unfortunately, this caused a temporary interruption as certain processes had to be paused. The issue arose because the part of the database being modified was also in use by scheduled tasks. We've resolved the situation, and our teams are working to ensure smoother updates in the future.

Time: Feb. 20, 2024, 2:15 p.m.

Status: Resolved

Update: We encountered a brief service disruption in the Central Server from 03:20:00 to 03:36:00 UTC on 20/02/2024. During this period Integrators would have been unable to communicate with the Central Server, and hence unable to complete extractions or start new extractions. By design the Integrators continued to progress their existing extractions and completed them once the service was available again The issue was caused by transaction locks interfering with the module update, and a managed downtime of the service was required, resulting in the service disruption The issue was resolved at 03:36:00 UTC, and systems are operating healthy. No disruption to Integrators or ongoing extractions is seen The issue was caused by a planned system update that included changes to our database. Unfortunately, this caused a temporary interruption as certain processes had to be paused. The issue arose because the part of the database being modified was also in use by scheduled tasks. We've resolved the situation, and our teams are working to ensure smoother updates in the future.

Time: Feb. 9, 2024, 1:59 p.m.

Status: Resolved

Update: We encountered a brief service disruption on UIX from 17:25:00 to 17:42:00 UTC on 08/02/2025. During this period an increased error rate was seen for the APIs and page loads being slow and in a few cases timeouts. The issue was resolved at 17:42:00 UTC systems are operating healthy During the root cause analysis of this disruption, we have identified an area of application that under specific conditions requires a significantly higher amount of memory, than expected, for a short duration. This area of our application was triggered by multiple simultaneous requests. We have also identified improvements in our load balancer configuration to improve traffic routing in such a scenario. Engineering and Platform teams are currently working on improving these areas of the application to ensure healthy service to our users. In the meantime, we have scaled the application to ensure stability.

Time: Feb. 9, 2024, 1:59 p.m.

Status: Resolved

Update: We encountered a brief service disruption on UIX from 17:25:00 to 17:42:00 UTC on 08/02/2025. During this period an increased error rate was seen for the APIs and page loads being slow and in a few cases timeouts. The issue was resolved at 17:42:00 UTC systems are operating healthy During the root cause analysis of this disruption, we have identified an area of application that under specific conditions requires a significantly higher amount of memory, than expected, for a short duration. This area of our application was triggered by multiple simultaneous requests. We have also identified improvements in our load balancer configuration to improve traffic routing in such a scenario. Engineering and Platform teams are currently working on improving these areas of the application to ensure healthy service to our users. In the meantime, we have scaled the application to ensure stability.