Juspay experienced a minor incident on December 30, 2025, lasting 2m. The incident has been resolved; the full update timeline is below.
Update timeline
- identified Dec 30, 2025, 11:34 AM UTC
Initial analysis indicates hardware failure of one our AWS database writer instances resulting in 504s and timeouts of our APIs..
- resolved Dec 30, 2025, 11:36 AM UTC
One of our database writer instances based out of AWS Mumbai DC had a hardware failure. AWS tried to automatically failover the instance to a healthy one, but from the logs we could see that the failover got stuck and hence delayed, causing an intermittent spike in latencies, affecting a small portion of our overall volume. We are working with AWS to understand why the process was stuck and delayed..