Skip to content

Outage tracker / GoCardless

Is GoCardless down?

I'm having a problem

Operationalchecked 17 minutes ago

We reached GoCardless from all 10 regions we check.

As of Oct 5, 2026, 7:59 PM UTC, GoCardless answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

our independent probeslive · checked Oct 5, 2026, 7:59 PM UTC
US-East418 msOperational
US-West370 msOperational
Europe99 msOperational
Asia-Pacific556 msOperational
US-Central190 msOperational
Canada907 msOperational
UK380 msOperational
Southeast Asia829 msOperational
Australia318 msOperational
South America600 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
478msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 485ms2026-09-07 UTC: p95 422ms2026-09-08 UTC: p95 327ms2026-09-09 UTC: p95 363ms2026-09-10 UTC: p95 378ms2026-09-11 UTC: p95 677ms2026-09-12 UTC: p95 358ms2026-09-13 UTC: p95 262ms2026-09-14 UTC: p95 435ms2026-09-15 UTC: p95 294ms2026-09-16 UTC: p95 404ms2026-09-17 UTC: p95 463ms2026-09-18 UTC: p95 418ms2026-09-19 UTC: p95 388ms2026-09-20 UTC: p95 491ms2026-09-21 UTC: p95 487ms2026-09-22 UTC: p95 417ms2026-09-23 UTC: p95 415ms2026-09-24 UTC: p95 444ms2026-09-25 UTC: p95 424ms2026-09-26 UTC: p95 541ms2026-09-27 UTC: p95 476ms2026-09-28 UTC: p95 399ms2026-09-29 UTC: p95 528ms2026-09-30 UTC: p95 533ms2026-10-01 UTC: p95 490ms2026-10-02 UTC: p95 490ms2026-10-03 UTC: p95 579ms2026-10-04 UTC: p95 462ms2026-10-05 UTC: p95 478ms
Sep 6Sep 20Oct 5
US-West
656msp95 · 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-09-06 UTC: p95 530ms2026-09-07 UTC: p95 551ms2026-09-08 UTC: p95 529ms2026-09-09 UTC: p95 338ms2026-09-10 UTC: p95 336ms2026-09-11 UTC: p95 352ms2026-09-12 UTC: p95 409ms2026-09-13 UTC: p95 376ms2026-09-14 UTC: p95 406ms2026-09-15 UTC: p95 472ms2026-09-16 UTC: p95 588ms2026-09-17 UTC: p95 491ms2026-09-18 UTC: p95 583ms2026-09-19 UTC: p95 575ms2026-09-20 UTC: p95 701ms2026-09-21 UTC: p95 599ms2026-09-22 UTC: p95 712ms2026-09-23 UTC: p95 525ms2026-09-24 UTC: p95 596ms2026-09-25 UTC: p95 640ms2026-09-26 UTC: p95 670ms2026-09-27 UTC: p95 506ms2026-09-28 UTC: p95 590ms2026-09-29 UTC: p95 533ms2026-09-30 UTC: p95 476ms2026-10-01 UTC: p95 692ms2026-10-02 UTC: p95 349ms2026-10-03 UTC: p95 618ms2026-10-04 UTC: p95 510ms2026-10-05 UTC: p95 656ms
Sep 6Sep 20Oct 5
Europe
222msp95 · latest
500ms250ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 258ms2026-09-07 UTC: p95 263ms2026-09-08 UTC: p95 312ms2026-09-09 UTC: p95 291ms2026-09-10 UTC: p95 314ms2026-09-11 UTC: p95 300ms2026-09-12 UTC: p95 316ms2026-09-13 UTC: p95 268ms2026-09-14 UTC: p95 255ms2026-09-15 UTC: p95 267ms2026-09-16 UTC: p95 314ms2026-09-17 UTC: p95 417ms2026-09-18 UTC: p95 239ms2026-09-19 UTC: p95 223ms2026-09-20 UTC: p95 425ms2026-09-21 UTC: p95 318ms2026-09-22 UTC: p95 299ms2026-09-23 UTC: p95 419ms2026-09-24 UTC: p95 414ms2026-09-25 UTC: p95 352ms2026-09-26 UTC: p95 292ms2026-09-27 UTC: p95 403ms2026-09-28 UTC: p95 444ms2026-09-29 UTC: p95 287ms2026-09-30 UTC: p95 311ms2026-10-01 UTC: p95 272ms2026-10-02 UTC: p95 197ms2026-10-03 UTC: p95 280ms2026-10-04 UTC: p95 258ms2026-10-05 UTC: p95 222ms
Sep 6Sep 20Oct 5
Asia-Pacific
677msp95 · latest
1s500ms0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 815ms2026-09-07 UTC: p95 700ms2026-09-08 UTC: p95 653ms2026-09-09 UTC: p95 697ms2026-09-10 UTC: p95 668ms2026-09-11 UTC: p95 617ms2026-09-12 UTC: p95 642ms2026-09-13 UTC: p95 758ms2026-09-14 UTC: p95 896ms2026-09-15 UTC: p95 704ms2026-09-16 UTC: p95 804ms2026-09-17 UTC: p95 829ms2026-09-18 UTC: p95 794ms2026-09-19 UTC: p95 861ms2026-09-20 UTC: p95 812ms2026-09-21 UTC: p95 936ms2026-09-22 UTC: p95 710ms2026-09-23 UTC: p95 762ms2026-09-24 UTC: p95 907ms2026-09-25 UTC: p95 838ms2026-09-26 UTC: p95 784ms2026-09-27 UTC: p95 705ms2026-09-28 UTC: p95 688ms2026-09-29 UTC: p95 567ms2026-09-30 UTC: p95 763ms2026-10-01 UTC: p95 774ms2026-10-02 UTC: p95 731ms2026-10-03 UTC: p95 699ms2026-10-04 UTC: p95 774ms2026-10-05 UTC: p95 677ms
Sep 6Sep 20Oct 5
US-Central
678msp95 · 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-06 UTC: p95 622ms2026-09-07 UTC: p95 438ms2026-09-08 UTC: p95 522ms2026-09-09 UTC: p95 529ms2026-09-10 UTC: p95 637ms2026-09-11 UTC: p95 605ms2026-09-12 UTC: p95 383ms2026-09-13 UTC: p95 570ms2026-09-14 UTC: p95 469ms2026-09-15 UTC: p95 432ms2026-09-16 UTC: p95 434ms2026-09-17 UTC: p95 478ms2026-09-18 UTC: p95 427ms2026-09-19 UTC: p95 472ms2026-09-20 UTC: p95 460ms2026-09-21 UTC: p95 269ms2026-09-22 UTC: p95 374ms2026-09-23 UTC: p95 585ms2026-09-24 UTC: p95 570ms2026-09-25 UTC: p95 362ms2026-09-26 UTC: p95 271ms2026-09-27 UTC: p95 322ms2026-09-28 UTC: p95 484ms2026-09-29 UTC: p95 572ms2026-09-30 UTC: p95 468ms2026-10-01 UTC: p95 611ms2026-10-02 UTC: p95 560ms2026-10-03 UTC: p95 800ms2026-10-04 UTC: p95 723ms2026-10-05 UTC: p95 678ms
Sep 6Sep 20Oct 5
Canada
817msp95 · 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-06 UTC: p95 514ms2026-09-07 UTC: p95 553ms2026-09-08 UTC: p95 357ms2026-09-09 UTC: p95 310ms2026-09-10 UTC: p95 564ms2026-09-11 UTC: p95 357ms2026-09-12 UTC: p95 565ms2026-09-13 UTC: p95 343ms2026-09-14 UTC: p95 669ms2026-09-15 UTC: p95 997ms2026-09-16 UTC: p95 490ms2026-09-17 UTC: p95 258ms2026-09-18 UTC: p95 433ms2026-09-19 UTC: p95 563ms2026-09-20 UTC: p95 578ms2026-09-21 UTC: p95 595ms2026-09-22 UTC: p95 427ms2026-09-23 UTC: p95 349ms2026-09-24 UTC: p95 677ms2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 393ms2026-09-27 UTC: p95 347ms2026-09-28 UTC: p95 649ms2026-09-29 UTC: p95 571ms2026-09-30 UTC: p95 584ms2026-10-01 UTC: p95 575ms2026-10-02 UTC: p95 517ms2026-10-03 UTC: p95 354ms2026-10-04 UTC: p95 401ms2026-10-05 UTC: p95 817ms
Sep 6Sep 20Oct 5
UK
414msp95 · 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-06 UTC: p95 228ms2026-09-07 UTC: p95 284ms2026-09-08 UTC: p95 103ms2026-09-09 UTC: p95 217ms2026-09-10 UTC: p95 318ms2026-09-11 UTC: p95 280ms2026-09-12 UTC: p95 100ms2026-09-13 UTC: p95 303ms2026-09-14 UTC: p95 148ms2026-09-15 UTC: p95 277ms2026-09-16 UTC: p95 225ms2026-09-17 UTC: p95 175ms2026-09-18 UTC: p95 212ms2026-09-19 UTC: p95 294ms2026-09-20 UTC: p95 244ms2026-09-21 UTC: p95 418ms2026-09-22 UTC: p95 430ms2026-09-23 UTC: p95 412ms2026-09-24 UTC: p95 431ms2026-09-25 UTC: p95 344ms2026-09-26 UTC: p95 350ms2026-09-27 UTC: p95 431ms2026-09-28 UTC: p95 352ms2026-09-29 UTC: p95 385ms2026-09-30 UTC: p95 332ms2026-10-01 UTC: p95 314ms2026-10-02 UTC: p95 445ms2026-10-03 UTC: p95 422ms2026-10-04 UTC: p95 437ms2026-10-05 UTC: p95 414ms
Sep 6Sep 20Oct 5
Southeast Asia
1.2sp95 · 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-06 UTC: p95 1.0s2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 722ms2026-09-09 UTC: p95 861ms2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 936ms2026-09-12 UTC: p95 1s2026-09-13 UTC: p95 950ms2026-09-14 UTC: p95 1.0s2026-09-15 UTC: p95 921ms2026-09-16 UTC: p95 806ms2026-09-17 UTC: p95 1.1s2026-09-18 UTC: p95 942ms2026-09-19 UTC: p95 891ms2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.2s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.2s2026-10-02 UTC: p95 904ms2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.2s
Sep 6Sep 20Oct 5
Australia
484msp95 · 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-06 UTC: p95 959ms2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.5s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.6s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.5s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.4s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.2s2026-09-23 UTC: p95 1.3s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.6s2026-09-28 UTC: p95 1.8s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 847ms2026-10-05 UTC: p95 484ms
Sep 6Sep 20Oct 5
South America
811msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 741ms2026-09-07 UTC: p95 859ms2026-09-08 UTC: p95 739ms2026-09-09 UTC: p95 924ms2026-09-10 UTC: p95 826ms2026-09-11 UTC: p95 854ms2026-09-12 UTC: p95 864ms2026-09-13 UTC: p95 630ms2026-09-14 UTC: p95 902ms2026-09-15 UTC: p95 894ms2026-09-16 UTC: p95 763ms2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 747ms2026-09-19 UTC: p95 851ms2026-09-20 UTC: p95 805ms2026-09-21 UTC: p95 922ms2026-09-22 UTC: p95 670ms2026-09-23 UTC: p95 1.2s2026-09-24 UTC: p95 717ms2026-09-25 UTC: p95 714ms2026-09-26 UTC: p95 828ms2026-09-27 UTC: p95 451ms2026-09-28 UTC: p95 580ms2026-09-29 UTC: p95 778ms2026-09-30 UTC: p95 736ms2026-10-01 UTC: p95 848ms2026-10-02 UTC: p95 697ms2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 811ms
Sep 6Sep 20Oct 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

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

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.

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: 418msstatus code: 400checked: Oct 5, 2026, 7:57 PM 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: 370msstatus code: 400checked: Oct 5, 2026, 7:47 PM 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: 190msstatus code: 400checked: Oct 5, 2026, 7:21 PM 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: 907msstatus code: 400checked: Oct 5, 2026, 7:35 PM 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: 600msstatus code: 400checked: Oct 5, 2026, 7:25 PM 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: 99msstatus code: 400checked: Oct 5, 2026, 7:55 PM 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: 380msstatus code: 400checked: Oct 5, 2026, 7:24 PM 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: 556msstatus code: 400checked: Oct 5, 2026, 7:50 PM 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: 829msstatus code: 400checked: Oct 5, 2026, 7:41 PM 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: 318msstatus code: 400checked: Oct 5, 2026, 7:59 PM 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

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