Monnit had 6 outages in the last 2 years totaling 59h 57m of downtime — averaging 0.2 incidents per month.
There were 6 Monnit outages since July 7, 2025 totaling 59h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are investigating a service disruption affecting all production services.
We were able to get the secondary database node to take over processing. We’re monitoring that, and still evaluating root cause.
All services restored
We are investigating an issue in the database synchronization that is causing service disruption.
DB synchronization error has been remedied by ejecting the unhealthy node. There are still multiple active nodes processing data. The ejected node will be evaluated resolved and added back in later.
Service outage under investigation
Database transaction log issue resolve. Services back online
Transaction Log blocking commits
Administrators indicating resolution will be completed within an hour.
All services online
During routine certificate renewals, one certificate was inadvertently not upgraded. This certificate was associated with the backup process. Because it was not updated, automated backups began failing without immediate detection. As a result, the database transaction log continued to grow until it reached its configured size limit. Once this limit was reached, the database was unable to process transactions, resulting in the service interruption. The missed certificate has since been updated, backup operations have been verified to be functioning normally, and the transaction log has been returned to standard operating levels. We are currently reviewing monitoring and validation procedures to ensure all certificates are properly accounted for during renewals and that backup failures are detected more promptly in the future.