Revaly Status - Incident history https://status.revaly.co Revaly Mon, 8 Dec 2025 17:30:40 +0000 Connectivity for file uploads Type: Incident Duration: 2 hours and 25 minutes Affected Components: SFTP Dec 8, 17:30:40 GMT+0 - Investigating - We are currently investigating this incident. Dec 8, 18:39:37 GMT+0 - Identified - We are continuing to work on a fix for this incident. Dec 8, 19:39:51 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Dec 8, 19:56:05 GMT+0 - Resolved - This incident has been resolved, a full RCA will be made available via Customer Success manager. Type: Incident

Duration: 2 hours and 25 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>17:30:40</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>18:39:37</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>19:39:51</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>19:56:05</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved, a full RCA will be made available via Customer Success manager..</p> ]]> Mon, 8 Dec 2025 17:30:40 +0000 https://status.revaly.co/incident/cmixht7c705kwvkewcxsbn0dw https://status.revaly.co/incident/cmixht7c705kwvkewcxsbn0dw Merchant-facing applications experienced HTTP 500 errors resulting in service interruptions. Type: Incident Duration: 1 day, 21 hours and 7 minutes Affected Components: Enterprise API, Recovery Advisor API, Engaged Recovery API, Client Portal Oct 21, 16:05:00 GMT+0 - Investigating - We are currently investigating this incident. Oct 21, 16:15:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Oct 21, 16:45:00 GMT+0 - Monitoring - A full incident report has been prepared and will be made available upon request. Oct 23, 13:12:06 GMT+0 - Resolved - This incident has been resolved. **What happened:** On October 21 2025, we released a system update for the service that powers both the client portal and payment API. During the update, one of the system files failed to load correctly, causing parts of the platform to stop working. Between **11:55 AM and 12:09 PM**, portions of the transaction API and client portal were intermittently unavailable before the platform went **_fully offline_**. The FlexPay team detected the issue at **12:01 PM**, investigated, and rolled back to the previous version. By **12:11 PM**, all services were fully restored. **Why it happened:** The issue occurred during deployment when the pre-production environment was promoted to production. The application began initializing before all system dependencies were fully available, resulting in a file-loading failure that prevented the platform from starting correctly. **What we’re doing to prevent it:** We’ve added additional warm-up and validation steps to the deployment pipeline to ensure all files and dependencies load properly before promotion. FlexPay’s roadmap includes a migration to more resilient infrastructure to further reduce the risk of similar downtime in the future. Type: Incident

Duration: 1 day, 21 hours and 7 minutes

Affected Components: , , ,

<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>16:05:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>16:15:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>16:45:00</var> GMT+0</small><br><strong>Monitoring</strong> - A full incident report has been prepared and will be made available upon request..</p> <p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>13:12:06</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. **What happened:** On October 21 2025, we released a system update for the service that powers both the client portal and payment API. During the update, one of the system files failed to load correctly, causing parts of the platform to stop working. Between **11:55 AM and 12:09 PM**, portions of the transaction API and client portal were intermittently unavailable before the platform went **_fully offline_**. The FlexPay team detected the issue at **12:01 PM**, investigated, and rolled back to the previous version. By **12:11 PM**, all services were fully restored. **Why it happened:** The issue occurred during deployment when the pre-production environment was promoted to production. The application began initializing before all system dependencies were fully available, resulting in a file-loading failure that prevented the platform from starting correctly. **What we’re doing to prevent it:** We’ve added additional warm-up and validation steps to the deployment pipeline to ensure all files and dependencies load properly before promotion. FlexPay’s roadmap includes a migration to more resilient infrastructure to further reduce the risk of similar downtime in the future..</p> ]]> Tue, 21 Oct 2025 16:05:00 +0000 https://status.revaly.co/incident/cmh183pwd02h711l7dp30n5ux https://status.revaly.co/incident/cmh183pwd02h711l7dp30n5ux Service disruption Type: Incident Duration: 9 days, 20 hours and 21 minutes Affected Components: Enterprise API, Recovery Advisor API, Gateway Management API, Response Code API, Batch API Feb 25, 20:04:00 GMT+0 - Resolved - This incident has been resolved. An automated update process was triggered on one of our production Kubernetes clusters, leading to a temporary service disruption. This occurred due to an update management setting that allowed the update to proceed outside of our planned maintenance windows. During this period, critical services experienced a brief downtime, affecting transaction processing. Feb 25, 19:51:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 9 days, 20 hours and 21 minutes

Affected Components: , , , ,

<p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>20:04:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. An automated update process was triggered on one of our production Kubernetes clusters, leading to a temporary service disruption. This occurred due to an update management setting that allowed the update to proceed outside of our planned maintenance windows. During this period, critical services experienced a brief downtime, affecting transaction processing..</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>19:51:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Tue, 25 Feb 2025 19:51:00 +0000 https://status.revaly.co/incident/cm7oz0er9008cdsl9rlslvn9j https://status.revaly.co/incident/cm7oz0er9008cdsl9rlslvn9j SSL Certificate verification failure Type: Incident Duration: 3 hours and 5 minutes Affected Components: Enterprise API, Recovery Advisor API, Engaged Recovery API, Gateway Management API, Response Code API Nov 26, 21:00:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Nov 26, 23:53:47 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Nov 27, 00:05:11 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 hours and 5 minutes

Affected Components: , , , ,

<p><small>Nov <var data-var='date'> 26</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Nov <var data-var='date'> 26</var>, <var data-var='time'>23:53:47</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Nov <var data-var='date'> 27</var>, <var data-var='time'>00:05:11</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 26 Nov 2024 21:00:00 +0000 https://status.revaly.co/incident/cm3z2sk6m004rnsch17cso441 https://status.revaly.co/incident/cm3z2sk6m004rnsch17cso441 Batch processing capacity issue Type: Incident Duration: 1 day and 2 hours Affected Components: Batch API Aug 21, 14:18:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Aug 22, 16:18:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 day and 2 hours

Affected Components:

<p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>14:18:00</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Aug <var data-var='date'> 22</var>, <var data-var='time'>16:18:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 21 Aug 2024 14:18:00 +0000 https://status.revaly.co/incident/cm04cx7jg002iu0r4jto2tw1i https://status.revaly.co/incident/cm04cx7jg002iu0r4jto2tw1i Engaged Recovery: SSL certificate is expired Type: Incident Duration: 19 hours and 57 minutes Affected Components: Engaged Recovery API Jul 24, 14:59:13 GMT+0 - Identified - Resolution is underway. Jul 24, 18:10:43 GMT+0 - Resolved - This incident has been resolved. Jul 23, 22:14:00 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 19 hours and 57 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>14:59:13</var> GMT+0</small><br><strong>Identified</strong> - Resolution is underway..</p> <p><small>Jul <var data-var='date'> 24</var>, <var data-var='time'>18:10:43</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>22:14:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Tue, 23 Jul 2024 22:14:00 +0000 https://status.revaly.co/incident/clyzxhg0c58251i5ll7tom4yex https://status.revaly.co/incident/clyzxhg0c58251i5ll7tom4yex