Juspay Outage History

Type: Incident Duration: 2 minutes Affected Components: SDK, API, Payment Page May 27, 05:20:00 GMT+0 - Investigating - We are currently investigating this incident. May 27, 05:22:00 GMT+0 - Resolved - The issue was caused by an automated failover that occurred in our KV infrastructure hosted on AWS, which led to temporary increase in 5XX errors. The system detected an issue with primary nodes and automatically promoted replicas to maintain service continuity. The failover completed automatically, and all systems recovered without manual intervention.

Type: Incident Duration: 3 minutes Affected Components: Sandbox Mar 26, 14:30:56 GMT+0 - Investigating - Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service. Mar 26, 14:33:47 GMT+0 - Resolved - Sandbox is now operational! This update was created by an automated monitoring service.

Type: Incident Duration: 2 minutes Affected Components: Payment Page, API Dec 30, 11:34:00 GMT+0 - Identified - Initial analysis indicates hardware failure of one our AWS database writer instances resulting in 504s and timeouts of our APIs. Dec 30, 11:36:00 GMT+0 - Resolved - 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.

Type: Incident Duration: 20 minutes Affected Components: API May 6, 09:50:00 GMT+0 - Investigating - We are currently investigating this incident. May 6, 10:10:00 GMT+0 - Resolved - Some of our APIs had experienced spike in latency due to high DB load. This incident has been resolved.

Type: Incident Duration: 8 hours and 14 minutes Affected Components: API Jan 21, 08:26:10 GMT+0 - Investigating - API cannot be accessed at the moment. This incident was created by an automated monitoring service. Jan 21, 08:34:24 GMT+0 - Resolved - API is now operational! This update was created by an automated monitoring service.

Type: Incident Duration: 9 minutes Affected Components: API Aug 6, 15:36:00 GMT+0 - Investigating - We are currently investigating this incident. Aug 6, 15:49:00 GMT+0 - Resolved - This incident has been resolved. We are root causing the issue at the moment. Thank you for your patience.

Type: Incident Duration: 24 minutes Affected Components: API Jul 24, 16:09:00 GMT+0 - Investigating - We are experiencing intermittent fluctuations in some of our core APIs. We are root causing at the moment. Jul 24, 16:15:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. There seems to be high connections to our transactions database. We are trying to reduce the connections. Jul 24, 16:30:00 GMT+0 - Resolved - This incident has been resolved. We are monitoring the health of the APIs.