Istoricul incidentelor Blazemeter

1. 20 octombrie 2026 la 13:39 UTCidentified

   Există o pană Google Cloud care afectează în prezent Londra, Google locație pentru serviciile noastre. Problema afectează în primul rând Virtual Services care sunt difuzate pe Londra, Google locație. Serviciile care sunt configurate cu acea locaţie vor eşua în prezent pentru a începe, şi va experimenta probleme atunci când rulează teste împotriva lor. Testele noastre de performanță din Londra, Google Location funcționează în prezent, dar testele fiind efectuate în acea locație ar putea experimenta probleme cu alimentarea motorului. Vă recomandăm să evitați această locație până când Google rezolvă incidentul. Vom oferi actualizări în timp ce le primim de pe Google.

2. 20 octombrie 2026 la 16:04 UTCresolved

   Incidentul de pe partea Google a fost rezolvat. A existat o problemă persistentă care a necesitat aplicarea unui fix de către echipa de cercetare și dezvoltare. Acest fix a ieșit și locaţia de vest a UE (Londra, Google) este disponibilă din nou.

Traducere automată din actualizarea oficială a incidentului.

1. 13 octombrie 2026 la 12:40 UTCmonitoring

   Echipa de cercetare și dezvoltare efectuează unele teste pe sistemele noastre de suport care ar putea provoca lentoare în BlazeMeter UI. Monitorizăm sistemul şi vom readuce sistemul la funcţionalitatea normală dacă observăm că orice încetinire începe să apară din cauza testării. Testele ar trebui să continue să fie normale în acest timp, deși dacă observați orice probleme, atunci vă rugăm să contactați echipa noastră de sprijin.

2. 13 octombrie 2026 la 13:26 UTCresolved

   Am terminat testul acum. A fost o scurta incetinire in UI, dar functionalitatea a revenit la normal acum. Orice teste de funcționare ar fi trebuit să fie finalizate în mod normal, dar dacă sunt observate probleme atunci vă rugăm să contactați echipa noastră de sprijin.

Traducere automată din actualizarea oficială a incidentului.

1. 7 octombrie 2026 la 12:20 UTCmonitoring

   Echipa de cercetare și dezvoltare efectuează unele teste pe sistemele noastre de suport care ar putea provoca lentoare în BlazeMeter UI. Monitorizăm sistemul şi vom readuce sistemul la funcţionalitatea normală dacă observăm că orice încetinire începe să apară din cauza testării. Testele ar trebui să continue să fie normale în acest timp, deși dacă observați orice probleme, atunci vă rugăm să contactați echipa noastră de sprijin.

2. 7 octombrie 2026 la 13:06 UTCresolved

   Echipa de cercetare și dezvoltare și-a finalizat testarea acum și sistemul a revenit la funcționalitatea normală.

Traducere automată din actualizarea oficială a incidentului.

1. 1 octombrie 2026 la 12:30 UTCmonitoring

   Echipa de cercetare și dezvoltare efectuează unele teste pe sistemele noastre de suport care ar putea provoca lentoare în BlazeMeter UI. Monitorizăm sistemul şi vom readuce sistemul la funcţionalitatea normală dacă observăm că orice încetinire începe să apară din cauza testării. Testele ar trebui să continue să fie normale în acest timp, deși dacă observați orice probleme, atunci vă rugăm să contactați echipa noastră de sprijin.

2. 1 octombrie 2026 la 14:15 UTCresolved

   C&D a finalizat testarea lor acum. Am observat o scurta incetinire a sistemului in timpul testului, dar am restaurat sistemul la functionalitate normala acum. Orice teste de funcționare ar trebui să fi terminat în continuare ca normal, dar dacă observați orice probleme cu testele care au rulat în această perioadă, atunci vă rugăm să ajungeți la Support.

Traducere automată din actualizarea oficială a incidentului.

1. 18 septembrie 2026 la 13:09 UTCinvestigating

   Investigăm în prezent o problemă care cauzează o încetinire extremă în UI BlazeMeter. Echipa de cercetare și dezvoltare lucrează pentru a rezolva problema acum și vă vom oferi o actualizare cât mai curând posibil.

2. 18 septembrie 2026 la 13:17 UTCmonitoring

   Echipa de cercetare și dezvoltare a identificat cauza încetinirii și a luat măsuri pentru a îmbunătăți capacitatea de reacție a BlazeMeter. Vedem performanţe îmbunătăţite în UI din partea noastră. Vom continua să monitorizăm problema pentru a ne asigura că lentoarea nu reapare.

3. 18 septembrie 2026 la 14:24 UTCresolved

   Nu am mai observat lentețe în UI așa cum am monitorizat soluționarea problemei. Rezolvăm incidentul acum.

Traducere automată din actualizarea oficială a incidentului.

1. 15 septembrie 2026 la 14:59 UTCmonitoring

   Datorită unei probleme de capacitate pe partea Google, există în prezent probleme de disponibilitate a motorului în Iowa, Google locație publică. Testele folosind această locație pot avea timpi de pornire lent, sau nu reușesc să înceapă în mod corespunzător. Vă recomandăm evitarea utilizării Google, Iowa locație, și potențial folosind AWS sau Azure în schimb pentru moment.

2. 15 septembrie 2026 la 16:45 UTCresolved

   Problemele acute cu capacitate în Google, locaţia Iowa au fost rezolvate pentru moment. Încă lucrăm cu Google pentru a le oferi o soluție permanentă. Încă recomandăm evitarea utilizării Google, Iowa locație pentru moment.

Traducere automată din actualizarea oficială a incidentului.

1. 26 mai 2026 la 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. 27 mai 2026 la 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. 1 iunie 2026 la 16:27 UTCresolved

   This incident has been resolved.

1. 7 mai 2026 la 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. 8 mai 2026 la 10:42 UTCresolved

   The incident with new user registration has been resolved

1. 30 martie 2026 la 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. 30 martie 2026 la 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. 30 martie 2026 la 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. 21 ianuarie 2026 la 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. 21 ianuarie 2026 la 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. 21 ianuarie 2026 la 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. 7 octombrie 2025 la 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. 7 octombrie 2025 la 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. 3 octombrie 2025 la 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. 3 octombrie 2025 la 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. 3 octombrie 2025 la 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. 24 septembrie 2025 la 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. 24 septembrie 2025 la 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. 24 septembrie 2025 la 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. 24 septembrie 2025 la 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. 11 septembrie 2025 la 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. 11 septembrie 2025 la 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. 11 septembrie 2025 la 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. 25 iulie 2025 la 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. 25 iulie 2025 la 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. 25 iulie 2025 la 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. 25 iulie 2025 la 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. 25 iulie 2025 la 07: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. 25 iulie 2025 la 08: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. 25 iulie 2025 la 09: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. 25 iulie 2025 la 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. 25 iulie 2025 la 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. 14 iulie 2025 la 03:36 UTCinvestigating

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

2. 14 iulie 2025 la 05:32 UTCinvestigating

   We are continuing to investigate this issue.

3. 14 iulie 2025 la 06:36 UTCmonitoring

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

4. 14 iulie 2025 la 06:37 UTCresolved

   This incident has been resolved.

1. 10 iulie 2025 la 07:22 UTCinvestigating

   We are currently investigating this issue.

2. 10 iulie 2025 la 07:49 UTCidentified

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

3. 10 iulie 2025 la 10:40 UTCmonitoring

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

4. 10 iulie 2025 la 10:41 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 10 iulie 2025 la 12:17 UTCresolved

   This incident has been resolved.

1. 23 iunie 2025 la 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. 23 iunie 2025 la 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. 12 iunie 2025 la 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. 12 iunie 2025 la 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. 12 iunie 2025 la 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. 12 iunie 2025 la 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. 12 iunie 2025 la 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. 12 iunie 2025 la 22:37 UTCresolved

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