Skip to content

Outage tracker / GoCardless

Is GoCardless down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached GoCardless from all 10 regions we check.

Functional endpoints verified

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

our independent probeslive · checked Sep 5, 2026, 2:06 AM UTC
US-East317 msOperational
US-West326 msOperational
Europe184 msOperational
Asia-Pacific570 msOperational
US-Central309 msOperational
Canada592 msOperational
UK281 msOperational
Southeast Asia1108 msOperational
Australia723 msOperational
South America481 msOperational
their status pagetheir claim, not our reading

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

GoCardless response time, by region

US-East
368msp95 · 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 827ms2026-08-23 UTC: p95 1.0s2026-08-24 UTC: p95 964ms2026-08-25 UTC: p95 1.2s2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 1.1s2026-08-29 UTC: p95 870ms2026-08-30 UTC: p95 1.0s2026-08-31 UTC: p95 821ms2026-09-01 UTC: p95 828ms2026-09-02 UTC: p95 922ms2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 368ms
Aug 7Aug 21Sep 5
US-West
566msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 346ms2026-08-23 UTC: p95 322ms2026-08-24 UTC: p95 502ms2026-08-25 UTC: p95 391ms2026-08-26 UTC: p95 427ms2026-08-27 UTC: p95 784ms2026-08-28 UTC: p95 652ms2026-08-29 UTC: p95 436ms2026-08-30 UTC: p95 333ms2026-08-31 UTC: p95 537ms2026-09-01 UTC: p95 565ms2026-09-02 UTC: p95 770ms2026-09-03 UTC: p95 617ms2026-09-04 UTC: p95 549ms2026-09-05 UTC: p95 566ms
Aug 7Aug 21Sep 5
Europe
182msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 266ms2026-08-23 UTC: p95 330ms2026-08-24 UTC: p95 612ms2026-08-25 UTC: p95 201ms2026-08-26 UTC: p95 315ms2026-08-27 UTC: p95 386ms2026-08-28 UTC: p95 219ms2026-08-29 UTC: p95 347ms2026-08-30 UTC: p95 353ms2026-08-31 UTC: p95 441ms2026-09-01 UTC: p95 405ms2026-09-02 UTC: p95 492ms2026-09-03 UTC: p95 365ms2026-09-04 UTC: p95 267ms2026-09-05 UTC: p95 182ms
Aug 7Aug 21Sep 5
Asia-Pacific
696msp95 · 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-08-22 UTC: p95 507ms2026-08-23 UTC: p95 890ms2026-08-24 UTC: p95 1.0s2026-08-25 UTC: p95 798ms2026-08-26 UTC: p95 697ms2026-08-27 UTC: p95 857ms2026-08-28 UTC: p95 906ms2026-08-29 UTC: p95 802ms2026-08-30 UTC: p95 877ms2026-08-31 UTC: p95 943ms2026-09-01 UTC: p95 870ms2026-09-02 UTC: p95 719ms2026-09-03 UTC: p95 1.0s2026-09-04 UTC: p95 893ms2026-09-05 UTC: p95 696ms
Aug 7Aug 21Sep 5
US-Central
464msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 532ms2026-09-04 UTC: p95 679ms2026-09-05 UTC: p95 464ms
Aug 7Aug 21Sep 5
Canada
579msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 593ms2026-09-04 UTC: p95 558ms2026-09-05 UTC: p95 579ms
Aug 7Aug 21Sep 5
UK
279msp95 · latest
500ms250ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 267ms2026-09-04 UTC: p95 382ms2026-09-05 UTC: p95 279ms
Aug 7Aug 21Sep 5
Southeast Asia
1.6sp95 · 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.5s2026-09-05 UTC: p95 1.6s
Aug 7Aug 21Sep 5
Australia
890msp95 · 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-03 UTC: p95 1.4s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 890ms
Aug 7Aug 21Sep 5
South America
508msp95 · latest
1s500ms0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 892ms2026-09-04 UTC: p95 474ms2026-09-05 UTC: p95 508ms
Aug 7Aug 21Sep 5

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

What we measured, function by function

GoCardless 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
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: 317msstatus code: 400checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach GoCardless normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 326msstatus code: 400checked: Sep 5, 2026, 2:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach GoCardless normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 309msstatus code: 400checked: Sep 5, 2026, 2:01 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach GoCardless normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 592msstatus code: 400checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach GoCardless normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 481msstatus code: 400checked: Sep 5, 2026, 1:57 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach GoCardless normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 184msstatus code: 400checked: Sep 5, 2026, 1:42 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach GoCardless normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 281msstatus code: 400checked: Sep 5, 2026, 2:05 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach GoCardless 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: 570msstatus code: 400checked: Sep 5, 2026, 1:54 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach GoCardless normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1108msstatus code: 400checked: Sep 5, 2026, 2:00 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach GoCardless normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 723msstatus code: 400checked: Sep 5, 2026, 2:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach GoCardless 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 GoCardless, 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 GoCardless yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for GoCardless.

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

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

Full availability history for GoCardless: 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 GoCardless, and again when they can reach it again. That is our own measurement from ten regions, not GoCardless'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

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

At or above your target

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