BlazeMeter incident
Some Multi-tests are not running with some engines stuck in the Pending state
BlazeMeter experienced a minor incident on April 15, 2024 affecting BlazeMeter Platform, lasting 22h 56m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Apr 15, 2024, 04:56 PM UTC
We are currently investigating this issue.
- investigating Apr 15, 2024, 07:34 PM UTC
We are aware of some customers experiencing an issue with some engines failing to start when running multi-tests. We are still investigating the cause of this issue and will provide updates as new information becomes available. All other aspects of the product are functioning as normal.
- investigating Apr 15, 2024, 09:19 PM UTC
We are aware of some customers experiencing an issue where some engines in their multi-tests are stuck in a pending status. We are still investigating the cause of this issue and will provide updates as new information becomes available. All other aspects of the product are functioning as normal.
- monitoring Apr 16, 2024, 12:32 PM UTC
R&D has deployed a hotfix to production to address most of the issues with engines failing to start when running multi-tests. We are continuing to monitor the system for any reoccurrences of the issue.
- monitoring Apr 16, 2024, 02:48 PM UTC
We are seeing improved stability with the majority of multi-tests that were experiencing issues and have deployed another hotfix to address any lingering execution issues. We will continue to monitor the situation and provide updates.
- resolved Apr 16, 2024, 03:52 PM UTC
This incident has been resolved.