Clearhaus Outage History
Clearhaus is up right nowPingoru has recorded 61 incidents for Clearhaus: 10 in the last 12 months and 7 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 1 | 1 of 744 (0%) |
| August 2026 | 3 | 30 of 744 (4%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 4 | 54 of 518 (10%) |
Incidents, newest first
Major October 14, 2026 Visa Credit and Debit transactions failing 1d 23h Gateway API (gateway.clearhaus.com)
Started Oct 14, 2026, 08:55 AM UTC· resolved Oct 16, 2026, 08:08 AM UTC
- investigating Oct 14, 2026, 08:55 AM UTC
Since 2026-10-14 07:15 CEST, we have seen an increased rate of rejections on Visa credit and debit transactions (Visa Direct OCT and AFT, sent via the /credits and /debits endpoints), including refunds of debits. This concerns these transaction types only, not Visa credit cards or Visa debit cards. Unfortunately, we see the same underlying issue as we did yesterday, and we are in constant communication with Visa trying to resolve the issue fully. Regular Visa authorizations, captures, refunds, and voids are unaffected, as are all Mastercard transactions. We are working with our upstream provider to investigate and will post an update when we know more.
- monitoring Oct 14, 2026, 10:38 AM UTC
A hotfix was deployed at 12:03 CEST, and the affected service is performing normally again. We are monitoring the situation and will post an update once we have confirmed the issue is resolved.
- resolved Oct 16, 2026, 08:08 AM UTC
We deployed a stable fix at 2026-10-14 14:09 CEST which we have been monitoring and confirmed to be successful. We are still in communication with Visa to understand the root cause on the Visa side, but as there is no more impact of this incident, it will hereby be considered resolved. During the incident period 07:15–12:03 CEST, 86 % of Visa credits or debits received status code 50000. Impacted merchants will receive direct communication from us to clarify the actual state of the impacted transactions that received status code 50000 and a status message indicating “status unknown”.
Notice October 13, 2026 Settlements unavailable in Merchant API 53m
Started Oct 13, 2026, 06:00 PM UTC· resolved Oct 13, 2026, 06:53 PM UTC
- resolved Oct 13, 2026, 07:15 PM UTC
Between 18:18 and 18:53 UTC, settlement data was unavailable in the Merchant API due to a database outage. Gateway transaction processing was not affected at any point. We apologise for any inconvenience.
Minor October 9, 2026 Connectivity issue towards upstream 2h 16m Gateway API (gateway.clearhaus.com)
Started Oct 09, 2026, 07:20 AM UTC· resolved Oct 09, 2026, 09:37 AM UTC
- 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.
- 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.
- 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.
Notice August 27, 2026 Visa authorizations briefly failing –
Started Aug 27, 2026, 12:30 AM UTC· resolved Aug 27, 2026, 12:30 AM UTC
- 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.
Major August 11, 2026 Mastercard credits failing 14h 7m Gateway API (gateway.clearhaus.com)
Started Aug 11, 2026, 01:24 PM UTC· resolved Aug 12, 2026, 03:32 AM UTC
- 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.
- 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.
- 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.
Notice August 6, 2026 Google Pay transaction failures 15h 56m
Started Aug 06, 2026, 01:00 AM UTC· resolved Aug 06, 2026, 04:56 PM UTC
- resolved Aug 07, 2026, 08:33 AM UTC
On 2026-08-06 between 12:52 and 16:56 UTC (4h 04m), all Google Pay transactions failed with status code 40000, "Google Pay input error, no valid signature of intermediate key". No other payment methods, including Apple Pay and regular card transactions, were affected. We are improving our alerting in this area to prevent future regressions.
- postmortem Sep 01, 2026, 09:42 AM 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.
Major July 6, 2026 Transactions unavailable in Merchant API 44m Production (merchant.clearhaus.com)
Started Jul 06, 2026, 12:17 PM UTC· resolved Jul 06, 2026, 01:02 PM UTC
- investigating Jul 06, 2026, 12:17 PM UTC
We are currently investigating the issue. Gateway transaction processing is not affected.
- 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.
- resolved Jul 06, 2026, 01:02 PM UTC
This incident has been resolved.
Minor February 4, 2026 Settlements briefly unavailable in Merchant API – Production (merchant.clearhaus.com)
Started Feb 04, 2026, 12:21 PM UTC· resolved Feb 04, 2026, 12:21 PM UTC
- 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.
Notice April 11, 2025 Some subsequent recurring transactions fail upstream 1h
Started Apr 11, 2025, 09:00 AM UTC· resolved Apr 11, 2025, 10:00 AM UTC
- resolved Apr 25, 2025, 07:15 AM UTC
Starting April 11th 11:00 CEST, approximately 8% of subsequent-in-series Mastercard transactions were rejected with status code 40416 by specific issuers. For the affected issuers, a significant percentage of subsequent-in-series are rejected. No Visa transactions nor non-series Mastercard transactions were affected by this. On April 14th, the problem was noticed, and investigations have been ongoing together with Mastercard, an affected issuer, and our upstream provider. On April 17th, the problem was confirmed to be an issue with our upstream provider. On April 18th 22:00 CEST, our upstream provider released a fix. On April 19th, we confirmed that the fix was working for PAN-initiated transactions, but the problem still persisted on token-initiated subsequent-in-series Mastercard authorizations. We continued to work with our upstream provider to get this fully fixed. On April 24th 12:00 CEST, we managed to implement a workaround to mitigate the problems for token-initiated subsequent-in-series Mastercard authorizations. This fully resolved the impact of this incident. We continue to work with our upstream provider to coordinate the removal of the workaround when a fix is in place. Partners and merchants are recommended to retry both PAN- and token-initiated subsequent-in-series Mastercard authorizations that failed with 40416.
Minor October 31, 2024 Merchant API: Degraded performance 8d 5h Production (merchant.clearhaus.com), My Clearhaus (my.clearhaus.com)
Started Oct 31, 2024, 04:09 AM UTC· resolved Nov 08, 2024, 09:16 AM UTC
- 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.
- 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.