Skip to main content
Razorpay logo

Is Razorpay Down?

No — Razorpay is up

Reachable from all 8 checked regions

Average response time: 927ms

Last checked · checks run every 6 hours

Official status page: https://status.razorpay.com

Razorpay uptime

100%
Last 7 days
100%
Last 30 days
99.90%
Last 90 days
590ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 33 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

31-day clean streak
Sep 12: 100.00% uptime, 30 checks
Sep 13: 100.00% uptime, 31 checks
Sep 14: 100.00% uptime, 31 checks
Sep 15: 100.00% uptime, 30 checks
Sep 16: 100.00% uptime, 28 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 30 checks
Sep 21: 100.00% uptime, 29 checks
Sep 22: 100.00% uptime, 31 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 28 checks
Sep 25: 100.00% uptime, 31 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 31 checks
Sep 28: 100.00% uptime, 31 checks
Sep 29: 100.00% uptime, 29 checks
Sep 30: 100.00% uptime, 40 checks
Oct 1: 100.00% uptime, 30 checks
Oct 2: 100.00% uptime, 29 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 28 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 31 checks
Oct 10: 100.00% uptime, 28 checks
Oct 11: 100.00% uptime, 31 checks
Sep 12 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

iad
149ms
DNS 70ms TCP 2ms TLS 4ms TTFB 118ms
jnb
2220ms
DNS 188ms TCP 0ms TLS 5ms TTFB 1887ms
lax
1115ms
DNS 1ms TCP 3ms TLS 4ms TTFB 1088ms
lhr
150ms
DNS 84ms TCP 2ms TLS 4ms TTFB 124ms
nrt
1853ms
DNS 0ms TCP 1ms TLS 4ms TTFB 1062ms
ord
130ms
DNS 22ms TCP 1ms TLS 3ms TTFB 93ms
sin
913ms
DNS 0ms TCP 1ms TLS 3ms TTFB 628ms
sjc
888ms
DNS 1ms TCP 1ms TLS 4ms TTFB 871ms

What Razorpay does

Razorpay is an Indian payments company. It provides a payment gateway and checkout for collecting money online through cards, UPI and net banking, and through RazorpayX it also handles outbound payouts and payroll. Businesses use it on both sides of their cash flow, so an incident can stop revenue arriving or stop salaries and vendor payments going out.

What an outage looks like

Checkout fails to open or hangs after a customer picks a payment method, so orders are abandoned at the last step. Payments API calls return errors or time out. UPI collections stop completing. Payment links will not load for the customers sent them. Payouts and payroll runs fail or stay pending in the dashboard.

What to do about it

Read status.razorpay.com, which lists Payments API, Checkout, Dashboard, Payment Link, RazorpayX Payouts, RazorpayX Payroll and Optimizer as separate components with ninety days of history each. Money coming in and money going out are reported separately, so check the side you actually need. Avoid re-running a payout or payroll batch that shows as pending until the component is operational.

Is it down for everyone, or just you?

If this page says Razorpay is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Stripe
Stripe
Adyen
Adyen
Square
Square
Authorize.Net
Authorize.Net

Razorpay outage FAQ

Collections are working but payouts are failing. Is Razorpay down?
It can still be a Razorpay incident. RazorpayX Payouts and RazorpayX Payroll are components separate from Payments API and Checkout on status.razorpay.com, so the outbound side can fail while customers pay you normally. Check those rows specifically. Payroll failures carry a deadline that the collections side does not, so treat them as the more urgent of the two.
A customer says checkout would not open. Is that an outage?
Check the Checkout component, which is listed separately from Payments API. Checkout failing affects the customer-facing step even when the API behind it is healthy, and the symptom is an abandoned order rather than a visible error on your side. A single customer's browser or network produces the same result, so compare against your overall order rate.
Will payments taken during an incident be lost?
A payment is captured once Razorpay records it, so check the dashboard for the affected window rather than assuming either way. The bigger risk during an incident is the opposite one: a customer who saw no confirmation may pay a second time. Reconcile against Razorpay's own records before refunding or re-charging anyone, because duplicates are easier to create than to unwind.
Is it Razorpay, or the bank, or UPI?
Razorpay routes payments on to banks and the UPI network, and that last hop is outside its control, so a bank or network problem produces failures that look identical from your checkout. status.razorpay.com covers Razorpay's own components only. If everything there is operational and failures cluster on one bank or one payment method, the cause is likely downstream.
Does the dashboard being down mean payments have stopped?
No. Dashboard is its own component on status.razorpay.com, so you can lose the interface while Payments API and Checkout keep collecting money normally. That is worth checking before announcing anything to customers, because losing your own visibility is the thing most likely to feel like an outage when the payment path is actually fine.

How we measure this

  • We request Razorpay's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Razorpay publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Razorpay goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required