Runscope Status

Thu Apr 17 2025 14:06:48 GMT+0000 (Coordinated Universal Time)

Users experiencing delays in stopping tests as well as starting in some cases

Apr 17, 07:06 PDT
Resolved - We have not seen any reoccurrences of the data processing delays in some time. We are resolving the incident now.

Apr 17, 04:59 PDT
Update - The functionality has been restored. We are currently monitoring the performance closely.

Apr 17, 03:12 PDT
Update - 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.

Apr 17, 03:11 PDT
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.

Apr 17, 02:21 PDT
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.


Thu Apr 17 2025 11:59:54 GMT+0000 (Coordinated Universal Time)

Users experiencing delays in stopping tests as well as starting in some cases

Apr 17, 04:59 PDT
Update - The functionality has been restored. We are currently monitoring the performance closely.

Apr 17, 03:12 PDT
Update - 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.

Apr 17, 03:11 PDT
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.

Apr 17, 02:21 PDT
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.


Thu Apr 17 2025 10:12:33 GMT+0000 (Coordinated Universal Time)

Users experiencing delays in stopping tests as well as starting in some cases

Apr 17, 03:12 PDT
Update - 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.

Apr 17, 03:11 PDT
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.

Apr 17, 02:21 PDT
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.


Thu Apr 17 2025 10:11:30 GMT+0000 (Coordinated Universal Time)

Users experiencing delays in stopping tests as well as starting in some cases

Apr 17, 03:11 PDT
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.

Apr 17, 02:21 PDT
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.


Thu Apr 17 2025 09:20:58 GMT+0000 (Coordinated Universal Time)

Users experiencing delays in stopping tests as well as starting in some cases

Apr 17, 02:20 PDT
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.


Thu Apr 17 2025 09:21:00 GMT+0000 (Coordinated Universal Time)

Users experiencing delays in stopping tests as well as starting in some cases

Apr 17, 02:21 PDT
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.


Tue Apr 15 2025 16:05:41 GMT+0000 (Coordinated Universal Time)

Performance tests running in US West (California) GCP locations cannot be started

Apr 15, 09:05 PDT
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.

Apr 15, 04:42 PDT
Update - 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.

Apr 15, 03:21 PDT
Update - 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.

Apr 15, 01:55 PDT
Update - 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

Apr 15, 01:39 PDT
Identified - The issue has been identified and is only impacting Performance tests running on certain Google (GCP) Locations

Apr 15, 01:09 PDT
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.


Tue Apr 15 2025 11:42:13 GMT+0000 (Coordinated Universal Time)

Performance tests running in US West (California) GCP locations cannot be started

Apr 15, 04:42 PDT
Update - 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.

Apr 15, 03:21 PDT
Update - 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.

Apr 15, 01:55 PDT
Update - 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

Apr 15, 01:39 PDT
Identified - The issue has been identified and is only impacting Performance tests running on certain Google (GCP) Locations

Apr 15, 01:09 PDT
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.


Tue Apr 15 2025 10:46:57 GMT+0000 (Coordinated Universal Time)

Performance tests running in US West (California) GCP locations cannot be started

Apr 15, 03:21 PDT
Update - 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.

Apr 15, 01:55 PDT
Update - 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

Apr 15, 01:39 PDT
Identified - The issue has been identified and is only impacting Performance tests running on certain Google (GCP) Locations

Apr 15, 01:09 PDT
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.


Tue Apr 15 2025 10:21:53 GMT+0000 (Coordinated Universal Time)

Performance tests running in US West (California) GCP locations cannot be started

Apr 15, 03:21 PDT
Update - We have identified the cause of IMPACT experienced by some customers and reported it to Google. We are working with them to resolve the issue.
The next update will be provided as new information is available.

Apr 15, 01:55 PDT
Update - 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

Apr 15, 01:39 PDT
Identified - The issue has been identified and is only impacting Performance tests running on certain Google (GCP) Locations

Apr 15, 01:09 PDT
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.