Skip to content

Outage tracker / Alipay

Is Alipay down?

I'm having a problem

Operationalchecked moments ago

We reached Alipay from all 10 regions we check.

As of Oct 5, 2026, 8:18 PM UTC, Alipay answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

Last outage: 40 min on Oct 5, 2026 (web surface, from Australia).

our independent probeslive · checked Oct 5, 2026, 8:18 PM UTC
US-East1803 msOperational
US-West1249 msOperational
Europe1488 msOperational
Asia-Pacific1761 msOperational
US-Central1775 msOperational
Canada1986 msOperational
UK1463 msOperational
Southeast Asia1724 msOperational
Australia3324 msOperational
South America3761 msOperational
their status pagetheir claim, not our reading

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

Alipay response time, by region

US-East
2.9sp95 · 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-06 UTC: p95 4.7s2026-09-07 UTC: p95 5.6s2026-09-08 UTC: p95 4.7s2026-09-09 UTC: p95 5.6s2026-09-10 UTC: p95 5.7s2026-09-11 UTC: p95 5.5s2026-09-12 UTC: p95 5.2s2026-09-13 UTC: p95 5.6s2026-09-14 UTC: p95 4.8s2026-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.9s
Sep 6Sep 20Oct 5
US-West
2.0sp95 · 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-06 UTC: p95 5.4s2026-09-07 UTC: p95 5.3s2026-09-08 UTC: p95 5.6s2026-09-09 UTC: p95 5.3s2026-09-10 UTC: p95 5.5s2026-09-11 UTC: p95 5.4s2026-09-12 UTC: p95 5.5s2026-09-13 UTC: p95 5.7s2026-09-14 UTC: p95 5.7s2026-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 2.0s
Sep 6Sep 20Oct 5
Europe
4.1sp95 · 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-06 UTC: p95 5.7s2026-09-07 UTC: p95 5.7s2026-09-08 UTC: p95 5.7s2026-09-09 UTC: p95 5.9s2026-09-10 UTC: p95 6.0s2026-09-11 UTC: p95 5.8s2026-09-12 UTC: p95 5.8s2026-09-13 UTC: p95 5.8s2026-09-14 UTC: p95 5.8s2026-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.1s
Sep 6Sep 20Oct 5
Asia-Pacific
6.5sp95 · 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-06 UTC: p95 9.5s2026-09-07 UTC: p95 9.2s2026-09-08 UTC: p95 9.8s2026-09-09 UTC: p95 9.8s2026-09-10 UTC: p95 10.0s2026-09-11 UTC: p95 9.3s2026-09-12 UTC: p95 9.7s2026-09-13 UTC: p95 10.3s2026-09-14 UTC: p95 10.2s2026-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 6.5s
Sep 6Sep 20Oct 5
US-Central
3.1sp95 · 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-06 UTC: p95 6.1s2026-09-07 UTC: p95 7.4s2026-09-08 UTC: p95 7.0s2026-09-09 UTC: p95 7.5s2026-09-10 UTC: p95 7.1s2026-09-11 UTC: p95 8.2s2026-09-12 UTC: p95 8.0s2026-09-13 UTC: p95 8.1s2026-09-14 UTC: p95 9.0s2026-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.1s
Sep 6Sep 20Oct 5
Canada
3.2sp95 · 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-06 UTC: p95 9.0s2026-09-07 UTC: p95 8.5s2026-09-08 UTC: p95 9.0s2026-09-09 UTC: p95 9.0s2026-09-10 UTC: p95 8.0s2026-09-11 UTC: p95 8.3s2026-09-12 UTC: p95 8.7s2026-09-13 UTC: p95 8.9s2026-09-14 UTC: p95 8.4s2026-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.2s
Sep 6Sep 20Oct 5
UK
3.7sp95 · 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-06 UTC: p95 5.5s2026-09-07 UTC: p95 5.6s2026-09-08 UTC: p95 5.7s2026-09-09 UTC: p95 5.7s2026-09-10 UTC: p95 5.9s2026-09-11 UTC: p95 5.7s2026-09-12 UTC: p95 5.8s2026-09-13 UTC: p95 5.7s2026-09-14 UTC: p95 5.8s2026-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.7s
Sep 6Sep 20Oct 5
Southeast Asia
2.9sp95 · 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-06 UTC: p95 9.1s2026-09-07 UTC: p95 9.9s2026-09-08 UTC: p95 8.2s2026-09-09 UTC: p95 8.6s2026-09-10 UTC: p95 8.7s2026-09-11 UTC: p95 8.6s2026-09-12 UTC: p95 8.2s2026-09-13 UTC: p95 8.8s2026-09-14 UTC: p95 7.7s2026-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 2.9s
Sep 6Sep 20Oct 5
Australia
5.3sp95 · 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-06 UTC: p95 11.3s2026-09-07 UTC: p95 10.5s2026-09-08 UTC: p95 11.3s2026-09-09 UTC: p95 10.7s2026-09-10 UTC: p95 10.5s2026-09-11 UTC: p95 10.4s2026-09-12 UTC: p95 10.4s2026-09-13 UTC: p95 11.5s2026-09-14 UTC: p95 11.4s2026-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.3s
Sep 6Sep 20Oct 5
South America
4.4sp95 · 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-06 UTC: p95 12.1s2026-09-07 UTC: p95 12.3s2026-09-08 UTC: p95 12.5s2026-09-09 UTC: p95 11.8s2026-09-10 UTC: p95 11.4s2026-09-11 UTC: p95 12.7s2026-09-12 UTC: p95 12.0s2026-09-13 UTC: p95 12.5s2026-09-14 UTC: p95 12.3s2026-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.4s
Sep 6Sep 20Oct 5

Is it Alipay, 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 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: 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 Alipay go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Alipay, and again when they can reach it again. That is our own measurement from ten regions, not Alipay'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: 1803msstatus code: 200checked: Oct 5, 2026, 8:09 PM 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
      Operationallatency: 1249msstatus code: 200checked: Oct 5, 2026, 8:18 PM 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
      Operationallatency: 1775msstatus code: 200checked: Oct 5, 2026, 8:05 PM 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
      Operationallatency: 1986msstatus code: 200checked: Oct 5, 2026, 8:10 PM 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
    Operationallatency: 3761msstatus code: 200checked: Oct 5, 2026, 8:03 PM 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 1488msstatus code: 200checked: Oct 5, 2026, 8:09 PM 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
      Operationallatency: 1463msstatus code: 200checked: Oct 5, 2026, 8:07 PM 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1761msstatus code: 200checked: Oct 5, 2026, 8:15 PM 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
      Operationallatency: 1724msstatus code: 200checked: Oct 5, 2026, 8:15 PM 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
      Operationallatency: 3324msstatus code: 200checked: Oct 5, 2026, 8:03 PM 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 outages

Partial outage, 40mmeasured by our probes · Australia2026-10-05
Partial outage, 1h 20mmeasured by our probes · Australia2026-10-05
Partial outage, 2hmeasured by our probes · Australia2026-10-05
Partial outage, 41mmeasured by our probes · Australia2026-10-05
Partial outage, 20mmeasured by our probes · Australia2026-10-04
Partial outage, 1h 40mmeasured by our probes · Australia2026-10-04
Outage, 1h 22mmeasured by our probes · South America and Australia2026-10-04
Outage, 1h 40mmeasured by our probes · US-East and Australia2026-10-04

measured 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 measurements and Alipay's own claim at the time, side by side.

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

Alipay uptime measured by RealUptimeLive, from this page's own readings.
[![Alipay uptime measured by RealUptime](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 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 Alipay's SLA implies, from our measurement

Below your target

We measured 31h 36m of downtime for Alipay over the last 30 days, which is 95.6091% uptime by our reading. A 99.9% target allows 43 minutes over that period.

That is 30h 53m more than the target allows. The figure above is the pro-rata share of one month's fee for the time we could not reach it. 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.

Separately, we measured 77h 23m where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.

This is computed from our own probe measurements, 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/
RealUptime is not affiliated with Alipay; the name identifies what we measured, 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 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.