- Detected by Pingoru
- Oct 09, 2026, 10:59 AM UTC
- Resolved
- Oct 09, 2026, 12:36 PM UTC
- Duration
- 1h 37m
Affected: Sensor Data StreamExternal Message QueueNotifications
Timeline · 2 updates
-
investigating Oct 09, 2026, 10:59 AM UTC
We are currently experiencing an issue with our data ingress for our noise sensors. Data might not be available or delayed. We are currently investigating the issue. This will also have effect on things like notifications.
-
resolved Oct 09, 2026, 12:36 PM UTC
This issue was resolved around 13:30, we see that all devices have sent their data. We are still investigating the root cause in our backoffice. If you encounter any problems or if you are missing data please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2026, 09:24 AM UTC
- Resolved
- Sep 25, 2026, 12:41 PM UTC
- Duration
- 3h 17m
Affected: Sensor Data Stream
Timeline · 3 updates
-
investigating Sep 25, 2026, 09:24 AM UTC
We currently see an increasing number of (water) devices not being able to connect to our backoffice. The issue is currently being investigated. If you have any questions please contact us at [email protected]
-
monitoring Sep 25, 2026, 10:30 AM UTC
Since ~12:05 we are starting to see the data coming in again. Still investigating the root cause. We will update as soon as we have more information but feel free to contact [email protected] if you have any questions,
-
resolved Sep 25, 2026, 12:41 PM UTC
All data is flowing normally, we are hereby closing this statuspage. All devices are expected to (re-)send their data in the next 24hours. If you continue to see any problems please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 07:33 AM UTC
- Resolved
- Jun 18, 2026, 11:43 AM UTC
- Duration
- 4h 9m
Affected: Sensor Data Stream
Timeline · 2 updates
-
investigating Jun 18, 2026, 07:33 AM UTC
We are currently not receiving realtime weather data from the KNMI (for most of the stations). This has effect on the calculation of realtime water levels. Those cannot be calculated at this point in time. We are currently contacting the KNMI about this problem.
-
resolved Jun 18, 2026, 11:43 AM UTC
Since ~12:00 we are receiving data again from the KNMI. As soon as the hourly validated data is available we will import that to fill any missing data. If you have any problems and/or missing data please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 07:17 AM UTC
- Resolved
- Apr 17, 2026, 08:34 AM UTC
- Duration
- 1h 17m
Affected: Sensor Data Stream
Timeline · 3 updates
-
investigating Apr 17, 2026, 07:17 AM UTC
Since ~08:50 we are not receiving data for our mslv8 devices. We are currently investigating the issue and will give more information as soon as possible.
-
monitoring Apr 17, 2026, 07:26 AM UTC
Since about 09:18 we are receiving data again. We are still investigating the root cause. If your node was supposed to send data between 08:50 and 09:18 we have not received this. It will retry the next time (usually within 24hours)
-
resolved Apr 17, 2026, 08:34 AM UTC
We will be closing this statuspage as we have not observed any more questions. If you notice any problems please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 01:08 PM UTC
- Resolved
- Feb 27, 2026, 02:54 PM UTC
- Duration
- 1h 46m
Affected: Sensor Data Stream
Timeline · 4 updates
-
investigating Feb 27, 2026, 01:08 PM UTC
We have noticed an issue with our mobile provider causing (possible) delayed water level data for our mslv8 devices. We are currently investigating this issue. Non mslv8 devices should not be affected
-
investigating Feb 27, 2026, 01:31 PM UTC
We have determined that currently no data is being received for our mslv8 devices. We have escalated the issue to our provider and hope to come with an update soon.
-
monitoring Feb 27, 2026, 01:48 PM UTC
We have received answer from our provider that the problem was been resolved. We are currently seeing data coming in again and are monitoring the situation.
-
resolved Feb 27, 2026, 02:54 PM UTC
We have not observed any more issues, all devices that missed their window to send data will try again the next time and are expected to send all missing data in the next 24 hours. If you continue to see any problems please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 08:21 AM UTC
- Resolved
- Feb 10, 2026, 08:32 AM UTC
- Duration
- 1d
Affected: Sensor Data StreamNotifications
Timeline · 4 updates
-
identified Feb 09, 2026, 08:21 AM UTC
Since yesterday 22:41 we are no longer receiving barometric data from the KNMI. This data is used to calculate the actual water level in the portal. Unfortunately this means that you are currently not able to see any realtime data in the portal or receive any notifications on such data. The KNMI is aware of an ongoing issue (https://developer.dataplatform.knmi.nl/news) and we have notified them about the realtime data issue. When the KNMI provides more information or a solution we will update this incident.
-
identified Feb 09, 2026, 08:21 AM UTC
We are monitoring this issue and await more info from the KNMI.
-
monitoring Feb 09, 2026, 11:37 AM UTC
Real time KNMI data has been restored, therefore real time water levels are being calculated. Back-filling the KNMI data gap will take longer. Once that has been done we will start recalculating water levels for this period.
-
resolved Feb 10, 2026, 08:32 AM UTC
We have not seen anymore issues with the KNMI data. As soon as the delayed data comes available from the KNMI we will import it as soon as possible.
Read the full incident report →
Critical December 19, 2025 - Detected by Pingoru
- Dec 19, 2025, 03:38 PM UTC
- Resolved
- Dec 19, 2025, 05:37 PM UTC
- Duration
- 1h 58m
Affected: Sensor Data StreamExternal Message Queue
Timeline · 2 updates
-
investigating Dec 19, 2025, 03:38 PM UTC
We are seeing delayed ingress of sensor data. Devices may appear offline. We are investigating.
-
resolved Dec 19, 2025, 05:37 PM UTC
This incident has been resolved, we apologize for any inconvenience. We have not observed any data loss.
Read the full incident report →
- Detected by Pingoru
- Nov 07, 2025, 10:13 AM UTC
- Resolved
- Nov 07, 2025, 11:11 AM UTC
- Duration
- 57m
Affected: Sensor Data StreamSensor Data Stream
Timeline · 2 updates
-
monitoring Nov 07, 2025, 10:13 AM UTC
We have detected a significant drop in KNMI stations reporting 10 minute data. We have contacted the KNMI and they reply the following: 'Unfortunately, KNMI is experiencing an outage in observation data from The Netherlands. This means some datasets are not fully updating, such as the 10-minute-in-situ-meteorological-observations dataset for both the EDR and the Open Data API. KNMI is actively working to address the issue and restore normal operations as quickly as possible. We apologize for any inconvenience this may cause.' This means we currently have no access to the latest data. This will impact fieldwork. We will keep you updated on any newer updates from the KNMI, see also: https://developer.dataplatform.knmi.nl/news
-
resolved Nov 07, 2025, 11:11 AM UTC
The KNMI has resolved their outage. We are again taking in data from their meteo stations. If you continue having problems with meteo data please contact Munisense support.
Read the full incident report →
- Detected by Pingoru
- Oct 16, 2025, 05:58 AM UTC
- Resolved
- Oct 16, 2025, 12:00 PM UTC
- Duration
- 6h 1m
Affected: Customer Portal
Timeline · 4 updates
-
investigating Oct 16, 2025, 05:58 AM UTC
We have noticed an increased amount of errors on the water portal sometimes preventing it from loading it entirely. We are investigating the issue.
-
identified Oct 16, 2025, 06:09 AM UTC
We have deployed a new database as an emergency measure. This allow the portal to work right now. We are still investigating the issue. The validation of water levels might be delayed and/or not work at all for the time being.
-
monitoring Oct 16, 2025, 08:37 AM UTC
All waiting validation jobs have been processed. We are still investigating the root cause but for now it is running stable.
-
resolved Oct 16, 2025, 12:00 PM UTC
We have not seen any more issues and are hereby closing this statuspage. If you have any questions please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Oct 08, 2025, 08:53 AM UTC
- Resolved
- Oct 08, 2025, 11:46 AM UTC
- Duration
- 2h 53m
Affected: Sensor Data Stream
Timeline · 3 updates
-
investigating Oct 08, 2025, 08:53 AM UTC
We noticed an issue with the datastream for our mslv4 and mslv5 devices. We are currently not receiving data from these devices. Other types (mslvr / mslv8 etc) are not affected. We are contacting our mobile operator to investigate the issue
-
investigating Oct 08, 2025, 10:57 AM UTC
We just got word from our provider that the issue is still being investigated. There is a larger outage and they are working on the investigation. As soon as we have any more info we will update this page. If you have any questions about this outage please contact [email protected]
-
resolved Oct 08, 2025, 11:46 AM UTC
Since about 13:05 the connectivity of the mslv4/5 devices has been restored. We expect all devices to send their missing data within the next 24 hours. If you have any questions please contact our support.
Read the full incident report →
- Detected by Pingoru
- Oct 05, 2025, 01:10 PM UTC
- Resolved
- Oct 06, 2025, 07:18 AM UTC
- Duration
- 18h 8m
Affected: Sensor Data StreamCustomer PortalPortal Webservice API
Timeline · 3 updates
-
identified Oct 05, 2025, 01:10 PM UTC
We have seen one of our database servers is malfunctioning. We are currently investigating the issue and taking action to restore data ingress.
-
monitoring Oct 05, 2025, 01:45 PM UTC
We switched one of our database serves to the backup location, and it has taken over the job of the faulty server. Sensor data is being ingested again and should be up to data in about 15m.
-
resolved Oct 06, 2025, 07:18 AM UTC
This night the systems have been running stable. We expect no data-loss. We will now close this incident.
Read the full incident report →
- Detected by Pingoru
- Aug 04, 2025, 07:57 AM UTC
- Resolved
- Aug 04, 2025, 10:55 AM UTC
- Duration
- 2h 57m
Affected: Sensor Data Stream
Timeline · 3 updates
-
identified Aug 04, 2025, 07:57 AM UTC
We have identified a problem where water data is currently being delayed. We are working to resolve this issue as soon as possible.
-
monitoring Aug 04, 2025, 08:55 AM UTC
All delayed data has been processed, we are investigating the root cause of this problem. If you notice any problems or missing data please contact [email protected]
-
resolved Aug 04, 2025, 10:55 AM UTC
We have not seen any more delays so we will be closing this statuspage. The root cause investigation is still in progress and we will do our best to make sure this will not happen again. If you continue to see problems with your data please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Jul 30, 2025, 11:53 AM UTC
- Resolved
- Jul 30, 2025, 05:35 PM UTC
- Duration
- 5h 42m
Affected: Sensor Data StreamExternal Message Queue
Timeline · 3 updates
-
investigating Jul 30, 2025, 11:53 AM UTC
We are seeing a delay in the processing of sound measurements. Devices might appear offline. We are investigating this issue right away.
-
monitoring Jul 30, 2025, 02:01 PM UTC
We have resolved the problem and data is being processed again. We continue monitoring the situation.
-
resolved Jul 30, 2025, 05:35 PM UTC
We have not observed any more disruptions. All delayed sensor data should be processed by our system. No dataloss is expected. If you note any problems or missing data please contact our support so that we can investigate the problem. We are still analyzing the root cause in order to prevent this from happening in the future
Read the full incident report →
- Detected by Pingoru
- May 19, 2025, 08:26 AM UTC
- Resolved
- May 19, 2025, 11:00 AM UTC
- Duration
- 2h 34m
Affected: Sensor Data Stream
Timeline · 2 updates
-
monitoring May 19, 2025, 08:26 AM UTC
Our systems had an issue where we were unable validate water levels since last Friday 12:00. We currently resolved the issue, but we are still processing all data to be validated. If we have an estimate we will update it here. If you have changed some metadata this might cause your data to be not visible at all for the time being. We are working on speeding-up this process.
-
resolved May 19, 2025, 11:00 AM UTC
All data has been processed and should now be visible. If you are still missing data please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- May 16, 2025, 12:13 PM UTC
- Resolved
- May 16, 2025, 02:03 PM UTC
- Duration
- 1h 49m
Affected: Customer Portal
Timeline · 2 updates
-
identified May 16, 2025, 12:13 PM UTC
We are aware that our water portals are currently not reachable. We have identified the issue and are working to solve this asap. This has no effect on the sensor data or notifications.
-
resolved May 16, 2025, 02:03 PM UTC
This incident has been resolved, if you encounter any errors please let us know by emailing Support
Read the full incident report →
- Detected by Pingoru
- May 09, 2025, 06:46 AM UTC
- Resolved
- May 09, 2025, 09:59 AM UTC
- Duration
- 3h 12m
Affected: Sensor Data StreamAudio Streaming
Timeline · 3 updates
-
investigating May 09, 2025, 06:46 AM UTC
Since ~04:45 our audio streaming infrastructure is down. An engineer is en-route to the datacenter to investigate the issue. This also has effect on a large portion of sound devices unable to send their regular measurement data. We will update this page shortly when more information is available.
-
monitoring May 09, 2025, 08:18 AM UTC
We have replaced a faulty switch in the datacenter and every is up and running again. We will monitor the situation for the time being. If you have any questions please contact [email protected]
-
resolved May 09, 2025, 09:59 AM UTC
We have not noticed any more disruptions to our systems. If your device was set to only stream to our backoffice, that data is unfortunately lost between 04:45 and 10:00. Some meters might also have a gap in their regular data, while others will fill the missing data on a later moment. If you have any questions about this or want to know if we can import the data please send us a message on [email protected] Our apologies for any inconvenience caused. We are taking steps to improve our backoffice and prevent this in the future.
Read the full incident report →
- Detected by Pingoru
- May 02, 2025, 01:33 PM UTC
- Resolved
- May 02, 2025, 07:15 PM UTC
- Duration
- 5h 41m
Affected: Sensor Data StreamCustomer PortalNotificationsPortal Webservice API
Timeline · 3 updates
-
identified May 02, 2025, 01:33 PM UTC
We have seen that our data ingress is slower than usual, also the portals may be slower and/or unavailable. We are actively working on a solution.
-
monitoring May 02, 2025, 02:41 PM UTC
Data ingress is now working on the backlog of data. We expect all data is up to date in about an hour.
-
resolved May 02, 2025, 07:15 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2025, 09:38 AM UTC
- Resolved
- Apr 25, 2025, 09:38 AM UTC
- Duration
- 1d
Affected: Sensor Data StreamSensor Data StreamAudio Streaming
Timeline · 6 updates
-
investigating Apr 24, 2025, 09:38 AM UTC
We are seeing problems with the audio stream data. Audio stream data may not be working at the moment, we are investigating.
-
investigating Apr 24, 2025, 11:04 AM UTC
We have also noticed a problem with old (first-gen) mslv4 and mslv5 devices, we are investigating this issue.
-
identified Apr 24, 2025, 11:24 AM UTC
Some of our sound meters (MSSP and MSGD types) are offline and unable to connect, this is related to the audio stream problems. Specifically, devices that were configured to stream audio are affected. We expect them to come back online when the audio streaming problems have been resoled. There is no expected time for a fix yet.
-
identified Apr 24, 2025, 02:23 PM UTC
More problems have arisen: currently all LTE-M sound meters (MSSP and MSGD) are not sending their sensor data. Our engineers are working on the issue, but there is no expected resolution time. As a customer there is currently no action needed.
-
monitoring Apr 24, 2025, 05:14 PM UTC
Emergency fixes have been implemented, sensor data and audio stream data is coming into our platform again. Work to fully resolve these issues will continue, which might cause some more disruptions.
-
resolved Apr 25, 2025, 09:38 AM UTC
This incident has been resolved. Audio stream data has been lost between ~11h and ~19:30h yesterday. Sensor data for some devices (LTE-M sound meters) might be missing, please contact support if this affects you and we can try to recover parts of this data. We will investigate the root cause and take steps to reduce the change of similar incidents in the future.
Read the full incident report →
- Detected by Pingoru
- Apr 11, 2025, 09:56 AM UTC
- Resolved
- Apr 16, 2025, 09:34 AM UTC
- Duration
- 4d 23h
Affected: Customer Portal
Timeline · 3 updates
-
identified Apr 11, 2025, 09:56 AM UTC
Due to a bug in our systems there have been cases where incorrect data ended up in certain tubes with imported data. This is most likely visible as it are often large jumps in the data. We have identified the issue and are working on resolving it. We have temporarily disabled the (manual) validation to make sure we will not undo any data you have been validating. We expect to have fixed this early next week. Our apologies for any inconvenience caused. If you notice any strange data feel free to contact our support to confirm whether you are affected or not. We will work with affected parties in the coming days to restore all data. (Realtime) Telemetric data is NOT affected, this is only for historic imported data. Roughly between the year 2004 and 2024. Only a small part of wells and their time-ranges are affected.
-
identified Apr 15, 2025, 11:54 AM UTC
The process is well underway and we expect everything to be restored somewhere today. After verification we will restore the manual validation feature. We hope to be able to do this tomorrow. If not we will update this statuspage. As always: if you have any questions please contact [email protected]
-
resolved Apr 16, 2025, 09:34 AM UTC
We have good news: all the incorrect data has been removed. We are still running some extra checks but we have not observed any wrong data. The validation functionality has been restored: feel free to use this without any problems. If you have any doubt about your data or see some strange things. Please contact [email protected] so we can investigate. Our apologies for any inconvenience, we are working on a root cause analysis on how to prevent this from happening in the future.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2025, 01:00 PM UTC
- Resolved
- Apr 01, 2025, 07:29 AM UTC
- Duration
- 18h 28m
Affected: Sensor Data Stream
Timeline · 4 updates
-
investigating Mar 31, 2025, 01:00 PM UTC
We are currently investigating a problem where the realtime water data is not available or delayed. We will update as soon as possible.
-
identified Mar 31, 2025, 01:49 PM UTC
We have implemented some fixes, realtime dataflow should be available again. We are still investigating the problem so it might still be unstable.
-
monitoring Mar 31, 2025, 02:46 PM UTC
We have implemented some fixes and added extra database. We are still investigating the root cause but for now we have a stable system again. Validated data might still be delayed, we are processing this as quickly as we can.
-
resolved Apr 01, 2025, 07:29 AM UTC
During last night we have not seen any more issues and our databases are in fully working order. We are taking steps to investigate the root cause so that we can prevent this in the future. Our apologies for any inconvenience and if you have any questions please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2025, 09:12 AM UTC
- Resolved
- Mar 19, 2025, 09:36 AM UTC
- Duration
- 24m
Affected: Notifications
Timeline · 2 updates
-
investigating Mar 19, 2025, 09:12 AM UTC
We are currently investigating an issues with sending emails. We are currently unable to send out notifications or invites for example. Our support email is working correctly.
-
resolved Mar 19, 2025, 09:36 AM UTC
We have resolved the issues and email is being sent again. We estimate that we were unable to send out notifications between 08:00 and 10:30. We apologize for any inconvenience, if you are missing email please contact [email protected] so we can check if we can re-sent those.
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2025, 07:53 AM UTC
- Resolved
- Mar 11, 2025, 12:42 PM UTC
- Duration
- 4h 49m
Affected: Sensor Data Stream
Timeline · 5 updates
-
investigating Mar 11, 2025, 07:53 AM UTC
We are measuring an increased error rate when our water devices are connecting to our backoffice. We are currently investigating the issue.
-
monitoring Mar 11, 2025, 08:13 AM UTC
We have implemented a fix and are monitoring the situation.
-
investigating Mar 11, 2025, 08:43 AM UTC
The situation improved a lot, but we are still seeing (some) problems. We will investigate the problem again.
-
monitoring Mar 11, 2025, 09:31 AM UTC
A new fix seems to be working, we are monitoring the situation
-
resolved Mar 11, 2025, 12:42 PM UTC
We have not observed any more issues. The root cause is still being investigated. All devices that missed their connect window should report back within 6 to 24 hours (depending on configuration). We estimate that about 300 devices were affected. If you have any questions please contact [email protected]
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2025, 12:10 PM UTC
- Resolved
- Mar 10, 2025, 12:32 PM UTC
- Duration
- 22m
Affected: Customer Portal
Timeline · 3 updates
-
investigating Mar 10, 2025, 12:10 PM UTC
We are noticing our portals are currently stuck in a update loop. We are investigating this issue and are looking for solutions.
-
monitoring Mar 10, 2025, 12:29 PM UTC
A fix has been implemented we are monitoring the issues
-
resolved Mar 10, 2025, 12:32 PM UTC
This incident has been resolved, if you have any issues don't hesitate to contact our support
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2025, 09:23 AM UTC
- Resolved
- Mar 06, 2025, 04:05 PM UTC
- Duration
- 6h 42m
Affected: Sensor Data Stream
Timeline · 3 updates
-
investigating Mar 06, 2025, 09:23 AM UTC
We have observed a problem with water nodes connecting to our backoffice. First investigation it looks like devices that are connecting over T-Mobile/Odido are not able to connect at all times. We have reported this issue to our provider and are currently investigating. The problem started last night and we do see some data currently coming in. If you have any questions feel free to reach out. Devices connecting via Tele2 (which is also Odido) are connecting without any problem.
-
monitoring Mar 06, 2025, 11:23 AM UTC
We have received notification from our provider that a fix was implemented. We see lots of nodes connecting again. The situation is being monitored so that we can confirm everything is up and running. If your device failed to send it's data it is expected that that is retried within the nest 24 hours.
-
resolved Mar 06, 2025, 04:05 PM UTC
We have not observed any more issues. Our provider is investigating the root cause so that we can prevent this in the future. All devices are expected to contact our backoffice and send their data in the next 24 hours. If you continue to see problems please reach out to us via [email protected]
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2025, 10:59 AM UTC
- Resolved
- Mar 06, 2025, 02:53 PM UTC
- Duration
- 1d 3h
Affected: Sensor Data StreamSensor Data Stream
Timeline · 4 updates
-
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.
-
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.
-
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.
-
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 →