Munisense Outage History

Started Mar 05, 2025, 10:59 AM UTC· resolved Mar 06, 2025, 02:53 PM UTC

1. identified Mar 05, 2025, 10:59 AM UTC

   We have received the following report from the KNMI: "Due to a power failure, we are currently experiencing no network at the KNMI office. Multiple datasets are not updating due to the the power failure. Engineers are working hard to resolve this critical issue." This has the effect that we are currently unable to fetch realtime meteo data. The most impact is expected for fieldworkers installing new sensors as there is also no barometric pressure available. If you are affected please reach out to us, we can see if there are any other (non-KNMI) meteo stations that can be used. As soon as we have more information from the KNMI we will update this statuspage. No Munisense devices are affected.

2. identified Mar 05, 2025, 03:10 PM UTC

   We have heard from the KNMI that the radar is currently up and running again. The realtime 10-minute data is still being worked in and they are unable to provide a timeline at this time.

3. monitoring Mar 06, 2025, 06:51 AM UTC

   Since about midnight we see data from almost all KNMI sensors again. We have not yet gotten confirmation from the KNMI. As soon as we do we will resolve this statuspage. When the data is backfilled we will import it as soon as possible.

4. resolved Mar 06, 2025, 02:53 PM UTC

   We have not yet seen any more issues, all KNMI data is available realtime. We expect to be able to import the missing data tomorrow when that is available. We are discussing ways to limit the impact in case this ever occurs again. If you have any questions please reach out to [email protected]

Read the full incident report →

Started Jan 22, 2025, 06:22 PM UTC· resolved Jan 23, 2025, 01:22 PM UTC

1. identified Jan 22, 2025, 06:22 PM UTC

   An issue has been detected with one of the database servers causing the ingress of noise data to be delayed and data not being accessible. We are working on the problem.

2. identified Jan 22, 2025, 10:16 PM UTC

   We are still working on restoring all the delayed data. A large portion is now available but you might still notice delays for certain sensors.

3. monitoring Jan 22, 2025, 10:34 PM UTC

   As of right now 99% of the data is in realtime available again. For the 1% that is left: a repair is running to allow the ingress of this data again. Unfortunately the repair is a slow process. We are unable to ingress this data until the repair is completed. We are expecting that that will take 2~4 hours. Once everything has been repaired we will update this incident again. If you have any questions feel free to contact [email protected]

4. monitoring Jan 23, 2025, 08:16 AM UTC

   All data was successfully repaired during the night and all incoming data is stored as expected. We are currently running some final checks but all data should be available. If you notice any problems or missing data please contact [email protected]

5. resolved Jan 23, 2025, 01:22 PM UTC

   We will now be closing this incident. We continue to monitor for any data that still might need to be repaired (we will get notified if that is the case). If you see anything strange or missing please reach out to [email protected]

Read the full incident report →

Started Dec 17, 2024, 08:30 AM UTC· resolved Dec 17, 2024, 02:54 PM UTC

1. identified Dec 17, 2024, 08:30 AM UTC

   Due to an outage at the KNMI we are currently not receiving realtime barometric pressure data. We use this data to calculate the actual water level for your measurement point. We are contacting the KNMI to inform about an ETA. Not all sensors are affected, only the ones that use a KNMI station for the barometric pressures. When we receive the data again we will calculate the missing data again. This will have mostly effect for fieldworkers that are currently installing a new sensor. If you need any help feel free to contact our support.

2. identified Dec 17, 2024, 08:32 AM UTC

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

3. identified Dec 17, 2024, 12:18 PM UTC

   Since 11:00 we are receiving about 1 measurement every hour from the KNMI (normally every 10 minutes). This should be enough to calculate the realtime data. We will update as soon as more information is available.

4. resolved Dec 17, 2024, 02:54 PM UTC

   Since 13:40 we are receiving data regularly again. We have not yet received an official resolved notification from the KNMI but our data-stream seems stable. It is our intention to fix any missing data (gaps) in the coming days as soon as they will become available at the KNMI. For any more information about the outage please see: https://developer.dataplatform.knmi.nl/news If you require any assistance please reach out to our support via [email protected]

Read the full incident report →

Started Nov 29, 2024, 08:20 AM UTC· resolved Dec 03, 2024, 03:34 PM UTC

1. investigating Nov 29, 2024, 08:20 AM UTC

   We currently notice a problem with mslv4/mvls5 device with a Tele2 sim. We are currently investigating the problem.

2. investigating Nov 29, 2024, 12:54 PM UTC

   We are unfortunately still waiting on a response from our provider. They are investigating this issue. Our systems are working and part of the sensors connect without any problems. It it not yet clear exactly why certain devices cannot connect. We will report back as soon as we have any more information.

3. investigating Nov 29, 2024, 02:38 PM UTC

   Just now we had contact again with our provider. The issue has been escalated to KPN/Tele2 and others where needed. Unfortunately they could not provide us with an estimate at this point in time. This has our highest priority and we will keep monitoring the progress. At this time dataloss is not expected as the devices should send their data as soon as the connection is available again. If you have any further issues please contact [email protected]

4. investigating Nov 29, 2024, 03:54 PM UTC

   So far the problem is still being investigated by our providers. We will keep track of this during the weekend but unfortunately we cannot share an estimated time yet. If you have any questions please contact [email protected]

5. investigating Dec 02, 2024, 08:00 AM UTC

   Unfortunately we have not received an update from our provider this weekend and where not successful in contacting them. We will contact then as soon as possible and then provide an update here.

6. investigating Dec 02, 2024, 09:16 AM UTC

   We have contacted our provider again this morning and it has been escalated again directly to the mobile provider (Tele2). As of this time we cannot provide any more updates as it is being investigated by the provider. Please be assured that we apply as much pressure as possible in order to have this resolved as quickly as possible. If you have any other questions please reach out to our support via [email protected] but we do not have any more information there. As soon as we have an update it will be posted here.

7. investigating Dec 02, 2024, 04:00 PM UTC

   We are sorry to inform that there currently is no update. We have again escalated the issue (multiple times) but the investigation at the provider is still ongoing. They cannot provide us with a time frame yet. We have compiled a list of all affected devices and asked them to verify all SIM cards related. A new update will be posted as soon as there is information, or if there is none yet: tomorrow morning.

8. investigating Dec 03, 2024, 07:32 AM UTC

   We currently have some insights in what the problem may be. We are working with the operators to test this and then develop a solution. Be assured: this issue has the top priority in our company and we are doing everything we can in order to resolve it as quickly as possible. Thank you for your understanding and if you have any questions feel free to contact [email protected]

9. identified Dec 03, 2024, 09:05 AM UTC

   We have implemented a fix and are now confirming if this has the expected effect.

10. monitoring Dec 03, 2024, 09:40 AM UTC

    Our fix has been implemented as per 10:05, all connection attempts after that time should be going through. We are monitoring the situation and start working on a way to improve our processes to prevent the issue from happening in the future and also improve our process in finding the root cause. We expect all nodes to connect over the coming 24 hours. If after tomorrow 10:00 your device has not connected yet please contact our support. We will keep monitoring the situation.

11. resolved Dec 03, 2024, 03:34 PM UTC

    Everything is working as expected. We are still in the process of doing a full root cause analysis but have already improved monitoring for these issues. We expect all nodes to connect in the coming hours (before 10:00 tomorrow). If your node has an (exceptionally) bad radio connection it might take more then one or two attempts to send all the data. No data loss is expected and all data should be transmitted. If you see any problems, missing data or delayed data please do contact our support via [email protected] Again our apologize for any inconvenience caused by this problem and thank you for your understanding.

Read the full incident report →

Started Nov 26, 2024, 12:21 PM UTC· resolved Nov 27, 2024, 08:20 AM UTC

1. investigating Nov 26, 2024, 12:21 PM UTC

   We are currently seeing and investigating an issue related to the availability of our real-time audio stream. This may result in data-loss regarding the audio stream. Sensor-data itself seems unaffected for now. Updates will be posted here when new information becomes available.

2. investigating Nov 26, 2024, 12:39 PM UTC

   We are continuing to investigate this issue.

3. monitoring Nov 26, 2024, 03:32 PM UTC

   The system is stable once again but we keep monitoring the situation. There will be some gaps in the audio-stream data, roughly between 12:45 and 15:30 CET.

4. resolved Nov 27, 2024, 08:20 AM UTC

   Last night the root cause was found and confirmed repaired. We will now close this statuspage. If you notice any problems with your devices please contact [email protected]

Read the full incident report →