BlazeMeter incident

Historical Data not visible in UI for API Monitoring Tests

Notice Resolved View vendor source →

BlazeMeter experienced a notice incident on June 23, 2025 affecting API Monitoring (Runscope), lasting 3h 56m. The incident has been resolved; the full update timeline is below.

Started
Jun 23, 2025, 06:28 PM UTC
Resolved
Jun 23, 2025, 10:25 PM UTC
Duration
3h 56m
Detected by Pingoru
Jun 23, 2025, 06:28 PM UTC

Affected components

API Monitoring (Runscope)

Update timeline

  1. identified Jun 23, 2025, 06:28 PM UTC

    We are aware of an issue that is causing historical data to currently not be visible in API Monitoring tests. The R&D is currently working on a fix that will restore the data for the affected tests. When the fix is implemented there will initially be a gap in the data in the reports from 5:30am UTC, June 22nd until the time that the fix is implemented. The R&D team will then be working to restore the data from the gap over the next two days.

  2. resolved Jun 23, 2025, 10:25 PM UTC

    The fix for the missing historical data for API Monitoring tests has been released. You should now be able to see historical data from up to 5:30am UTC, June 22nd in your historic metrics again. The data from the gap will be restored to the tests in the next day or two.