Skip to content

Outage tracker / Razorpay

Is Razorpay down?

I'm having a problem

Checks passingchecked 1 minute ago

Our checks of Razorpay pass from all 2 regions we check.

As of Oct 23, 2026, 9:54 AM UTC, RealUptime's checks of Razorpay passed in all 2 regions that returned a reading.

Front-door and live API checks

Our checks of Razorpay did not fail from two or more distant regions in the 64 days we have checked it (since Aug 20, 2026). This does not show Razorpay works for users.

our check readinglive · checked Oct 23, 2026, 9:54 AM UTC
Europe944 msChecks passing
Asia-Pacific1917 msChecks passing

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 reading here is our check reading on the left.

Razorpay response time, by region

Europe
968msp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 768ms2026-09-25 UTC: p95 608ms2026-09-26 UTC: p95 880ms2026-09-27 UTC: p95 582ms2026-09-28 UTC: p95 648ms2026-09-29 UTC: p95 654ms2026-09-30 UTC: p95 572ms2026-10-01 UTC: p95 683ms2026-10-02 UTC: p95 785ms2026-10-03 UTC: p95 579ms2026-10-04 UTC: p95 713ms2026-10-05 UTC: p95 701ms2026-10-06 UTC: p95 747ms2026-10-07 UTC: p95 710ms2026-10-08 UTC: p95 733ms2026-10-09 UTC: p95 712ms2026-10-10 UTC: p95 667ms2026-10-11 UTC: p95 739ms2026-10-12 UTC: p95 797ms2026-10-13 UTC: p95 619ms2026-10-14 UTC: p95 604ms2026-10-15 UTC: p95 603ms2026-10-16 UTC: p95 545ms2026-10-17 UTC: p95 898ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 942ms2026-10-23 UTC: p95 968ms
Sep 24Oct 8Oct 23
Asia-Pacific
2.8sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.2s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.4s2026-10-17 UTC: p95 2s2026-10-18 UTC: p95 2.3s2026-10-19 UTC: p95 2.2s2026-10-20 UTC: p95 2.3s2026-10-21 UTC: p95 2.5s2026-10-22 UTC: p95 2.6s2026-10-23 UTC: p95 2.8s
Sep 24Oct 8Oct 23

Check your own site while you wait on Razorpay

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.

Get an email when our checks of Razorpay fail from two or more distant regions, and again when they pass

Get an email when our checks change

We will email you when our checks of Razorpay fail from two or more distant regions, and again when they pass. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when our checks fail from two or more distant regions, one when they pass, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is our own reading from outside. It is not Razorpay's official status.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • 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
    • 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
  • South America
    Not monitored from this regionRazorpay is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 944msstatus code: 401checked: Oct 23, 2026, 9:54 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.
    • UK
      Not monitored from this regionRazorpay is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1917msstatus code: 401checked: Oct 23, 2026, 9:37 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.
    • 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

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 probe events

No probe events on record yet for Razorpay.

check 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 check readings and Razorpay's own claim at the time, side by side.

Full check history for Razorpay: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Put this badge in your README

Razorpay uptime by RealUptime's checksLive, from this page's own readings.
[![Razorpay uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Razorpay down?", https://realuptime.io/outages/razorpay. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

How our checks compare with Razorpay's stated SLA

At or above your target

Our checks of Razorpay failed for none over the last 30 days, which is 100% uptime by our checks. A 99.9% target allows 43 minutes over that period.

Our checks show no gap in this period. That does not rule out one you saw.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, 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/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.razorpay.com

RealUptime is not affiliated with Razorpay; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. 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.