tag:munisense.statuspage.io,2005:/historyMunisense Status - Incident History2024-03-01T13:10:59+01:00Munisensetag:munisense.statuspage.io,2005:Incident/198929282024-02-03T23:05:20+01:002024-02-03T23:05:20+01:00Database restart<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>23:05</var> CET</small><br><strong>Completed</strong> - All maintenance has been completed, the (portal) downtime was less then 5 minutes.<br /><br />If you have any questions please contact support@munisense.com</p><p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>22:00</var> CET</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>13:58</var> CET</small><br><strong>Scheduled</strong> - To keep our systems available to our customers it is needed that we restart our databases to execute some configuration changes. We will do this between 22:00 and 00:00 on Saturday 03-02-2024. The expected downtime is about 10~20 minutes for each part of our system (portal and backoffice).<br /><br />During this downtime sensor data may be delayed, notifications will not be sent and the portal might be unavailable. During this maintenance window performance might be worse then normal.<br /><br />If you have any questions please contact support@munisense.com</p>tag:munisense.statuspage.io,2005:Incident/189218872023-10-30T11:51:33+01:002023-10-30T11:51:33+01:00Loggers (lv7/lv8) installed in a new location are unable to connect to the mobile network<p><small>Oct <var data-var='date'>30</var>, <var data-var='time'>11:51</var> CET</small><br><strong>Resolved</strong> - The issue regarding new devices not being able to connect has been solved. If you continue to see problems or have any other issues please contact support@munisense.com</p><p><small>Oct <var data-var='date'>26</var>, <var data-var='time'>10:42</var> CEST</small><br><strong>Update</strong> - We have received word from our operators that the issue should be resolved. However we are still seeing issues with some devices so we are escalating the issue with them.</p><p><small>Oct <var data-var='date'>25</var>, <var data-var='time'>11:32</var> CEST</small><br><strong>Identified</strong> - We have just received word from our provider that devices are not able to register to the mobile network. Devices that are currently already registered (everything "in place") should continue to work. Devices that are being moved (e.g. installed) might not connect to the network. We have not yet received a timeframe. As soon we have more information we will update this page.</p>tag:munisense.statuspage.io,2005:Incident/185452162023-09-21T14:54:44+02:002023-09-21T14:54:44+02:00Degraded performance noise platform<p><small>Sep <var data-var='date'>21</var>, <var data-var='time'>14:54</var> CEST</small><br><strong>Resolved</strong> - We have received confirmation from the Datacenter. The cable that was causing our issues has been replaced. We will keep an extra eye on it the coming days but are closing this statuspage.<br /><br />If you have any questions please contact support@munisense.com</p><p><small>Sep <var data-var='date'>20</var>, <var data-var='time'>17:02</var> CEST</small><br><strong>Monitoring</strong> - The situation seems to be better, we did not observe any issues this afternoon. We will continue to monitor the situation.</p><p><small>Sep <var data-var='date'>20</var>, <var data-var='time'>10:21</var> CEST</small><br><strong>Identified</strong> - It seems that the issue is still not resolved, we are contacting the datacenter again!</p><p><small>Sep <var data-var='date'>20</var>, <var data-var='time'>09:19</var> CEST</small><br><strong>Monitoring</strong> - The issue has been identified. A broken network-cable was replaced last night. All issues should be resolved, we are monitoring the situation. Our apologies for any inconvenience caused.<br /><br />If you have any questions please contact support@munisense.com</p><p><small>Sep <var data-var='date'>19</var>, <var data-var='time'>14:26</var> CEST</small><br><strong>Investigating</strong> - Due to an network related issue our noise platform has degraded performance. Loading could be slower then normal or it might fail every once in a while. Please refresh the page or try again after a minute. We have contacted our provider requesting more information.</p>tag:munisense.statuspage.io,2005:Incident/185322212023-09-18T12:59:22+02:002023-09-18T12:59:22+02:00Small part of water nodes offline<p><small>Sep <var data-var='date'>18</var>, <var data-var='time'>12:59</var> CEST</small><br><strong>Resolved</strong> - We see no more issue and are now closing this incident. The root cause has been found: a system upgrade resulted in a slight change in configuration. This was detected by us automatically but needed some time to fully understand it and resolve it.<br /><br />Your sensor should send its data again within 24 hours. If you continue to have problems please contact support@munisense.com</p><p><small>Sep <var data-var='date'>18</var>, <var data-var='time'>10:57</var> CEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we see new devices come back online. <br />Devices that missed their window will report back in tomorrow. <br />We are currently monitoring the dataflow.<br />If you have any issues when installing new devices please let us know by contacting our support<support@munisense.com></p><p><small>Sep <var data-var='date'>18</var>, <var data-var='time'>10:13</var> CEST</small><br><strong>Identified</strong> - We have identified where the issue is located. The only devices affected are our LV8's.<br />We are working hard to find a solution. We will update this ticket when we have resolved the issue.</p><p><small>Sep <var data-var='date'>18</var>, <var data-var='time'>09:08</var> CEST</small><br><strong>Investigating</strong> - After our maintenance a small part of our water nodes are unable to connect. We are investigating the issue.</p>tag:munisense.statuspage.io,2005:Incident/185002132023-09-18T08:00:15+02:002023-09-18T08:00:15+02:00Hardware replacement, scheduled (noise) portal downtime<p><small>Sep <var data-var='date'>18</var>, <var data-var='time'>08:00</var> CEST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Sep <var data-var='date'>18</var>, <var data-var='time'>06:01</var> CEST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Sep <var data-var='date'>14</var>, <var data-var='time'>13:56</var> CEST</small><br><strong>Scheduled</strong> - Some of our hardware in the datacenter needs to replaced after the cooling failure from last week (https://munisense.statuspage.io/incidents/rlqnsh1gln66). Unfortunately this will result into downtime for our noise portals. We will try to limit the impact but in order to achieve the highest quality of our platform we cannot avoid this.<br /><br />On Monday 18th of September around 06:00 (CEST) we will start a maintenance window. During this time the portal might be unavailable for some time. This might happen more then once. We expect to have everything back online before 08:00 (CEST).<br /><br />Other parts of our system are also being replaces, we don't expect customer impact in regards to that.<br /><br />If you have any questions regarding this maintenance please contact support@munisense.com</p>tag:munisense.statuspage.io,2005:Incident/184895582023-09-13T14:34:22+02:002023-09-13T14:34:22+02:00Portals unavailable<p><small>Sep <var data-var='date'>13</var>, <var data-var='time'>14:34</var> CEST</small><br><strong>Resolved</strong> - As far as we can see there are no longer any issues with the portals. <br />We consider this issue now resolved.</p><p><small>Sep <var data-var='date'>13</var>, <var data-var='time'>14:04</var> CEST</small><br><strong>Monitoring</strong> - A fix has been implemented and released, we are currently monitoring our services</p><p><small>Sep <var data-var='date'>13</var>, <var data-var='time'>13:43</var> CEST</small><br><strong>Identified</strong> - We are currently that seeing all portals are unavailable. The cause has been identified and a solution is being implemented at this moment.</p>tag:munisense.statuspage.io,2005:Incident/184377982023-09-11T09:00:42+02:002023-09-11T09:00:42+02:00Noise platform down<p><small>Sep <var data-var='date'>11</var>, <var data-var='time'>09:00</var> CEST</small><br><strong>Resolved</strong> - We do not see any issues with our systems and are now marking this issue as resolved. Our datacenter has also marked it as resolved but has not (yet) provided any more information.<br /><br />If you see any issues with your devices please contact support@munisense.com</p><p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>04:08</var> CEST</small><br><strong>Monitoring</strong> - All systems are started again. It is possible you still see some delayed data. Whatever data is received is being processed. We will monitor the situation.</p><p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>22:17</var> CEST</small><br><strong>Update</strong> - We are still awaiting more information from the datacenter.</p><p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>21:17</var> CEST</small><br><strong>Update</strong> - We have arrived on scene. A new airconditioning unit is expected around 22:00. Maintenance by the datacenter is needed after that so it is expected for us to enter the server floor not before 01:00. It is currently unknown if the servers are currently running as some server racks have been powered down.<br /><br />Depending on the state of our servers it can take several our to restart out systems after the datacenter issue has been resolved.<br /><br />As soon as there is more information we will update it here.</p><p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>20:09</var> CEST</small><br><strong>Identified</strong> - The datacenter is working on repairing / replacing the air conditioning. We are also en route to be able to work on restoring service as soon as that is possible.<br /><br />Currently there is no time known yet.</p><p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>19:27</var> CEST</small><br><strong>Update</strong> - It appears that do to a problem with the air conditioning several servers went offline. We are contacting the datacenter to gather more information.<br /><br />Currently the time to resolve is uknown. We will update as soon as possible.</p><p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>19:15</var> CEST</small><br><strong>Investigating</strong> - We are currently experiencing issues in our data center. We are investering the issue.</p>tag:munisense.statuspage.io,2005:Incident/184060522023-09-06T12:12:22+02:002023-09-06T12:12:56+02:00Audio stream outage<p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>12:12</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved. About 20 minutes of real-time audio stream can be missing from your measurement points (between roughly 10:50 and 11:10). For the MSSP sound meters, these can be recovered by the use of audio snippets.</p><p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>11:24</var> CEST</small><br><strong>Monitoring</strong> - Fortunately this appears to have been a very short problem, and it has been resolved. Of course we'll keep an eye on things.</p><p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>11:07</var> CEST</small><br><strong>Investigating</strong> - We are investigating a problem in our infrastructure. This might be affecting audio stream, other impact is unknown at this moment. We will update this incident when we know more.</p>tag:munisense.statuspage.io,2005:Incident/180514852023-08-04T15:52:49+02:002023-08-04T15:52:49+02:00Audiostreaming currently unavailable<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>15:52</var> CEST</small><br><strong>Resolved</strong> - The issue has been resolved, we are still investigating the root cause. We are expecting about 15~20minutes of missing data in the audio stream if your node does not support storing audio data on the sensor itself.</p><p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>15:34</var> CEST</small><br><strong>Investigating</strong> - Our audio streaming is currently unavailable, we are investigating the problem.</p>tag:munisense.statuspage.io,2005:Incident/180050412023-08-01T09:13:58+02:002023-08-01T09:13:58+02:00Delayed sensor data<p><small>Aug <var data-var='date'> 1</var>, <var data-var='time'>09:13</var> CEST</small><br><strong>Resolved</strong> - We have not seen any more issues and are now closing this incident. We are still investigating the root cause of this problem.<br /><br />If you need any more info or assistance please contact: support@munisense.com</p><p><small>Jul <var data-var='date'>31</var>, <var data-var='time'>06:52</var> CEST</small><br><strong>Monitoring</strong> - The database server is working as expected, all data should be available again. We will monitor the situation.<br /><br />If you have any questions please contact support@munisense.com</p><p><small>Jul <var data-var='date'>31</var>, <var data-var='time'>03:51</var> CEST</small><br><strong>Update</strong> - We are still working on recovering the database, this is taking longer then expected. It looks like this process will be finished around the start of the working day. If we have more updates we will let them know as soon as possible.</p><p><small>Jul <var data-var='date'>30</var>, <var data-var='time'>22:01</var> CEST</small><br><strong>Identified</strong> - We are again experiencing some delay in some sound measurement data. We are working on resolving the issue.<br /><br />The root cause of this issue will also be investigated as soon as possible to prevent this from happening again.</p>tag:munisense.statuspage.io,2005:Incident/179957422023-07-30T07:00:56+02:002023-07-30T07:00:56+02:00Noise portals unavailable and no new data available for water customers<p><small>Jul <var data-var='date'>30</var>, <var data-var='time'>07:00</var> CEST</small><br><strong>Resolved</strong> - All systems are working correctly. The spare router will be replaced in the upcoming week.</p><p><small>Jul <var data-var='date'>30</var>, <var data-var='time'>02:40</var> CEST</small><br><strong>Monitoring</strong> - Database server is operational. We are monitoring the situation. We expect to change the issue to resolved this morning if we see no errors the upcoming night.</p><p><small>Jul <var data-var='date'>29</var>, <var data-var='time'>22:31</var> CEST</small><br><strong>Update</strong> - Connectivity to the portals is restored, however one of our database servers is currently still unavailable so you might be unable to see (part of) the data.</p><p><small>Jul <var data-var='date'>29</var>, <var data-var='time'>22:23</var> CEST</small><br><strong>Identified</strong> - An (unrelated) crash of the database server is breaking connectivity again. We are working to resolve this as soon as possible.</p><p><small>Jul <var data-var='date'>29</var>, <var data-var='time'>20:59</var> CEST</small><br><strong>Monitoring</strong> - The new router has been installed and configured and connectivity is restored.<br /><br />Most devices should have sent their delayed data by now with the exception of:<br />- audio stream (streamed to the platform, data stored by nodes themselves should be ok)<br />- any meter connected to a ZGD gateway (small white gateway), mostly mssp8 devices<br /><br />If you want to know any more information of have any questions about this outage please contact support@munisense.com<br /><br />We will monitor this for the next couple of hours before we set this page to resolved.</p><p><small>Jul <var data-var='date'>29</var>, <var data-var='time'>20:24</var> CEST</small><br><strong>Update</strong> - For most sensors connectivity should be restored, we are working to restore service for the last ones (connecting via ZGD gateway)</p><p><small>Jul <var data-var='date'>29</var>, <var data-var='time'>19:49</var> CEST</small><br><strong>Update</strong> - Currently data for our water customers is coming in again. If you are missing data please wait 24 hours to allow the device to try it again.<br /><br />For our noise customers: we are still working on resolving the last few of our systems.</p><p><small>Jul <var data-var='date'>29</var>, <var data-var='time'>19:01</var> CEST</small><br><strong>Update</strong> - We are continue to work on restoring service as quickly as possible. Currently the portals may be available however not all data is being processed. We will update as soon as there is more information available.</p><p><small>Jul <var data-var='date'>29</var>, <var data-var='time'>18:29</var> CEST</small><br><strong>Update</strong> - We are still working on configuring the replacement hardware. A new update will come as soon as there is more info.</p><p><small>Jul <var data-var='date'>29</var>, <var data-var='time'>17:42</var> CEST</small><br><strong>Identified</strong> - Our engineer has determined that some hardware (a router) is defective and needs to be replaced. He brought a spare one and is currently working on that. A new update is expected within an hour.</p><p><small>Jul <var data-var='date'>29</var>, <var data-var='time'>16:39</var> CEST</small><br><strong>Update</strong> - An engineer has been dispatched to the datacenter to investigate the issue. We expect more information in about 60~90 minutes. As soon as we have more information this page will be updated. We apologize for any inconvenience.<br /><br />If you require assistance or want to contact us about the outage please email to: support@munisense.com</p><p><small>Jul <var data-var='date'>29</var>, <var data-var='time'>16:16</var> CEST</small><br><strong>Investigating</strong> - We are currently experiencing an outage for our noise measurement portals. We are currently investigating the issue.<br /><br />For our water customers: the portals are running but new measurement data might not be received currently.</p>tag:munisense.statuspage.io,2005:Incident/179136162023-07-21T13:47:28+02:002023-07-21T13:47:28+02:00Audio stream not being stored<p><small>Jul <var data-var='date'>21</var>, <var data-var='time'>13:47</var> CEST</small><br><strong>Resolved</strong> - All audio stream has been processed and the green bar is now once again up to date in the portal.</p><p><small>Jul <var data-var='date'>21</var>, <var data-var='time'>09:48</var> CEST</small><br><strong>Update</strong> - We are seeing that the audio stream availability (the green bar in the graphs) is not being displayed. The audio stream of last night has been stored by our system, but the green bar is not up to date. This is being worked on and we expect the green bar to be fully up to date somewhere today.</p><p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>19:08</var> CEST</small><br><strong>Monitoring</strong> - Audio streaming is working again. If your device was streaming audio there is unfortunately a gap of around two hours that we cannot recover. If your device was recording audio internally that audio can be recovered by downloading snippets of audio.</p><p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>18:17</var> CEST</small><br><strong>Investigating</strong> - There are problems in the data-center where audio stream is being stored. An engineer has been dispatched to investigate.</p>tag:munisense.statuspage.io,2005:Incident/179135612023-07-21T08:58:26+02:002023-07-21T08:58:26+02:00Portals unavailable<p><small>Jul <var data-var='date'>21</var>, <var data-var='time'>08:58</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>19:05</var> CEST</small><br><strong>Monitoring</strong> - Noise portals are available again. We are monitoring the situation but at this moment everything seems to be working again.</p><p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>18:28</var> CEST</small><br><strong>Update</strong> - Our water portals are operational again.</p><p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>18:17</var> CEST</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>18:15</var> CEST</small><br><strong>Investigating</strong> - We are currently that seeing all portals are unavailable. The cause has been identified and a solution is being implemented at this moment.</p>tag:munisense.statuspage.io,2005:Incident/176638102023-07-03T10:14:14+02:002023-07-03T10:14:14+02:00Water nodes not connecting when on KPN network<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>10:14</var> CEST</small><br><strong>Resolved</strong> - All sensor nodes should have connected by now. We see all systems working again. We have not yet received the official 'resolved' communication so we will continue to monitor.<br /><br />If you still have device that do not seem to connect please contact support@munisense.com so we can investigate your case further.</p><p><small>Jun <var data-var='date'>30</var>, <var data-var='time'>16:41</var> CEST</small><br><strong>Monitoring</strong> - The issue is supposed to be resolved, we will continue to monitor the situation in order to make sure we see the devices connecting correctly over the next days.<br /><br />Update from our provider:<br />Tele2 meldt dat de oplossing van de 2G problemen succesvol zijn uitgevoerd. Alle netwerktesten zjin succesvol.<br /><br />Op dit moment wordt de status uitgebreid gemonitord door Tele2 en haar partners.<br /><br />Zodra er een officiƫle afmelding van de storing is, zullen we dat hier dele</p><p><small>Jun <var data-var='date'>30</var>, <var data-var='time'>12:56</var> CEST</small><br><strong>Update</strong> - We have received a new update from our provider:<br /><br />"<br />Tele2 meldt dat de oorzaak gevonden is. Er wordt op dit moment gewerkt aan een oplossing.<br />"<br /><br />We will keep you updated when we learn more.</p><p><small>Jun <var data-var='date'>30</var>, <var data-var='time'>09:09</var> CEST</small><br><strong>Update</strong> - We have received an update from our provider:<br /><br />"Tele2 heeft de diverse teams en roamingpartners betrokken bij het escalatieproces om de oorzaak te lokaliseren van de 2G datasessies.<br />We dringen bij alle betrokken partijen aan om zo snel mogelijk een oplossing te vinden.<br />De volgende update zal zijn wanneer er nieuwe informatie beschikbaar is."<br /><br />We will update this statuspage when there are new updates.</p><p><small>Jun <var data-var='date'>28</var>, <var data-var='time'>16:31</var> CEST</small><br><strong>Update</strong> - We have got a new update from our provider:<br /><br />Er worden momenteel verbeteringen in waargenomen in het 2G dataverkeer bij Tele2. Sommige klanten ondervinden echter nog steeds problemen op het 2G netwerk, de onderzoeken lopen nog steeds door bij Tele2 samen met de Roaming Partners.<br /><br />De volgende update volgt over 24 uur of wanneer er nieuwe informatie beschikbaar is.<br /><br />We will continue to monitor the situation and make sure it is handled with the highest priority!</p><p><small>Jun <var data-var='date'>28</var>, <var data-var='time'>11:04</var> CEST</small><br><strong>Identified</strong> - We do see a lot of nodes making contact again however, according to our provider there can still be cases where connectivity does not work. It is again being investigated.<br /><br /><br />We will do all we can to make sure this is done with the highest priority.</p><p><small>Jun <var data-var='date'>27</var>, <var data-var='time'>14:28</var> CEST</small><br><strong>Monitoring</strong> - Our provider reports that connectivity is restored, we will be monitoring the situation for the next day.</p><p><small>Jun <var data-var='date'>27</var>, <var data-var='time'>09:10</var> CEST</small><br><strong>Update</strong> - Our provider has also opened an incident to track the progress:<br />https://status.vtmgroep.nl/event/189340/</p><p><small>Jun <var data-var='date'>26</var>, <var data-var='time'>14:55</var> CEST</small><br><strong>Identified</strong> - Our operator has find the issue and it still working in order to resolve it. We estimate that only 1~5% of the nodes are affected.</p><p><small>Jun <var data-var='date'>23</var>, <var data-var='time'>22:00</var> CEST</small><br><strong>Update</strong> - The issue is still being investigated. It looks to be limited to only a small portion of our devices. We continue to work with the operator to resolve it as soon as possible.</p><p><small>Jun <var data-var='date'>23</var>, <var data-var='time'>15:07</var> CEST</small><br><strong>Investigating</strong> - We are currently observing an issue with a small amount of water sensor with a Tele2 (VTM) SIM that are trying to connect to a KPN network. These devices are unable to connect. We are contacting the operator on this issue and ask for an investegation.</p>tag:munisense.statuspage.io,2005:Incident/176281222023-06-20T16:14:29+02:002023-06-20T16:14:29+02:00Outage mobile provider (Tele2)<p><small>Jun <var data-var='date'>20</var>, <var data-var='time'>16:14</var> CEST</small><br><strong>Resolved</strong> - We do not see any issues right now so we are closing this issue. We will monitor the situation tomorrow morning in order to verify connectivity is restored for affected nodes.</p><p><small>Jun <var data-var='date'>20</var>, <var data-var='time'>14:29</var> CEST</small><br><strong>Monitoring</strong> - Our provider reports the issue has been mitigated. Since ~14:00 we do see the connections stabelize. We will continue to monitor the situation.<br /><br />All missing data should be sent again in the next 24 hours then the sensor will do another connection attempt.</p><p><small>Jun <var data-var='date'>20</var>, <var data-var='time'>11:09</var> CEST</small><br><strong>Update</strong> - Our provider has identified the issue and is currently working on a solution.</p><p><small>Jun <var data-var='date'>20</var>, <var data-var='time'>10:08</var> CEST</small><br><strong>Identified</strong> - Our mobile partner informed us of an outage at the Tele2 mobile provider. New data sessions cannot be started. This can affect any device with a "VTM/Tele2" SIM card, most likely mslv4 and mslv5 nodes are affected as they most likely have this SIM card.<br /><br />We will monitor the situation and update here once we get an update.<br /><br />(More information at our provider via: https://status.vtmgroep.nl/event/189262/)</p>tag:munisense.statuspage.io,2005:Incident/175454592023-06-12T13:38:45+02:002023-06-12T13:38:45+02:00Delayed sound sensor data<p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>13:38</var> CEST</small><br><strong>Resolved</strong> - All systems are back up and running. Please contact our support if you continue to experience problems.</p><p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>12:34</var> CEST</small><br><strong>Monitoring</strong> - Services are coming back and sensor data is being processes again. We expect to be fully operational again in the next half an hour. In the mean time we will keep motoring the progress.</p><p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>11:46</var> CEST</small><br><strong>Identified</strong> - We have identified the underlying problem and are working on restoring normal service as soon as possible.</p><p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>11:13</var> CEST</small><br><strong>Investigating</strong> - We are noticing that the sound sensor data is not being processed as quickly as it should. An investigation has started.</p>tag:munisense.statuspage.io,2005:Incident/175201682023-06-10T17:25:19+02:002023-06-10T17:25:20+02:00Infrastructure upgrade for the water environment<p><small>Jun <var data-var='date'>10</var>, <var data-var='time'>17:25</var> CEST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed. All systems are working with no problem and less than a minute downtime was observed. If you see any problems please contact support@munisense.com</p><p><small>Jun <var data-var='date'>10</var>, <var data-var='time'>08:00</var> CEST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>09:41</var> CEST</small><br><strong>Scheduled</strong> - This weekend part of the infrastructure for our water environment will be upgraded. Downtime is not expected but some delays might be experienced.<br /><br />All sensor data should still be processed (or delayed until the next connect cycle). The portal and notifications should work as expected.<br /><br />When finished we will update this page.<br /><br />If you have any questions please contact support@munisense.com</p>tag:munisense.statuspage.io,2005:Incident/173767102023-05-26T16:55:09+02:002023-05-26T16:55:09+02:00Noise portals / network unavailable<p><small>May <var data-var='date'>26</var>, <var data-var='time'>16:55</var> CEST</small><br><strong>Resolved</strong> - We are now closing this incident, we deem the issue to be resolved. We will continue to work with the datacenter the coming weeks to find out the root case and add measures where needed.</p><p><small>May <var data-var='date'>26</var>, <var data-var='time'>15:48</var> CEST</small><br><strong>Update</strong> - We have just received word from the datacenter that the issue is resolved. We will be monitoring this for the rest of the day.<br /><br />All (historic) data should been processed by now. If you are missing data please contact our support (support@munisense.com) so that we can investigate.</p><p><small>May <var data-var='date'>26</var>, <var data-var='time'>15:19</var> CEST</small><br><strong>Monitoring</strong> - We are currently seeing connectivity restored. It might be possible that there are still a few small moments where connectivity is dropped. If the issue becomes bigger again we will update this ticket. An update will also be posted when we get the official ok from the datacenter.</p><p><small>May <var data-var='date'>26</var>, <var data-var='time'>13:47</var> CEST</small><br><strong>Update</strong> - Our support phone number is also currently unavailable. Please send any questions to: support@munisense.com and we will reply as soon as possible.</p><p><small>May <var data-var='date'>26</var>, <var data-var='time'>13:32</var> CEST</small><br><strong>Update</strong> - Earlier was mentioned that water customers where unaffected, this was incorrect. Although the portal / API will continue to work for those customers, however new data received might be delayed or currently unavailable.</p><p><small>May <var data-var='date'>26</var>, <var data-var='time'>13:17</var> CEST</small><br><strong>Update</strong> - An engineer has been dispatched to the datacenter to investigate the issue. We expect more information in about half an hour. We will update as soon as we have more information.<br /><br />(Groundwater customers are not affected)</p><p><small>May <var data-var='date'>26</var>, <var data-var='time'>13:07</var> CEST</small><br><strong>Investigating</strong> - We are currently experiencing some network problems in our datacenter. We are investigating the issue.<br /><br />This will have effect on the portals (slow or unreachable), notifications and the API/datastream.<br /><br />We will update as soon as we have more information.</p>tag:munisense.statuspage.io,2005:Incident/165155992023-03-15T21:58:47+01:002023-03-15T21:58:47+01:00Delayed data for sound portals<p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>21:58</var> CET</small><br><strong>Resolved</strong> - All the data has been processed as of ~21:00. Our systems are in working order now. We will close this statuspage and start the investigation to the root cause of this issue. If you have any questions or continue to see problems please contact support@munisense.com</p><p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>20:24</var> CET</small><br><strong>Monitoring</strong> - The issue seems to be resolved, currently the backlog of data is being processed. We estimate that this will take about an hour before all delayed data is available. We will monitor this issue to make sure this processes as quickly as possible. When resolved we will update this issue.</p><p><small>Mar <var data-var='date'>15</var>, <var data-var='time'>20:13</var> CET</small><br><strong>Identified</strong> - We are currently having an issue resulting in some sound related measurements being delayed. We are working on resolving this issue.</p>tag:munisense.statuspage.io,2005:Incident/161771142023-02-17T20:24:52+01:002023-02-17T20:24:52+01:00Noise portal query problems<p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>20:24</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>20:24</var> CET</small><br><strong>Update</strong> - It seems like all our portals and services are up and running again, if you are experiencing any issues please contact our support at support@munisense.com. We will keep monitoring our services but for now have a nice weekend!</p><p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>19:59</var> CET</small><br><strong>Monitoring</strong> - We are currently working on getting the portals back online. <br />It might be that your portal is working but loading data is slow this is expected.<br />We are monitoring our services. Notifications might not be working yet.</p><p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>19:24</var> CET</small><br><strong>Update</strong> - We continue to work on restoring our service. <br />Our gateways are reporting again but we are still keeping our portals down to avoid extra load. <br />Once the the data tidal wave has been dealt with we will enable our portals.</p><p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>18:25</var> CET</small><br><strong>Update</strong> - We continue to work on restoring our service. The database problems are under control but recovery still takes time. When that is done we will re-enable the portals.</p><p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>17:04</var> CET</small><br><strong>Update</strong> - We still continue to work on restoring our services.</p><p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>16:00</var> CET</small><br><strong>Update</strong> - We continue to work on restoring our service.</p><p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>15:28</var> CET</small><br><strong>Identified</strong> - In an effort to reduce the load on our systems we have temporarily disabled the noise portals. Meanwhile we are working to restore services as quickly as we can.</p><p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>15:23</var> CET</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>15:14</var> CET</small><br><strong>Investigating</strong> - We are having some problems with our internal databases. We are actively working on the issue.</p>tag:munisense.statuspage.io,2005:Incident/159945782023-02-01T12:10:26+01:002023-02-01T12:10:26+01:00Delayed sensor data<p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>12:10</var> CET</small><br><strong>Resolved</strong> - All data has been processed and should be visible in the portal. We have not observed any data-loss. If you see data missing or have other questions please contact support@munisense.com We will keep an eye on this and investigate the root cause.<br /><br />All notifications and sensor data should be coming in as expected as of ~12:00</p><p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>11:50</var> CET</small><br><strong>Monitoring</strong> - We have found an fixed the issue, our systems are currently processing the backlog of data. I can take about 30 minutes for all data to be available again. Until that time you can still see delayed data and notifications may not trigger.</p><p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>11:21</var> CET</small><br><strong>Investigating</strong> - We are currently having some issues receiving sensor data. This can result in sensor data being later available then expected. Also notifications might not trigger when expected. We are investigating this issue.</p>tag:munisense.statuspage.io,2005:Incident/138819932022-11-29T08:46:10+01:002022-11-29T08:46:10+01:00Delayed sound sensor data<p><small>Nov <var data-var='date'>29</var>, <var data-var='time'>08:46</var> CET</small><br><strong>Resolved</strong> - We have not seen any more issues. If you observe any more problems please contact our support.</p><p><small>Nov <var data-var='date'>28</var>, <var data-var='time'>20:29</var> CET</small><br><strong>Monitoring</strong> - There are currently small outages in our datacenter traffic. This could result in your sensor temporally not able to send data to our backoffice resulting in a delay. We will keep an eye on this issue and implement measures where possible.</p>tag:munisense.statuspage.io,2005:Incident/137416212022-11-28T08:30:00+01:002022-11-28T08:30:00+01:00Delayed sound sensor data<p><small>Nov <var data-var='date'>28</var>, <var data-var='time'>08:30</var> CET</small><br><strong>Resolved</strong> - We have not observed any more issues. If you continue to see problems please contact our support.</p><p><small>Nov <var data-var='date'>26</var>, <var data-var='time'>21:25</var> CET</small><br><strong>Monitoring</strong> - The devices seem to be working as expected at the moment. We will keep monitoring the situation.</p><p><small>Nov <var data-var='date'>26</var>, <var data-var='time'>18:23</var> CET</small><br><strong>Investigating</strong> - We are seeing some delayed sensor data for some of our sound measurement sensors and we are investigating the issue.</p>tag:munisense.statuspage.io,2005:Incident/130422162022-11-15T09:10:55+01:002022-11-15T09:10:55+01:00Water nodes offline<p><small>Nov <var data-var='date'>15</var>, <var data-var='time'>09:10</var> CET</small><br><strong>Resolved</strong> - It looks like all nodes are connecting again. It can take a couple of more hours for your node to try again. We expect all data being restored before the end of the day. The root cause of this issue is still being investigated. If you have any questions please contact our support.</p><p><small>Nov <var data-var='date'>14</var>, <var data-var='time'>15:25</var> CET</small><br><strong>Monitoring</strong> - The issue seems to be resolved, we are monitoring the situation. We expect all nodes to send their data over the coming hours/day. If you have any questions please contact support.</p><p><small>Nov <var data-var='date'>14</var>, <var data-var='time'>10:37</var> CET</small><br><strong>Identified</strong> - We have identified that mslv4 and mslv5 nodes connecting with a Tele2 sim are affected. We have urgently escalated the issue at Tele2 and are waiting on their investigation. We will update as soon as we receive more info.</p><p><small>Nov <var data-var='date'>14</var>, <var data-var='time'>08:58</var> CET</small><br><strong>Investigating</strong> - We see a large number of water nodes offline at this point in time. We are currently investigating this issue and will update as soon as we have more information. Not all water nodes are affected, if you have any questions please contact support.</p>tag:munisense.statuspage.io,2005:Incident/118241552022-10-11T15:42:45+02:002022-10-11T15:42:45+02:00Partial outage for water level sensors<p><small>Oct <var data-var='date'>11</var>, <var data-var='time'>15:42</var> CEST</small><br><strong>Resolved</strong> - All issues seem to be resolved, if you continue to have issues please contact our support via support@munisense.com<br /><br />Please note that it can take up to 24 hours for the missing data to be sent again.</p><p><small>Oct <var data-var='date'>11</var>, <var data-var='time'>14:01</var> CEST</small><br><strong>Monitoring</strong> - We have identified and resolved the problem. We are currently monitoring to see if nodes are successful in their connection. It can take up to 24 hours for data transmitted between 05:00 and 14:00 to become available. Our apologies for any inconvenience.</p><p><small>Oct <var data-var='date'>11</var>, <var data-var='time'>13:24</var> CEST</small><br><strong>Investigating</strong> - We have noticed a problem with water sensor not being able to connect to our backoffice. We are investigating the problem.<br />(It could be related with the sound meter issue but that is currently undetermined)</p>