Is BlazeMeter Down Right Now? Check if there is a current outage ongoing.

We are aware of an issue affecting Google Cloud servers that is causing BlazeMeter tests to either not run or not produce data. Tests that are configured to run on Google Cloud will not be able to initiate due to engine availability issues. Tests that run on AWS, Azure, or Private Locations will run, but are not currently producing data to populate in the reports.

R&D has applied a fix for the issue affecting Performance Test validations. Scripts are now able to pass validation and be run again at this time.

We have identified the cause of the issue and the R&D team is working resolve the validation process for Performance Tests now. We will provide additional updates as soon as possible.

We are aware of an issue that is causing tests to be stuck in validation and be unable to run. We are investigating the cause and will provide updates as soon as possible

R&D has applied a fix for the issue affecting Performance Test validations. Scripts are now able to pass validation and be run again at this time.

We have identified the cause of the issue and the R&D team is working resolve the validation process for Performance Tests now. We will provide additional updates as soon as possible.

We are aware of an issue that is causing tests to be stuck in validation and be unable to run. We are investigating the cause and will provide updates as soon as possible

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

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

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.

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.

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.

We have received notice from Google that the issue with the South Carolina & California locations has been resolved. We have verified with our own testing and confirmed that the GCP South Carolina & California locations are available in BlazeMeter again at this time.

We have identified the cause of the issue where performance tests are not starting in the GCP US West (California, Google) & US East (South Carolina, Google) regions, which is being experienced by some customers and this has been reported to Google. We are working with them to resolve the issue. The next update will be provided as new information is available.

We have identified the cause of the issue where performance tests are not starting in the GCP US West region which is being experienced by some customers and this has been reported to Google. We are working with them to resolve the issue. The next update will be provided as new information is available.

The issue has been identified and is only impacting Performance tests running in the US West (California) Google / GCP Location. All other tests are unaffected

The issue has been identified and is only impacting Performance tests running on certain Google (GCP) Locations

We are aware of an issue with Blazemeter Performance and Functional tests running on GCP location. We are currently Investigating this issue. We will post and update here as soonas we have more information.

The incident has been resolved.

As of 18:15 UTC, the issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

As of TIME_STAMP UTC, the issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

The issue with Performance Test results being delayed has been identified and fixed.

We are aware of some customers experiencing issues with Performance Test results being delayed. We are currently investigating the cause of this issue and will provide updates as new information becomes available. All other aspects of the product are functioning as normal.

As of 00:30 UTC, the issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

The root cause of the issue has been identified by the R&D team. Unfortunately an automated fix cannot be rolled out to the affected Agents so they will need to be manually restarted if they are in Error state due to this issue. The steps to restart the Agents are as follows: Docker Steps: sudo docker ps -a sudo docker start {{crane containerId}} Kubernetes Step: kubectl rollout restart deployment {{deployment_name}} -n {{namespace}}

The root cause of the issue has been identified by the R&D team. Unfortunately an automated fix cannot be rolled out to the affected Agents so they will need to be manually restarted if they are in Error state due to this issue. The steps to restart the Agents are as follows: Docker Steps: sudo docker ps -a sudo docker start {{crane containerId}} Kubernetes Step: kubectl rollout restart deployment {{deployment_name}} -n {{namespace}}

We are still continuing to identify the root cause of the issue. However most Agents can be returned to a functional state by restarting them. The steps for restarting an Agent are: Docker Steps: sudo docker ps -a sudo docker start {{crane containerId}} Kubernetes Step: kubectl rollout restart deployment {{deployment_name}} -n {{namespace}}

We are continuing to investigate this issue.

We are aware of an issue with Private Locations at this time that has caused them to go into Error state. We are actively investigating the issue now and will provide updates as soon as possible. Restarting or Regenerating the Agents has resolved the issue for some customers so we recommend attempting that for Agents currently in and Error state.

As of 7:50 am UTC, the issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

As of 7:42 am UTC, the issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

As of 6:51 am UTC, the issue experienced by some customers has been addressed and functionality has been restored. We are currently monitoring the performance closely. The next update will be provided as new information is available.

We are continuing to investigate this issue.

We are experiencing performance issues with the Service Virtualization and the BlazeMeter UI. We are aware of the problem and are working to resolve the issue at this time.

The issue has been fixed and normal operations for API Monitoring have been restored.

The cause has been identified and things should be running normally, we will be watching to make sure things continue to run smoothly.

We are aware of a slowdown in API Monitoring Test Execution and this is being looked into by the engineering team.

The JMeter plugin repository site is available again now.

The Jmeter plugin repository service is offline/unavailable, which will cause issues with tests relying on the plugin server. We recommend users upload any required plugins (JARs) to the test to avoid this error. Note that the Plugin repository is a third-party open-source site. BlazeMeter tests may utilise the site, but we do not support or maintain it. You may report & track the issue on community groups - https://groups.google.com/g/jmeter-plugins/c/I4FScaeY_aE

The fix has been implemented and the system has finished processing the test result metrics so they are now visible in the UI again.

A fix has been implemented and metrics are continuing to be processed for earlier test results. We still expect it to take a few more hours for the system to finish processing the test metrics so we are continuing to monitor it's progress.

R&D has identified the issue and is working on a fix for it at this time. The metrics for earlier test runs are currently being calculated now as well.

The test metrics of API Monitoring test runs are currently displaying as empty in the UI. Tests are still running as expected otherwise. R&D is aware of the issue and is actively investigating at this time.

We are no longer seeing issues with tests running on Google locations. Resolving the incident now, thank you for your patience.

A fix has been implemented for the issue and we are seeing Performance Tests being able to run on Google locations. We are continuing to monitor the system for any re-occurrences of the issue.

Performance Tests still can't be run on Google locations. Azure and AWS locations are still operational at this time, as well as Functional Tests. We are continuing to investigate the root cause of the issue with Google engines now.

Tests currently can't be run on Google locations. We are investigating this issue now.

A hotfix was deployed and the issue has now been resolved

We are continuing to work on a fix for the issue. Though there is a workaround that can be used in the meantime. The Request Stats CSV can de downloaded in the proper format by making the following API call: curl -X GET "https://a.blazemeter.com/api/v4/masters/{{{masterId}}}/reports/aggregatereport/data.csv" -o data.csv --user "{{{api_key}}}:{{{api_secret}}}"

The issue has been identified and there is a fix in place on the testing environment being vetted before release. In the meantime, a workaround is that you can look in the artifacts.zip file from the logstab of your test results page.

We are still investigating the issue with the download of the Request Stats Reports. Performance tests, Mock Services and API Monitoring are all operational and functioning as expected.

We are continuing to investigate the issue with the download of the Request Stats Reports. Performance tests are operational and functioning as expected.

We are currently aware of an issue with downloading CSV files from the Request Stats Report. The issue has been escalated and is currently being investigated.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We are seeing improved stability with the majority of multi-tests that were experiencing issues and have deployed another hotfix to address any lingering execution issues. We will continue to monitor the situation and provide updates.

R&D has deployed a hotfix to production to address most of the issues with engines failing to start when running multi-tests. We are continuing to monitor the system for any reoccurrences of the issue.

We are aware of some customers experiencing an issue where some engines in their multi-tests are stuck in a pending status. We are still investigating the cause of this issue and will provide updates as new information becomes available. All other aspects of the product are functioning as normal.

We are aware of some customers experiencing an issue with some engines failing to start when running multi-tests. We are still investigating the cause of this issue and will provide updates as new information becomes available. All other aspects of the product are functioning as normal.

We are currently investigating this issue.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

This incident has been resolved.

As of 10:30AM PDT, the issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

As of 11:00 am UTC, the issue experienced by some customers regarding degraded UI performance has been addressed and functionality has been restored. We are currently monitoring the performance closely. The next update will be provided as new information is available.

We are aware of an issue with BlazeMeter and are presently investigating. We will post an update here as soon as we have more information.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are aware of an issue with BlazeMeter and are presently investigating. We will post an update here as soon as we have more information.

As of 12:00 PM UTC, the issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

We are aware of an issue with BlazeMeter and are presently investigating. We will post an update here as soon as we have more information.

We have not observed any reoccurrences of the issue since the fix was applied so we are marking the incident as Resolved now.

The issue experienced by some customers has been addressed and functionality has been restored. We are currently monitoring the performance closely. The next update will be provided as new information is available.

As of TIME_STAMP UTC, the issue experienced by some customers has been addressed and functionality has been restored. We are currently monitoring the performance closely. The next update will be provided as new information is available.

We are continuing to work on a fix

The Issue with BlazeMeter performance test results has been Identified and the team are still investigating the issue.

We are aware of an issue with BlazeMeter and are presently investigating. We will post an update here as soon as we have more information.

A fix has been applied to reinstate the plans of any teams who had not already written in to have the plan re-enabled. For the affected users who had not written in, another communication will be sent out explaining what the fix did. If you have any additional questions then please reach out to support.

We have identified the cause of IMPACT experienced by some customers and are currently working on mitigation. If you observe that your team has been incorrectly reset to Free and has not been re-enabled yet then please open a support ticket. If you have never opened a support ticket before then please take a moment to review this guide for instructions on how to do so: https://help.blazemeter.com/docs/answers/support-ticket.html The next update will be provided as new information is available.

We have identified an issue where some API Monitoring (Runscope) teams were reverted to a Free plan incorrectly. We are in the process of re-enabling the teams that we have identified as having been affected by this issue. If you observe that your team has been incorrectly reset to Free and has not been re-enabled yet then please open a support ticket. If you have never opened a support ticket before then please take a moment to review this guide for instructions on how to do so: https://help.blazemeter.com/docs/answers/support-ticket.html

This incident has been resolved.

As of now, the issue experienced by some customers has been addressed and functionality has been restored. We are currently monitoring the performance closely. The next update will be provided as new information is available.

The issue has been identified and a fix is being implemented.

Users may experience issues while opening/editing their tests (404 "hiccup error", not for all tests - only Azure) We are aware of some customers experiencing IMPACT. We are currently investigating the cause of this issue and will provide updates as new information becomes available. All other aspects of the product are functioning as normal.

We are aware of an issue with BlazeMeter Platform, i.e. components that are powered by Azure. We are investingating this and we will post an update here as soon as we have more information.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

API Monitoring users are receiving agent-expired notifications from https://stage.runscope.com instead of https://www.runscope.com where the same tests do not fail because of agent-expired problems

The issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

The issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

The issue experienced by some customers has been addressed and functionality has been restored. We are currently monitoring the performance closely. The next update will be provided as new information is available.

We have identified the cause of IMPACT experienced by some customers and we are currently working on a fix that will be deployed to production once it is verified. The next update will be provided as new information is available.

We have identified the cause of IMPACT experienced by some customers and are currently working on a fix that will deployed. The next update will be provided as new information is available.

We have identified the cause of IMPACT experienced by some customers and are currently working on mitigation. The next update will be provided as new information is available.

We have identified the cause of the inability of restoring archived reports experienced by some customers and are currently working on mitigation. Customers with plans that allow unlimited report retention can continue to use the API to recover archived reports until this issue is finally resolved. The next update will be provided as new information is available.

We are aware that some customers are not able to restore archived reports. We are still investigating the cause of this issue and will provide updates as new information becomes available. It is still possible to use the API provided to manually restore any reports until the root cause of the issue is determined and a fix implemented. All other aspects of the product are functioning as normal.

We are aware of an issue with restoring archived reports in BlazeMeter and are still investigating. As a workaround, for accounts with Plans that allow unlimited reporting, archived reports can be manually restored by using the following API, until this issue is resolved: curl -X 'POST' \ 'https://a.blazemeter.com/api/v4/masters/{masterId}/restore-reports' \ -H 'accept: application/json' \ -d '' \ --user '{api_key}:{api_secret}' where {masterId} is the number from the URL of the report as seen in the browser. The next update will be provided as new information becomes available.

We are aware of an issue with BlazeMeter and are presently investigating. As a workaround, for accounts with Plans that allow unlimited reporting, archived reports can be manually restored by using the following API, until this issue is resolved: curl -X 'POST' \ 'https://a.blazemeter.com/api/v4/masters/{masterId}/restore-reports' \ -H 'accept: application/json' \ -d '' \ --user '{api_key}:{api_secret}' where {masterId} is the number from the URL of the report as seen in the browser. We will post an update here as soon as we have more information.

This incident has been resolved.

We've observed improved stability in the system with both the slowdowns in load times and the sporadic logouts. We are continuing to monitor for any reoccurrence of the issues at this time.

The sporadic slowness and logouts are still occurring and we are continuing to investigate the issue at this time. We will provide an update as soon as we have more information.

We are aware of an issue with BlazeMeter performance tests and are presently investigating. The issues are primarily causing slowness in BlazeMeter as well as logging users out unexpectedly. We are continuing to investigate and will provide an update as soon as we have more information

This incident has been resolved.

This Sunday, August 13th we will be performing scheduled maintenance on our Production systems. The maintenance window is 2 hours long and will take place between 1:00 AM-3:00 AM EDT. During this maintenance, there will be a 20-30 minute window where user logins will not be possible. Existing user sessions will not be affected and scheduled tests will run as normal. You’ll receive a separate notification when the maintenance window starts. Your BlazeMeter team

This incident has been resolved.

A fix has been deployed to Production and is working as we have observed so far. We are continuing to monitor the situation for any reoccurrences of the issue. We will provide another update soon.

The issue editing performance tests affects new and old tests alike, whenever attempting to change something on the test a message in the lower-right corner "Failed to update test" is displayed. This issue is only with JMX tests where the threads value in the JMX itself is not defined by a literal integer but is defined by value like a UDV or property. Work on the fix for this issue is still ongoing at this time. We will provide another update once we have more information.

The issue editing performance tests affects new and old tests alike, whenever attempting to change something on the test a message in the lower-right corner "Failed to update test" is displayed. This issue is only with JMX tests where the threads value in the JMX itself is not defined by a literal integer but is defined by value like a UDV or property. The issue has been identified and a fix is being implemented.

We are aware of an issue with BlazeMeter when editing Performance tests and are presently investigating. We will post an update here as soon as we have more information.

As of 10:16 UTC, the issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

A Fix has been implemented and we are monitoring the platform

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We are aware of an issue with BlazeMeter and are presently investigating. We will post an update here as soon as we have more information.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have identified the cause of IMPACT experienced by some customers and are currently working on mitigation. We are continuing to investigate instances of slowness and are testing a fix he next update will be provided as new information is available.

Functioning as expected in most cases. We are continuing to investigate instances of slowness and are testing a fix; extra resources allocated to make up the difference in the meantime.

Continuing to investigate, working as expected in most cases. Some slowdowns reported, extra resources allocated to make up the difference in the meantime.

There are still issues with this. We are continuing to investigate....

This incident should be resolved at this time.

There has been a fix released which we believe resolves the issue with API Monitoring (Runscope) we will continue to monitor the situation and if the resolution holds we will consider this issue resolved.

We have identified the cause of IMPACT experienced by some customers and are currently working on mitigation. A temporary fix has been applied but we are yet to resolve and deploy the fix. The next update will be provided as new information is available.

We are continuing to work on a fix for this issue.

The issue has been identified.

We are aware of an issue with API Monitoring (Runscope) and are presently investigating. We will post an update here as soon as we have more information.

The issues with Mock services has been addressed and functionality has been restored. This incident is now resolved.

The Timeout issue has been resolved but we are still investigating an issue when deploying mock service to EU West

We have identified the cause of the Mock service issue and are currently working on mitigation. The next update will be provided as new information is available.

We are aware of an issue with BlazeMeter and are presently investigating. We will post an update here as soon as we have more information.

Incident Test Complete

BlazeMeter Incident Test - Please Ignore

The issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

We are aware of an issue with BlazeMeter and are presently investigating. We will post an update here as soon as we have more information.

The incident has been resolved.

The issue has been identified and a fix is being implemented.

We are aware of an issue with BlazeMeter Functional tests not running in the US East location and are presently investigating. We will post an update here as soon as we have more information.

This incident has been resolved.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We are aware of an issue with BlazeMeter tests - both Functional and Performance - not validating and/or starting, and are presently investigating. We will post an update here as soon as we have more information.

The issue has been identified and a fix has been deployed. The incident is now closed.

A fix has been implemented and put in place, we are monitoring the situation to make sure the issue has resolved.

We are continuing to work on a fix for this issue.

We have identified the problem and are in the process of testing a fix.

The Mock Service issue has been identified and a fix is in progress

We are aware of an issue with BlazeMeter Mock Services and are presently investigating. We will post an update here as soon as we have more information.

The issue should be resolved.

The cause of the issue has been identified and we are monitoring the situation to make sure the issue is resolved.

The issue with test failing to start intermittently and unexpected logouts is still ongoing and under investigation. All other aspects of the product are functioning as normal.

The issue with test failing to start intermittently and unexpected logouts is still ongoing and under investigation. All other aspects of the product are functioning as normal.

The issue with test failing to start intermittently and unexpected logouts is still ongoing and under investigation. All other aspects of the product are functioning as normal.

The issue with test failing to start intermittently and unexpected logouts is still ongoing and under investigation. All other aspects of the product are functioning as normal.

A fix has been implemented and we are monitoring the results for now. The next update will be provided as new information is available.

The issue with test failing to start intermittently and unexpected logouts is still ongoing and under investigation.

The issue with test failing to start intermittently and unexpected logouts is still ongoing and under investigation.

We are aware of some customers experiencing IMPACT. The issue is mainly observed for tests utilizing test data. We are currently investigating the cause of this issue and will provide updates as new information becomes available. All other aspects of the product are functioning as normal.

A fix has been implemented and we are monitoring the results for now.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate the cause of this issue and will provide further updates as new information becomes available.

We are continuing to investigate the cause of this issue and will provide further updates as new information becomes available.

We are continuing to investigate the cause of this issue and will provide further updates as new information becomes available.

We are continuing to investigate of the cause of this issue and will provide further updates as new information becomes available.

We are continuing to investigate this issue.

We are aware of some customers experiencing issues with tests failing to start intermittently due to timeouts. We are continuing with the investigation of the cause of this issue and will provide updates as new information becomes available.

We are aware of some customers experiencing issues with tests failing to start intermittently due to timeouts. We are currently investigating the cause of this issue and will provide updates as new information becomes available. All other aspects of the product are functioning as normal.

The issue experienced by some customers has been addressed and functionality has been restored. We are currently monitoring the performance closely. The next update will be provided as new information is available.

We are aware of an issue with BlazeMeter tests not starting and displaying the following error "Timeout occurred while trying to retrieve Mock Configuration / Test Data" the team are currently investigating. We will post an update here as soon as we have more information.

This incident has been resolved.

The issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

The issue experienced by some customers has been addressed and functionality has been restored. We are currently monitoring the performance closely. The next update will be provided as new information is available.

The ongoing issue with Mock Services is also causing some Functional and Performance tests to not start with the following error - Timeout occurred while trying to retrieve Mock Configuration / Test Data and random logouts. R&D are still investigating the issue.

We are aware of an issue with BlazeMeter Mock Services and are presently investigating. We will post an update here as soon as we have more information.

The incident has been resolved.

We are continuing to investigate this issue.

We are aware of some customers experiencing IMPACT. We are currently investigating the cause of this issue and will provide updates as new information becomes available. All other aspects of the product are functioning as normal.

As of 21:10 UTC, the delayed notifications issue experienced by customers has been addressed and functionality has been restored. This incident is now resolved.

As of 20:30 UTC, the issue with delayed notifications experienced by customers has been addressed and functionality has been restored. We are currently monitoring the performance closely. The next update will be provided as new information is available.

We have identified the cause of the notification delays experienced by customers and are currently working on mitigation. The next update will be provided as new information is available.

API Monitoring notifications (webhooks, email, slack) are being delivered with some delay. We are aware of the issue and are currently investigating.

A work around has been put in place to allow BlazeMeter support tickets to be created. This incident is now resolved.

We are aware of an issue when creating support tickets from the BlazeMeter help Center and are presently investigating. We will post an update here as soon as we have more information. If you need to create a support ticket please email support@blazemeter.com

This incident has been resolved.

As of 10:15pm UTC, the intermittent 500 errors experienced by customers has been addressed and functionality has been restored. We are currently monitoring the performance closely. The next update will be provided as new information is available.

We are still investigating the intermittent 500 errors, and we will provide an update when new information or a final solution is implemented.

We are still investigating the intermittent 500 errors, and we will provide an update when new information or a final solution is implemented.

We are still investigating the intermittent 500 errors, and we will provide an update when new information or final solution implemented.

We have identified the cause of the intermittent 500 errors experienced by some customers and are currently working on mitigation. The next update will be provided as new information is available.

We have identified the cause of the intermittent 500 errors experienced by some customers and are currently working on mitigation. The next update will be provided as new information is available.

The issue experienced by some customers with 500 errors has been addressed and functionality has been restored. We are currently monitoring the performance closely. The next update will be provided as new information is available.

We are continuing to work on a Fix for this issue. The next update will be provided as new information is available.

We have identified the cause of the intermittent 500 errors experienced by some customers and are currently working on mitigation. The next update will be provided as new information is available.

The issue experienced by some customers has been addressed and functionality has been restored. We are currently monitoring the performance closely. The next update will be provided as new information is available.

We are aware of an issue with BlazeMeter API Monitoring and are presently investigating. We will post an update here as soon as we have more information.

The issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

We are aware of an issue with API Monitoring and are presently investigating. We will post an update here as soon as we have more information.

The issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

The issue experienced by some customers has been addressed and we are now processing the backlog of messages caused by the incident. We are currently monitoring the performance closely. The next update will be provided as new information is available.

We have identified the cause of the API Monitoring Agent issue experienced by some customers and are currently working on mitigation. The next update will be provided as new information is available.

We are aware of an issue with BlazeMeter and are presently investigating. We will post an update here as soon as we have more information.

The incident has been resolved. Mock Services are now fully available in all locations.

We are continuing to investigate this issue. Cloud based mock services in the US - Virginia location are not running and cannot be deployed. Customers can use EU West London location to deploy and run their mock services.

We are continuing to investigate this issue.

We are aware of an issue where cloud based Mock Services are not running and are failing to be deployed. Engineering is aware and working on the issue.

Deployment of a new service backed up the processing queue causing the execution delay. Additional resources were added to alleviate the back-up. This issue has been resolved.

We are aware of an issue with BlazeMeter API Monitoring where API tests with incoming requests are experiencing a delay in execution. We are presently investigating and will post an update here as soon as we have more information.

This incident has been resolved.

As of 5:55 UTC, the issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

We are continuing to investigate this issue.

As of 5:54 UTC, the issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.

We are aware of an issue with BlazeMeter and are presently investigating. We will post an update here as soon as we have more information.

This incident has been resolved.

We are continuing to investigate this issue. Please note that users may encounter issues validating and running performance tests.

We are continuing to investigate this issue.

We are aware of an issue with BlazeMeter and are presently investigating. We will post an update here as soon as we have more information.

This incident has been resolved.

We are continuing to investigate this issue.

We are experiencing issues with tests completion at several locations from APAC and USA, due to client connections issues.

This incident has been resolved

The issue has been identified and our engineering team are working on a fix

We are aware of an issue with BlazeMeter booting performance tests and are presently investigating. We will post an update here as soon as we have more information.

The incident has been resolved, The instructions in the Incident should be used to correct any agents that have been stuck in the Download state since Sunday August 21st.

We have identified the issue with some of the on premise BlazeMeter agents that have auto updated enabled being in a stuck Download state since Sunday 21st August. For any agents that are affected, and due to the nature of the failure, the only method to resolve this issue involves the agent being manually removed and redeployed using the procedure below : Log in to the machine containing the agent and run the following command to list all the containers: $ sudo docker ps -a Remove the bzm-crane-<shipId> container with the following command (You need the container ID from the previous step to run this command): $ sudo docker rm -f <Container_ID> To remove the images for the BlazeMeter Crane, list out all the images on the machine using the following command: $ sudo docker images Identify the blazemeter/crane image id for version 3.6.8 and use the following command to delete the docker image $sudo docker rmi <Image_ID> Download the latest version of the crane 3.6.9 by running this command $sudo docker pull gcr.io/verdant-bulwark-278/blazemeter/crane:3.6.9 Tag the newly downloaded image $sudo docker tag 3f96b07b8382 blazemeter/crane:3.6.9 $sudo docker tag 3f96b07b8382 blazemeter/crane:latest Run the docker run command to start the agent with the relevant environment variables (if applicable for you) and wait for the agent to enter the idle state If you have any additional issues please contact BlazeMeter Support.

We are aware of an issue with BlazeMeter agent that have auto updated enabled being in a stuck Download state since Sunday. We are working to resolve the issue. For further information please contact BlazeMeter support.