53 Bringg incidents · kwiecień 2023 — official updates, affected components, duration and resolution details.
Między 12: 42 UTC a 14: 15 UTC w dniu 24 sierpnia 2026 r. część żądań geokodowania adresów nie wypełniła się w oczekiwanym czasie i powróciła do błędów czasowych. Serwis powrócił do normalnej pracy o 14: 15 UTC. Wpis ten został opublikowany z mocą wsteczną w następstwie przeglądu wewnętrznego.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Obecnie badamy tę kwestię.
Problem został zidentyfikowany i jest w trakcie wdrażania.
Wprowadzono rozwiązanie i monitorujemy wyniki.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Obecnie doświadczamy zdegradowanej wydajności dzięki naszym usługom optymalizacji. Badamy problem. Następna aktualizacja będzie dostępna o 17: 15 UTC.
Kontynuujemy badanie tej kwestii. Następna aktualizacja będzie dostępna o 17: 55 UTC.
Przyczyna została znaleziona, a nasz zespół pracuje nad naprawą. Następna aktualizacja będzie dostępna o godzinie 18: 10 UTC.
Nadal pracujemy nad rozwiązaniem tej kwestii. Obserwujemy postępującą poprawę stabilności usług. Następna aktualizacja będzie dostępna o godzinie 18: 45 UTC.
Trwają prace nad pełnym rozwiązaniem tego incydentu. Następna aktualizacja będzie dostępna o 19: 20 UTC.
Regeneracja jest w toku, a my oczekujemy pełnej odbudowy we właściwym czasie. Następna aktualizacja będzie dostępna o 20: 00 UTC.
Wprowadzono rozwiązanie i monitorujemy wyniki. Następna aktualizacja będzie dostępna o 20: 40 UTC.
Monitorujemy wydajność usług, aby potwierdzić pełną regenerację. Następna aktualizacja będzie dostępna o 21: 20 UTC.
Kontynuujemy monitorowanie wydajności systemu, aby zapewnić pełną regenerację.
Ten incydent został rozwiązany
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
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.
We are currently investigating an 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’re currently experiencing a degraded experience related to pickup tasks in the Driver App or web UI. Drivers may encounter issues such as being unable to scan items or start loading, though assigned routes and tasks may still be visible. Our team has identified the root cause and is actively working on a fix. Resolving this remains a top priority, and we’ll continue to provide updates as we make progress. Thank you for your continued patience.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved
We're currently experiencing an issue with the partial downtime in one of our services due to increased load on the database. Our team is actively working on a fix, and we’ll provide updates as soon as it's resolved.
Our team is continuing to investigate the issue. We’ll share updates as soon as we have more information.
The issue has been identified and the fix is being implemented
After implementing a fix, we see that system is back online and responsive. We are monitoring the results
This incident has been resolved.
We're currently experiencing an issue with the Reports UI in Analytics - the page may not load as expected. Our team is actively working on a fix, and we’ll provide updates as soon as it's resolved. Please note: Scheduling of existing reports is not affected. Thank you for your patience and understanding.
The issue with the Reports UI in Analytics has been resolved, and everything is now working as expected. Thank you for your patience!