Skip to content

Outage tracker / Paytm

Is Paytm down?

I'm having a problem

Operationalchecked moments ago

We reached Paytm from all 10 regions we check.

As of Oct 6, 2026, 10:00 PM UTC, Paytm answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

our independent probeslive · checked Oct 6, 2026, 10:00 PM UTC
US-East1642 msOperational
US-West710 msOperational
Europe772 msOperational
Asia-Pacific918 msOperational
US-Central585 msOperational
Canada1780 msOperational
UK621 msOperational
Southeast Asia871 msOperational
Australia1556 msOperational
South America1201 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.4sp95 · 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-09-07 UTC: p95 874ms2026-09-08 UTC: p95 811ms2026-09-09 UTC: p95 925ms2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 1.0s2026-09-12 UTC: p95 827ms2026-09-13 UTC: p95 973ms2026-09-14 UTC: p95 647ms2026-09-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.7s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 911ms2026-09-20 UTC: p95 829ms2026-09-21 UTC: p95 813ms2026-09-22 UTC: p95 953ms2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 980ms2026-09-28 UTC: p95 992ms2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 934ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.4s
Sep 7Sep 21Oct 6
US-West
1.8sp95 · 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-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 934ms2026-09-11 UTC: p95 816ms2026-09-12 UTC: p95 1.0s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 917ms2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 1.5s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.7s2026-10-06 UTC: p95 1.8s
Sep 7Sep 21Oct 6
Europe
1.7sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-07 UTC: p95 2.0s2026-09-08 UTC: p95 2.0s2026-09-09 UTC: p95 1.9s2026-09-10 UTC: p95 1.9s2026-09-11 UTC: p95 1.8s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.7s2026-09-14 UTC: p95 1.7s2026-09-15 UTC: p95 1.8s2026-09-16 UTC: p95 1.9s2026-09-17 UTC: p95 1.9s2026-09-18 UTC: p95 1.9s2026-09-19 UTC: p95 1.9s2026-09-20 UTC: p95 1.9s2026-09-21 UTC: p95 1.9s2026-09-22 UTC: p95 2.0s2026-09-23 UTC: p95 1.8s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.5s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.7s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.4s2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.7s
Sep 7Sep 21Oct 6
Asia-Pacific
1.7sp95 · 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.9s2026-09-08 UTC: p95 2.0s2026-09-09 UTC: p95 2.0s2026-09-10 UTC: p95 1.9s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.7s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.6s2026-09-15 UTC: p95 1.8s2026-09-16 UTC: p95 1.5s2026-09-17 UTC: p95 1.8s2026-09-18 UTC: p95 1.7s2026-09-19 UTC: p95 1.7s2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 1.6s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.6s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.5s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.4s2026-10-06 UTC: p95 1.7s
Sep 7Sep 21Oct 6
US-Central
1.3sp95 · 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-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 963ms2026-09-12 UTC: p95 840ms2026-09-13 UTC: p95 946ms2026-09-14 UTC: p95 948ms2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.0s2026-09-17 UTC: p95 900ms2026-09-18 UTC: p95 956ms2026-09-19 UTC: p95 916ms2026-09-20 UTC: p95 773ms2026-09-21 UTC: p95 858ms2026-09-22 UTC: p95 1.1s2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 960ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 918ms2026-09-28 UTC: p95 1.0s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.0s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 926ms2026-10-04 UTC: p95 1.0s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.3s
Sep 7Sep 21Oct 6
Canada
1.6sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.6s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.9s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.2s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.8s2026-10-03 UTC: p95 1.5s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.6s
Sep 7Sep 21Oct 6
UK
839msp95 · 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-07 UTC: p95 694ms2026-09-08 UTC: p95 737ms2026-09-09 UTC: p95 702ms2026-09-10 UTC: p95 629ms2026-09-11 UTC: p95 687ms2026-09-12 UTC: p95 637ms2026-09-13 UTC: p95 604ms2026-09-14 UTC: p95 529ms2026-09-15 UTC: p95 551ms2026-09-16 UTC: p95 696ms2026-09-17 UTC: p95 605ms2026-09-18 UTC: p95 560ms2026-09-19 UTC: p95 587ms2026-09-20 UTC: p95 612ms2026-09-21 UTC: p95 544ms2026-09-22 UTC: p95 622ms2026-09-23 UTC: p95 609ms2026-09-24 UTC: p95 630ms2026-09-25 UTC: p95 649ms2026-09-26 UTC: p95 686ms2026-09-27 UTC: p95 696ms2026-09-28 UTC: p95 678ms2026-09-29 UTC: p95 719ms2026-09-30 UTC: p95 773ms2026-10-01 UTC: p95 765ms2026-10-02 UTC: p95 777ms2026-10-03 UTC: p95 779ms2026-10-04 UTC: p95 754ms2026-10-05 UTC: p95 670ms2026-10-06 UTC: p95 839ms
Sep 7Sep 21Oct 6
Southeast Asia
2.2sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-09-07 UTC: p95 837ms2026-09-08 UTC: p95 712ms2026-09-09 UTC: p95 788ms2026-09-10 UTC: p95 742ms2026-09-11 UTC: p95 761ms2026-09-12 UTC: p95 798ms2026-09-13 UTC: p95 903ms2026-09-14 UTC: p95 774ms2026-09-15 UTC: p95 875ms2026-09-16 UTC: p95 879ms2026-09-17 UTC: p95 771ms2026-09-18 UTC: p95 973ms2026-09-19 UTC: p95 823ms2026-09-20 UTC: p95 850ms2026-09-21 UTC: p95 1.0s2026-09-22 UTC: p95 1.9s2026-09-23 UTC: p95 2.8s2026-09-24 UTC: p95 2.4s2026-09-25 UTC: p95 2.7s2026-09-26 UTC: p95 2.5s2026-09-27 UTC: p95 2.5s2026-09-28 UTC: p95 2.6s2026-09-29 UTC: p95 2.6s2026-09-30 UTC: p95 2.1s2026-10-01 UTC: p95 2.4s2026-10-02 UTC: p95 2.4s2026-10-03 UTC: p95 2.1s2026-10-04 UTC: p95 2.4s2026-10-05 UTC: p95 2.0s2026-10-06 UTC: p95 2.2s
Sep 7Sep 21Oct 6
Australia
1.6sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-07 UTC: p95 1.7s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.6s2026-09-11 UTC: p95 1.8s2026-09-12 UTC: p95 1.8s2026-09-13 UTC: p95 1.6s2026-09-14 UTC: p95 1.6s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.5s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.5s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.5s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 1.7s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.7s2026-10-05 UTC: p95 1.5s2026-10-06 UTC: p95 1.6s
Sep 7Sep 21Oct 6
South America
2.2sp95 · 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-07 UTC: p95 2.6s2026-09-08 UTC: p95 2.3s2026-09-09 UTC: p95 2.6s2026-09-10 UTC: p95 2.6s2026-09-11 UTC: p95 2.4s2026-09-12 UTC: p95 2.4s2026-09-13 UTC: p95 2.4s2026-09-14 UTC: p95 2.1s2026-09-15 UTC: p95 2.1s2026-09-16 UTC: p95 2.2s2026-09-17 UTC: p95 2.5s2026-09-18 UTC: p95 2.4s2026-09-19 UTC: p95 2.2s2026-09-20 UTC: p95 2.9s2026-09-21 UTC: p95 2.4s2026-09-22 UTC: p95 2.3s2026-09-23 UTC: p95 2.2s2026-09-24 UTC: p95 2.3s2026-09-25 UTC: p95 2.1s2026-09-26 UTC: p95 2.2s2026-09-27 UTC: p95 2.6s2026-09-28 UTC: p95 2.5s2026-09-29 UTC: p95 2.3s2026-09-30 UTC: p95 2.6s2026-10-01 UTC: p95 2.4s2026-10-02 UTC: p95 2.3s2026-10-03 UTC: p95 2.3s2026-10-04 UTC: p95 2.4s2026-10-05 UTC: p95 2.2s2026-10-06 UTC: p95 2.2s
Sep 7Sep 21Oct 6

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: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

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

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.

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: 1642msstatus code: 200checked: Oct 6, 2026, 9:57 PM 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: 710msstatus code: 200checked: Oct 6, 2026, 10:00 PM 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: 585msstatus code: 200checked: Oct 6, 2026, 9:49 PM 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: 1780msstatus code: 200checked: Oct 6, 2026, 9:42 PM 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: 1201msstatus code: 200checked: Oct 6, 2026, 9:49 PM 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: 772msstatus code: 200checked: Oct 6, 2026, 9:51 PM 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: 621msstatus code: 200checked: Oct 6, 2026, 9:51 PM 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: 918msstatus code: 200checked: Oct 6, 2026, 9:53 PM 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: 871msstatus code: 200checked: Oct 6, 2026, 9:45 PM 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: 1556msstatus code: 200checked: Oct 6, 2026, 9:41 PM 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

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 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 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.