BlazeMeter incident
Performance tests running in US West (California) GCP locations cannot be started
BlazeMeter experienced a minor incident on April 15, 2025 affecting Functional Testing and Performance Testing, lasting 7h 55m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.