On Wednesday 29th March at approximately 19:49 (UTC +1) our internal health check reported an outage which was automatically added to our status page.
Causaly Cloud was operational and fully available throughout this time and more details are available regarding the underlying cause from Google (https://status.cloud.google.com/incidents/nieR2aLyg1rwFKq1aWZU#7Nro3snGH5YXCyUfQuKS).
It was determined that high and variable network latency was affecting the connection between our monitoring platform and our customer platform and resulting in sporadic but invalid failing checks. These 'false positive' alerts did not impact the availability of our services.
No components marked as affected
Resolved
On Wednesday 29th March at approximately 19:49 (UTC +1) our internal health check reported an outage which was automatically added to our status page.
Causaly Cloud was operational and fully available throughout this time and more details are available regarding the underlying cause from Google (https://status.cloud.google.com/incidents/nieR2aLyg1rwFKq1aWZU#7Nro3snGH5YXCyUfQuKS).
It was determined that high and variable network latency was affecting the connection between our monitoring platform and our customer platform and resulting in sporadic but invalid failing checks. These 'false positive' alerts did not impact the availability of our services.