BIM Track incident

Partial Service Degradation - US Datacenter

Minor Resolved View vendor source →

BIM Track experienced a minor incident on August 17, 2026 affecting Web Application and REST API and 1 more component, lasting 28d 20h. The incident has been resolved; the full update timeline is below.

Started
Aug 17, 2026, 03:46 PM UTC
Resolved
Sep 15, 2026, 12:35 PM UTC
Duration
28d 20h
Detected by Pingoru
Aug 17, 2026, 03:46 PM UTC

Affected components

Web ApplicationREST APIBackend Service

Update timeline

  1. investigating Aug 17, 2026, 03:46 PM UTC

    We are currently experiencing partially degraded performance affecting services hosted in our US datacenter. Users may encounter increased latency, slower response times, or intermittent service disruptions. As a precautionary measure and to maintain platform stability during remediation efforts, all NPC migrations have been temporarily disabled. Our engineering teams are actively investigating and working to restore full service performance as quickly as possible.

  2. monitoring Aug 17, 2026, 04:17 PM UTC

    Service performance has recovered following the temporary disablement of NPC migrations, and the platform is currently operating normally. We will continue to monitor system health closely.

  3. investigating Aug 17, 2026, 04:27 PM UTC

    We are currently investigating a new issue causing degraded service performance. Users may experience increased latency and intermittent disruptions while our teams work to identify the root cause. As a precautionary measure, NPC migrations remain temporarily disabled. This mitigation continues to help maintain platform stability while we investigate the underlying cause of the performance degradation.

  4. monitoring Aug 17, 2026, 06:59 PM UTC

    Service performance has recovered and the platform is currently operating normally. We will continue to monitor system health closely.

  5. monitoring Aug 18, 2026, 04:23 PM UTC

    We have been experiencing degraded performance since approximately 9:00 AM EST and continue to investigate the underlying cause. Our engineering teams are actively analyzing system behavior and reviewing available telemetry to identify the core issue.

  6. monitoring Aug 18, 2026, 08:19 PM UTC

    We believe we have identified a likely cause of the degraded performance and have begun implementing a series of mitigations. In addition, we have significantly increased platform resources, which has led to noticeable improvements in overall system stability and performance. At this time, we are continuing to monitor the environment closely while validating our findings. Although the implemented changes appear to be having a positive impact, the investigation remains ongoing as we work to confirm the root cause and ensure a long-term resolution.

  7. investigating Aug 19, 2026, 02:51 PM UTC

    The mitigations and fixes implemented yesterday have improved overall platform stability and helped reduce the impact of the issue. However, they have not fully resolved the underlying problem. We are once again observing periods of degraded performance and continue to actively investigate the root cause. Our engineering teams remain engaged, monitoring system health, analyzing telemetry, and implementing additional mitigations as needed.

  8. monitoring Aug 20, 2026, 06:38 PM UTC

    The mitigations implemented over the past several days have resulted in improved overall platform health, and we are seeing better system stability across the environment. Our teams are now focused on implementing more permanent fixes to address the underlying issue. While conditions have improved, we continue to closely monitor platform health and validate the effectiveness of these changes as our investigation remains ongoing. As a precautionary measure, we have again temporarily disabled all migrations from NPC to Konekt. Migrations will remain suspended until the permanent fixes have been implemented and validated to ensure long-term stability. We will continue to provide updates as progress is made and additional information becomes available.

  9. monitoring Aug 26, 2026, 02:28 PM UTC

    Over the past several days, we have continued to monitor the platform closely and implement additional improvements. Overall system health has significantly improved. As part of our ongoing remediation efforts, we will be deploying a new version of Konekt tonight that includes additional fixes and optimizations designed to further strengthen platform stability and performance. Based on the positive results we have observed, we are planning to re-enable NPC to Konekt migrations tomorrow morning. To ensure a controlled rollout and maintain platform stability, migrations will initially be re-enabled at a reduced capacity while we continue to monitor system performance and validate the effectiveness of the recent changes. We will provide another update tomorrow morning with more information on the deployment outcome and the status of NPC migrations. Thank you for your patience as we continue to work toward a complete and permanent resolution.

  10. monitoring Aug 27, 2026, 01:43 PM UTC

    Following the successful deployment of the latest Konekt release and continued improvements in platform health, NPC to Konekt migrations have now been re-enabled. As a precaution, migrations are currently operating at a reduced capacity while we continue to monitor system performance and validate the recent fixes.

  11. resolved Sep 15, 2026, 12:35 PM UTC

    This incident has been resolved.