Think Lumo incident
Delay in outgoing alerts
Resolved after 39 minutes, on March 5, 2024.
We can confirm that autoscaling of the database fixed the issue and we are back to BAU. There will be no root cause for this incident unless the spike in database requests is found to be due to a off-normal event (such as infrastructure failure). If the spike was due to increased customer demand, the system behaved as expected and scaled up to meet the demand. The incident is now closed.
Update timeline
- monitoring Mar 05, 2024, 09:24 PM UTC
We are investigating a delay in outgoing alerts.
- monitoring Mar 05, 2024, 09:38 PM UTC
The issue appears to have been caused by a temporary spike in database workload. The databases autoscaled based on the load and alerts are flowing again. We will continue to monitor.
- monitoring Mar 05, 2024, 10:03 PM UTC
We can confirm that autoscaling of the database fixed the issue and we are back to BAU. There will be no root cause for this incident unless the spike in database requests is found to be due to a off-normal event (such as infrastructure failure). If the spike was due to increased customer demand, the system behaved as expected and scaled up to meet the demand. The incident is now closed.
Your product runs on more than Think Lumo
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