Skip to content

Outage tracker / Razorpay

Is Razorpay down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Razorpay from all 2 regions we check.

As of Oct 6, 2026, 9:57 PM UTC, Razorpay answered RealUptime's probes in all 2 regions that returned a reading.

Functional endpoints verified

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

our independent probeslive · checked Oct 6, 2026, 9:57 PM UTC
Europe422 msOperational
Asia-Pacific825 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
759msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-07 UTC: p95 590ms2026-09-08 UTC: p95 579ms2026-09-09 UTC: p95 536ms2026-09-10 UTC: p95 665ms2026-09-11 UTC: p95 646ms2026-09-12 UTC: p95 710ms2026-09-13 UTC: p95 700ms2026-09-14 UTC: p95 636ms2026-09-15 UTC: p95 671ms2026-09-16 UTC: p95 698ms2026-09-17 UTC: p95 730ms2026-09-18 UTC: p95 689ms2026-09-19 UTC: p95 692ms2026-09-20 UTC: p95 791ms2026-09-21 UTC: p95 801ms2026-09-22 UTC: p95 756ms2026-09-23 UTC: p95 776ms2026-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 759ms
Sep 7Sep 21Oct 6
Asia-Pacific
1.3sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.1s2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 982ms2026-09-17 UTC: p95 1.0s2026-09-18 UTC: p95 967ms2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 2.1s2026-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.3s
Sep 7Sep 21Oct 6

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.

Get an email when we see Razorpay go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Razorpay, and again when they can reach it again. That is our own measurement from ten regions, not Razorpay's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

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 we measured, 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
      Operationallatency: 422msstatus code: 401checked: Oct 6, 2026, 9:30 PM 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
      Operationallatency: 825msstatus code: 401checked: Oct 6, 2026, 9:57 PM 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 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

Put this badge in your README

Razorpay uptime measured by RealUptimeLive, 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

At or above your target

We measured none of downtime for Razorpay over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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.