USAEpay Outage History

USAEpay is up right now

USAEpay had 6 outages in the last 2 years totaling 277h 46m of downtime — averaging 0.2 incidents per month.

There were 6 USAEpay outages since April 28, 2026 totaling 277h 46m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.usaepay.com

Minor June 9, 2026

Transaction Processing

Detected by Pingoru
Jun 09, 2026, 06:23 PM UTC
Resolved
Jun 09, 2026, 08:42 PM UTC
Duration
2h 19m
Affected: Transaction ProcessingPayment Engine (Point of Sale Middleware) (primary)
Timeline · 2 updates
  1. investigating Jun 09, 2026, 06:23 PM UTC

    We are investigating an issue impacting transaction processing performance. Merchants may see an error message: “Error (Unable to connect to processor)” Please retry any failed transactions.

  2. identified Jun 09, 2026, 08:14 PM UTC

    We are actively working with our partners to resolve the issue and will share updates as recovery progresses.

Read the full incident report →

Minor June 4, 2026

Batch Closure

Detected by Pingoru
Jun 04, 2026, 10:00 PM UTC
Resolved
Jun 05, 2026, 07:38 PM UTC
Duration
21h 38m
Affected: GatewayPayment Engine (Point of Sale Middleware) (primary)
Timeline · 3 updates
  1. investigating Jun 04, 2026, 10:00 PM UTC

    We are investigating an issue with our batch closure system. Our gateway remains operational at this time.

  2. identified Jun 05, 2026, 04:00 PM UTC

    Our engineers have identified the issue and are currently working on implementing a fix.

  3. monitoring Jun 05, 2026, 05:10 PM UTC

    Batch closure has been stable after our engineers resolved the issue. We will continue to monitor for further errors.

Read the full incident report →

Minor May 28, 2026

Sandbox Environment

Detected by Pingoru
May 28, 2026, 08:07 PM UTC
Resolved
May 31, 2026, 08:31 PM UTC
Duration
3d
Affected: SandboxSandbox (01-uswest)
Timeline · 2 updates
  1. investigating May 28, 2026, 08:07 PM UTC

    We are aware of an issue impacting processing on sandbox. Our Site Reliability Engineers are currently investigating the issue. This is only contained to sandbox and production systems are unaffected and remain operational.

  2. monitoring May 28, 2026, 08:29 PM UTC

    Our Site Reliability Engineers have identified and resolved the issue. Currently we are monitoring for anything further. We appreciate your patience while our team looked into this.

Read the full incident report →

Minor May 13, 2026

Connectivity issues

Detected by Pingoru
May 13, 2026, 06:47 PM UTC
Resolved
May 13, 2026, 07:23 PM UTC
Duration
36m
Affected: Transaction ProcessingPayment Engine (Point of Sale Middleware) (primary)
Timeline · 2 updates
  1. investigating May 13, 2026, 06:47 PM UTC

    We are currently investigating a potential issue affecting a third-party provider. This may be impacting some services. Our team is working to confirm and assess impact.

  2. monitoring May 13, 2026, 06:59 PM UTC

    The upstream issue appears to be resolved. We are monitoring performance to ensure services remain stable.

Read the full incident report →

Minor April 30, 2026

Batch Processing Delays(Pending State)

Detected by Pingoru
Apr 30, 2026, 06:27 PM UTC
Resolved
May 06, 2026, 04:14 PM UTC
Duration
5d 21h
Affected: Transaction ProcessingPayment Engine (Point of Sale Middleware) (primary)
Timeline · 1 update
  1. identified Apr 30, 2026, 06:27 PM UTC

    We are aware of an issue causing some batches to remain in a pending state and are actively working to resolve it. If you encounter this issue, please contact our support team for assistance. We appreciate your patience.

Read the full incident report →

Major April 28, 2026

Rest API Requests

Detected by Pingoru
Apr 28, 2026, 09:00 PM UTC
Resolved
Apr 30, 2026, 12:00 PM UTC
Duration
1d 15h
Affected: Transaction ProcessingPayment Engine (Point of Sale Middleware) (primary)
Timeline · 4 updates
  1. investigating Apr 28, 2026, 09:00 PM UTC

    We are currently investigating issues with the Rest API requests.

  2. identified Apr 29, 2026, 07:00 PM UTC

    We have identified the cause and are working promptly on restoring services.

  3. monitoring Apr 29, 2026, 11:32 PM UTC

    We have pushed a fix and are currently monitoring for any further errors. We’ll provide another update once we’ve confirmed the issue is fully resolved.

  4. monitoring Apr 30, 2026, 06:58 AM UTC

    We’ve implemented a fix and are continuing to monitor the system closely. We’ll share another update once we’ve confirmed everything is fully resolved.

Read the full incident report →