Munisense incident

Delayed data ingress for sound measurements

Resolved after 5 hours 42 minutes, affecting Sensor Data Stream and External Message Queue, on July 30, 2025.

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

Started
Jul 30, 2025, 11:53 AM UTC
Resolved
Jul 30, 2025, 05:35 PM UTC
Duration
5h 42m
Detected by Pingoru
Jul 30, 2025, 11:53 AM UTC

Affected components

Sensor Data StreamExternal Message Queue

Update timeline

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

  2. monitoring Jul 30, 2025, 02:01 PM UTC

    We have resolved the problem and data is being processed again. We continue monitoring the situation.

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

Your product runs on more than Munisense

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →