Resolved after 1 hour, affecting Platform, on October 20, 2025.
* Our cloud provider detected an infrastructure issue \(with the physical servers or network\) and automatically failed over to our standby database. * Service was read-only for approximately 15 minutes while database integrity was protected during the switchover. * Service has been fully restored. We have opened an high priority case with our cloud provider to confirm the root cause and will update. * ~~We do not believe this incident was related to the AWS US East outage; our systems run in AWS AP Southeast \(Sydney\).~~ * New information: We have been informed it is indeed related to the widespread AWS US East issue \(Likely their control plane\). We are continuing to work with our cloud provider.
Affected components
Update timeline
- investigating Oct 20, 2025, 10:53 PM UTC
We're aware of an issue affecting our primary database. Investigation is underway.
- monitoring Oct 20, 2025, 11:00 PM UTC
We're observing the recovery of the platform.
- resolved Oct 20, 2025, 11:53 PM UTC
This incident has been resolved.
- postmortem Oct 21, 2025, 01:24 AM UTC
* Our cloud provider detected an infrastructure issue \(with the physical servers or network\) and automatically failed over to our standby database. * Service was read-only for approximately 15 minutes while database integrity was protected during the switchover. * Service has been fully restored. We have opened an high priority case with our cloud provider to confirm the root cause and will update. * ~~We do not believe this incident was related to the AWS US East outage; our systems run in AWS AP Southeast \(Sydney\).~~ * New information: We have been informed it is indeed related to the widespread AWS US East issue \(Likely their control plane\). We are continuing to work with our cloud provider.
Your product runs on more than The Lookout Way
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