Pushover incident
Website and API issues, errant network monitor alerts
Resolved after 1 hour 38 minutes, affecting Dashboard and Outbound Message Queue, on June 22, 2026.
An incorrect deployment to the backend code was made which caused new messages to be stored in our database in a format incompatible with some other components. As soon as the problem was noticed the change was rolled back, but the already-stored messages caused problems for the users that received those messages. This also affected our network monitors for teams, which caused our backend system to identify a number of monitors as not having been updated properly and then send out false alerts. An update mechanism had to be created to identify and re-encode all of those stored messages which took some time to create, test, and deploy. As of 18:00 CDT, all such messages have been re-encoded and sent out, restoring service for those affected users.
Affected components
Update timeline
- monitoring Jun 22, 2026, 09:40 PM UTC
An incorrect deployment to the backend code was made which caused new messages to be stored in our database in a format incompatible with some other components. As soon as the problem was noticed the change was rolled back, but the already-stored messages caused problems for the users that received those messages. This also affected our network monitors for teams, which caused our backend system to identify a number of monitors as not having been updated properly and then send out false alerts. An update mechanism had to be created to identify and re-encode all of those stored messages which took some time to create, test, and deploy. As of 18:00 CDT, all such messages have been re-encoded and sent out, restoring service for those affected users.
- resolved Jun 22, 2026, 11:18 PM UTC
The incident has been resolved.
Your product runs on more than Pushover
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services