- Detected by Pingoru
- Apr 24, 2026, 10:28 AM UTC
- Resolved
- Apr 27, 2026, 01:14 PM UTC
- Duration
- 3d 2h
Timeline · 2 updates
-
investigating Apr 24, 2026, 10:28 AM UTC
We would like to inform you that technical irregularities occurred during the payout runs on Monday, April 20th. As a result, some payouts in CHF and USD could not be successfully processed. We are currently in close contact with our payout partner to clarify the exact reasons for this delay and to ensure that the outstanding payments are processed as quickly as possible.
-
resolved Apr 27, 2026, 01:14 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 01:43 PM UTC
- Resolved
- Mar 17, 2026, 03:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 18, 2026, 01:43 PM UTC
Summary: Between March 17, 16:00 UTC and March 18, 12:00 UTC, we experienced intermittent issues where some static files (CSS, JavaScript, and images) failed to load via our CDN. Impact: This occurred specifically when a certain number of requests were made within a short period, triggering a WAF security challenge. For affected users, this led to rendering issues in the UI and prevented some payments from being completed. Resolution: We have adjusted the WAF challenge thresholds to correctly handle high-frequency requests for static assets. The service has been fully stable since 12:00 UTC. We apologize for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- Feb 10, 2026, 06:50 AM UTC
- Resolved
- Feb 10, 2026, 08:16 AM UTC
- Duration
- 1h 26m
Timeline · 4 updates
-
investigating Feb 10, 2026, 06:50 AM UTC
We are currently investigating this issue.
-
identified Feb 10, 2026, 06:56 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Feb 10, 2026, 07:27 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 10, 2026, 08:16 AM UTC
Merchants using just the plugin integrations (without custom webhooks) experienced delivery delays between 4:04 and 7:16 UTC. All pending webhooks have now been sent.
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 01:23 PM UTC
- Resolved
- Feb 07, 2026, 06:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 09, 2026, 01:23 PM UTC
Incident Status: Resolved Message: Between 19:04 UTC and 22:50 UTC on Saturday, February 7th, 2026, our platform experienced intermittent performance issues and brief connectivity outages. Analysis: Our monitoring identified an unusually high volume of malicious traffic patterns (automated SQL injection attempts). While our security layers blocked these attempts, the massive surge in requests acted as a Distributed Denial of Service (DDoS), leading to temporary API timeouts for some users. Timeline (UTC): - 19:04 – 19:06: Service interruption (2 min) - 19:26 – 19:27: Brief outage (1 min) - 19:58 – 19:59: Brief outage (1 min) - 20:30 – 20:31: Brief outage (1 min) - 22:49 – 22:50: Final brief interruption (1 min) - 22:50: Mitigation complete; system stability fully restored. We have since updated our edge security filtering to handle similar traffic spikes in the future better.
Read the full incident report →
Critical February 4, 2026 - Detected by Pingoru
- Feb 04, 2026, 11:34 AM UTC
- Resolved
- Feb 04, 2026, 11:41 AM UTC
- Duration
- 7m
Affected: Payrexx PaymentPayment Adapters
Timeline · 2 updates
-
identified Feb 04, 2026, 11:34 AM UTC
We are currently experiencing a temporary service interruption on the Payrexx platform due to a system update. Our IT team is actively working on resolving the issue as quickly as possible.
-
resolved Feb 04, 2026, 11:41 AM UTC
The problem has been identified and resolved. The platform has been fully accessible again since 11:12 AM (UTC).
Read the full incident report →
- Detected by Pingoru
- Jan 27, 2026, 06:31 AM UTC
- Resolved
- Jan 27, 2026, 11:06 AM UTC
- Duration
- 4h 34m
Affected: Merchant Backend
Timeline · 2 updates
-
identified Jan 27, 2026, 06:31 AM UTC
We are currently experiencing technical difficulties affecting transactions since Friday, January 23rd. Payouts: Payments are currently delayed due to a system status error. Invoice Payments: Bank transfers (Payment method "Kauf auf Rechnung") received since Friday have not yet been posted to accounts. Our team is working on a fix. Your funds are safe, and all transactions will be processed automatically as soon as possible. No action is required on your part.
-
resolved Jan 27, 2026, 11:06 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 14, 2026, 01:13 PM UTC
- Resolved
- Jan 18, 2026, 03:44 AM UTC
- Duration
- 3d 14h
Affected: Payrexx PaymentPOS Terminals (Card Readers)
Timeline · 2 updates
-
identified Jan 14, 2026, 01:13 PM UTC
Cloudflare is currently experiencing an incident. They are already working on a resolution.
-
resolved Jan 18, 2026, 09:28 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 23, 2025, 10:48 AM UTC
- Resolved
- Dec 23, 2025, 11:15 AM UTC
- Duration
- 26m
Affected: Payrexx PaymentApply (signup.payrexx.com)Payment AdaptersServersDatabasesMerchant BackendAPIBackoffice DashboardPOS Terminals (Card Readers)
Timeline · 2 updates
-
investigating Dec 23, 2025, 10:48 AM UTC
Since approximately 11:30 CET we are partially not available. We are currently investigating this issue.
-
resolved Dec 23, 2025, 11:15 AM UTC
The issues causing performance degradation and partial unavailability between 10:29 UTC and 11:04 UTC have been fully resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 05, 2025, 09:26 AM UTC
- Resolved
- Dec 05, 2025, 09:26 AM UTC
- Duration
- —
Affected: Support Platform (support.payrexx.com)Website (www.payrexx.com)POS Terminals (Card Readers)
Timeline · 1 update
-
resolved Dec 05, 2025, 09:26 AM UTC
Due to a technical issue with the service provider Cloudflare, payments on POS devices were not possible on Dec. 05.12.2025 between 08:56 - 09:20 UTC. All services are actually up-to-date and back in operation.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 01:32 PM UTC
- Resolved
- Nov 18, 2025, 04:52 PM UTC
- Duration
- 3h 20m
Affected: POS Terminals (Card Readers)
Timeline · 2 updates
-
identified Nov 18, 2025, 01:32 PM UTC
Due to a technical issue with the service provider Cloudflare, there are still problems with payments on POS. The issue persists and will be examined.
-
resolved Nov 18, 2025, 04:52 PM UTC
Due to a technical issue with the service provider Cloudflare, payments on POS devices were not possible between 11:48 - 14:42 UTC. All services are actually up-to-date and back in operation.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 12:59 PM UTC
- Resolved
- Nov 18, 2025, 12:59 PM UTC
- Duration
- —
Affected: POS Terminals (Card Readers)
Timeline · 1 update
-
resolved Nov 18, 2025, 12:59 PM UTC
Due to a technical issue with the service provider Cloudflare, payments on POS devices were not possible between 11:59 - 12:18 UTC. All services are actually up-to-date and back in operation.
Read the full incident report →
Critical November 5, 2025 - Detected by Pingoru
- Nov 05, 2025, 12:13 PM UTC
- Resolved
- Nov 05, 2025, 03:02 PM UTC
- Duration
- 2h 48m
Affected: POS Terminals (Card Readers)
Timeline · 3 updates
-
investigating Nov 05, 2025, 12:13 PM UTC
We are currently investigating reports of widespread connectivity issues affecting our POS terminal network. This may prevent terminals from connecting, syncing data, or processing transactions. Our engineering team is aware of the situation and is actively working to identify the root cause. We apologize for the disruption and will provide another update as soon as more information is available.
-
monitoring Nov 05, 2025, 12:46 PM UTC
A fix has been implemented and we are monitoring the results. A solution has been deployed to address the connectivity issues affecting POS terminals. We are currently observing network recovery and seeing positive results. Our team will continue to monitor the situation to ensure full service stability before this incident is marked as resolved.
-
resolved Nov 05, 2025, 03:02 PM UTC
We have confirmed that the fix implemented has been successful, and all POS terminal services are now fully operational. Based on our transaction logs, the service disruption appears to have lasted from 2025-11-05 12:42:07 CET until 2025-11-05 13:07:28 CET. All systems have been stable since recovery. Our team will conduct a post-incident review to determine the root cause and implement measures to prevent a recurrence. If you continue to experience any connectivity issues, please try restarting your terminal. We sincerely apologize for the impact this disruption caused.
Read the full incident report →
- Detected by Pingoru
- Oct 14, 2025, 01:00 PM UTC
- Resolved
- Oct 14, 2025, 01:00 PM UTC
- Duration
- —
Affected: Payment Adapters
Timeline · 1 update
-
resolved Oct 14, 2025, 01:00 PM UTC
Resolved: We experienced a period of degraded performance affecting our PSP Adapter (External) payments for Payrexx white-label platforms. Following a patch release, this component began failing to process payments correctly. The issue started at 11:34 UTC and was detected by our team after approximately 15 minutes. We immediately implemented and deployed a fix, which successfully restored full functionality by 12:33 UTC. All affected services are now operating normally. We apologize for the disruption and are conducting an internal review to prevent recurrence.
Read the full incident report →
- Detected by Pingoru
- Oct 08, 2025, 08:34 AM UTC
- Resolved
- Oct 08, 2025, 08:57 AM UTC
- Duration
- 22m
Affected: Payrexx PaymentPayment Adapters
Timeline · 3 updates
-
investigating Oct 08, 2025, 08:34 AM UTC
We are currently experiencing occasional issues with payments. Our technical team has been informed and is already working on resolving the matter.
-
identified Oct 08, 2025, 08:45 AM UTC
Our development team is currently working on implementing a fix to resolve the issue.
-
resolved Oct 08, 2025, 08:57 AM UTC
The fix has been successfully deployed, and payment processing is back to normal.
Read the full incident report →
Notice September 22, 2025 - Detected by Pingoru
- Sep 22, 2025, 12:40 PM UTC
- Resolved
- Sep 22, 2025, 12:56 PM UTC
- Duration
- 15m
Affected: Payrexx PaymentPayment Adapters
Timeline · 2 updates
-
investigating Sep 22, 2025, 12:40 PM UTC
We are currently seeing problems with gateway payments. In some cases, payments via a gateway are not possible. Our team of specialists is already investigating the problem. As soon as we have more information and the issue has been resolved, we will inform you again.
-
resolved Sep 22, 2025, 12:56 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 28, 2025, 09:39 AM UTC
- Resolved
- Aug 28, 2025, 12:46 PM UTC
- Duration
- 3h 6m
Affected: Payrexx Payment
Timeline · 2 updates
-
identified Aug 28, 2025, 09:39 AM UTC
We would like to inform you about a delay in the CHF payouts from yesterday, 27 August 2025. Some payouts could not be carried out as planned. The error was caused by our payout partner. There was an error during the execution of the payouts and the execution was cancelled. The technical team of our payout partner is currently investigating this incident. The affected payouts are expected to be resent today.
-
resolved Aug 28, 2025, 12:46 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 28, 2025, 09:22 AM UTC
- Resolved
- Aug 27, 2025, 08:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 28, 2025, 09:22 AM UTC
We would like to inform you that the outage affecting the Apple Pay payment method has been resolved. The fault occurred on 27 August, between 10 AM - 5:00 PM. Due to a technical error, Apple Pay payments via Payrexx Pay were temporarily not possible. Our technical team identified the problem and successfully resolved it with a hotfix on 27 August at PM 5:00. Apple Pay is since then available to you again without restrictions.
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2025, 07:20 AM UTC
- Resolved
- Aug 19, 2025, 01:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 20, 2025, 07:20 AM UTC
On 19/08/2025 between approx. 15:00 and 18:30 there was a critical overload of our API infrastructure, which led to considerable latency and partial outages for all customers. The services have been stable again since 19/08/2025 18:30.
Read the full incident report →
- Detected by Pingoru
- Jun 27, 2025, 12:24 PM UTC
- Resolved
- Jul 01, 2025, 09:07 AM UTC
- Duration
- 3d 20h
Affected: Payrexx Payment
Timeline · 2 updates
-
identified Jun 27, 2025, 12:24 PM UTC
TWINT has informed us, that the onboarding for TWINT in Payrexx Pay is at the moment not possible due to a bug. TWINT is currently investigating the case in order to create a bug fix.
-
resolved Jul 01, 2025, 09:07 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 07:13 AM UTC
- Resolved
- Jun 12, 2025, 07:49 AM UTC
- Duration
- 35m
Affected: API
Timeline · 2 updates
-
investigating Jun 12, 2025, 07:13 AM UTC
Since yesterday evening at 4 pm, the Bill API (creation of invoices) no longer works properly. Invoices were created but not sent and accordingly no response was sent to the requesting server. We are currently deploying a hotfix that should fix the problem.
-
resolved Jun 12, 2025, 07:49 AM UTC
The problem with sending the invoices has been fixed with a hotfix. Correct functioning is still being monitored. We recommend deleting the affected invoices and creating new invoices.
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2025, 12:56 PM UTC
- Resolved
- Jun 05, 2025, 01:06 PM UTC
- Duration
- 9m
Affected: Payrexx PaymentPayment Adapters
Timeline · 2 updates
-
investigating Jun 05, 2025, 12:56 PM UTC
The payment provider Twint is currently unavailable due to technical problems at Twint. Current Status Investigating Status Update Incident: Investigating Twint is aware of technical issues with the following services and Twint is investigating the issue. Impact Services: P2P, P2M, Partner functions, Re-/Onboarding Impact TWINT overall ecosystem: 100% Next information: 16:00 Incident Start Time 05/06/2025, 14:34 CEST | 05/06/2025, 12:34 UTC Incident Status Updated At 05/06/2025, 14:34 CEST | 05/06/2025, 12:34 UTC
-
resolved Jun 05, 2025, 01:06 PM UTC
Current Status Resolved Status Update Incident: Resolved The issue was found and solved. The situation is stable and Twint is fully available again. Next steps on Twint: extra monitoring established and start of problem management Incident Start Time 05/06/2025, 14:34 CEST | 05/06/2025, 12:34 UTC Incident End Time 05/06/2025, 14:49 CEST | 05/06/2025, 12:49 UTC
Read the full incident report →
- Detected by Pingoru
- May 23, 2025, 09:06 AM UTC
- Resolved
- May 23, 2025, 11:48 AM UTC
- Duration
- 2h 41m
Affected: Payment Adapters
Timeline · 2 updates
-
investigating May 23, 2025, 09:06 AM UTC
Since 21.5.2025, there is a problem with payments with the payment provider Concardis. The payment provider Concardis is currently investigating the problem. We are currently in contact with Concardis so that the problem can be resolved quickly.
-
resolved May 23, 2025, 11:48 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 19, 2025, 09:03 AM UTC
- Resolved
- May 19, 2025, 01:12 PM UTC
- Duration
- 4h 8m
Timeline · 2 updates
-
identified May 19, 2025, 09:03 AM UTC
The onboarding process of new Tap to Pay Terminals and the reset passwort functionality for Tap to Pay are currently not working. Tap to Pay Twint Transactions are also affected by this. The issue has been identified by our development team and a hotfix will be deployed soon. Affected features on our side: - Twint transaction processing - Password reset functionality - Onboarding process of new terminals
-
resolved May 19, 2025, 01:12 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 19, 2025, 05:39 AM UTC
- Resolved
- May 20, 2025, 09:50 AM UTC
- Duration
- 1d 4h
Affected: Merchant Backend
Timeline · 3 updates
-
investigating May 19, 2025, 05:39 AM UTC
We are currently experiencing issues with the delivery of transactional emails from our platform. As a result, some messages may not reach their recipients as expected. Our team is actively investigating the issue and working to restore full functionality. We apologize for the inconvenience and will provide updates as soon as more information is available.
-
monitoring May 19, 2025, 09:11 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 20, 2025, 09:50 AM UTC
This incident has been resolved.
Read the full incident report →