Skip to content

Outage tracker / Alipay

Is Alipay down?

I'm having a problem

Checks passingchecked 4 minutes ago

Our checks of Alipay pass from all 10 regions we check.

As of Oct 14, 2026, 4:07 AM UTC, RealUptime's checks of Alipay passed in all 10 regions that returned a reading.

Front-door and live API checks

Last time our checks failed from two or more distant regions: 1h 22m on Oct 4, 2026 (web surface, from South America and Australia).

our check readinglive · checked Oct 14, 2026, 4:07 AM UTC
US-East2393 msChecks passing
US-West1706 msChecks passing
Europe3914 msChecks passing
Asia-Pacific2272 msChecks passing
US-Central2677 msChecks passing
Canada1843 msChecks passing
UK3130 msChecks passing
Southeast Asia1291 msChecks passing
Australia4250 msChecks passing
South America3906 msChecks passing
their status pagetheir claim, not our reading

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

Alipay response time, by region

US-East
2.5sp95 · latest
10s5s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 7.5s2026-09-16 UTC: p95 9.1s2026-09-17 UTC: p95 9.4s2026-09-18 UTC: p95 9.9s2026-09-19 UTC: p95 9.0s2026-09-20 UTC: p95 8.6s2026-09-21 UTC: p95 8.6s2026-09-22 UTC: p95 8.5s2026-09-23 UTC: p95 8.8s2026-09-24 UTC: p95 9.6s2026-09-25 UTC: p95 8.5s2026-09-26 UTC: p95 9.6s2026-09-27 UTC: p95 8.3s2026-09-28 UTC: p95 7.6s2026-09-29 UTC: p95 9.8s2026-09-30 UTC: p95 8.6s2026-10-01 UTC: p95 4.4s2026-10-02 UTC: p95 3.0s2026-10-03 UTC: p95 3.3s2026-10-04 UTC: p95 2.7s2026-10-05 UTC: p95 2.8s2026-10-06 UTC: p95 3.3s2026-10-07 UTC: p95 3.3s2026-10-08 UTC: p95 3.1s2026-10-09 UTC: p95 3.0s2026-10-10 UTC: p95 4.0s2026-10-11 UTC: p95 3.1s2026-10-12 UTC: p95 2.7s2026-10-13 UTC: p95 3.1s2026-10-14 UTC: p95 2.5s
Sep 15Sep 29Oct 14
US-West
1.9sp95 · latest
10s5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 6.7s2026-09-16 UTC: p95 7.2s2026-09-17 UTC: p95 7.3s2026-09-18 UTC: p95 7.3s2026-09-19 UTC: p95 7.0s2026-09-20 UTC: p95 7.3s2026-09-21 UTC: p95 7.4s2026-09-22 UTC: p95 7.3s2026-09-23 UTC: p95 7.2s2026-09-24 UTC: p95 7.4s2026-09-25 UTC: p95 7.4s2026-09-26 UTC: p95 7.4s2026-09-27 UTC: p95 7.0s2026-09-28 UTC: p95 7.3s2026-09-29 UTC: p95 7.2s2026-09-30 UTC: p95 7.3s2026-10-01 UTC: p95 2.8s2026-10-02 UTC: p95 2.4s2026-10-03 UTC: p95 2.3s2026-10-04 UTC: p95 2.2s2026-10-05 UTC: p95 1.9s2026-10-06 UTC: p95 2.6s2026-10-07 UTC: p95 2.4s2026-10-08 UTC: p95 2.5s2026-10-09 UTC: p95 2.4s2026-10-10 UTC: p95 2.8s2026-10-11 UTC: p95 2.5s2026-10-12 UTC: p95 2.4s2026-10-13 UTC: p95 2.9s2026-10-14 UTC: p95 1.9s
Sep 15Sep 29Oct 14
Europe
2.9sp95 · latest
10s5s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 5.9s2026-09-16 UTC: p95 6.5s2026-09-17 UTC: p95 6.3s2026-09-18 UTC: p95 6.3s2026-09-19 UTC: p95 6.2s2026-09-20 UTC: p95 6.1s2026-09-21 UTC: p95 6.5s2026-09-22 UTC: p95 6.5s2026-09-23 UTC: p95 6.4s2026-09-24 UTC: p95 6.4s2026-09-25 UTC: p95 6.3s2026-09-26 UTC: p95 6.2s2026-09-27 UTC: p95 5.7s2026-09-28 UTC: p95 6.2s2026-09-29 UTC: p95 6.0s2026-09-30 UTC: p95 5.8s2026-10-01 UTC: p95 4.1s2026-10-02 UTC: p95 4.4s2026-10-03 UTC: p95 4.4s2026-10-04 UTC: p95 4.2s2026-10-05 UTC: p95 4.0s2026-10-06 UTC: p95 5.0s2026-10-07 UTC: p95 4.6s2026-10-08 UTC: p95 4.1s2026-10-09 UTC: p95 3.8s2026-10-10 UTC: p95 4.5s2026-10-11 UTC: p95 3.9s2026-10-12 UTC: p95 3.9s2026-10-13 UTC: p95 4.1s2026-10-14 UTC: p95 2.9s
Sep 15Sep 29Oct 14
Asia-Pacific
2.4sp95 · latest
20s10s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 20s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 9.3s2026-09-16 UTC: p95 10.0s2026-09-17 UTC: p95 10.2s2026-09-18 UTC: p95 9.8s2026-09-19 UTC: p95 10.1s2026-09-20 UTC: p95 9.8s2026-09-21 UTC: p95 9.7s2026-09-22 UTC: p95 10.5s2026-09-23 UTC: p95 10.2s2026-09-24 UTC: p95 10.1s2026-09-25 UTC: p95 9.6s2026-09-26 UTC: p95 10.3s2026-09-27 UTC: p95 10.4s2026-09-28 UTC: p95 10.1s2026-09-29 UTC: p95 10.1s2026-09-30 UTC: p95 10.3s2026-10-01 UTC: p95 3.0s2026-10-02 UTC: p95 3.6s2026-10-03 UTC: p95 3.3s2026-10-04 UTC: p95 4.4s2026-10-05 UTC: p95 4.6s2026-10-06 UTC: p95 3.3s2026-10-07 UTC: p95 4.8s2026-10-08 UTC: p95 3.3s2026-10-09 UTC: p95 3.2s2026-10-10 UTC: p95 3.5s2026-10-11 UTC: p95 3.7s2026-10-12 UTC: p95 3.7s2026-10-13 UTC: p95 3.7s2026-10-14 UTC: p95 2.4s
Sep 15Sep 29Oct 14
US-Central
2.0sp95 · latest
10s5s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 8.3s2026-09-16 UTC: p95 7.1s2026-09-17 UTC: p95 7.1s2026-09-18 UTC: p95 8.5s2026-09-19 UTC: p95 7.7s2026-09-20 UTC: p95 7.4s2026-09-21 UTC: p95 7.3s2026-09-22 UTC: p95 9.3s2026-09-23 UTC: p95 8.3s2026-09-24 UTC: p95 7.1s2026-09-25 UTC: p95 7.2s2026-09-26 UTC: p95 8.1s2026-09-27 UTC: p95 7.9s2026-09-28 UTC: p95 7.3s2026-09-29 UTC: p95 7.6s2026-09-30 UTC: p95 8.7s2026-10-01 UTC: p95 3.1s2026-10-02 UTC: p95 3.2s2026-10-03 UTC: p95 3.2s2026-10-04 UTC: p95 2.6s2026-10-05 UTC: p95 3.0s2026-10-06 UTC: p95 3.3s2026-10-07 UTC: p95 2.8s2026-10-08 UTC: p95 3.1s2026-10-09 UTC: p95 2.8s2026-10-10 UTC: p95 3.1s2026-10-11 UTC: p95 2.9s2026-10-12 UTC: p95 3.2s2026-10-13 UTC: p95 2.9s2026-10-14 UTC: p95 2.0s
Sep 15Sep 29Oct 14
Canada
2.7sp95 · latest
20s10s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 20s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 7.7s2026-09-16 UTC: p95 7.7s2026-09-17 UTC: p95 8.2s2026-09-18 UTC: p95 8.9s2026-09-19 UTC: p95 8.6s2026-09-20 UTC: p95 8.4s2026-09-21 UTC: p95 9.4s2026-09-22 UTC: p95 10.1s2026-09-23 UTC: p95 9.6s2026-09-24 UTC: p95 8.6s2026-09-25 UTC: p95 9.9s2026-09-26 UTC: p95 9.1s2026-09-27 UTC: p95 10.1s2026-09-28 UTC: p95 9.3s2026-09-29 UTC: p95 8.7s2026-09-30 UTC: p95 8.8s2026-10-01 UTC: p95 3.4s2026-10-02 UTC: p95 4.4s2026-10-03 UTC: p95 3.5s2026-10-04 UTC: p95 3.0s2026-10-05 UTC: p95 3.3s2026-10-06 UTC: p95 3.2s2026-10-07 UTC: p95 3.0s2026-10-08 UTC: p95 3.2s2026-10-09 UTC: p95 3s2026-10-10 UTC: p95 3.8s2026-10-11 UTC: p95 3.1s2026-10-12 UTC: p95 3.1s2026-10-13 UTC: p95 3.2s2026-10-14 UTC: p95 2.7s
Sep 15Sep 29Oct 14
UK
3.4sp95 · latest
10s5s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 5.8s2026-09-16 UTC: p95 5.7s2026-09-17 UTC: p95 5.9s2026-09-18 UTC: p95 6.1s2026-09-19 UTC: p95 5.7s2026-09-20 UTC: p95 5.7s2026-09-21 UTC: p95 6.6s2026-09-22 UTC: p95 5.8s2026-09-23 UTC: p95 5.9s2026-09-24 UTC: p95 5.9s2026-09-25 UTC: p95 5.8s2026-09-26 UTC: p95 5.7s2026-09-27 UTC: p95 6.0s2026-09-28 UTC: p95 5.8s2026-09-29 UTC: p95 6.1s2026-09-30 UTC: p95 5.8s2026-10-01 UTC: p95 3.8s2026-10-02 UTC: p95 3.3s2026-10-03 UTC: p95 3.2s2026-10-04 UTC: p95 4.0s2026-10-05 UTC: p95 3.6s2026-10-06 UTC: p95 3.6s2026-10-07 UTC: p95 4.2s2026-10-08 UTC: p95 5.0s2026-10-09 UTC: p95 3.3s2026-10-10 UTC: p95 4.8s2026-10-11 UTC: p95 3.0s2026-10-12 UTC: p95 5.2s2026-10-13 UTC: p95 3.9s2026-10-14 UTC: p95 3.4s
Sep 15Sep 29Oct 14
Southeast Asia
6.4sp95 · latest
20s10s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 20s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 9.2s2026-09-16 UTC: p95 8.7s2026-09-17 UTC: p95 9.1s2026-09-18 UTC: p95 9.3s2026-09-19 UTC: p95 9.1s2026-09-20 UTC: p95 10.3s2026-09-21 UTC: p95 11.6s2026-09-22 UTC: p95 10.9s2026-09-23 UTC: p95 15.9s2026-09-24 UTC: p95 10.6s2026-09-25 UTC: p95 10.5s2026-09-26 UTC: p95 10.8s2026-09-27 UTC: p95 11.0s2026-09-28 UTC: p95 11.0s2026-09-29 UTC: p95 9.8s2026-09-30 UTC: p95 8.6s2026-10-01 UTC: p95 6.0s2026-10-02 UTC: p95 4.9s2026-10-03 UTC: p95 5.4s2026-10-04 UTC: p95 4.3s2026-10-05 UTC: p95 3.3s2026-10-06 UTC: p95 4.9s2026-10-07 UTC: p95 3.2s2026-10-08 UTC: p95 6.0s2026-10-09 UTC: p95 4.1s2026-10-10 UTC: p95 5.7s2026-10-11 UTC: p95 5.2s2026-10-12 UTC: p95 5.0s2026-10-13 UTC: p95 4.8s2026-10-14 UTC: p95 6.4s
Sep 15Sep 29Oct 14
Australia
4.6sp95 · latest
20s10s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 20s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 11.7s2026-09-16 UTC: p95 10.6s2026-09-17 UTC: p95 11.0s2026-09-18 UTC: p95 10.4s2026-09-19 UTC: p95 10.4s2026-09-20 UTC: p95 10.1s2026-09-21 UTC: p95 11.2s2026-09-22 UTC: p95 12.2s2026-09-23 UTC: p95 11.3s2026-09-24 UTC: p95 10.7s2026-09-25 UTC: p95 10.7s2026-09-26 UTC: p95 10.9s2026-09-27 UTC: p95 10.8s2026-09-28 UTC: p95 11.5s2026-09-29 UTC: p95 10.7s2026-09-30 UTC: p95 10.7s2026-10-01 UTC: p95 6.7s2026-10-02 UTC: p95 4.8s2026-10-03 UTC: p95 4.7s2026-10-04 UTC: p95 5.6s2026-10-05 UTC: p95 5.3s2026-10-06 UTC: p95 6.9s2026-10-07 UTC: p95 4.8s2026-10-08 UTC: p95 5.2s2026-10-09 UTC: p95 4.6s2026-10-10 UTC: p95 4.9s2026-10-11 UTC: p95 5.0s2026-10-12 UTC: p95 5.7s2026-10-13 UTC: p95 6.3s2026-10-14 UTC: p95 4.6s
Sep 15Sep 29Oct 14
South America
4.9sp95 · latest
20s10s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 20s. Days with no samples are not plotted, not shown as zero.2026-09-15 UTC: p95 11.6s2026-09-16 UTC: p95 13.4s2026-09-17 UTC: p95 12.4s2026-09-18 UTC: p95 11.5s2026-09-19 UTC: p95 11.4s2026-09-20 UTC: p95 11.0s2026-09-21 UTC: p95 11.9s2026-09-22 UTC: p95 13.1s2026-09-23 UTC: p95 11.3s2026-09-24 UTC: p95 11.7s2026-09-25 UTC: p95 13.5s2026-09-26 UTC: p95 11.9s2026-09-27 UTC: p95 11.5s2026-09-28 UTC: p95 10.8s2026-09-29 UTC: p95 11.9s2026-09-30 UTC: p95 13.2s2026-10-01 UTC: p95 6.5s2026-10-02 UTC: p95 5.5s2026-10-03 UTC: p95 5.3s2026-10-04 UTC: p95 7.0s2026-10-05 UTC: p95 4.3s2026-10-06 UTC: p95 6.2s2026-10-07 UTC: p95 5.8s2026-10-08 UTC: p95 4.7s2026-10-09 UTC: p95 4.8s2026-10-10 UTC: p95 5.3s2026-10-11 UTC: p95 4.9s2026-10-12 UTC: p95 5.3s2026-10-13 UTC: p95 5.7s2026-10-14 UTC: p95 4.9s
Sep 15Sep 29Oct 14

Check your own site while you wait on Alipay

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 Alipay. It cannot diagnose Alipay's own systems.

What we measured, function by function

Alipay 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: Checks passingSouth America: Checks passing

Get an email when our checks of Alipay 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 Alipay 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 Alipay'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: 2393msstatus code: 200checked: Oct 14, 2026, 4:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Alipay normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1706msstatus code: 200checked: Oct 14, 2026, 4:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Alipay normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 2677msstatus code: 200checked: Oct 14, 2026, 3:54 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Alipay normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 1843msstatus code: 200checked: Oct 14, 2026, 4:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Alipay normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 3906msstatus code: 200checked: Oct 14, 2026, 4:05 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Alipay 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: 3914msstatus code: 200checked: Oct 14, 2026, 4:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Alipay normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 3130msstatus code: 200checked: Oct 14, 2026, 4:07 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Alipay normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2272msstatus code: 200checked: Oct 14, 2026, 4:01 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Alipay normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 1291msstatus code: 200checked: Oct 14, 2026, 4:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Alipay normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 4250msstatus code: 200checked: Oct 14, 2026, 3:57 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Alipay 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 Alipay, 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 Alipay yet, which is not evidence that nothing is wrong.

Recent probe events

Checks failing, 1h 22mour checks · South America and Australia2026-10-04
Checks failing, 1h 40mour checks · US-East and Australia2026-10-04
Checks failing, 2h 59mour checks · Europe and South America and Australia2026-10-03
Checks failing, 3h 22mour checks · South America and Australia2026-10-03
Checks failing, 1hour checks · Australia and Canada2026-10-03
Checks failing, 2hour checks · South America and Australia2026-10-02
Checks failing, 2h 1mour checks · US-West and Australia2026-10-01
Checks failing, 4h 12mour checks · South America and Australia2026-09-15

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

We have been measuring Alipay 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 Alipay covering any window you pick, with our check readings and Alipay's own claim at the time, side by side.

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

Alipay uptime by RealUptime's checksLive, from this page's own readings.
[![Alipay uptime by RealUptime's checks](https://realuptime.io/outages/alipay/badge.svg?days=30)](https://realuptime.io/outages/alipay)
<a href="https://realuptime.io/outages/alipay"><img src="https://realuptime.io/outages/alipay/badge.svg?days=30" alt="Alipay 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 Alipay down?", https://realuptime.io/outages/alipay. 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 Alipay's stated SLA

Below your target

Our checks of Alipay failed for 18h 35m over the last 30 days, which is 97.4187% uptime by our checks. A 99.9% target allows 43 minutes over that period.

That is 17h 51m more than the target allows. The figure above is the pro-rata share of one month's fee for the time our checks failed, an estimate from our checks. Alipaydecides what counts. Your contract probably uses a tiered credit schedule instead, and we have not read it, so treat this as one common way to reason about a credit rather than the amount they owe.

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 Alipay'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://openapi.alipay.com/gateway.do
secondary
https://global.alipay.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: openapi.alipay.com

RealUptime is not affiliated with Alipay; the name identifies what we checked, and nothing here speaks for Alipay's own team. We send a single web request to Alipay from 10 regions on our own schedule and time the response. We do not see inside Alipay's systems, do not use an account or real transaction, and are not the same signal Alipay's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Alipay 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.