BlazeMeter Outage History

BlazeMeter is up right now

BlazeMeter had 9 outages in the last 2 years totaling 170h 43m of downtime — averaging 0.4 incidents per month.

There were 9 BlazeMeter outages since October 3, 2025 totaling 170h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.blazemeter.com

Notice October 1, 2026

Potential Slowness in BlazeMeter UI

Detected by Pingoru
Oct 01, 2026, 12:30 PM UTC
Resolved
Oct 01, 2026, 02:15 PM UTC
Duration
1h 45m
Affected: BlazeMeter Platform
Timeline · 2 updates
  1. monitoring Oct 01, 2026, 12:30 PM UTC

    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.

  2. resolved Oct 01, 2026, 02:15 PM UTC

    The R&D has completed their testing now. We did observe some brief slowness in the system during the testing, but we have restored the system to normal functionality now. Any running tests should still have completed as normal, but if you observe any issues with your tests that ran during this period then please reach out to Support.

Read the full incident report →

Critical September 18, 2026

Slowness in BlazeMeter

Detected by Pingoru
Sep 18, 2026, 01:09 PM UTC
Resolved
Sep 18, 2026, 02:24 PM UTC
Duration
1h 15m
Affected: BlazeMeter Platform
Timeline · 3 updates
  1. investigating Sep 18, 2026, 01:09 PM UTC

    We are currently investigating an issue that is causing extreme slowness in the BlazeMeter UI. The R&D team is working to resolve the issue now and we will provide an update as soon as possible.

  2. monitoring Sep 18, 2026, 01:17 PM UTC

    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.

  3. resolved Sep 18, 2026, 02:24 PM UTC

    We have not observed anymore slowness in the UI as we've monitored the resolution of the issue. We are resolving the incident now.

Read the full incident report →

Notice September 15, 2026

Load Engine Availability Issues in Google, Iowa

Detected by Pingoru
Sep 15, 2026, 02:59 PM UTC
Resolved
Sep 15, 2026, 04:45 PM UTC
Duration
1h 46m
Affected: Performance Testing
Timeline · 2 updates
  1. monitoring Sep 15, 2026, 02:59 PM UTC

    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.

  2. resolved Sep 15, 2026, 04:45 PM UTC

    The acute issues with capacity in the Google, Iowa location have been resolved for the time being. We are still working with Google to get them to provide a permanent solution. We still recommend avoiding the use of the Google, Iowa location for the time being.

Read the full incident report →

Notice May 26, 2026

Capacity Issues with Google Public Locations

Detected by Pingoru
May 26, 2026, 03:52 PM UTC
Resolved
Jun 01, 2026, 04:27 PM UTC
Duration
6d
Affected: Functional TestingPerformance Testing
Timeline · 3 updates
  1. identified May 26, 2026, 03:52 PM UTC

    There are currently capacity issues with Google Cloud Platform that are causing some tests utilizing Google public locations to not be able to provision enough engines while in the Booting phase. If you have tests that are encountering these issues, you can temporarily use AWS and Azure public locations instead.

  2. monitoring May 27, 2026, 01:18 PM UTC

    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.

  3. resolved Jun 01, 2026, 04:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 7, 2026

New User Registrations are currently broken

Detected by Pingoru
May 07, 2026, 09:05 PM UTC
Resolved
May 08, 2026, 10:42 AM UTC
Duration
13h 37m
Affected: BlazeMeter Platform
Timeline · 2 updates
  1. investigating May 07, 2026, 09:05 PM UTC

    There is currently an issue that is preventing the registration of new users to BlazeMeter. Users who are attempting to register will encounter an unexpected error when submitting the form on https://www.blazemeter.com/signup We are investigating the issue now and will provide an update as soon as possible

  2. resolved May 08, 2026, 10:42 AM UTC

    The incident with new user registration has been resolved

Read the full incident report →

Minor March 30, 2026

Issue with JMeter Plugins Repository Certificate

Detected by Pingoru
Mar 30, 2026, 02:51 PM UTC
Resolved
Mar 30, 2026, 06:29 PM UTC
Duration
3h 38m
Affected: Performance Testing
Timeline · 3 updates
  1. identified Mar 30, 2026, 02:51 PM UTC

    There is an issue with the Certificate of the JMeter Plugins Repository that is causing some tests to fail to start. The team is currently working on implementing a fix for the issue and we will provide updates as we receive them. In the meantime, there is a workaround that can be used to point affected tests at the fallback repository. The following can be implemented in any affected tests: JMeter (add the following in jmeter.properties or user.properties files): # BlazeMeter JMeter Plugins Mirror jpgc.repo.sendstats=False jpgc.repo.address=https://jmeter-plugins-fallback.blazemeter.com/jmeter-plugins.json Taurus (add the following to YAML file): modules: jmeter: properties: jpgc.repo.sendstats: false jpgc.repo.address: https://jmeter-plugins-fallback.blazemeter.com/jmeter-plugins.json

  2. monitoring Mar 30, 2026, 05:01 PM UTC

    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.

  3. resolved Mar 30, 2026, 06:29 PM UTC

    Our tests are continuing to run as expected and we have received confirmation from other sources as well. At this time, we are resolving the incident.

Read the full incident report →

Minor January 21, 2026

Some Dedicated IPs Encountering Issues when Running Tests

Detected by Pingoru
Jan 21, 2026, 02:36 PM UTC
Resolved
Jan 21, 2026, 03:50 PM UTC
Duration
1h 14m
Affected: Performance Testing
Timeline · 3 updates
  1. identified Jan 21, 2026, 02:36 PM UTC

    We have identified an issue with Dedicated IPs that is causing some of them to not be able to be utilized for test runs at the moment. When attempting to start a test with Dedicated IPs, you may see an error with the text "Bad Request - Failed to create master" that prevents the test from starting. This issue does not affect all IPs, some may still be functioning properly. The R&D team is working on resolving the issue for any affected IPs now. We will provide additional updates as work on the fix progresses

  2. monitoring Jan 21, 2026, 03:09 PM UTC

    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.

  3. resolved Jan 21, 2026, 03:50 PM UTC

    The fixes that have been applied are working as expected and teams should be able to use their Dedicated IPs again without issue. We are resolving the incident at this time

Read the full incident report →

Notice October 7, 2025

mock.blazemeter.com was briefly displaying a 404 when navigating to it.

Detected by Pingoru
Oct 07, 2025, 03:17 PM UTC
Resolved
Oct 07, 2025, 04:33 PM UTC
Duration
1h 16m
Affected: Service Virtualization
Timeline · 2 updates
  1. monitoring Oct 07, 2025, 03:17 PM UTC

    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.

  2. resolved Oct 07, 2025, 04:33 PM UTC

    We are resolving the incident now as the issue has been fixed for some time and we have given time for users to see the message. As a reminder, if you Services are in Failed state then you just need to restart them and they should again be functioning as expected.

Read the full incident report →

Minor October 3, 2025

The US Illinois Location for API Monitoring is offline

Detected by Pingoru
Oct 03, 2025, 09:17 PM UTC
Resolved
Oct 03, 2025, 10:52 PM UTC
Duration
1h 35m
Affected: API Monitoring (Runscope)
Timeline · 3 updates
  1. investigating Oct 03, 2025, 09:17 PM UTC

    We are currently experiencing an issue with the US Illinois location in API Monitoring. This is causing tests run on that location to end with errors, primarily with the message "System Error - Test Expired". All other locations are currently functioning as normal. To avoid false errors in your tests, please turn disable the US Illinois location for the time being.

  2. identified Oct 03, 2025, 10:00 PM UTC

    Our R&D team has identified the cause of the issue and has applied an initial fix. We are seeing our tests pass on the US Illinois location now. However we will continue to monitor the issue to ensure continued stability on the US Illinois location for API Monitoring.

  3. resolved Oct 03, 2025, 10:52 PM UTC

    Our tests have continued to run successfully from the US Illinois location. At this time you may resume utilizing the US Illinois location in your tests if you would like. We are closing the incident now.

Read the full incident report →