- 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
-
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
-
resolved May 08, 2026, 10:42 AM UTC
The incident with new user registration has been resolved
Read the full incident report →
- 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
-
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
-
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.
-
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 →
- 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
-
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
-
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.
-
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 →
- 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
-
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.
-
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 →
- 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
-
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.
-
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.
-
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 →
- 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
-
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.
-
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.
-
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.
-
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 →
- 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
-
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.
-
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.
-
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 →
- 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
-
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.
-
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.
-
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.
-
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 →
- 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
-
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.
-
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.
-
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.
-
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.
-
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 →
- 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
-
investigating Jul 14, 2025, 03:36 AM UTC
We are aware of an issue with tests not starting and are currently investigating.
-
investigating Jul 14, 2025, 05:32 AM UTC
We are continuing to investigate this issue.
-
monitoring Jul 14, 2025, 06:36 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 14, 2025, 06:37 AM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
investigating Jul 10, 2025, 07:22 AM UTC
We are currently investigating this issue.
-
identified Jul 10, 2025, 07:49 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 10, 2025, 10:40 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jul 10, 2025, 10:41 AM UTC
We are continuing to monitor for any further issues.
-
resolved Jul 10, 2025, 12:17 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2025, 06:28 PM UTC
- Resolved
- Jun 23, 2025, 10:25 PM UTC
- Duration
- 3h 56m
Affected: API Monitoring (Runscope)
Timeline · 2 updates
-
identified Jun 23, 2025, 06:28 PM UTC
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.
-
resolved Jun 23, 2025, 10:25 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 06:46 PM UTC
- Resolved
- Jun 12, 2025, 10:37 PM UTC
- Duration
- 3h 51m
Affected: Performance Testing
Timeline · 6 updates
-
investigating Jun 12, 2025, 06:46 PM UTC
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.
-
investigating Jun 12, 2025, 07:31 PM UTC
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.
-
monitoring Jun 12, 2025, 08:43 PM UTC
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.
-
monitoring Jun 12, 2025, 09:41 PM UTC
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.
-
investigating Jun 12, 2025, 10:33 PM UTC
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.
-
resolved Jun 12, 2025, 10:37 PM UTC
As of this time functionality has been restored to Performance Tests and we are resolving the incident.
Read the full incident report →
- Detected by Pingoru
- May 24, 2025, 02:30 PM UTC
- Resolved
- May 24, 2025, 05:56 PM UTC
- Duration
- 3h 25m
Affected: Performance Testing
Timeline · 3 updates
-
investigating May 24, 2025, 02:30 PM UTC
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
-
identified May 24, 2025, 02:52 PM UTC
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.
-
resolved May 24, 2025, 05:56 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2025, 09:21 AM UTC
- Resolved
- Apr 17, 2025, 02:06 PM UTC
- Duration
- 4h 45m
Affected: Performance Testing
Timeline · 5 updates
-
investigating Apr 17, 2025, 09:21 AM UTC
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.
-
monitoring Apr 17, 2025, 10:11 AM UTC
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.
-
monitoring Apr 17, 2025, 10:12 AM UTC
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.
-
monitoring Apr 17, 2025, 11:59 AM UTC
The functionality has been restored. We are currently monitoring the performance closely.
-
resolved Apr 17, 2025, 02:06 PM UTC
We have not seen any reoccurrences of the data processing delays in some time. We are resolving the incident now.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2025, 08:09 AM UTC
- Resolved
- Apr 15, 2025, 04:05 PM UTC
- Duration
- 7h 55m
Affected: Functional TestingPerformance Testing
Timeline · 6 updates
-
investigating Apr 15, 2025, 08:09 AM UTC
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.
-
identified Apr 15, 2025, 08:39 AM UTC
The issue has been identified and is only impacting Performance tests running on certain Google (GCP) Locations
-
identified Apr 15, 2025, 08:55 AM UTC
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
-
identified Apr 15, 2025, 10:21 AM UTC
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.
-
identified Apr 15, 2025, 11:42 AM UTC
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.
-
resolved Apr 15, 2025, 04:05 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 30, 2025, 06:26 PM UTC
- Resolved
- Mar 30, 2025, 07:34 PM UTC
- Duration
- 1h 7m
Affected: BlazeMeter Platform
Timeline · 4 updates
-
investigating Mar 30, 2025, 01:08 PM UTC
We are currently investigating this issue.
-
investigating Mar 30, 2025, 06:26 PM UTC
As of TIME_STAMP UTC, the issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.
-
investigating Mar 30, 2025, 06:27 PM UTC
As of 18:15 UTC, the issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.
-
resolved Mar 30, 2025, 07:34 PM UTC
The incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2025, 06:58 AM UTC
- Resolved
- Mar 25, 2025, 07:35 AM UTC
- Duration
- 36m
Affected: BlazeMeter Platform
Timeline · 3 updates
-
investigating Mar 25, 2025, 06:58 AM UTC
We are currently investigating this issue.
-
monitoring Mar 25, 2025, 07:11 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 25, 2025, 07:35 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 09, 2025, 05:20 PM UTC
- Resolved
- Mar 09, 2025, 06:53 PM UTC
- Duration
- 1h 32m
Affected: Performance Testing
Timeline · 2 updates
-
investigating Mar 09, 2025, 05:20 PM UTC
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.
-
resolved Mar 09, 2025, 06:53 PM UTC
The issue with Performance Test results being delayed has been identified and fixed.
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2025, 02:24 PM UTC
- Resolved
- Mar 06, 2025, 04:38 AM UTC
- Duration
- 14h 14m
Affected: BlazeMeter Platform
Timeline · 6 updates
-
investigating Mar 05, 2025, 02:24 PM UTC
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.
-
investigating Mar 05, 2025, 02:27 PM UTC
We are continuing to investigate this issue.
-
investigating Mar 05, 2025, 02:58 PM UTC
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}}
-
monitoring Mar 05, 2025, 03:33 PM UTC
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}}
-
monitoring Mar 05, 2025, 03:53 PM UTC
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}}
-
resolved Mar 06, 2025, 04:38 AM UTC
As of 00:30 UTC, the issue experienced by some customers has been addressed and functionality has been restored. This incident is now resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 30, 2024, 12:44 PM UTC
- Resolved
- Oct 01, 2024, 07:49 AM UTC
- Duration
- 19h 4m
Affected: BlazeMeter PlatformMock Services
Timeline · 5 updates
-
investigating Sep 30, 2024, 12:44 PM UTC
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.
-
investigating Sep 30, 2024, 06:51 PM UTC
We are continuing to investigate this issue.
-
monitoring Oct 01, 2024, 06:51 AM UTC
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.
-
investigating Oct 01, 2024, 07:42 AM UTC
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.
-
resolved Oct 01, 2024, 07:49 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Sep 06, 2024, 05:57 PM UTC
- Resolved
- Sep 06, 2024, 06:32 PM UTC
- Duration
- 35m
Affected: API Monitoring (Runscope)
Timeline · 3 updates
-
investigating Sep 06, 2024, 05:57 PM UTC
We are aware of a slowdown in API Monitoring Test Execution and this is being looked into by the engineering team.
-
monitoring Sep 06, 2024, 06:09 PM UTC
The cause has been identified and things should be running normally, we will be watching to make sure things continue to run smoothly.
-
resolved Sep 06, 2024, 06:32 PM UTC
The issue has been fixed and normal operations for API Monitoring have been restored.
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2024, 08:31 AM UTC
- Resolved
- Aug 05, 2024, 08:52 PM UTC
- Duration
- 12h 20m
Affected: Performance Testing
Timeline · 2 updates
-
identified Aug 05, 2024, 08:31 AM UTC
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
-
resolved Aug 05, 2024, 08:52 PM UTC
The JMeter plugin repository site is available again now.
Read the full incident report →
- Detected by Pingoru
- Jul 29, 2024, 12:58 PM UTC
- Resolved
- Jul 29, 2024, 07:06 PM UTC
- Duration
- 6h 7m
Affected: API Monitoring (Runscope)
Timeline · 4 updates
-
investigating Jul 29, 2024, 12:58 PM UTC
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.
-
identified Jul 29, 2024, 02:12 PM UTC
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.
-
monitoring Jul 29, 2024, 04:25 PM UTC
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.
-
resolved Jul 29, 2024, 07:06 PM UTC
The fix has been implemented and the system has finished processing the test result metrics so they are now visible in the UI again.
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2024, 12:52 PM UTC
- Resolved
- Jun 26, 2024, 03:57 PM UTC
- Duration
- 3h 4m
Affected: Functional TestingPerformance Testing
Timeline · 4 updates
-
investigating Jun 26, 2024, 12:52 PM UTC
Tests currently can't be run on Google locations. We are investigating this issue now.
-
investigating Jun 26, 2024, 01:38 PM UTC
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.
-
monitoring Jun 26, 2024, 03:08 PM UTC
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.
-
resolved Jun 26, 2024, 03:57 PM UTC
We are no longer seeing issues with tests running on Google locations. Resolving the incident now, thank you for your patience.
Read the full incident report →
