Chowly incident

Degraded performance with Chowly Online Ordering

Minor Resolved View vendor source →

Chowly experienced a minor incident on June 10, 2025 affecting Chowly Online Ordering, lasting 4h 41m. The incident has been resolved; the full update timeline is below.

Started
Jun 10, 2025, 09:48 PM UTC
Resolved
Jun 11, 2025, 02:30 AM UTC
Duration
4h 41m
Detected by Pingoru
Jun 10, 2025, 09:48 PM UTC

Affected components

Chowly Online Ordering

Update timeline

  1. identified Jun 10, 2025, 09:48 PM UTC

    We are currently experiencing degraded performance with Chowly online ordering. Our team has identified the issue and is actively investigating the root cause. Users may encounter delays or intermittent failures when attempting to place online orders. We’ll share further updates as we work toward a resolution. Thank you for your continued patience.

  2. identified Jun 10, 2025, 10:37 PM UTC

    Our team has identified the issue and is actively investigating the underlying cause. As a result, users may experience delays or intermittent failures when placing orders through Chowly Online Ordering. We are working diligently to resolve the issue and will provide timely updates as progress is made. We appreciate your continued patience and understanding.

  3. monitoring Jun 10, 2025, 11:30 PM UTC

    Service has been restored; however, our team continues to actively monitor performance and carry out additional validations to ensure stability. We will provide further updates. Thank you for your continued patience and support.

  4. monitoring Jun 11, 2025, 12:31 AM UTC

    Our team is actively engaged in monitoring system performance and performing additional validations to ensure continued stability. We appreciate your ongoing patience and will provide any relevant updates as they arise.

  5. monitoring Jun 11, 2025, 02:04 AM UTC

    Our team is actively engaged in monitoring system performance and performing additional validations to ensure continued stability. We appreciate your ongoing patience and will provide any relevant updates as they arise.

  6. resolved Jun 11, 2025, 02:30 AM UTC

    This incident has been resolved.