Orderful Outage History

Orderful is up right now

Orderful had 3 outages in the last 2 years totaling 4h 17m of downtime — averaging 0.1 incidents per month.

There were 3 Orderful outages since July 31, 2025 totaling 4h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.orderful.com

Minor March 13, 2026

Transaction Processing Degradation

Detected by Pingoru
Mar 13, 2026, 07:29 PM UTC
Resolved
Mar 13, 2026, 08:29 PM UTC
Duration
59m
Affected: Transactions Processing
Timeline · 3 updates
  1. investigating Mar 13, 2026, 07:29 PM UTC

    We're currently aware of an issue causing a small percentage of transactions to not be processed successfully. We're investigating the root cause and working to resolve affected transactions.

  2. monitoring Mar 13, 2026, 07:44 PM UTC

    A fix is in place and the transaction processing issue appears to be resolved. We're continuing to monitor.

  3. resolved Mar 13, 2026, 08:29 PM UTC

    All unprocessed transactions have been reprocessed. The issue is resolved and a long-term mitigation is underway.

Read the full incident report →

Minor February 6, 2026

Transaction Delivery Degredation

Detected by Pingoru
Feb 06, 2026, 07:40 PM UTC
Resolved
Feb 06, 2026, 09:04 PM UTC
Duration
1h 24m
Affected: Trading Partner Delivery Services
Timeline · 2 updates
  1. identified Feb 06, 2026, 07:40 PM UTC

    There is a degradation on one shard of delivery queues. Cause is slow servers, implementing fix to isolate them.

  2. resolved Feb 06, 2026, 09:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 25, 2025

Transaction Processing, UI Access, and API Instability

Detected by Pingoru
Nov 25, 2025, 05:23 PM UTC
Resolved
Nov 25, 2025, 07:17 PM UTC
Duration
1h 54m
Affected: UIAS2Transactions ProcessingSFTP/FTPAPI
Timeline · 5 updates
  1. investigating Nov 25, 2025, 05:23 PM UTC

    We’re Investigating Issues Affecting UI, API, and Transaction Processing

  2. investigating Nov 25, 2025, 05:40 PM UTC

    Update – Still Investigating

  3. identified Nov 25, 2025, 05:53 PM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Nov 25, 2025, 06:15 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Nov 25, 2025, 07:17 PM UTC

    The issue has been resolved. We are still in the process of recovery, which should be completed within the hour.

Read the full incident report →