ACME Technologies Outage History

ACME Technologies is up right now

ACME Technologies had 7 outages in the last 2 years totaling 8h 12m of downtime — averaging 0.3 incidents per month.

There were 7 ACME Technologies outages since June 18, 2025 totaling 8h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://acmetechnologies.statuspage.io

Critical May 19, 2026

ACME eCommerce Service Disruption

Detected by Pingoru
May 19, 2026, 05:59 PM UTC
Resolved
May 19, 2026, 06:28 PM UTC
Duration
29m
Affected: ACME eCommerce (B2C)
Timeline · 4 updates
  1. identified May 19, 2026, 05:59 PM UTC

    ACME is experiencing a service disruption that is impacting the eCommerce (B2C) application. POS and Backoffice are operational. Our engineering team is investigating the issue and we will update this incident as soon as possible.

  2. identified May 19, 2026, 06:24 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved May 19, 2026, 06:28 PM UTC

    Service is gradually normalizing across all regions. We are continuing to monitor to ensure the issue is fully resolved.

  4. postmortem May 21, 2026, 10:51 PM UTC

    A sudden traffic surge of concurrent users exceeded the capacity of portions of the online booking web tier, leading to gateway timeouts \(504s\). As traffic controls were applied and additional capacity was brought online, service stabilized and the booking experience recovered.

Read the full incident report →

Critical March 19, 2026

Platform Service Disruption - POS and Backoffice

Detected by Pingoru
Mar 19, 2026, 01:16 PM UTC
Resolved
Mar 19, 2026, 02:43 PM UTC
Duration
1h 26m
Affected: ACME Backoffice (B2B)ACME Sales POS application
Timeline · 4 updates
  1. investigating Mar 19, 2026, 01:16 PM UTC

    ACME is experiencing a service disruption that is impacting the ACME Sales (POS) and Backoffice (B2B) application(s). ACME eCommerce is operational. Our engineering team is investigating the issue and we will update this incident as soon as possible.

  2. investigating Mar 19, 2026, 02:20 PM UTC

    We are continuing to investigate this issue.

  3. resolved Mar 19, 2026, 02:43 PM UTC

    The Issue has been resolved and service has been restored to all channels.

  4. postmortem Mar 19, 2026, 06:49 PM UTC

    The immediate issue has been resolved, and we understand the disruption this caused for customers this morning. We have identified the underlying infrastructure issue and are already putting additional safeguards in place to strengthen system reliability and help prevent this type of issue from happening again. We are also improving the client \(POS\) experience during service degradation so any future issues are handled more gracefully.

Read the full incident report →

Critical February 11, 2026

Disruption with ACME Fraud Shield - 3DS

Detected by Pingoru
Feb 11, 2026, 08:57 PM UTC
Resolved
Feb 11, 2026, 10:09 PM UTC
Duration
1h 11m
Affected: VISA Cardinal 3D-Secure Service
Timeline · 3 updates
  1. investigating Feb 11, 2026, 08:57 PM UTC

    We are currently experiencing a critical error with our VISA 3DS solution. The matter has been escalated and we are working on a solution. For the interim, 3DS has been disabled at applicable venues to unblock legitimate purchasers.

  2. monitoring Feb 11, 2026, 09:36 PM UTC

    A service provider that powers our 3DS and Advanced Fraud Shield features is currently experiencing a platform outage, which is impacting our integration. Our 3DS service has been temporarily disabled until this issue is resolved. Our team is closely monitoring and will re-enable this feature for applicable venues once the service has normalized.

  3. resolved Feb 11, 2026, 10:09 PM UTC

    3DS service has been restored and will be reactivated for participating venues.

Read the full incident report →

Critical January 6, 2026

Platform Service Disruption - Backoffice

Detected by Pingoru
Jan 06, 2026, 02:15 PM UTC
Resolved
Jan 06, 2026, 03:32 PM UTC
Duration
1h 16m
Affected: ACME Backoffice (B2B)
Timeline · 4 updates
  1. investigating Jan 06, 2026, 02:15 PM UTC

    ACME is experiencing a service disruption that is impacting the ACME Backoffice (B2B) application. ACME eCommerce is operational. Our engineering team is investigating the issue, and we will update this incident as soon as possible.

  2. investigating Jan 06, 2026, 02:57 PM UTC

    We are continuing to investigate this issue. Thank you for your patience.

  3. monitoring Jan 06, 2026, 03:22 PM UTC

    We have applied a fix, and service is normalizing. You may need to refresh your browser before logging in again.

  4. resolved Jan 06, 2026, 03:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 31, 2025

Platform Service Disruption - Payment Processing

Detected by Pingoru
Aug 31, 2025, 01:26 PM UTC
Resolved
Aug 31, 2025, 02:27 PM UTC
Duration
1h
Affected: Worldpay Express
Timeline · 4 updates
  1. investigating Aug 31, 2025, 01:26 PM UTC

    ACME is experiencing a service disruption with the Express payment processor that is impacting credit card processing on all channels We are investigating the issue, and we will update this incident as soon as possible.

  2. investigating Aug 31, 2025, 01:55 PM UTC

    Worldpay is continuing to investigate and work on the issue.

  3. resolved Aug 31, 2025, 02:27 PM UTC

    This incident has been resolved.

  4. postmortem Aug 31, 2025, 02:28 PM UTC

    **Resolved -** Worldpay technical resources resolved an internal database issue to restore service. Worldpay will continue to monitor the processing environment for stability. Aug 31, 14:27 UTC

Read the full incident report →

Minor August 19, 2025

ACME eCommerce Degraded Service

Detected by Pingoru
Aug 19, 2025, 11:52 PM UTC
Resolved
Aug 20, 2025, 01:27 AM UTC
Duration
1h 35m
Affected: ACME eCommerce (B2C)
Timeline · 5 updates
  1. investigating Aug 19, 2025, 11:52 PM UTC

    ACME is experiencing a service disruption that is impacting the display of eCommerce (B2C) application. POS and Backoffice are operational. Our engineering team is investigating the issue and we will update this incident as soon as possible.

  2. identified Aug 19, 2025, 11:52 PM UTC

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

  3. monitoring Aug 20, 2025, 01:06 AM UTC

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

  4. resolved Aug 20, 2025, 01:27 AM UTC

    This incident has been resolved.

  5. postmortem Aug 21, 2025, 08:10 PM UTC

    The CSS variable issue was caused by an incorrect Trust Store \(SSL certificate\) configuration on the Java server instances. This issue was resolved by our team and we are taking steps to ensure this misconfiguration does not occur again.

Read the full incident report →