Following a sustained period of stable service and continued monitoring, we have confirmed that metric processing has returned to normal and no further issues have been identified. As a result, we are now closing this incident.
We appreciate your continued patience and understanding throughout this incident.
Posted Oct 21, 2026 - 14:11 UTC
Update
We would like to provide another update on the ongoing monitoring stack incident.
Following the recovery actions taken, metric processing remains stable, and metrics continue to be processed successfully and displayed within the portal.
We are currently observing stable platform behavior and have not identified any further issues. We will continue monitoring the platform through 16:00 and will provide further updates if necessary.
We appreciate your continued patience and understanding throughout this incident.
Posted Oct 21, 2026 - 11:14 UTC
Monitoring
We would like to provide another update on the ongoing monitoring stack incident.
Following the recovery actions taken, metric processing has returned to a stable state. Metrics are now being processed successfully and are becoming visible within the portal.
At this time, we continue to closely monitor the platform to ensure stability and verify that recovery progress is maintained. While service behavior has returned to normal, we remain actively engaged and are monitoring the environment for any signs of regression.
We will continue to monitor the situation and provide further updates as needed. Our next update is planned for approximately 13:00.
We appreciate your continued patience and understanding throughout this incident.
Posted Oct 21, 2026 - 10:04 UTC
Update
We would like to provide another update on the ongoing monitoring stack incident.
Recovery efforts continue; however, we are still experiencing challenges in processing the existing backlog of metrics at the rate required to fully restore the platform. Despite ongoing mitigation efforts, the current recovery approach has not enabled us to catch up to the accumulated data volume.
To support recovery and restore service stability, we have made the decision to discard older queued metrics and resume processing from the current state. As a result, historical metric data generated during the affected period may not be available within the portal. This action is intended to accelerate recovery and allow the platform to return to normal metric processing as quickly as possible.
We will continue to provide regular updates as more information becomes available. Our next update is planned for approximately 13:00.
We appreciate your continued patience and understanding as we work through the remaining recovery efforts.
Posted Oct 21, 2026 - 09:20 UTC
Update
We would like to provide an update on the ongoing monitoring stack incident.
Recovery efforts remain underway. At this time, we do not have sufficient information to provide a reliable estimate for full resolution.
We would like to emphasize that the impact of this incident is limited to metric availability within the portal. The operation of the underlying services, including alerting functionality, remains unaffected.
Our engineering teams remain fully engaged in investigating and resolving the issue. We will continue to provide regular updates as more information becomes available. Our next update is planned for approximately 11:00.
We appreciate your patience and understanding as we work to restore full metric availability within the portal.
Posted Oct 21, 2026 - 07:10 UTC
Update
We would like to provide an update on the ongoing monitoring stack incident.
The underlying issue has been resolved, and our recovery efforts are now focused on processing the remaining backlog of metrics. As we continue to restore normal operations, we have determined that not all metrics affected during the incident can be recovered. As a result, historical monitoring data for portions of the affected period may remain incomplete.
Our primary focus is now on stabilizing the monitoring platform and ensuring the reliable processing and availability of newly received metrics. New metrics are being successfully received and processed, while the team continues to actively monitor the infrastructure and reduce the remaining backlog as quickly as possible.
We will continue to closely monitor progress and provide our next update tomorrow at 09:00. We appreciate your patience and understanding as we work to fully restore normal operations.
Posted Oct 20, 2026 - 14:35 UTC
Update
We are continuing our efforts to restore normal processing of metrics. While data is being processed and the backlog is decreasing, the processing rate is still below the desired level.
Our team is actively working on increasing the processing rate to catch up with the remaining backlog as quickly as possible and make all data accessible again within the platform.
We appreciate your patience and understanding while we continue these recovery efforts. The next update will be provided around 16:00.
Posted Oct 20, 2026 - 13:09 UTC
Update
We are still actively working on restoring normal processing of metrics and logs. As part of our recovery efforts and ongoing platform optimizations, logs and metrics may temporarily become unavailable within the platform.
We apologize for any inconvenience this may cause and will continue to provide updates as we make progress.
Posted Oct 20, 2026 - 10:14 UTC
Investigating
We are currently experiencing issues with our monitoring stack. While metrics are still being received successfully, they are not being processed quickly enough, resulting in delays before they become visible within the monitoring platform.
Our team is actively investigating the root cause of this issue and working to restore normal operation as quickly as possible.
During this period, monitoring data may be incomplete or unavailable. We will provide an update as soon as we have more information or when the issue has been resolved.
We apologize for any inconvenience this may cause and appreciate your patience while we work on restoring the service.
Posted Oct 20, 2026 - 06:51 UTC
This incident affected: Monitoring stack (Current stack).