Resolved after 7 hours 14 minutes, affecting Dashboard, on November 1, 2026.
A network connectivity problem between our Chicago and West Coast datacenters caused database replication to go offline. Once connectivity was restored, replication failed due to conflicting information which had to be manually resolved. During this outage, new accounts and devices may not have been able to be created depending on which server handled the request. Network monitors were also not alerting during this period due to a built-in mechanism that does not alert when databases are detected to be out of synchronization. The connectivity problem was resolved and databases were fully synchronized by 08:36:00 CST.
Affected components
Update timeline
- resolved Nov 01, 2026, 02:36 PM UTC
A network connectivity problem between our Chicago and West Coast datacenters caused database replication to go offline. Once connectivity was restored, replication failed due to conflicting information which had to be manually resolved. During this outage, new accounts and devices may not have been able to be created depending on which server handled the request. Network monitors were also not alerting during this period due to a built-in mechanism that does not alert when databases are detected to be out of synchronization. The connectivity problem was resolved and databases were fully synchronized by 08:36:00 CST.
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