Historial de interrupciones de Bringg

1. 24 de agosto de 2026 a las 15:43 UTCresolved

   Entre las 12:42 UTC y las 14:15 UTC el 24 de agosto de 2026, una parte de las solicitudes de geocodificación de direcciones no se completaron dentro del tiempo previsto y devolvieron errores de timeout. El servicio volvió a la operación normal a las 14:15 UTC. Esta entrada ha sido publicada retrospectivamente después del examen interno.

Traducido automáticamente desde la actualización oficial del incidente.

1. 28 de junio de 2026 a las 12:36 UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. 28 de junio de 2026 a las 12:43 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. 28 de junio de 2026 a las 12:43 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. 28 de junio de 2026 a las 13:57 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 23 de junio de 2026 a las 16:41 UTCinvestigating

   Actualmente estamos experimentando un rendimiento degradado con nuestros servicios de optimización. Estamos investigando el problema. Next Update estará disponible a las 17:15 UTC.

2. 23 de junio de 2026 a las 17:11 UTCinvestigating

   Seguimos investigando la cuestión. La siguiente actualización estará disponible a las 17:55 UTC.

3. 23 de junio de 2026 a las 17:29 UTCidentified

   La causa raíz se ha encontrado, y nuestro equipo está trabajando en la solución. La siguiente actualización estará disponible a las 18:10 UTC.

4. 23 de junio de 2026 a las 18:05 UTCidentified

   Seguimos trabajando en una solución para esta cuestión. Estamos observando una mejora progresiva de la estabilidad de servicio. La siguiente actualización estará disponible a las 18:45 UTC.

5. 23 de junio de 2026 a las 18:40 UTCidentified

   Se está trabajando para resolver plenamente este incidente. La siguiente actualización estará disponible a las 19:20 UTC.

6. 23 de junio de 2026 a las 19:23 UTCidentified

   La rehabilitación permanece en curso, y anticipamos la restauración total a su debido tiempo. La siguiente actualización estará disponible a las 20:00 UTC.

7. 23 de junio de 2026 a las 19:58 UTCmonitoring

   Se ha aplicado una solución, y estamos monitoreando los resultados. La siguiente actualización estará disponible a las 20:40 UTC.

8. 23 de junio de 2026 a las 20:39 UTCmonitoring

   Estamos monitoreando el rendimiento del servicio para confirmar la recuperación completa. La siguiente actualización estará disponible a las 21:20 UTC.

9. 23 de junio de 2026 a las 21:15 UTCmonitoring

   Seguimos vigilando el desempeño del sistema para garantizar la plena recuperación.

10. 23 de junio de 2026 a las 22:04 UTCresolved

    Este incidente se ha resuelto

Traducido automáticamente desde la actualización oficial del incidente.

1. 15 de junio de 2026 a las 15:03 UTCinvestigating

   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.

2. 15 de junio de 2026 a las 15:34 UTCmonitoring

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

3. 15 de junio de 2026 a las 17:43 UTCresolved

   The incident has been resolved.

1. 8 de mayo de 2026 a las 12:17 UTCinvestigating

   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.

2. 8 de mayo de 2026 a las 12:48 UTCinvestigating

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

3. 8 de mayo de 2026 a las 13:03 UTCmonitoring

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

4. 8 de mayo de 2026 a las 13:13 UTCresolved

   The issue has been resolved.

1. 5 de mayo de 2026 a las 14:05 UTCinvestigating

   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.

2. 5 de mayo de 2026 a las 14:08 UTCmonitoring

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

3. 5 de mayo de 2026 a las 14:37 UTCresolved

   The issue has been resolved.

1. 24 de marzo de 2026 a las 16:10 UTCinvestigating

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

2. 24 de marzo de 2026 a las 16:20 UTCmonitoring

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

3. 24 de marzo de 2026 a las 17:13 UTCresolved

   The incident has been resolved.

1. 16 de diciembre de 2025 a las 19:45 UTCidentified

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

2. 16 de diciembre de 2025 a las 20:13 UTCmonitoring

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

3. 16 de diciembre de 2025 a las 20:50 UTCresolved

   This incident has been resolved.

1. 5 de diciembre de 2025 a las 9:14 UTCidentified

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

2. 5 de diciembre de 2025 a las 9:41 UTCresolved

   This incident has been resolved.

1. 18 de noviembre de 2025 a las 17:00 UTCidentified

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

2. 18 de noviembre de 2025 a las 17:37 UTCidentified

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

3. 18 de noviembre de 2025 a las 19:32 UTCresolved

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

1. 9 de noviembre de 2025 a las 11:16 UTCinvestigating

   We are currently investigating this issue.

2. 9 de noviembre de 2025 a las 11:34 UTCidentified

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

3. 9 de noviembre de 2025 a las 11:34 UTCmonitoring

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

4. 9 de noviembre de 2025 a las 11:57 UTCresolved

   This incident has been resolved.

1. 27 de octubre de 2025 a las 21:09 UTCinvestigating

   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.

2. 28 de octubre de 2025 a las 19:15 UTCresolved

   This incident has been resolved.

1. 21 de octubre de 2025 a las 19:55 UTCinvestigating

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

2. 21 de octubre de 2025 a las 20:26 UTCinvestigating

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

3. 21 de octubre de 2025 a las 21:11 UTCinvestigating

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

4. 21 de octubre de 2025 a las 21:32 UTCmonitoring

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

5. 21 de octubre de 2025 a las 21:52 UTCmonitoring

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

6. 21 de octubre de 2025 a las 22:25 UTCresolved

   The incident was resolved.

1. 20 de octubre de 2025 a las 11:36 UTCidentified

   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.

2. 21 de octubre de 2025 a las 4:59 UTCresolved

   This incident has been resolved.

1. 16 de octubre de 2025 a las 19:15 UTCmonitoring

   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.

2. 17 de octubre de 2025 a las 19:28 UTCresolved

   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.

1. 6 de septiembre de 2025 a las 11:38 UTCinvestigating

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

2. 6 de septiembre de 2025 a las 11:53 UTCidentified

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

3. 6 de septiembre de 2025 a las 12:22 UTCidentified

   Still checking.

4. 6 de septiembre de 2025 a las 12:47 UTCidentified

   Issue is fixed. Monitoring.

5. 6 de septiembre de 2025 a las 13:12 UTCresolved

   This incident has been resolved.

1. 5 de agosto de 2025 a las 17:03 UTCinvestigating

   We are currently investigating an issue.

2. 5 de agosto de 2025 a las 17:32 UTCidentified

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

3. 5 de agosto de 2025 a las 18:11 UTCmonitoring

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

4. 6 de agosto de 2025 a las 14:39 UTCresolved

   This incident has been resolved

1. 5 de agosto de 2025 a las 13:07 UTCidentified

   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.

2. 5 de agosto de 2025 a las 17:00 UTCidentified

   We are continuing to work on a fix for this issue.

3. 5 de agosto de 2025 a las 17:00 UTCmonitoring

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

4. 5 de agosto de 2025 a las 17:07 UTCresolved

   This incident has been resolved

1. 22 de julio de 2025 a las 16:32 UTCinvestigating

   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.

2. 22 de julio de 2025 a las 17:05 UTCinvestigating

   Our team is continuing to investigate the issue. We’ll share updates as soon as we have more information.

3. 22 de julio de 2025 a las 17:56 UTCidentified

   The issue has been identified and the fix is being implemented

4. 22 de julio de 2025 a las 18:23 UTCmonitoring

   After implementing a fix, we see that system is back online and responsive. We are monitoring the results

5. 22 de julio de 2025 a las 19:12 UTCresolved

   This incident has been resolved.

1. 23 de junio de 2025 a las 11:35 UTCidentified

   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.

2. 23 de junio de 2025 a las 11:57 UTCresolved

   The issue with the Reports UI in Analytics has been resolved, and everything is now working as expected. Thank you for your patience!