According to the documentation, the World map shows if your monitoring locations are online or have an outage, helping you distinguish between global and local outages.
One of the tests having continues outage, only for a single test, but all the remaining tests do not have any issue from the same public locations.
How to interpret this situation?
the evidence would suggest that either there is a problem with the site under test, if it's different from the others you are testing or that the monitor needs tweaking to allow it work better. You would need to look at the errors rather than the high level view to investigate further.
If you are unable to find the cause or remedy it from looking at the errors, then raise a Support ticket for assistance.
Best wishes, Hannah
Yes, so that would point to an issue with that site. Does it allow Synthetic testing? Perhaps the site admins need to whitelist our IP addresses or the 'RuxitSynthetic/1.0' user agent.
What happens when you play back the monitor locally? Does it playback successfully?
Hi Babar, if you would like Support to investigate this issue, you will need to create a Support ticket and provide information on the monitor. You could try changing the waits as it may be that the site loads slower on some locations than others.
Hello @Hannah M.
The page is loading completely.
"description": "Loading of \"https://www.abc.com\"",
That code shows that it is waiting for the page to load completely. When you look at the screenshots for the failed executions do you see a fully loaded page or an incomplete one? If the page looks fully loaded, I would recommend you try a different wait. If the page looks like it has not fully loaded then it seems that this is a true reflection of the behaviour in that location
Great, thanks. We cannot code around that as it is a message returned from the Browser that the site took too long to respond. It is likely that your customers are also intermittently seeing that message. You could try testing from other locations nearby but the best solution would be to talk to the site's application team and look at ways of improving the speed the site is loaded in the parts of the world you most commonly see the behaviour.