Skip to content

Outage tracker / Paytm

Is Paytm down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Paytm from all 10 regions we check.

Functional endpoints verified

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

our independent probeslive · checked Sep 5, 2026, 2:07 AM UTC
US-East738 msOperational
US-West742 msOperational
Europe917 msOperational
Asia-Pacific1977 msOperational
US-Central1215 msOperational
Canada1010 msOperational
UK448 msOperational
Southeast Asia1335 msOperational
Australia425 msOperational
South America1308 msOperational
their status pagetheir claim, not our reading

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

Paytm response time, by region

US-East
1.1sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 1.4s2026-08-23 UTC: p95 935ms2026-08-24 UTC: p95 990ms2026-08-25 UTC: p95 860ms2026-08-26 UTC: p95 932ms2026-08-27 UTC: p95 773ms2026-08-28 UTC: p95 1.2s2026-08-29 UTC: p95 884ms2026-08-30 UTC: p95 925ms2026-08-31 UTC: p95 848ms2026-09-01 UTC: p95 892ms2026-09-02 UTC: p95 972ms2026-09-03 UTC: p95 1.3s2026-09-04 UTC: p95 1.3s2026-09-05 UTC: p95 1.1s
Aug 7Aug 21Sep 5
US-West
1.3sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 1.3s2026-08-23 UTC: p95 1.4s2026-08-24 UTC: p95 1.3s2026-08-25 UTC: p95 1.4s2026-08-26 UTC: p95 1.6s2026-08-27 UTC: p95 1.5s2026-08-28 UTC: p95 1.4s2026-08-29 UTC: p95 1.4s2026-08-30 UTC: p95 1.7s2026-08-31 UTC: p95 1.4s2026-09-01 UTC: p95 1.4s2026-09-02 UTC: p95 1.6s2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 1.5s2026-09-05 UTC: p95 1.3s
Aug 7Aug 21Sep 5
Europe
1.3sp95 · 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-08-22 UTC: p95 1.1s2026-08-23 UTC: p95 1.7s2026-08-24 UTC: p95 2.0s2026-08-25 UTC: p95 1.7s2026-08-26 UTC: p95 1.8s2026-08-27 UTC: p95 1.9s2026-08-28 UTC: p95 1.8s2026-08-29 UTC: p95 1.7s2026-08-30 UTC: p95 1.8s2026-08-31 UTC: p95 1.9s2026-09-01 UTC: p95 1.8s2026-09-02 UTC: p95 1.9s2026-09-03 UTC: p95 1.8s2026-09-04 UTC: p95 1.8s2026-09-05 UTC: p95 1.3s
Aug 7Aug 21Sep 5
Asia-Pacific
2.2sp95 · 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-08-22 UTC: p95 1.1s2026-08-23 UTC: p95 1.8s2026-08-24 UTC: p95 1.7s2026-08-25 UTC: p95 1.9s2026-08-26 UTC: p95 1.8s2026-08-27 UTC: p95 1.8s2026-08-28 UTC: p95 1.9s2026-08-29 UTC: p95 1.8s2026-08-30 UTC: p95 2.1s2026-08-31 UTC: p95 2.2s2026-09-01 UTC: p95 2.0s2026-09-02 UTC: p95 2.2s2026-09-03 UTC: p95 2.4s2026-09-04 UTC: p95 2.5s2026-09-05 UTC: p95 2.2s
Aug 7Aug 21Sep 5
US-Central
1.2sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.4s2026-09-04 UTC: p95 1.4s2026-09-05 UTC: p95 1.2s
Aug 7Aug 21Sep 5
Canada
1.3sp95 · latest
2.5s1.3s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 2.1s2026-09-05 UTC: p95 1.3s
Aug 7Aug 21Sep 5
UK
644msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 768ms2026-09-04 UTC: p95 884ms2026-09-05 UTC: p95 644ms
Aug 7Aug 21Sep 5
Southeast Asia
1.3sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.2s2026-09-04 UTC: p95 1.3s2026-09-05 UTC: p95 1.3s
Aug 7Aug 21Sep 5
Australia
941msp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 2.1s2026-09-04 UTC: p95 1.7s2026-09-05 UTC: p95 941ms
Aug 7Aug 21Sep 5
South America
1.7sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 2.5s2026-09-04 UTC: p95 2.4s2026-09-05 UTC: p95 1.7s
Aug 7Aug 21Sep 5
Why some readings show as awaiting data. 1 of 20 readings for Paytm came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 406, 429 or 451, a redirect loop, or a timeout we could rule out as a real outage using a second endpoint) rather than a normal success or failure. That tells us about our own probe's reception, not about Paytm's actual health, so we publish no verdict for those readings rather than guessing in either direction. 1 of those reading received an actual response: we confirmed the connection, the TLS handshake, and the edge all answered, with a real measured latency. That is a positive result, we verified reachability, just not through the specific path automated checks are filtered on. Read how we tell the difference.

Is it Paytm, 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 Paytm -- it cannot diagnose Paytm's own systems.

What we measured, function by function

Paytm answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: Awaiting dataCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
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
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 738msstatus code: 200checked: Sep 5, 2026, 2:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Paytm normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 742msstatus code: 200checked: Sep 5, 2026, 2:00 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Paytm normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 1215msstatus code: 200checked: Sep 5, 2026, 2:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Paytm normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 1010msstatus code: 200checked: Sep 5, 2026, 2:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Paytm normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 1308msstatus code: 200checked: Sep 5, 2026, 1:59 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Paytm normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 917msstatus code: 200checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Paytm normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 448msstatus code: 200checked: Sep 5, 2026, 1:56 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Paytm normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1977msstatus code: 200checked: Sep 5, 2026, 2:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Paytm normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1335msstatus code: 200checked: Sep 5, 2026, 1:56 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Paytm normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 425msstatus code: 200checked: Sep 5, 2026, 1:59 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Paytm normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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

These are unverified reports from people using Paytm, 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 Paytm yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for Paytm.

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

We have been measuring Paytm since August 22, 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 Paytm covering any window you pick, with our measurements and Paytm's own claim at the time, side by side.

Full availability history for Paytm: 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

Get told when we measure this

We will tell you when our probes stop reaching Paytm, and again when they can reach it again. That is our own measurement from ten regions, not Paytm'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.

Put this badge in your README

Paytm uptime measured by RealUptimeLive, from this page's own readings.
[![Paytm uptime measured by RealUptime](https://realuptime.io/outages/paytm/badge.svg?days=30)](https://realuptime.io/outages/paytm)
<a href="https://realuptime.io/outages/paytm"><img src="https://realuptime.io/outages/paytm/badge.svg?days=30" alt="Paytm 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 Paytm's SLA implies, from our measurement

At or above your target

We measured none of downtime for Paytm over the 338h 7m since we started watching it on 2026-08-22, 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 Paytm'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: live API
https://securegw.paytm.in/theia/api/v1/showPaymentPage
secondary
https://paytm.com/
RealUptime is not affiliated with Paytm; the name identifies what we measured, and nothing here speaks for Paytm's own team. We send a single web request to Paytm from 10 regions on our own schedule and time the response. We do not see inside Paytm's systems, do not use an account or real transaction, and are not the same signal Paytm's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Paytm 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. Read the full methodology.