BlazeMeter Status

Resolved: 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.

Identified: 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.

Identified: 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: 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: The issue has been identified and is only impacting Performance tests running on certain Google (GCP) Locations

Investigating: 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.

Resolved: 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.

Identified: 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.

Identified: 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: 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: The issue has been identified and is only impacting Performance tests running on certain Google (GCP) Locations

Investigating: 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.

Resolved: We have not seen any reoccurrences of the data processing delays in some time. We are resolving the incident now.

Monitoring: The functionality has been restored. We are currently monitoring the performance closely.

Monitoring: 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: 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.

Investigating: 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.