Ryft Pay Outage History
Ryft Pay is up right nowPingoru has recorded 8 incidents for Ryft Pay: 4 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 1 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 1 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 511 (0%) |
Incidents, newest first
Major June 23, 2026 Elevated payment processing errors for Card Present Payments 26m Payments API
Started Jun 23, 2026, 08:17 PM UTC· resolved Jun 23, 2026, 08:44 PM UTC
- investigating Jun 23, 2026, 08:17 PM UTC
An ongoing issue with a third party provider means an elevated payment failure rate for card present payments. The team is tracking the issue with the third party and will provide a resolution as soon as possible.
- investigating Jun 23, 2026, 08:17 PM UTC
We are continuing to investigate this issue.
- monitoring Jun 23, 2026, 08:30 PM UTC
The third party has begun to recover and transactions are now processing successfully as of 20:20UTC. We will continue to monitor performance of the payment transactions.
- resolved Jun 23, 2026, 08:44 PM UTC
The issue is now resolved with payments processing as expected.
Major April 30, 2026 Elevated payment processing errors 1h 2m Payments API
Started Apr 30, 2026, 06:30 PM UTC· resolved Apr 30, 2026, 07:33 PM UTC
- identified Apr 30, 2026, 06:30 PM UTC
We are seeing elevated errors during payment processing with one of our primary acquirers, leading to increased failures. Traffic is being re-routed to several backup acquirers. Note that this may take some time but we are seeing approvals raise back up steadily
- monitoring Apr 30, 2026, 07:19 PM UTC
Traffic has been restored across all acquirers. We are actively monitoring the failed acquirer for further errors. Currnelty we are operating as normal.
- resolved Apr 30, 2026, 07:33 PM UTC
This incident has now been resolved.
Minor March 13, 2026 Elevated Payment Errors 3d 20h Payments API, Webhooks
Started Mar 13, 2026, 03:04 PM UTC· resolved Mar 17, 2026, 11:48 AM UTC
- investigating Mar 13, 2026, 03:04 PM UTC
We are currently investigate an issue between 14:15 - 14:40pm UTC whereby increased errors were being returned from our API. Please be aware that due to the nature of the errors, webhooks for the impact payments will be delayed. Note that the API is now fully operational and this was an issue during the above time period. The team are currently assessing the issue and will follow up once we have identified the impact payments.
- monitoring Mar 13, 2026, 10:07 PM UTC
The majority of impacted transactions have now been rectified. The team will continue to monitor throughout the next 48 hours and provide updates once we consider the issue fully resolved.
- monitoring Mar 17, 2026, 09:31 AM UTC
Please note that we are in the final stages of restoring some impacted transactions from Friday March 13th. The team expect this to be completed by the end of today.
- resolved Mar 17, 2026, 11:48 AM UTC
The incident has now been resolved. All impacted payments have been restored and should be visible within the dashboard. Please notify the tech team if you've any concerns. Apologies for any inconvenience this may have caused.
Major November 24, 2025 Elevated API errors 15m Payments API
Started Nov 24, 2025, 05:40 PM UTC· resolved Nov 24, 2025, 05:55 PM UTC
- investigating Nov 24, 2025, 05:51 PM UTC
We are currently investigating this issue.
- identified Nov 24, 2025, 05:51 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Nov 24, 2025, 05:51 PM UTC
The elevated error rates lasting approx 20 minutes have now been resolved. We apologise for any inconvenience caused
- resolved Nov 24, 2025, 05:55 PM UTC
The incident has now been resolved.
- postmortem Nov 25, 2025, 09:30 AM UTC
**Summary** The root cause of the incident was due to a faulty configuration update during a deployment. This lead to a period of time whereby the deployment partially served traffic prior to being classified as unhealthy. The impacted API resources were as follows: * `v1/payment-sessions` **Timeline** The erroneous deployment went live at 5:21pm UTC. Live traffic was switched to the new instances at 5:23pm. On-site developers noticed elevated errors originating from the new nodes at 5:25pm and initiated a rollback at 5:30pm. The rollback was completed at 5:49pm and saw an instant reduction of the errors introduced by the previous deployment. The total impact time was approx 25 minutes. **What are we doing about it?** * Developers have introduced additional measures to detect faulty configuration updates. These steps will prevent bad configuration being deployable going forward. * Improvements to our rollback policies will ensure a more timely rollback in the future * The team will make adjustments to our rolling deployments whereby live traffic will be served for a longer period of time prior to being switched over to the latest deployed instances. This gives a larger window of time in which bad updates can be detected and averted before impacting our customers.
Minor November 7, 2024 Payout Delays 2h 33m Payouts
Started Nov 07, 2024, 07:50 AM UTC· resolved Nov 07, 2024, 10:23 AM UTC
- identified Nov 07, 2024, 07:50 AM UTC
We are currently experiencing delays in payouts clearing with our external banking partner. We will provide further updates once the issue has been resolved on their end.
- resolved Nov 07, 2024, 10:23 AM UTC
This incident has been resolved.