Is Wattsense Down Right Now? Check if there is a current outage ongoing.

This incident has been resolved.

We no longer see errors when handling data uplink activations. We'll continue monitoring the service.

We have deployed a fix and are monitoring the situation.

The issue was identified and we're deploying a fix shortly

We are continuing to work on a fix for this issue.

We are experiencing a technical problem that prevents the data uplink activation on the console for the Bridge or the Connect Box On Premise. We are sorry about the inconvenience, and we will do our best to get the situation back to normal.

This incident has been resolved.

We no longer see errors when handling data uplink activations. We'll continue monitoring the service.

We have deployed a fix and are monitoring the situation.

The issue was identified and we're deploying a fix shortly

We are continuing to work on a fix for this issue.

We are experiencing a technical problem that prevents the data uplink activation on the console for the Bridge or the Connect Box On Premise. We are sorry about the inconvenience, and we will do our best to get the situation back to normal.

Due to an unexpected technical incident with our sim card provider, we are currently seeing irregularities in data traffic. This may cause errors in data transmission but not data will be lost.

This incident has been resolved.

Due to an unexpected technical incident with our sim card provider, we are currently seeing irregularities in Bridge communication activation. This may cause errors in Bridge Activation but no data will be lost.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have an ongoing problem involving a delay in sending values, events and alarms via datastreams. We have identified the problem and are working to resolve it.

A deployment was scheduled for Monday evening at 8pm. The planned downtime was 30 minutes, but it lasted around 1.5 hours.

We were able to absorb the delayed messages. A more long term fix is being worked on to avoid this kind of issues in the future.

Due to a partial downtime of our infrastructure, part of our devices' data is not up to date and will be available slower than usual. Sending commands to the devices is working, however commands will be marked as Timeout.

Our latest version migrated the services that delivers property values to use reactive frameworks. During this migration, the validity check of the API signing message was by mistake altered. This made the query parameters mandatory for any request made to the API. In some cases, the need for query parameters is not needed, in particular as when one wants to get the latest value of a property. Sadly, we noticed that we didn’t have a specific test for this scenario, hence missing this critical issue.

Due to a recent version deployment, any request to the properties values API that did not provide a query parameter (such as calls to get the latest value of a property) returned 401. The issue is now resolved.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We've got an ongoing issue where data is not processed. We've identified the issue and working on fixing it.

Services are now back to normal and all missing data was restored

Due to an internal error, all data and commands were no longer being processed

Issue was resolved and archive requests that were made will be fulfilled automatically during the next few hours.

We've identified, and are deploying a fix where archives recovery is not working properly.

During a deployment today at 13:45 CEST, the console became unavailable for 15min. The cause is being investigated, meanwhile we reverted to the previous version. No impact on the rest of services.

All data from 2023-05-24 12:00:00UTC until today have been restored. Data from 2023-05-23 16:45:00 UTC to 2023-05-04 12:00:00 UTC will be restored on June 2nd.

We are continuing to monitor for any further issues.

Due to a mis-configuration, the archives data from 2023-05-23 to 2023-05-31 are temporarily unavailable. We identified the issue, created a fix. The archives are being propagated at the moment and will be available June 1st, 2023. Part of the data from 2023-05-23 and 2023-05-24 might stay unavailable until June 2nd, 2023. -- À cause d'une mauvaise configuration, les données du 23/05/2023 au 31/05/2023 sont temporairement indisponibles. L'erreur a été résolue et la mise à disposition des archives est en cours, les données seront disponibles le 1er Juin 2023. Une partie des données du 23/05/2023 et du 24/05/2023 seront indisponibles jusqu'au 2 Juin 2023.