Our maintenance is complete. We have successfully migrated API Monitoring to Google Cloud Platform. Our Illinois and Texas locations are not yet available but should be soon. Thank you for your patience!
Posted May 27, 2020 - 00:58 PDT
We’re getting closer. The BlazeMeter API Monitoring (Runscope) services are being restarted and system testing is in progress. Please refrain from running tests and/or making any modifications as we test. We will communicate when the system is back to 100% and ready for use. Thank you.
Posted May 27, 2020 - 00:12 PDT
API Monitoring is now functioning. We are working to bring up all our locations.
Posted May 27, 2020 - 00:00 PDT
Everything is going to be 200 OK, but our engineering team requires some additional time. We are extending the maintenance window until 1:00am PDT. We will provide an update on progress by 12:00AM PDT. Thank you for your patience.
Posted May 26, 2020 - 22:52 PDT
Apologies, it’s taking a little longer than expected, we are working to complete our maintenance window as soon as possible. We expect to have our service restored by 11:00pm PDT.
Posted May 26, 2020 - 21:54 PDT
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted May 26, 2020 - 18:00 PDT
We will be undergoing scheduled maintenance during this time.
Posted May 14, 2020 - 10:29 PDT
We have a planned maintenance window for the API Monitoring component (formerly known as Runscope) of the BlazeMeter Continuous Testing Platform on May 26th, 2020, from 6pm to 10pm PDT (0100 - 0500 UTC).
During this time:
Tests under the API Monitoring tab will not be executed in any way (schedules, Trigger URLs, or API calls) The API Monitoring tab will not be available The API Monitoring API will not be available
This will only impact the API Monitoring component. The Functional, Performance, and Mock Services components of the BlazeMeter platform will continue to run.
Why is this happening?
We are migrating our infrastructure from Amazon Web Services to Google Cloud Platform. Our team has been working on this to provide a better experience for our users, and in our efforts to continue to improve the integration of API Monitoring with the overall BlazeMeter platform.
What's going to happen to my API Monitoring tests during the maintenance window?
A few minutes after the maintenance window starts, we will stop any tests that are scheduled from being executed. Any Trigger URLs and API calls will return a 503 status code.
Is there anything I need to do?
There is no action you need to do in regards to your tests. Once our maintenance window is complete and we have finished migrating our infrastructure, any tests that you had schedules for will resume running.
There also won't be any changes necessary to Remote Radar Agent configuration files, or API calls to the API Monitoring API.
If you would like to stay up-to-date in regards to the maintenance window status, please go to our status page at status.blazemeter.com.
We understand that this downtime can be disruptive to teams, and we sincerely apologize for the inconvenience. We're doing everything we can to help mitigate any risks associated with this infrastructure change, and reduce the impact for our customers.
If you have any questions or concerns about this, please reach out to us by replying to this email.
The BlazeMeter Team
Posted May 13, 2020 - 11:57 PDT
This scheduled maintenance affected: API Monitoring (Runscope).