Ciptex incident

PCI - Intermittent Card Payment Failures

Minor Resolved View vendor source →

Ciptex experienced a minor incident on August 14, 2026 affecting Ciptex NOC General Notifications, lasting 3d. The incident has been resolved; the full update timeline is below.

Started
Aug 14, 2026, 08:39 AM UTC
Resolved
Aug 17, 2026, 09:29 AM UTC
Duration
3d
Detected by Pingoru
Aug 14, 2026, 08:39 AM UTC

Affected components

Ciptex NOC General Notifications

Update timeline

  1. investigating Aug 14, 2026, 08:39 AM UTC

    We are aware of a further occurrence of intermittent card payment failures, following the issue resolved earlier today. Engineers are investigating whether this is linked to the same cause or a separate factor. We will provide a further update within the next 2 hours, or sooner if new information becomes available.

  2. investigating Aug 14, 2026, 11:53 AM UTC

    We are continuing to investigate the root cause of intermittent card payment failures. We will provide a further update within the next 2 hours, or sooner if new information becomes available.

  3. monitoring Aug 14, 2026, 02:15 PM UTC

    Our card payment provider has confirmed that services were fully restored from 12:45 BST and have remained stable since. Voice services were unaffected throughout. We're moving to monitoring over the weekend and will provide a further update once received from our provider.

  4. monitoring Aug 15, 2026, 08:52 AM UTC

    We continue to monitor following the restoration of services. No further issues have been reported and services remain stable. We will provide a further update once received from our provider, or sooner if anything changes.

  5. monitoring Aug 16, 2026, 12:50 PM UTC

    We continue to monitor following the restoration of services. No further issues have been reported and services remain stable. We will provide a further update once received from our provider, or sooner if anything changes.

  6. resolved Aug 17, 2026, 09:29 AM UTC

    No further occurrences have been reported since services were restored. This is now being marked as resolved.