BlazeMeter incident

Runscope tests are lagging and sometimes the UI shows 500 Error

Major Resolved View vendor source →

BlazeMeter experienced a major incident on May 18, 2023 affecting API Monitoring (Runscope), lasting 1d. The incident has been resolved; the full update timeline is below.

Started
May 18, 2023, 06:40 AM UTC
Resolved
May 19, 2023, 07:20 AM UTC
Duration
1d
Detected by Pingoru
May 18, 2023, 06:40 AM UTC

Affected components

API Monitoring (Runscope)

Update timeline

  1. investigating May 18, 2023, 06:40 AM UTC

    We are aware of an issue with API Monitoring (Runscope) and are presently investigating. We will post an update here as soon as we have more information.

  2. identified May 18, 2023, 07:46 AM UTC

    The issue has been identified.

  3. identified May 18, 2023, 09:58 AM UTC

    We are continuing to work on a fix for this issue.

  4. identified May 18, 2023, 12:11 PM UTC

    We have identified the cause of IMPACT experienced by some customers and are currently working on mitigation. A temporary fix has been applied but we are yet to resolve and deploy the fix. The next update will be provided as new information is available.

  5. identified May 18, 2023, 02:56 PM UTC

    There has been a fix released which we believe resolves the issue with API Monitoring (Runscope) we will continue to monitor the situation and if the resolution holds we will consider this issue resolved.

  6. identified May 18, 2023, 04:04 PM UTC

    This incident should be resolved at this time.

  7. identified May 18, 2023, 04:10 PM UTC

    There are still issues with this. We are continuing to investigate....

  8. identified May 18, 2023, 06:27 PM UTC

    Continuing to investigate, working as expected in most cases. Some slowdowns reported, extra resources allocated to make up the difference in the meantime.

  9. identified May 18, 2023, 11:38 PM UTC

    Functioning as expected in most cases. We are continuing to investigate instances of slowness and are testing a fix; extra resources allocated to make up the difference in the meantime.

  10. identified May 19, 2023, 02:39 AM UTC

    We have identified the cause of IMPACT experienced by some customers and are currently working on mitigation. We are continuing to investigate instances of slowness and are testing a fix he next update will be provided as new information is available.

  11. monitoring May 19, 2023, 04:19 AM UTC

    A fix has been implemented and we are monitoring the results.

  12. resolved May 19, 2023, 07:20 AM UTC

    This incident has been resolved.