Litium incident
Incident – Level 3: Critical Impact – Database service disruption
Resolved on June 22, 2026.
We experienced a database service disruption between 07.18 and 08.28. During this period, some customers experienced service unavailability. All other services continued to operate normally. The issue was caused by an OS service allocating memory than usual causing the SQL service to get OOM killed. Service was restored after restart, and the database is now operating normally. We are investigating why this service used up more memory than normal to see if its something we can prevent in the future. All systems are currently stable, and we continue to monitor closely. We apologize for the inconvenience and appreciate your patience. — Litium Support Team
Update timeline
- resolved Jun 22, 2026, 08:54 AM UTC
We experienced a database service disruption between 07.18 and 08.28. During this period, some customers experienced service unavailability. All other services continued to operate normally. The issue was caused by an OS service allocating memory than usual causing the SQL service to get OOM killed. Service was restored after restart, and the database is now operating normally. We are investigating why this service used up more memory than normal to see if its something we can prevent in the future. All systems are currently stable, and we continue to monitor closely. We apologize for the inconvenience and appreciate your patience. — Litium Support Team
Your product runs on more than Litium
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