Razorpay Outage History
3 incidents recorded over the last 365 days, 3 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Razorpay Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 17, 2026 | RazorpayX Payouts — unavailable | 412h 30m | Resolved |
| Apr 7, 2026 | Dashboard — unavailableLast error recorded: 2022-08-05T22:55:27.851864Z | 2834h 48m | Resolved |
| Apr 7, 2026 | Payments API — unavailableLast error recorded: 2022-08-04T22:44:04.073842Z | 2842h 6m | Resolved |
How to Read This Razorpay Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Razorpay acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Razorpay outage in this window ran 118d 10h, against a mean recovery of 84d 13h. If you depend on Razorpay in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.