BlazeMeter incident

Tests Stuck in Pending/Booting status

Resolved after 3 hours 59 minutes, affecting Functional Testing and Performance Testing, on July 25, 2025.

resolved Jul 25, 2025, 09:35 PM UTC

Tests have continued to run as expected again while we have been monitoring the system. At this time we are resolving the incident.

Started
Jul 25, 2025, 05:36 PM UTC
Resolved
Jul 25, 2025, 09:35 PM UTC
Duration
3h 59m
Detected by Pingoru
Jul 25, 2025, 05:36 PM UTC

Affected components

Functional TestingPerformance Testing

Update timeline

  1. investigating Jul 25, 2025, 05:36 PM UTC

    We are aware of an issue that is causing tests to get stuck in Pending/Booting status. We are currently investigating the cause of the issue and will provide updates as soon as possible.

  2. identified Jul 25, 2025, 07:39 PM UTC

    A fix has been implemented and we are seeing our tests being able to run again in many cases. The R&D team is continuing to work to restore full functionality so some tests may still experience prolonged booting times.

  3. monitoring Jul 25, 2025, 08:26 PM UTC

    Additional work has been done to further ensure the stability of tests on BlazeMeter. Our tests continue to run as expected as well. At this time we are moving the incident to Monitoring and we will continue to observe the system for any irregularities.

  4. resolved Jul 25, 2025, 09:35 PM UTC

    Tests have continued to run as expected again while we have been monitoring the system. At this time we are resolving the incident.

Your product runs on more than BlazeMeter

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →