Magensa had 12 outages in the last 2 years totaling 294h 15m of downtime — averaging 0.5 incidents per month.
There were 12 Magensa outages since August 12, 2025 totaling 294h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.
TSYS testing environment is experiencing an unplanned event causing limited connectivity. This will impact testing only for those with TSYS Pilot accounts on Magensa. There is currently no impact to production transactions.
From WorldPay Incident Communications: Final Incident #: INC0505900 Incident Start: 2026-05-20 07:42:00 UTC | 2026-05-20 03:42:00 EDT Platform Affected: Integrated Payments - Express, MercuryPay, triPOS Cloud Issue: There was an incident affecting transaction processing on the Integrated Payments - Express, MercuryPay and triPOS Cloud platforms. Status: Final Impact: Some transactions may have resulted in an error. Actions Taken to Restore Service: Worldpay technical resources identified an unexpected issue during a scheduled change event. Worldpay will continue to monitor the processing environment for stability. Incident Resolved: 2026-05-20 08:12:00 UTC | 2026-05-20 04:12:00 EDT Worldpay Incident Communication Management Global Command Center
Slow/Intermittent transaction processing. Impacted services: MPPG, Unigate, DAF, Decrypt Network connections may have been delayed or rejected resulting in retries or failures (500 errors).
Magensa Unigate Service is down. We're working to resolve the issue.
As of 11:28am PT, this incident was resolved
We are currently investigating an intermittent Decryption failure issue.
This incident has been resolved.
Beginning at or around 7:17am PT today we started seeing long running transactions (> 20seconds) for MPPG/DAF transactions processing through Heartland – Production endpoints. Magensa systems are processing requests normally but the Processor Response coming back are showing the following messages: “System Error” or “Transaction has timed out. You may need to submit a reversal for the transaction.” The processor endpoint generating this error is: https://api2-c.heartlandportico.com/Hps.Exchange.PosGateway/PosGatewayService.asmx We will continue monitoring this situation.
The processor is aware of the issue and is working to resolve the situation.
It appears the Heartland processing issue has been resolved.
At 1:46pm PT transaction connections started failing. Communications issue has been resolved as of 1:52pm PT and should be processing normally. Investigation is ongoing.
This incident has been resolved.
Magensa services are currently unreachable. This is being investigated.
Connectivity restored.
We are investigating reports of intermittent connectivity/processing errors at this time.
A remedy has been implemented and we are monitoring results.
Issue has been resolved.
This incident has been resolved.
Intermittent processing errors with message similar to "Unable to read data from the transport connection" causing transaction failures has been resolved.
Notification: TSYS is currently experiencing connectivity/processing errors resulting in Magensa rsponses showing the following: "Payload post failed. Message The underlying connection was closed: An unexpected error occurred on a receive. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host."
Appears TSYS processing issue is resolved.