There was a discussion regarding Site Load scouts failing from certain ControlUp hives. Some users reported failures in Northern Virginia and Seattle, while others had no issues in these hives. One user’s site load scout was initially disabled but after testing, it seemed to be working fine. Upon further testing, Northern Virginia and Montreal started failing with the message that the resources haven’t finished loading. Another user suggested opening a ticket for further investigation and mentioned that they have not heard similar reports from other customers. One user speculated that the failures may be due to their security measures blocking the cloud hive IP addresses. The conversation ended with the suggestion to open a ticket for further investigation.
Read the entire ‘ControlUp Site Load Scouts Failing from Certain Hives’ thread below:
anyone seeing Site Load scouts fail from certain CU hives? Northern Virginia and Seattle fail but Montreal works.
My site load scout was disabled. Testing now
First test seems fine
subsequent tests also no issues on my end. 100% uptime
100% success to be precise
i’ll look more tomorrow
now Northern Virginia and Montreal are failing:
The site’s resources and sub-resources have not finished loading within the specified timeout.
I had one failure from Virginia around midnight EDT with the same message but likely just a brief connectivity issue in Azure. For the rest I’m consistently green
If you’d like to investigate further please open a ticket for this
Will do. We have near constant failures. Sounds like it might be isolated to us and probably our security measures.
I don’t know what resource you are testing and where it resides, but I have not heard any reports from other customers
Could be that something is blocking the cloud hive IP addresses, but that would result in constant failures
Continue reading and comment on the thread ‘ControlUp Site Load Scouts Failing from Certain Hives’. Not a member? Join Here!
Categories: All Archives, ControlUp Synthetic Monitoring