BlazeMeter incident
Some API Monitoring Users Incorrectly Reverted to Free
BlazeMeter experienced a major incident on February 12, 2024 affecting API Monitoring (Runscope), lasting 1d 7h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Feb 12, 2024, 03:16 PM UTC
We have identified an issue where some API Monitoring (Runscope) teams were reverted to a Free plan incorrectly. We are in the process of re-enabling the teams that we have identified as having been affected by this issue. If you observe that your team has been incorrectly reset to Free and has not been re-enabled yet then please open a support ticket. If you have never opened a support ticket before then please take a moment to review this guide for instructions on how to do so: https://help.blazemeter.com/docs/answers/support-ticket.html
- identified Feb 13, 2024, 07:01 AM UTC
We have identified the cause of IMPACT experienced by some customers and are currently working on mitigation. If you observe that your team has been incorrectly reset to Free and has not been re-enabled yet then please open a support ticket. If you have never opened a support ticket before then please take a moment to review this guide for instructions on how to do so: https://help.blazemeter.com/docs/answers/support-ticket.html The next update will be provided as new information is available.
- resolved Feb 13, 2024, 11:12 PM UTC
A fix has been applied to reinstate the plans of any teams who had not already written in to have the plan re-enabled. For the affected users who had not written in, another communication will be sent out explaining what the fix did. If you have any additional questions then please reach out to support.