Skip to content

Outage tracker / GoCardless

Is GoCardless down?

I'm having a problem

Vendor lists an old incident, not shown as liveWhat GoCardless reports

GoCardless still lists an incident opened on 2026-09-24 with no update since 2026-10-07; we do not show it as live.

As of the last successful poll, 2026-10-23 04:00 UTC.

GoCardless's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 2 minutes ago

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

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

Front-door and live API checks

our check readinglive · checked Oct 23, 2026, 4:07 AM UTC
US-East915 msChecks passing
US-West1166 msChecks passing
Europe172 msChecks passing
Asia-Pacific1219 msChecks passing
US-Central1148 msChecks passing
Canada446 msChecks passing
UK66 msChecks passing
Southeast Asia570 msChecks passing
Australia675 msChecks passing
South America1953 msChecks passing
their status pagetheir claim, not our reading

GoCardless reports: Minor incident (“Partial System Degradation”)

from GoCardless's own status page, checked Oct 23, 2026, 4:03 AM UTC
GoCardless's status page reports Partial System Degradation. Our checks of GoCardless currently pass with normal latency. Our checks currently pass from all 10 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show the vendor's report and our check reading side by side. A check can miss problems that users see. Read both before you draw a conclusion.

GoCardless's own component breakdown, as they publish it

  • LiveOperational
  • SandboxOperational
  • LiveOperational
  • SandboxOperational
  • LiveOperational
  • SandboxOperational
  • ReportingOperational
  • PayoutsOperational
  • SubmissionsDegraded performance
  • Instant bank paymentsOperational
  • LiveOperational
  • SandboxOperational
  • GoCardless for Xero (GC4X)Operational
  • QuickbooksOperational
  • GoCardless for NetsuiteOperational
  • GoCardless ZapierOperational
  • WoocommerceOperational

These are GoCardless's components, named and scored by GoCardless. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is GoCardless's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

GoCardless response time, by region

US-East
1.1sp95 · 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-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 478ms2026-10-06 UTC: p95 564ms2026-10-07 UTC: p95 563ms2026-10-08 UTC: p95 496ms2026-10-09 UTC: p95 493ms2026-10-10 UTC: p95 505ms2026-10-11 UTC: p95 482ms2026-10-12 UTC: p95 404ms2026-10-13 UTC: p95 583ms2026-10-14 UTC: p95 474ms2026-10-15 UTC: p95 496ms2026-10-16 UTC: p95 435ms2026-10-17 UTC: p95 976ms2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.1s
Sep 24Oct 8Oct 23
US-West
1.1sp95 · 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-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 625ms2026-10-06 UTC: p95 491ms2026-10-07 UTC: p95 618ms2026-10-08 UTC: p95 537ms2026-10-09 UTC: p95 560ms2026-10-10 UTC: p95 563ms2026-10-11 UTC: p95 612ms2026-10-12 UTC: p95 585ms2026-10-13 UTC: p95 642ms2026-10-14 UTC: p95 652ms2026-10-15 UTC: p95 597ms2026-10-16 UTC: p95 569ms2026-10-17 UTC: p95 868ms2026-10-18 UTC: p95 808ms2026-10-19 UTC: p95 998ms2026-10-20 UTC: p95 910ms2026-10-21 UTC: p95 949ms2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 1.1s
Sep 24Oct 8Oct 23
Europe
359msp95 · 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-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 223ms2026-10-06 UTC: p95 376ms2026-10-07 UTC: p95 297ms2026-10-08 UTC: p95 217ms2026-10-09 UTC: p95 270ms2026-10-10 UTC: p95 250ms2026-10-11 UTC: p95 222ms2026-10-12 UTC: p95 223ms2026-10-13 UTC: p95 193ms2026-10-14 UTC: p95 310ms2026-10-15 UTC: p95 355ms2026-10-16 UTC: p95 276ms2026-10-17 UTC: p95 238ms2026-10-18 UTC: p95 293ms2026-10-19 UTC: p95 405ms2026-10-20 UTC: p95 263ms2026-10-21 UTC: p95 364ms2026-10-22 UTC: p95 305ms2026-10-23 UTC: p95 359ms
Sep 24Oct 8Oct 23
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-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 662ms2026-10-06 UTC: p95 852ms2026-10-07 UTC: p95 704ms2026-10-08 UTC: p95 816ms2026-10-09 UTC: p95 856ms2026-10-10 UTC: p95 799ms2026-10-11 UTC: p95 852ms2026-10-12 UTC: p95 807ms2026-10-13 UTC: p95 758ms2026-10-14 UTC: p95 664ms2026-10-15 UTC: p95 751ms2026-10-16 UTC: p95 780ms2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 1.8s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.7s2026-10-23 UTC: p95 1.3s
Sep 24Oct 8Oct 23
US-Central
1.3sp95 · 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-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 662ms2026-10-06 UTC: p95 670ms2026-10-07 UTC: p95 538ms2026-10-08 UTC: p95 512ms2026-10-09 UTC: p95 706ms2026-10-10 UTC: p95 694ms2026-10-11 UTC: p95 546ms2026-10-12 UTC: p95 616ms2026-10-13 UTC: p95 639ms2026-10-14 UTC: p95 756ms2026-10-15 UTC: p95 475ms2026-10-16 UTC: p95 598ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.3s
Sep 24Oct 8Oct 23
Canada
410msp95 · 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-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 800ms2026-10-06 UTC: p95 443ms2026-10-07 UTC: p95 317ms2026-10-08 UTC: p95 510ms2026-10-09 UTC: p95 539ms2026-10-10 UTC: p95 454ms2026-10-11 UTC: p95 517ms2026-10-12 UTC: p95 653ms2026-10-13 UTC: p95 353ms2026-10-14 UTC: p95 297ms2026-10-15 UTC: p95 306ms2026-10-16 UTC: p95 300ms2026-10-17 UTC: p95 255ms2026-10-18 UTC: p95 868ms2026-10-19 UTC: p95 246ms2026-10-20 UTC: p95 477ms2026-10-21 UTC: p95 328ms2026-10-22 UTC: p95 675ms2026-10-23 UTC: p95 410ms
Sep 24Oct 8Oct 23
UK
145msp95 · 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-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 435ms2026-10-06 UTC: p95 517ms2026-10-07 UTC: p95 441ms2026-10-08 UTC: p95 396ms2026-10-09 UTC: p95 465ms2026-10-10 UTC: p95 431ms2026-10-11 UTC: p95 507ms2026-10-12 UTC: p95 464ms2026-10-13 UTC: p95 141ms2026-10-14 UTC: p95 275ms2026-10-15 UTC: p95 207ms2026-10-16 UTC: p95 245ms2026-10-17 UTC: p95 486ms2026-10-18 UTC: p95 598ms2026-10-19 UTC: p95 581ms2026-10-20 UTC: p95 528ms2026-10-21 UTC: p95 332ms2026-10-22 UTC: p95 364ms2026-10-23 UTC: p95 145ms
Sep 24Oct 8Oct 23
Southeast Asia
622msp95 · 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-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.2s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 913ms2026-10-09 UTC: p95 711ms2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 868ms2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 866ms2026-10-21 UTC: p95 595ms2026-10-22 UTC: p95 788ms2026-10-23 UTC: p95 622ms
Sep 24Oct 8Oct 23
Australia
655msp95 · 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-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 935ms2026-10-06 UTC: p95 843ms2026-10-07 UTC: p95 981ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 863ms2026-10-10 UTC: p95 720ms2026-10-11 UTC: p95 798ms2026-10-12 UTC: p95 734ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 823ms2026-10-15 UTC: p95 982ms2026-10-16 UTC: p95 813ms2026-10-17 UTC: p95 989ms2026-10-18 UTC: p95 856ms2026-10-19 UTC: p95 855ms2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 869ms2026-10-23 UTC: p95 655ms
Sep 24Oct 8Oct 23
South America
2.1sp95 · 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-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 850ms2026-10-06 UTC: p95 810ms2026-10-07 UTC: p95 795ms2026-10-08 UTC: p95 875ms2026-10-09 UTC: p95 978ms2026-10-10 UTC: p95 952ms2026-10-11 UTC: p95 885ms2026-10-12 UTC: p95 921ms2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 813ms2026-10-15 UTC: p95 710ms2026-10-16 UTC: p95 652ms2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 2.4s2026-10-21 UTC: p95 2.7s2026-10-22 UTC: p95 2.7s2026-10-23 UTC: p95 2.1s
Sep 24Oct 8Oct 23

Check your own site while you wait on GoCardless

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

Email me when GoCardless reports an incident on its status page, and again when it reports it resolved.

Get an email when GoCardless reports an incident

Email me when GoCardless reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is GoCardless's own statement from its status page, with our regional reading beside it.

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: 915msstatus code: 400checked: Oct 23, 2026, 3:51 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
      Checks passinglatency: 1166msstatus code: 400checked: Oct 23, 2026, 3:58 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
      Checks passinglatency: 1148msstatus code: 400checked: Oct 23, 2026, 3:53 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
      Checks passinglatency: 446msstatus code: 400checked: Oct 23, 2026, 3:43 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
    Checks passinglatency: 1953msstatus code: 400checked: Oct 23, 2026, 3:53 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 172msstatus code: 400checked: Oct 23, 2026, 3:55 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
      Checks passinglatency: 66msstatus code: 400checked: Oct 23, 2026, 3:47 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1219msstatus code: 400checked: Oct 23, 2026, 4:07 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
      Checks passinglatency: 570msstatus code: 400checked: Oct 23, 2026, 3:53 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
      Checks passinglatency: 675msstatus code: 400checked: Oct 23, 2026, 3:12 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 probe events

GoCardless Dashboard - SSO Login Issues, 55mdeclared on their status page2026-10-20
Email delivery issues affecting Yahoo and AOL addresses, 71h 50mdeclared on their status page2026-10-12
Bacs Processing Issue Affecting Payments Scheduled for Collection on 2 October, 92h 38mdeclared on their status page2026-10-01
Intermittent ARUDD-8 failures for Nationwide Bankdeclared on their status page2026-09-24
Delayed BACS reports, 24h 29mdeclared on their status page2026-09-21
AUDDIS-I errors affecting transferred mandates, 403h 38mdeclared on their status page2026-09-04
Issue with USD payments to be collected on 31 August 2026, 187h 49mdeclared on their status page2026-09-02
Delay in GBP Payouts, 4h 2mdeclared on their status page2026-08-24

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

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

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

The badge shows the share of our checks that passed over the last 30 days. 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 GoCardless down?", https://realuptime.io/outages/gocardless. 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.

What we check

primaryfunctional: live API
https://api.gocardless.com/customers
secondary
https://gocardless.com/

What our check can and cannot see

A pass means the service's servers answered our request with the error they give a request that carries no account or valid input. It does not show that sign-in works or that any real request succeeds.

Host checked: api.gocardless.com

RealUptime is not affiliated with GoCardless; the name identifies what we checked, 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 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.