BlazeMeter incident
Historical Data not visible in UI for API Monitoring Tests
Resolved after 3 hours 56 minutes, affecting API Monitoring (Runscope), on June 23, 2025.
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.
Affected components
Update timeline
- 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.
- 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.
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.
Amazon Web Services