Bringg incident

Optimization Services — Degraded Performance

Major Resolved View vendor source →

Bringg experienced a major incident on June 23, 2026 affecting Planning / Optimization (EU2-GCP) and Planning / Optimization (US3-GCP) and 1 more component, lasting 5h 22m. The incident has been resolved; the full update timeline is below.

Started
Jun 23, 2026, 04:41 PM UTC
Resolved
Jun 23, 2026, 10:04 PM UTC
Duration
5h 22m
Detected by Pingoru
Jun 23, 2026, 04:41 PM UTC

Affected components

Planning / Optimization (EU2-GCP)Planning / Optimization (US3-GCP)Planning / Optimization (US2-GCP)Planning / Optimization (US4-GCP)Planning / Optimization (EU3-GCP)

Update timeline

  1. investigating Jun 23, 2026, 04:41 PM UTC

    We are currently experiencing degraded performance with our optimization services. We are investigating the problem. Next Update will be available at 17:15 UTC.

  2. investigating Jun 23, 2026, 05:11 PM UTC

    We are continuing to investigate the issue. The next update will be available at 17:55 UTC.

  3. identified Jun 23, 2026, 05:29 PM UTC

    The root cause has been found, and our team is currently working on the fix. The next update will be available at 18:10 UTC.

  4. identified Jun 23, 2026, 06:05 PM UTC

    We are continuing to work on a fix for this issue. We are observing a progressive improvement in service stability. The next update will be available at 17:45 UTC.

  5. identified Jun 23, 2026, 06:40 PM UTC

    Work to fully resolve this incident is ongoing. The next update will be available at 19:20 UTC.

  6. identified Jun 23, 2026, 07:23 PM UTC

    Remediation remains underway, and we anticipate full restoration in due course. The next update will be available at 20:00 UTC.

  7. monitoring Jun 23, 2026, 07:58 PM UTC

    A fix has been implemented, and we are monitoring the results. The next update will be available at 20:40 UTC.

  8. monitoring Jun 23, 2026, 08:39 PM UTC

    We are monitoring service performance to confirm full recovery. The next update will be available at 21:20 UTC.

  9. monitoring Jun 23, 2026, 09:15 PM UTC

    We are continuing to monitor system performance to ensure full recovery.

  10. resolved Jun 23, 2026, 10:04 PM UTC

    This incident has been resolved