Clearhaus Outage History

Clearhaus is up right now

Clearhaus had 8 outages in the last 2 years totaling 214h 16m of downtime — averaging 0.3 incidents per month.

There were 8 Clearhaus outages since October 31, 2024 totaling 214h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.clearhaus.com

Minor October 9, 2026

Connectivity issue towards upstream

Detected by Pingoru
Oct 09, 2026, 07:20 AM UTC
Resolved
Oct 09, 2026, 09:37 AM UTC
Duration
2h 16m
Affected: Gateway API (gateway.clearhaus.com)
Timeline · 3 updates
  1. investigating Oct 09, 2026, 07:20 AM UTC

    Starting 2026-10-09T02:00Z we are experiencing intermittent connectivity issues towards our upstream provider for authorizations and voids (and Mastercard debits and debit refunds). Automatic failover and recovery is greatly alleviating the impact, but we have observed error rates of 0.75 % between 2026-10-09T02:00Z – 2026-10-09T07:00Z. We are investigating and reaching out to our upstream provider to resolve. Captures and capture refunds and Visa debits and debit refunds are not impacted.

  2. monitoring Oct 09, 2026, 08:26 AM UTC

    Since 06:36Z we locked all traffic to our upstream provider’s secondary data center where we saw a lower error rate of ~0.04 %. At 07:42Z we were informed that the problem was resolved by our upstream provider. Since 07:53Z we moved traffic back to the primary data center and have seen no further errors.

  3. resolved Oct 09, 2026, 09:37 AM UTC

    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.

Read the full incident report →

Notice August 27, 2026

Visa authorizations briefly failing

Detected by Pingoru
Aug 27, 2026, 12:30 AM UTC
Resolved
Aug 27, 2026, 12:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 10, 2026, 02:47 PM 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.

Read the full incident report →

Major August 11, 2026

Mastercard credits failing

Detected by Pingoru
Aug 11, 2026, 01:24 PM UTC
Resolved
Aug 12, 2026, 03:32 AM UTC
Duration
14h 7m
Affected: Gateway API (gateway.clearhaus.com)
Timeline · 3 updates
  1. investigating Aug 11, 2026, 01:24 PM UTC

    Since 2026-08-07 00:00 CEST, we’ve seen a rise in rejections of Credit transactions by Mastercard. Credit transactions using EUR as currency are not affected. We are reaching out to our upstream provider and will post another update once we have more information. Regular authorizations and all other transaction types are unaffected.

  2. identified Aug 11, 2026, 02:15 PM UTC

    We have now confirmed with our upstream provider that all non-EUR Credits are currently being rejected by Mastercard, due to a configuration change between Clearhaus, upstream provider and Mastercard. Our upstream provider are working on a rollback, and believe to be able to complete this during the night.

  3. resolved Aug 12, 2026, 03:32 AM UTC

    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.

Read the full incident report →

Major July 6, 2026

Transactions unavailable in Merchant API

Detected by Pingoru
Jul 06, 2026, 12:17 PM UTC
Resolved
Jul 06, 2026, 01:02 PM UTC
Duration
44m
Affected: Production (merchant.clearhaus.com)
Timeline · 3 updates
  1. investigating Jul 06, 2026, 12:17 PM UTC

    We are currently investigating the issue. Gateway transaction processing is not affected.

  2. monitoring Jul 06, 2026, 12:54 PM UTC

    Transactions available again in Merchant API This issue has been resolved. Transactions are now available in the Merchant API and the service is operating normally. Gateway transaction processing was not affected at any point. We apologise for any inconvenience.

  3. resolved Jul 06, 2026, 01:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 4, 2026

Settlements briefly unavailable in Merchant API

Detected by Pingoru
Feb 04, 2026, 12:21 PM UTC
Resolved
Feb 04, 2026, 12:21 PM UTC
Duration
—
Affected: Production (merchant.clearhaus.com)
Timeline · 1 update
  1. resolved Feb 04, 2026, 12:21 PM UTC

    The /settlements endpoint in Merchant API was unavailable and returning 500 between 2026-02-03T08:55Z - 2026-02-03T09:15Z. The incident was resolved with no lingering issues.

Read the full incident report →

Minor October 31, 2024

Merchant API: Degraded performance

Detected by Pingoru
Oct 31, 2024, 04:09 AM UTC
Resolved
Nov 08, 2024, 09:16 AM UTC
Duration
8d 5h
Affected: Production (merchant.clearhaus.com)My Clearhaus (my.clearhaus.com)
Timeline · 2 updates
  1. investigating Oct 31, 2024, 04:09 AM UTC

    Due to a service provider we are experiencing degraded performance in the Merchant API. This does not affect our ability to process transactions.

  2. resolved Nov 08, 2024, 09:16 AM UTC

    After taking remedial action, performance of the degraded components has returned to normal during the course of the week. Additionally, we have taken measures to improve visibility into the affected systems in order to strengthen our infrastructure and prevent similar events in the future. We are in contact with the service provider to continue to investigate the root cause of the issue and explore additional measures to increase the robustness of our systems.

Read the full incident report →