Clearhaus Status Page

Oct 9, 2026 · resolved Oct 9

We are closing this incident as no errors have been observed since 06:36Z and since the problem is confirmed to be resolved. An average failure rate of 1.14 % was observed between 2026-10-09T04:01Z and 2026-10-09T06:35Z (of when the first and last error occurred) with a peak error rate within a minute of 31 %. Additionally, we also observed a small collection of errors 2026-10-08T22:32Z – 2026-10-08T22:41Z at an average failure rate of ~11 %. Correction on affected transaction types! Authorizations, voids, capture refunds and Mastercard credits were affected. Remaining transaction types (captures, debits, debit refunds, and Visa credits) were not affected.

Aug 27, 2026 · resolved Aug 27

Between 2026-08-27T00:30:35Z and 2026-08-27T00:48:01Z, all Visa authorizations failed with status code 40400, "backend problem". A few Visa transactions were failing already starting 2026-08-27T00:25:25Z. Mastercard authorizations along with all captures, refunds, voids and credits were unaffected. We have seen no further connectivity errors since 2026-08-27T00:48:01Z. Failed authorizations were not charged and can be retried. We are working with our upstream provider to determine the root cause and to prevent similar issues in the future.

Aug 11, 2026 · resolved Aug 12

Since 2026-08-12 00:05 CEST, approval rate of Mastercard Credits are back to normal. We are still working with the upstream provider to investigate the core issue, and ensure continued operations. Regular authorizations and all other transaction types remain unaffected.

Aug 6, 2026 · resolved Aug 6

### What happened? A configuration change caused Google Pay transactions to fail. The change was made to clean up configuration inconsistencies between environments. Google Pay had an implicit dependency on one of these configurations. Before moving traffic to a new deployment, we always run automated test transactions. However, Google Pay is not tested automatically but only per need, as it is a convoluted payment method and difficult to automate. Since this deployment did not include any changes to Google Pay and was not expected to affect it, no additional effort was made to test Google Pay. ### Why were we slow to detect it? Google Pay has significantly less traffic than other payment methods so it hits below our alerting threshold, and because of this we were slow to notice the issue. ### Preventive actions * We have reviewed the remaining configuration for similar implicit dependencies and found none. * We have improved our alerting \(see below\). #### Improved alerting We have improved our alerting to catch failures affecting a small share of traffic. To avoid a significant number of false positives, we’ve done thorough analysis and backtesting to create advanced alerts that check to confirm that errors don't only happen on individual merchant accounts or for individual issuers. This allows us to be alerted per payment method — even for smaller ones like Google Pay — but also per transaction type — even for smaller ones like credits. With these new alerts in place we would have been alerted to the outage within, at most, 15 minutes.

Jul 6, 2026 · resolved Jul 6

This incident has been resolved.

Is Clearhaus down right now?

No — Clearhaus is up. All systems operational as of Oct 12, 7:45 AM UTC.

What is Clearhaus's current status?

Clearhaus: All Systems Operational. Alert24 checks Clearhaus's status page continuously and can notify you the moment it changes.

How do I get alerted when Clearhaus goes down?

Alert24 monitors Clearhaus and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.