Clearhaus logo and current status indicator

Clearhaus Incident History

Operational

clearhaus.com 3 components

checked Sep 11, 2026 1:38 PM UTC · Clearhaus's official status page

Clearhaus is up and running.

Clearhaus is currently operational with all systems functioning normally.

All components operational

Email only. No password. No card.

Be the first to know

Statusfield watches Clearhaus alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.

Email only. No password. Free.

Clearhaus incident history

2 reports published by Clearhaus in the last 30 days

When Clearhaus breaks, it is typically resolved in 7h 20m — median across 2 resolved incidents over 90 days.

September 10, 2026

Visa authorizations briefly failing

Last update
  1. resolvedAug 27 · 00:30 UTC

    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.

Reported by Clearhaus on their status page.

September 1, 2026

Google Pay transaction failures

Last update
  1. postmortemSep 1 · 09:42 UTC

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

Reported by Clearhaus on their status page.