Juspay Outage History

Juspay is up right now

Juspay had 5 outages in the last 2 years totaling 35m of downtime — averaging 0.2 incidents per month.

There were 5 Juspay outages since November 22, 2024 totaling 35m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.juspay.in

Minor May 27, 2026

Core APIs experienced timeouts

Detected by Pingoru
May 27, 2026, 05:20 AM UTC
Resolved
May 27, 2026, 05:22 AM UTC
Duration
2m
Timeline · 2 updates
  1. investigating May 27, 2026, 05:20 AM UTC

    We are currently investigating this incident..

  2. resolved May 27, 2026, 05:22 AM UTC

    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..

Read the full incident report →

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:33 PM UTC
Duration
2m
Timeline · 2 updates
  1. investigating Mar 26, 2026, 02:30 PM UTC

    Sandbox cannot be accessed at the moment. This incident was created by an automated monitoring service..

  2. resolved Mar 26, 2026, 02:33 PM UTC

    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:36 AM UTC
Duration
2m
Timeline · 2 updates
  1. 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..

  2. 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..

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, 10:10 AM UTC
Duration
20m
Timeline · 2 updates
  1. investigating May 06, 2025, 09:50 AM UTC

    We are currently investigating this incident..

  2. resolved May 06, 2025, 10:10 AM UTC

    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:34 AM UTC
Duration
8m
Timeline · 2 updates
  1. investigating Jan 21, 2025, 08:26 AM UTC

    API cannot be accessed at the moment. This incident was created by an automated monitoring service..

  2. resolved Jan 21, 2025, 08:34 AM UTC

    API is now operational! This update was created by an automated monitoring service..

Read the full incident report →