BlazeMeter Outage History

BlazeMeter is up right now

BlazeMeter had 12 outages in the last 2 years totaling 190h 28m of downtime — averaging 0.5 incidents per month.

There were 12 BlazeMeter outages since July 10, 2025 totaling 190h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.blazemeter.com

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: Mock Services
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 →

Minor September 24, 2025

DATA Processing delays in Blazemeter

Detected by Pingoru
Sep 24, 2025, 11:29 AM UTC
Resolved
Sep 24, 2025, 04:27 PM UTC
Duration
4h 58m
Affected: BlazeMeter Platform
Timeline · 4 updates
  1. investigating Sep 24, 2025, 11:29 AM UTC

    We are currently investigating the DATA Processing delays with Blazemeter. Tests are experiencing a delay in start/stop or, in some cases, restoring test reports.

  2. identified Sep 24, 2025, 12:51 PM UTC

    We have identified the issue in backend that is causing the data processing delays. The team is working to implement a fix to resolve the issue at this time. We will provide more updates as the fix progresses.

  3. monitoring Sep 24, 2025, 03:13 PM UTC

    A fix for the issue has been applied in the backend and we are seeing our tests run normally now as well. We will continue to monitor the issue for now to check for any reoccurrence.

  4. resolved Sep 24, 2025, 04:27 PM UTC

    We are no longer seeing the data processing delays with our tests at this time. We are resolving the incident now, but will continue to monitor for any potentially lingering issues.

Read the full incident report →

Minor September 11, 2025

Data Processing Delays Causing Long Test Shutdown Times

Detected by Pingoru
Sep 11, 2025, 10:10 PM UTC
Resolved
Sep 11, 2025, 11:56 PM UTC
Duration
1h 46m
Affected: Performance Testing
Timeline · 3 updates
  1. investigating Sep 11, 2025, 10:10 PM UTC

    We are currently experiencing an issue with our backend systems that is causing data processing delays. Tests may take an extended amount of time to shutdown due to this. We are actively working on resolving the situation now.

  2. identified Sep 11, 2025, 10:58 PM UTC

    We have identified the cause of the issue that is creating the data processing delays and a fix is being implemented now. We will provide updates as progress on the fix continues.

  3. resolved Sep 11, 2025, 11:56 PM UTC

    The fix for the data processing issue has been deployed now and we are seeing improvement in our tests as well. At this time we are resolving the incident.

Read the full incident report →

Critical July 25, 2025

Tests Stuck in Pending/Booting status

Detected by Pingoru
Jul 25, 2025, 05:36 PM UTC
Resolved
Jul 25, 2025, 09:35 PM UTC
Duration
3h 59m
Affected: Functional TestingPerformance Testing
Timeline · 4 updates
  1. investigating Jul 25, 2025, 05:36 PM UTC

    We are aware of an issue that is causing tests to get stuck in Pending/Booting status. We are currently investigating the cause of the issue and will provide updates as soon as possible.

  2. identified Jul 25, 2025, 07:39 PM UTC

    A fix has been implemented and we are seeing our tests being able to run again in many cases. The R&D team is continuing to work to restore full functionality so some tests may still experience prolonged booting times.

  3. monitoring Jul 25, 2025, 08:26 PM UTC

    Additional work has been done to further ensure the stability of tests on BlazeMeter. Our tests continue to run as expected as well. At this time we are moving the incident to Monitoring and we will continue to observe the system for any irregularities.

  4. resolved Jul 25, 2025, 09:35 PM UTC

    Tests have continued to run as expected again while we have been monitoring the system. At this time we are resolving the incident.

Read the full incident report →

Critical July 25, 2025

Blazemeter Tests not starting, Test Reports not accessible

Detected by Pingoru
Jul 25, 2025, 07:13 AM UTC
Resolved
Jul 25, 2025, 01:05 PM UTC
Duration
5h 51m
Affected: BlazeMeter PlatformFunctional TestingPerformance Testing
Timeline · 5 updates
  1. investigating Jul 25, 2025, 07:13 AM UTC

    We are aware of an issue with Blazemeter Tests not executing and are Presently Investigating, We will post an update to this status page as soon as we have more information.

  2. identified Jul 25, 2025, 08:07 AM UTC

    We are aware of an issue with Blazemeter Tests not executing, and it has been identified. We are working to fix this issue.

  3. identified Jul 25, 2025, 09:24 AM UTC

    We are aware of an issue with Blazemeter Tests not executing, and it has been identified. We are working to fix this issue. The next update will be provided as new information is available.

  4. monitoring Jul 25, 2025, 10:57 AM UTC

    The issue with Blazemeter Tests not executing & missing report data 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.

  5. resolved Jul 25, 2025, 01:05 PM UTC

    We've received confirmation that these issues affecting test executions and report data have been fixed. At this time we are resolving the incident.

Read the full incident report →

Critical July 14, 2025

Performance and Functional tests are not starting, getting stuck in validation phase.

Detected by Pingoru
Jul 14, 2025, 03:36 AM UTC
Resolved
Jul 14, 2025, 06:37 AM UTC
Duration
3h 1m
Affected: Functional TestingPerformance Testing
Timeline · 4 updates
  1. investigating Jul 14, 2025, 03:36 AM UTC

    We are aware of an issue with tests not starting and are currently investigating.

  2. investigating Jul 14, 2025, 05:32 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 14, 2025, 06:36 AM UTC

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

  4. resolved Jul 14, 2025, 06:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 10, 2025

Azure engines are not initializing

Detected by Pingoru
Jul 10, 2025, 07:22 AM UTC
Resolved
Jul 10, 2025, 12:17 PM UTC
Duration
4h 55m
Affected: Performance Testing
Timeline · 5 updates
  1. investigating Jul 10, 2025, 07:22 AM UTC

    We are currently investigating this issue.

  2. identified Jul 10, 2025, 07:49 AM UTC

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

  3. monitoring Jul 10, 2025, 10:40 AM UTC

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

  4. monitoring Jul 10, 2025, 10:41 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jul 10, 2025, 12:17 PM UTC

    This incident has been resolved.

Read the full incident report →