Bringg incident

Degraded API response time and optimization performance

Resolved after 1 hour 57 minutes, affecting API / Integrations (EU2-GCP) and API / Integrations (US3-GCP) and 1 more, on September 22, 2026.

monitoring Sep 22, 2026, 04:45 PM UTC

We are continuing to monitor the performance while our engineering team completes the investigation into the root cause.

Started: Sep 22, 2026, 03:02 PM UTC
Resolved: Sep 22, 2026, 04:59 PM UTC
Duration: 1h 57m
Detected by Pingoru: Sep 22, 2026, 03:02 PM UTC

Affected components

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

Update timeline

investigating Sep 22, 2026, 03:02 PM UTC

We are currently investigating this issue.
investigating Sep 22, 2026, 03:32 PM UTC

We are continuing to investigate this issue.
investigating Sep 22, 2026, 03:53 PM UTC

Investigation is ongoing; we'll share the next update shortly.
investigating Sep 22, 2026, 04:03 PM UTC

The system has been stabilized and we are actively monitoring performance. Our team continues to investigate the root cause of this issue.
monitoring Sep 22, 2026, 04:05 PM UTC

The system has been stabilized and we are actively monitoring performance. Our team continues to investigate the root cause of this issue.
monitoring Sep 22, 2026, 04:25 PM UTC

We have stabilized the system and are monitoring closely while we continue investigating the root cause.
monitoring Sep 22, 2026, 04:45 PM UTC

We are continuing to monitor the performance while our engineering team completes the investigation into the root cause.
resolved Sep 22, 2026, 04:59 PM UTC

The incident has been resolved.

Your product runs on more than Bringg

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.