Bringg outage history

We are investigating an issue affecting Route Optimization across all regions.

We are continuing to investigate this issue.

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 are continuing to monitor for any further issues.

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.

This incident has been resolved.

We are investigating the issue where SMS service is failing with timeout sometimes. Impact is low.

Delayed or undelivered SMS notifications (EU region) Since approximately 06:55 UTC on October 13, 2026, some SMS notifications to end customers in the EU region have been delayed or not delivered. Customers may not have received tracking links, ETA updates or other order-related text messages. We have traced the problem to intermittent connection failures between our EU infrastructure and our SMS provider’s network edge. Email notifications, the tracking page and all other platform functionality are not affected. Our engineering team is applying network-level changes to restore stable connectivity.

A fix has been applied and SMS notifications in the EU region have been delivering normally since approximately 20:20 UTC. We are continuing to monitor.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

Investigation is ongoing; we'll share the next update shortly.

The system has been stabilized and we are actively monitoring performance. Our team continues to investigate the root cause of this issue.

The system has been stabilized and we are actively monitoring performance. Our team continues to investigate the root cause of this issue.

We have stabilized the system and are monitoring closely while we continue investigating the root cause.

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

The incident has been resolved.

Mandrill, our third-party email delivery provider, is currently experiencing an issue. As a result, Bringg verification emails may be delayed or not delivered. Other Bringg services are operating normally.

This incident has been resolved.

Between 12:42 UTC and 14:15 UTC on 24 August 2026, a portion of address geocoding requests failed to complete within the expected time and returned timeout errors. Service returned to normal operation at 14:15 UTC. This entry has been published retrospectively following internal review.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

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

We are continuing to investigate the issue. The next update will be available at 17:55 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.

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 18:45 UTC.

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

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

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

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

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

This incident has been resolved

API response times in the US2 environment have returned to normal. We are continuing to monitor the situation while our engineering team completes the investigation into the root cause.

A fix has been implemented and we are monitoring the results.

The incident has been resolved.

We are currently experiencing issues with OTP Code not being send to users during login. Our team is aware of the problem and is actively working on a fix. We will keep you updated as soon as we have more information. Thank you for your patience.

We are continuing to investigate the issue. Thank you for your patience.

A fix has been implemented, and we are monitoring the results.

The issue has been resolved.

We are currently experiencing issues with access to the Bringg UI on all environments. Our team is aware of the problem and is actively working on a fix. We will keep you updated as soon as we have more information. Thank you for your patience.

A fix has been implemented, and we are monitoring the results.

The issue has been resolved.

We are currently investigating the issue. Next Update will be available at 16:50 UTC.

A fix has been implemented, and we are monitoring the results. Next Update will be available at 17:15 UTC.

The incident has been resolved.

We are currently monitoring this incident that may be tracked here: https://status.roadie.com/

Roadie team has implemented a fix, and we are monitoring the results. More details can be found here: https://status.roadie.com/

This incident has been resolved.

We are currently monitoring this incident that may be tracked here: https://www.doordashstatus.com/

This incident has been resolved.

We’re currently experiencing an outage with the Uber API. The next update will be available at 17:40 UTC.

The Uber team has confirmed a related outage. We are continuing to monitor the situation and will provide updates as they become available.

The Uber team has resolved the service interruption. The system is functioning normally.

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Users are currently unable to create tickets from the Bringg UI (dashboard), though ticket creation through the Salesforce portal is still working. The Salesforce team is investigating, and we’ll update you once we have more information.

This incident has been resolved.

We are currently investigating the issue. We will provide an update by 20:30 PM UTC.

We are still investigating the issue. We will provide an update by 21:10 PM UTC.

We are investigating the issue. We will provide an update by 21:40 PM UTC.

The system has been restored to normal operation, and we are actively monitoring the situation to ensure continued stability.

The system is fully operational now, but we are still monitoring the situation.

The incident was resolved.

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.

This incident has been resolved.

This problem is now identified by Bringg and the permanent solution is yet to be discussed with DoorDash. For now Bringg has put a temporal solution from our end.

In the staging environment we have confirmed that DoorDash has reverted the changes. We are keeping the solution in place in case this happens again and are waiting for DoorDash to provide clarifications on the cause.

We increased the memory of scheduler-db in eu2 which created an issue. Currently we are investigating it.

The issue was compounded when the memory of scheduler-db in eu2 was increased, right now we are fixing it.

Still checking.

Issue is fixed. Monitoring.

This incident has been resolved.