Pax8 incident

P3 - Degraded Features including Ordering

Minor Resolved View vendor source →

Pax8 experienced a minor incident on June 25, 2025 affecting Catalog, lasting 2d 2h. The incident has been resolved; the full update timeline is below.

Started
Jun 25, 2025, 01:22 PM UTC
Resolved
Jun 27, 2025, 04:18 PM UTC
Duration
2d 2h
Detected by Pingoru
Jun 25, 2025, 01:22 PM UTC

Affected components

Catalog

Update timeline

  1. identified Jun 25, 2025, 01:22 PM UTC

    We are currently investigating degraded features in the platform impacting some users and some products, preventing certain products to be added to a shopping cart. We will continue to post updates here.

  2. monitoring Jun 25, 2025, 06:53 PM UTC

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

  3. identified Jun 26, 2025, 08:59 AM UTC

    We are currently investigating degraded features in the platform impacting some users and some products, preventing certain products to be added to a shopping cart. We will continue to post updates here.

  4. monitoring Jun 26, 2025, 07:01 PM UTC

    Catalog Update – Functionality Restoring Gradually Over the next 2 hours, normal catalog functionality will be progressively restored. This will not occur all at once — but partners will begin to see expected behavior as data refreshes across the system. We appreciate your patience as full updates propagate for all partners. A final confirmation will be shared once the rollout is complete.

  5. monitoring Jun 26, 2025, 09:41 PM UTC

    Catalog Update – Data Refresh Delays Catalog data updates are taking longer than expected. Our teams are monitoring the process closely and will provide updates as soon as full functionality is restored. Thank you for your continued patience — we’ll keep you informed.

  6. monitoring Jun 27, 2025, 12:48 PM UTC

    Catalog data updates are completed. Our teams are monitoring the situation closely before marking the incident as 'Resolved'. Thank you for your continued patience — we’ll keep you informed.

  7. monitoring Jun 27, 2025, 04:17 PM UTC

    We are continuing to monitor for any further issues.

  8. resolved Jun 27, 2025, 04:18 PM UTC

    This incident has been resolved.