There have been multiple reports of VoIP registration faillure alarms in recent hours. The failure occurred at the component that processes the statuses of Octalarm alarms. As a result of the failure, the Octalarm alarm diallers tried to divert to a backup data centre. As a result, a VoIP registration faillure alarms was incorrectly reported. This failure did not affect the normal alerting of the Octalarm alarm diallers. Our engineers have since fully resolved this issue.
Disturbances and maintenance
Overview of (remedied) defects and maintenance since January 2019
'VoIP registration faillure' alarm no impact on normal alerting
Thursday 11 April 2024
Checkmyprocess not available
Monday 31 October 2022
[01-11-22 11:25h]
Checkmyprocess.com is accessible again. The failure was most likely caused by the conversion from summer time to winter time. Depending on your settings in terms of frequency of uploading to the cloud platform, logged data may have been lost in the intervening period from Sunday night until now. We apologise for the inconvenience.
[Original post from 31-10-22]
Since early this morning, Checkmyprocess.com has been unreachable and your SVL reporter may receive the response "503 Service Unavailable: Back-end server is at capacity", for example. It is still unclear what is causing this outage. For now, this outage has the following consequences:
- logged data SVL is not visible
- overview of SVA alarm diallers and SVL Webloggers is not visible
- remote settings for SVA and SVL devices are not possible. However, you can set your devicess locally via sv-prog (downloadable via 'read more').
The normal alarming of your dialler is NOT affected by this failure.
Recovery from Checkmyprocess.com has not yet succeeded. We are trying to solve this problem as soon as possible but unfortunately do not expect to have Checkmyprocess.com up and running again before the end of tomorrow morning. Our apologies for the inconvenience.
Remote setting via Checkmyprocess.com not possible
Friday 17 June 2022
Due to a malfunction on the Checkmyprocess Platform, remote settings are currently not possible. The normal alerting of your detector and logging of the data are not affected by this malfunction.
Our engineering department is busy solving this problem. As soon as the failure is resolved, we will report this on the website.
Since Tuesday, June 21, the problem is solved; Checkmyprocess.com works as before.
Malfunction in remote setting Checkmyprocess and problems line monitoring ACC
Thursday 19 August 2021
Remote setting possible again on Checkmyprocess.com
Today there were some connection problems with the remote settings on Checkmyprocess.com. These have been solved, but the recently logged data is not yet updated. Apologies for the inconvenience.
Since 13:15 the display on Checkmyprocess.com is up-to-date again. In some cases, the online status of alarm indicators of the SV product line does not synchronise automatically. You can synchronise in two ways:
- by refreshing the page on Checkmyprocess.com. This causes the status to jump from 'offline' to 'online';
- by restarting the detector to have the status updated.
Advice to stop using Adésys Control Centre (ACC) actively
The Adésys Control Centre (ACC) has also been experiencing problems since last night. We have heard from several customers that they received error messages. In addition to the cancellation of line monitoring, the sending of e-mail notifications from the alarm dialler is no longer possible due to the failure of the ACC. Alarm notifications such as voice message, SMS and paging will, of course, continue to work.
Since 15:19h the malfunction of the ACC has also been solved. As we don't support the ACC actively anymore since July 2021, we advise users who have enabled line monitoring of the ACC to deactivate it in the Octalarm-IP alarm dialler.