Is Razorpay down right now?

Operational. We reached Razorpay from all 2 regions we check.

How does RealUptime check if Razorpay is down?

RealUptime checks Razorpay with scheduled HTTP probes against its public, unauthenticated functional endpoints, run from named regions on a fixed cadence, plus an extra confirmation probe whenever a signal suggests a problem. This verifies that the functional endpoints we probe actually answer, not that every feature of Razorpay works end to end.

What does "degraded" mean for Razorpay?

Degraded means Razorpay answered our probe but at several times its own seven-day median response time. Degraded only ever applies to a reading that answered: a surface that is down, or one that refused our probe, is reported as down or awaiting data instead, never softened into "degraded".

What is Razorpay's current response time?

RealUptime's most recent measured response time for Razorpay, by region: Europe: 464 ms, Asia-Pacific: 956 ms. This is the latest single probe reading per region, not an average.

When did RealUptime last check Razorpay?

RealUptime's probes last checked Razorpay at 2026-09-03T01:22:07.309Z.

Is Razorpay down?

Short linkrlup.io/down/razorpay

I'm having a problem

Operationalchecked 8 minutes ago

We reached Razorpay from all 2 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Razorpay (since Aug 20, 2026).

our independent probeslive · checked Sep 3, 2026, 1:22 AM UTC

Europe464 msOperational

Asia-Pacific956 msOperational

Razorpay serves India; our Frankfurt and Tokyo regions are the closest probes we operate to that market, so those are the only ones we check from.

their status pagetheir claim, not our reading

Razorpay publishes no status feed we can read, so the only independent reading here is ours on the left.

Razorpay response time, by region

Europe

750msp95 · latest

1s500ms0ms

Aug 5Aug 19Sep 3

Asia-Pacific

1.4sp95 · latest

2s1s0ms

Aug 5Aug 19Sep 3

Is it Razorpay, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Razorpay -- it cannot diagnose Razorpay's own systems.

What we measured, and what people reported

US-East
Not monitored from this regionRazorpay is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
US-West
Not monitored from this regionRazorpay is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
Europe
Operationallatency: 464msstatus code: 401checked: Sep 3, 2026, 1:22 AM UTC
0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Razorpay normally. We do not have enough reports from Europe to say anything about what people there are seeing.
Asia-Pacific
Operationallatency: 956msstatus code: 401checked: Sep 3, 2026, 1:00 AM UTC
0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Razorpay normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
US-Central
Not monitored from this regionRazorpay is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
Canada
Not monitored from this regionRazorpay is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
UK
Not monitored from this regionRazorpay is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
Southeast Asia
Not monitored from this regionRazorpay is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
Australia
Not monitored from this regionRazorpay is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say
South America
Not monitored from this regionRazorpay is not monitored from this region.
0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Razorpay, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Razorpay yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Razorpay.

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Razorpay since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Razorpay covering any window you pick, with our measurements and Razorpay's own claim at the time, side by side.

Full availability history for Razorpay: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Put this badge in your README

Live, from this page's own readings.

[![Razorpay uptime measured by RealUptime](https://realuptime.io/outages/razorpay/badge.svg?days=30)](https://realuptime.io/outages/razorpay)

<a href="https://realuptime.io/outages/razorpay"><img src="https://realuptime.io/outages/razorpay/badge.svg?days=30" alt="Razorpay uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Razorpay's SLA implies, from our measurement

Window

What you pay per month

Uptime target in your contract

Include outages only one region saw (none)

At or above your target

We measured none of downtime for Razorpay over the 337h 29m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Razorpay's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional

https://api.razorpay.com/v1/payments

secondary

https://status.razorpay.com/

RealUptime is not affiliated with Razorpay; the name identifies what we measured, and nothing here speaks for Razorpay's own team. We send a single web request to Razorpay from 2 regions on our own schedule and time the response. We do not see inside Razorpay's systems, do not use an account or real transaction, and are not the same signal Razorpay's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Razorpay is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Razorpay serves India; our Frankfurt and Tokyo regions are the closest probes we operate to that market, so those are the only ones we check from. Read the full methodology.

Related services

Adyen Affirm Afterpay Alipay Binance