Blazemeter の障害履歴

1. 2026年10月20日 13:39 UTCidentified

   現在ロンドン、Googleのサービスの場所に影響を及ぼしているGoogle Cloudの停電があります。 問題は、主にロンドン、Googleの場所で実行されている仮想サービスに影響を与える. 現在、その場所で設定されているサービスは起動できません。また、テストの実行時に問題が発生します。 ロンドンのパフォーマンステストでは、Googleのロケーションが機能していますが、その場所で実行されているテストは、エンジンのプロビジョニングの問題が発生する可能性があります。 Googleが事件を解決するまで、この場所を回避することをお勧めします。 Googleから受け取るように、アップデートを配信します.

2. 2026年10月20日 16:04 UTCresolved

   Google 側のインシデントが解決しました。 R&Dチームによる修正が必要になったリンダリングの問題がありました。 その修正は、EU西(ロンドン、Google)の場所が再び利用可能になりました.

公式のインシデント更新を自動翻訳しています。

1. 2026年10月13日 12:40 UTCmonitoring

   R&D チームは、BlazeMeter UI で遅くなる可能性があるバックエンドシステムのテストを行っています。 システムの監視を行い、試験により発生する速度が遅くなると、通常の機能に戻ります。 問題が観察されると、サポートチームにご連絡ください.

2. 2026年10月13日 13:26 UTCresolved

   今回テストを完了しました。 UIに若干の低迷がありましたが、今では機能が正常に戻りました。 実行中のテストは、通常どおり完了する必要がありますが、問題が観察されている場合は、サポートチームにお問い合わせください.

公式のインシデント更新を自動翻訳しています。

1. 2026年10月7日 12:20 UTCmonitoring

   R&D チームは、BlazeMeter UI で遅くなる可能性があるバックエンドシステムのテストを行っています。 システムの監視を行い、試験により発生する速度が遅くなると、通常の機能に戻ります。 問題が観察されると、サポートチームにご連絡ください.

2. 2026年10月7日 13:06 UTCresolved

   R&Dチームは、現在テストを完了し、システムが通常の機能に戻りました.

公式のインシデント更新を自動翻訳しています。

1. 2026年10月1日 12:30 UTCmonitoring

   R&D チームは、BlazeMeter UI で遅くなる可能性があるバックエンドシステムのテストを行っています。 システムの監視を行い、試験により発生する速度が遅くなると、通常の機能に戻ります。 問題が観察されると、サポートチームにご連絡ください.

2. 2026年10月1日 14:15 UTCresolved

   R&Dは、現在、テストを完了しました。 試験中にシステムに若干の短時間を観察しましたが、システムを正常に動作させるようになりました。 実行中のテストは、通常どおり完了する必要がありますが、この期間中に実行されたテストで問題が発生した場合は、サポートに手を差し伸べてください.

公式のインシデント更新を自動翻訳しています。

1. 2026年9月18日 13:09 UTCinvestigating

   現在、BlazeMeter UI で極端な速度を引き起こしている問題について調査しています。 R&Dチームは、問題解決に取り組んでおり、できるだけ早くアップデートを提供します.

2. 2026年9月18日 13:17 UTCmonitoring

   R&Dチームは、減速の原因を特定し、BlazeMeterの応答性を向上させるための措置を講じています。 側面からUIのパフォーマンスが向上しました。 引き続き、問題の監視を行い、遅さが再発されないようにします.

3. 2026年9月18日 14:24 UTCresolved

   問題の解決を監視したため、UI ではもう遅くなっていませんでした。 今の事件を解決しています.

公式のインシデント更新を自動翻訳しています。

1. 2026年9月15日 14:59 UTCmonitoring

   Google 側の容量の問題のため、Iowa、Google の公共の場所にあるエンジンの可用性の問題があります。 この場所を使用してのテストは、起動時間が遅くなるか、正しく起動できません。 Google、Iowa の場所、および AWS または Azure の使用を時間内に使用することを避けることを推奨します.

2. 2026年9月15日 16:45 UTCresolved

   Google の容量の急激な問題、Iowa の場所は時間のために解決されました。 永続的に解決するためにGoogleと連携しています。 Google、Iowaの場所の使用を避けることをお勧めしています.

公式のインシデント更新を自動翻訳しています。

1. 2026年5月26日 15:52 UTCidentified

   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. 2026年5月27日 13:18 UTCmonitoring

   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. 2026年6月1日 16:27 UTCresolved

   This incident has been resolved.

1. 2026年5月7日 21:05 UTCinvestigating

   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. 2026年5月8日 10:42 UTCresolved

   The incident with new user registration has been resolved

1. 2026年3月30日 14:51 UTCidentified

   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. 2026年3月30日 17:01 UTCmonitoring

   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. 2026年3月30日 18:29 UTCresolved

   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.

1. 2026年1月21日 14:36 UTCidentified

   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. 2026年1月21日 15:09 UTCmonitoring

   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. 2026年1月21日 15:50 UTCresolved

   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

1. 2025年10月7日 15:17 UTCmonitoring

   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. 2025年10月7日 16:33 UTCresolved

   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.

1. 2025年10月3日 21:17 UTCinvestigating

   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. 2025年10月3日 22:00 UTCidentified

   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. 2025年10月3日 22:52 UTCresolved

   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.

1. 2025年9月24日 11:29 UTCinvestigating

   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. 2025年9月24日 12:51 UTCidentified

   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. 2025年9月24日 15:13 UTCmonitoring

   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. 2025年9月24日 16:27 UTCresolved

   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.

1. 2025年9月11日 22:10 UTCinvestigating

   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. 2025年9月11日 22:58 UTCidentified

   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. 2025年9月11日 23:56 UTCresolved

   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.

1. 2025年7月25日 17:36 UTCinvestigating

   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. 2025年7月25日 19:39 UTCidentified

   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. 2025年7月25日 20:26 UTCmonitoring

   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. 2025年7月25日 21:35 UTCresolved

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

1. 2025年7月25日 7:13 UTCinvestigating

   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. 2025年7月25日 8:07 UTCidentified

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

3. 2025年7月25日 9:24 UTCidentified

   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. 2025年7月25日 10:57 UTCmonitoring

   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. 2025年7月25日 13:05 UTCresolved

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

1. 2025年7月14日 3:36 UTCinvestigating

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

2. 2025年7月14日 5:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025年7月14日 6:36 UTCmonitoring

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

4. 2025年7月14日 6:37 UTCresolved

   This incident has been resolved.

1. 2025年7月10日 7:22 UTCinvestigating

   We are currently investigating this issue.

2. 2025年7月10日 7:49 UTCidentified

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

3. 2025年7月10日 10:40 UTCmonitoring

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

4. 2025年7月10日 10:41 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2025年7月10日 12:17 UTCresolved

   This incident has been resolved.

1. 2025年6月23日 18:28 UTCidentified

   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.

2. 2025年6月23日 22:25 UTCresolved

   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.

1. 2025年6月12日 18:46 UTCinvestigating

   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.

2. 2025年6月12日 19:31 UTCinvestigating

   There is currently an outage in the Google Cloud Platform Access Management Service. This is impacting performance testing, at the present time performance testing is not functional. Performance Tests that run on AWS, Azure, or Private Locations will run, but are not currently producing data to populate in the reports due to services hosted on GCP. Functional Test, Virtual Services, and API Monitoring appear unaffected by this. We are waiting for an ETA on remediation from GCP.

3. 2025年6月12日 20:43 UTCmonitoring

   Google Cloud has applied a fix and we are seeing some improvement in the availability of Performance Tests. Tests can now run and produce data in most cases on GCP, AWS, Azure, and Private Locations. Test boot times are longer than usual in most cases and there is still some instability in the report data. We are continuing to monitor the system and will provide updates as we know more.

4. 2025年6月12日 21:41 UTCmonitoring

   We are seeing further improved stability in our services as Google Cloud comes back online. Most tests are running as they did previously, though you may still see some delays in test booting & shutdown times. We are continuing to monitor the system and will provide another update soon.

5. 2025年6月12日 22:33 UTCinvestigating

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

6. 2025年6月12日 22:37 UTCresolved

   As of this time functionality has been restored to Performance Tests and we are resolving the incident.