Resolved -
This incident has been resolved.
May 19, 00:20 PDT
Monitoring -
A fix has been implemented and we are monitoring the results.
May 18, 21:19 PDT
Update -
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.
May 18, 19:39 PDT
Update -
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.
May 18, 16:38 PDT
Update -
Continuing to investigate, working as expected in most cases. Some slowdowns reported, extra resources allocated to make up the difference in the meantime.
May 18, 11:27 PDT
Update -
There are still issues with this. We are continuing to investigate....
May 18, 09:10 PDT
Update -
This incident should be resolved at this time.
May 18, 09:04 PDT
Update -
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.
May 18, 07:56 PDT
Update -
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.
May 18, 05:11 PDT
Update -
We are continuing to work on a fix for this issue.
May 18, 02:58 PDT
Identified -
The issue has been identified.
May 18, 00:46 PDT
Investigating -
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.
May 17, 23:40 PDT
