Bringg incident
Widespread AWS and Docker issues that are happening now are causing a significant impact on our operations
Bringg experienced a notice incident on October 20, 2025 affecting Access / Authentication (EU2-GCP) and Access / Authentication (US3-GCP) and 1 more component, lasting 17h 23m. The incident has been resolved; the full update timeline is below.
Affected components
Access / Authentication (EU2-GCP)Access / Authentication (US3-GCP)Access / Authentication (US2-GCP)Access / Authentication (EU3-GCP)API / Integrations (US3-GCP)API / Integrations (US2-GCP)API / Integrations (EU3-GCP)Customer Experience (EU2-GCP)Customer Experience (US3-GCP)Customer Experience (US2-GCP)
Update timeline
- identified Oct 20, 2025, 11:36 AM UTC
We notice various issues with our system now which are related to the services below https://www.dockerstatus.com/ https://health.aws.amazon.com/health/status We need you to please be patient and repeat all the attempts that you're trying to perform. Eventually it should let you do all the actions you need, but with a delay. We are looking for a solution on our end as well to provide you with stability that is required for your operability.
- resolved Oct 21, 2025, 04:59 AM UTC
This incident has been resolved.