Current answer
Bringg experienced a minor incident: Route Optimization delays and failures. ServiceAlert observed recovery on Oct 20, 2026.
Provider-reported start: . Notice published: .
Looking for an update now? Check the current status, or follow Bringg for future changes.
Incident Lifecycle
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)
Incident Timeline
Monitoring
Quote requests and route optimization are being processed within normal response times in our US2 environment.
We’re continuing to monitor performance to ensure it remains stable.
We’re continuing to monitor performance to ensure it remains stable.
Oct 20, 2026 at 1:49 PM UTC
Monitoring
We are continuing to monitor for any further issues.
Oct 20, 2026 at 12:36 PM UTC
Monitoring
The issue has been traced to a zonal networking incident at our cloud provider, Google Cloud (GCP). Our production infrastructure runs across multiple zones, which allowed the service to recover.
We continue to monitor closely while our cloud provider works to fully resolve the underlying issue.
We continue to monitor closely while our cloud provider works to fully resolve the underlying issue.
Oct 20, 2026 at 8:18 AM UTC
Investigating
We are continuing to investigate this issue.
Oct 20, 2026 at 7:09 AM UTC
Investigating
We are investigating an issue affecting Route Optimization across all regions.
Oct 20, 2026 at 7:07 AM UTC
Was your business affected by this Bringg outage?
Follow Bringg and route available status alerts to email or a team channel.