Munisense Outage History

Munisense is up right now

Munisense had 10 outages in the last 2 years totaling 64h 41m of downtime — averaging 0.4 incidents per month.

There were 10 Munisense outages since October 5, 2025 totaling 64h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://munisense.statuspage.io

Major September 25, 2026

Some (lv8) nodes are unable to connect to our backoffice

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
  1. 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]

  2. 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,

  3. 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 →

Major June 18, 2026

No realtime weather data

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
  1. 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.

  2. 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 →

Major April 17, 2026

mslv8 devices not sending data

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
  1. 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.

  2. 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)

  3. 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 →

Major February 27, 2026

No water data for mslv8 devices

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
  1. 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

  2. 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.

  3. 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.

  4. 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 →

Major February 9, 2026

No realtime water-level data due to issue at KNMI

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
  1. 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.

  2. identified Feb 09, 2026, 08:21 AM UTC

    We are monitoring this issue and await more info from the KNMI.

  3. 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.

  4. 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

Delayed data in the Noise platform

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
  1. investigating Dec 19, 2025, 03:38 PM UTC

    We are seeing delayed ingress of sensor data. Devices may appear offline. We are investigating.

  2. 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 →

Major November 7, 2025

No meteo data available due to an outage at the KNMI

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
  1. 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

  2. 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 →

Major October 16, 2025

Increased amount of errors on the water portal

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
  1. 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.

  2. 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.

  3. 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.

  4. 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 →

Major October 8, 2025

No data received for mslv4 and mslv5 devices

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
  1. 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

  2. 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]

  3. 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 →

Major October 5, 2025

Partial sensor data ingress outage

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
  1. 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.

  2. 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.

  3. 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 →