There were 4 Monnit outages since February 21, 2026 totaling 17h 2m 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.
Dear Customer, We would like to inform you of a scheduled infrastructure update for the monitoring platform. Maintenance Date: March 17, 2026 Start Time: 10:00 AM Eastern Time Estimated Duration: Up to 8 hours During this maintenance window, we will migrate to a cloud load balancer to improve redundancy and long-term platform stability. Most customers will not need to take any action. However, organizations that restrict outbound traffic by IP address must update their firewall rules to ensure uninterrupted device communication. Please ensure the following IP addresses are allowed. Gateway Traffic (Outbound Port 3000): 166.117.35.68 166.117.206.175 Website Traffic (Outbound Ports 80 and 443): 44.241.242.96 44.228.29.168 If your organization restricts outbound communication by IP address, please ensure these addresses are added to your allow list prior to the maintenance window. If you are unsure whether your network restricts outbound traffic, please forward this notice to your IT or networking team. If you have any questions or need assistance, please contact our support team. Thank you for your continued partnership. Best regards, Support Team
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.
Pingoru polls Monnit's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required