Reepay incident

Acquirer Elavon (native) communication errors

Critical Resolved View vendor source →

Reepay experienced a critical incident on February 19, 2026 affecting Elavon (native), lasting 56m. The incident has been resolved; the full update timeline is below.

Started
Feb 19, 2026, 07:28 AM UTC
Resolved
Feb 19, 2026, 08:24 AM UTC
Duration
56m
Detected by Pingoru
Feb 19, 2026, 07:28 AM UTC

Affected components

Elavon (native)

Update timeline

  1. investigating Feb 19, 2026, 07:28 AM UTC

    We are currently experiencing a connectivity issue with Elavon (native). We are investigating the issue with Elavon.

  2. identified Feb 19, 2026, 07:55 AM UTC

    The root cause of the incident has been identified. We are working on a fix with Elavon.

  3. monitoring Feb 19, 2026, 08:13 AM UTC

    A fix has been deployed, and we are now seeing normal transaction processing. We will continue to monitor the situation and work with Elavon to determine the root cause of the incident.

  4. resolved Feb 19, 2026, 08:24 AM UTC

    This incident has been resolved.