Juspay Outage History

Juspay is up right now

Juspay had 6 outages in the last 2 years — averaging 0.2 incidents per month.

There were 6 Juspay outages since July 24, 2024. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.juspay.in

Minor March 26, 2026

Sandbox isn't accessible at the moment (automated)

Detected by Pingoru
Mar 26, 2026, 02:30 PM UTC
Resolved
Mar 26, 2026, 02:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 26, 2026, 02:30 PM UTC

    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.

Read the full incident report →

Minor December 30, 2025

Timeouts observed for Express Checkout APIs

Detected by Pingoru
Dec 30, 2025, 11:34 AM UTC
Resolved
Dec 30, 2025, 11:34 AM UTC
Duration
Timeline · 1 update
  1. resolved Dec 30, 2025, 11:34 AM UTC

    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.

Read the full incident report →

Minor May 6, 2025

Latency spike in APIs

Detected by Pingoru
May 06, 2025, 09:50 AM UTC
Resolved
May 06, 2025, 09:50 AM UTC
Duration
Timeline · 1 update
  1. resolved May 06, 2025, 09:50 AM UTC

    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.

Read the full incident report →

Minor January 21, 2025

API isn't accessible at the moment (automated)

Detected by Pingoru
Jan 21, 2025, 08:26 AM UTC
Resolved
Jan 21, 2025, 08:26 AM UTC
Duration
Timeline · 1 update
  1. resolved Jan 21, 2025, 08:26 AM UTC

    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.

Read the full incident report →

Minor August 6, 2024

Intermittent fluctuations in Express Checkout APIs

Detected by Pingoru
Aug 06, 2024, 03:36 PM UTC
Resolved
Aug 06, 2024, 03:36 PM UTC
Duration
Timeline · 1 update
  1. resolved Aug 06, 2024, 03:36 PM UTC

    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.

Read the full incident report →

Minor July 24, 2024

Intermittent fluctuations in core APIs

Detected by Pingoru
Jul 24, 2024, 04:09 PM UTC
Resolved
Jul 24, 2024, 04:09 PM UTC
Duration
Timeline · 1 update
  1. resolved Jul 24, 2024, 04:09 PM UTC

    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.

Read the full incident report →