BlazeMeter Outage History

The R&D team is performing some testing on our backend systems that may potentially cause slowness in the BlazeMeter UI. We are monitoring the system and we will return the system to normal functionality if we notice any slowness start to occur due to the testing. Tests should continue to run as normal during this time, though if you observe any issues then please contact our Support team.

The R&D team have identified the cause of the slowness and have taken steps to improve the responsiveness of BlazeMeter. We are seeing improved performance in the UI from our side. We will continue to monitor the issue to ensure the slowness does not reoccur.

Due to a capacity issue on the Google side, there are currently engine availability issues in the Iowa, Google public location. Tests using this location may have slow booting times, or fail to start properly. We recommend avoiding the use of the Google, Iowa location, and potentially using AWS or Azure instead for the time being.

We are seeing significant improvements in our tests being able to boot up successfully on Google Public Locations. At this time we are moving the incident Monitoring status while we await confirmation that the capacity issue has been fully resolved.

A fix has been released for the JMeter Plugins issue that should allow affected tests to download the required plugins. We are seeing our affected tests working properly again. We will continue to monitor the system for the time being.

A fix has been applied and we are seeing our affected tests being able to run again. We are moving the incident into Monitoring and will continue to check for any lingering issues.

There was an issue causing a 404 when navigating to mock.blazemeter.com, a hotfix has been released to fix the issue. All mock services will show in a failed state and need to be restarted, but they should operate as expected now.