Skip to content

Outage tracker / Paytm

Is Paytm down?

I'm having a problem

Awaiting datachecked 2 minutes ago

Our checks of Paytm pass from 9 of the 10 regions we check, and have no usable reading from the rest. A missing reading is an absence of data, not an all-clear and not an outage.

As of Oct 14, 2026, 2:08 PM UTC, RealUptime's checks of Paytm passed in all 9 regions that returned a reading. RealUptime could not obtain a reading from Australia, which is a fact about our own check there and is not evidence about Paytm.

Front-door and live API checks

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

our check readinglive · checked Oct 14, 2026, 2:08 PM UTC
US-East606 msChecks passing
US-West654 msChecks passing
Europe560 msChecks passing
Asia-Pacific1640 msChecks passing
US-Central1150 msChecks passing
Canada802 msChecks passing
UK557 msChecks passing
Southeast Asia1828 msChecks passing
Australia10003 msAwaiting data
South America1620 msChecks passing
their status pagetheir claim, not our reading

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

Paytm response time, by region

US-East
805msp95 · 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-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.4s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 969ms2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 913ms2026-10-14 UTC: p95 805ms
Sep 15Sep 29Oct 14
US-West
1.6sp95 · 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-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.8s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.6s
Sep 15Sep 29Oct 14
Europe
1.6sp95 · 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-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.7s2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.8s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.6s
Sep 15Sep 29Oct 14
Asia-Pacific
1.3sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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.8s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.6s2026-10-09 UTC: p95 1.5s2026-10-10 UTC: p95 1.6s2026-10-11 UTC: p95 1.6s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.3s
Sep 15Sep 29Oct 14
US-Central
728msp95 · 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-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.2s2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.0s2026-10-09 UTC: p95 934ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 728ms
Sep 15Sep 29Oct 14
Canada
1sp95 · 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-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.6s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.4s2026-10-12 UTC: p95 1.5s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1s
Sep 15Sep 29Oct 14
UK
646msp95 · 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-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 860ms2026-10-07 UTC: p95 651ms2026-10-08 UTC: p95 731ms2026-10-09 UTC: p95 708ms2026-10-10 UTC: p95 698ms2026-10-11 UTC: p95 865ms2026-10-12 UTC: p95 768ms2026-10-13 UTC: p95 863ms2026-10-14 UTC: p95 646ms
Sep 15Sep 29Oct 14
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-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.2s2026-10-07 UTC: p95 2.0s2026-10-08 UTC: p95 2.1s2026-10-09 UTC: p95 2.1s2026-10-10 UTC: p95 2.2s2026-10-11 UTC: p95 2.1s2026-10-12 UTC: p95 2.2s2026-10-13 UTC: p95 1.9s2026-10-14 UTC: p95 2.2s
Sep 15Sep 29Oct 14
Australia
1.2sp95 · 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-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.6s2026-10-07 UTC: p95 1.5s2026-10-08 UTC: p95 1.8s2026-10-09 UTC: p95 1.7s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 2.4s2026-10-12 UTC: p95 2.0s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.2s
Sep 15Sep 29Oct 14
South America
1.9sp95 · 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-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.2s2026-10-07 UTC: p95 2.1s2026-10-08 UTC: p95 2.2s2026-10-09 UTC: p95 1.9s2026-10-10 UTC: p95 2.2s2026-10-11 UTC: p95 2.2s2026-10-12 UTC: p95 2.0s2026-10-13 UTC: p95 1.9s2026-10-14 UTC: p95 1.9s
Sep 15Sep 29Oct 14
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, 405, 406, 429 or 451, a redirect loop, or a timeout that a second endpoint answered) rather than a normal pass or failure. That tells us about our own probe's reception, not about Paytm's health, so we publish no verdict for those readings rather than guessing in either direction. Read how we tell the difference.

Check your own site while you wait on Paytm

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Awaiting dataSouth America: Checks passing

Get an email when our checks of Paytm 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 Paytm 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 Paytm'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
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 606msstatus code: 200checked: Oct 14, 2026, 2:02 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
      Checks passinglatency: 654msstatus code: 200checked: Oct 14, 2026, 2:05 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
      Checks passinglatency: 1150msstatus code: 200checked: Oct 14, 2026, 1:57 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
      Checks passinglatency: 802msstatus code: 200checked: Oct 14, 2026, 1:52 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
    Checks passinglatency: 1620msstatus code: 200checked: Oct 14, 2026, 2:08 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 560msstatus code: 200checked: Oct 14, 2026, 2:03 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
      Checks passinglatency: 557msstatus code: 200checked: Oct 14, 2026, 1:52 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
    Awaiting dataAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1640msstatus code: 200checked: Oct 14, 2026, 2:05 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
      Checks passinglatency: 1828msstatus code: 200checked: Oct 14, 2026, 1:55 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
      Awaiting datalatency: 10003msstatus code: nonecheck reading: nonechecked: Oct 14, 2026, 1:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayPaytm refused our Australia probe, so we have no reading from there, and a refused probe is not a confirmed outage. We also do not have enough reports from Australia to say anything on their own.

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

No probe events on record yet for Paytm.

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

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

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

The badge shows the share of our checks that passed 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 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 Paytm down?", https://realuptime.io/outages/paytm. 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 Paytm's stated SLA

At or above your target

Our checks of Paytm 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 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/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: securegw.paytm.in

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