BlazeMeter incident

Users experiencing delays in stopping tests as well as starting in some cases

Critical Resolved View vendor source →

BlazeMeter experienced a critical incident on April 17, 2025 affecting Performance Testing, lasting 4h 45m. The incident has been resolved; the full update timeline is below.

Started
Apr 17, 2025, 09:21 AM UTC
Resolved
Apr 17, 2025, 02:06 PM UTC
Duration
4h 45m
Detected by Pingoru
Apr 17, 2025, 09:21 AM UTC

Affected components

Performance Testing

Update timeline

  1. investigating Apr 17, 2025, 09:21 AM UTC

    We are aware of an issue with Blazemeter Performance tests not able to start or end as per the set duration. We are currently Investigating this issue. We will post and update here as soon as we have more information.

  2. monitoring Apr 17, 2025, 10:11 AM UTC

    The data delays causing this incident have been diminished, and functionality has been restored. We are currently monitoring the performance closely. The next update will be provided as new information is available.

  3. monitoring Apr 17, 2025, 10:12 AM UTC

    The data delays causing this incident have been diminished, and functionality has been restored. We are currently monitoring the performance closely. The next update will be provided as new information is available.

  4. monitoring Apr 17, 2025, 11:59 AM UTC

    The functionality has been restored. We are currently monitoring the performance closely.

  5. resolved Apr 17, 2025, 02:06 PM UTC

    We have not seen any reoccurrences of the data processing delays in some time. We are resolving the incident now.