Cronologia delle interruzioni di Bringg

1. 24 agosto 2026 alle ore 15:43 UTCresolved

   Tra 12:42 UTC e 14:15 UTC il 24 agosto 2026, una parte delle richieste di geocodifica degli indirizzi non è riuscita a completare entro il tempo previsto e ha restituito errori di timeout. Il servizio è tornato alla normale operazione alle 14:15 UTC. Questa voce è stata pubblicata in seguito alla revisione interna.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 28 giugno 2026 alle ore 12:36 UTCinvestigating

   Stiamo attualmente indagando su questo problema.

2. 28 giugno 2026 alle ore 12:43 UTCidentified

   Il problema è stato identificato e si sta attuando una correzione.

3. 28 giugno 2026 alle ore 12:43 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

4. 28 giugno 2026 alle ore 13:57 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 23 giugno 2026 alle ore 16:41 UTCinvestigating

   Stiamo attualmente sperimentando le prestazioni degradate con i nostri servizi di ottimizzazione. Stiamo indagando sul problema. Il prossimo aggiornamento sarà disponibile alle 17:15 UTC.

2. 23 giugno 2026 alle ore 17:11 UTCinvestigating

   Stiamo continuando a indagare sul problema. Il prossimo aggiornamento sarà disponibile alle 17:55 UTC.

3. 23 giugno 2026 alle ore 17:29 UTCidentified

   La causa principale è stata trovata, e il nostro team sta attualmente lavorando sulla correzione. Il prossimo aggiornamento sarà disponibile alle 18:10 UTC.

4. 23 giugno 2026 alle ore 18:05 UTCidentified

   Stiamo continuando a lavorare su una soluzione per questo problema. Stiamo osservando un progressivo miglioramento della stabilità dei servizi. Il prossimo aggiornamento sarà disponibile alle 18:45 UTC.

5. 23 giugno 2026 alle ore 18:40 UTCidentified

   Il lavoro per risolvere completamente questo incidente è in corso. Il prossimo aggiornamento sarà disponibile alle 19:20 UTC.

6. 23 giugno 2026 alle ore 19:23 UTCidentified

   Resta in corso la bonifica e prevediamo il restauro completo a tempo debito. Il prossimo aggiornamento sarà disponibile alle 20:00 UTC.

7. 23 giugno 2026 alle ore 19:58 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati. Il prossimo aggiornamento sarà disponibile alle 20:40 UTC.

8. 23 giugno 2026 alle ore 20:39 UTCmonitoring

   Stiamo monitorando le prestazioni del servizio per confermare il pieno recupero. Il prossimo aggiornamento sarà disponibile alle 21:20 UTC.

9. 23 giugno 2026 alle ore 21:15 UTCmonitoring

   Stiamo continuando a monitorare le prestazioni del sistema per garantire il pieno recupero.

10. 23 giugno 2026 alle ore 22:04 UTCresolved

    Questo incidente è stato risolto

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 15 giugno 2026 alle ore 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 giugno 2026 alle ore 15:34 UTCmonitoring

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

3. 15 giugno 2026 alle ore 17:43 UTCresolved

   The incident has been resolved.

1. 8 maggio 2026 alle ore 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 maggio 2026 alle ore 12:48 UTCinvestigating

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

3. 8 maggio 2026 alle ore 13:03 UTCmonitoring

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

4. 8 maggio 2026 alle ore 13:13 UTCresolved

   The issue has been resolved.

1. 5 maggio 2026 alle ore 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 maggio 2026 alle ore 14:08 UTCmonitoring

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

3. 5 maggio 2026 alle ore 14:37 UTCresolved

   The issue has been resolved.

1. 24 marzo 2026 alle ore 16:10 UTCinvestigating

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

2. 24 marzo 2026 alle ore 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 marzo 2026 alle ore 17:13 UTCresolved

   The incident has been resolved.

1. 16 dicembre 2025 alle ore 19:45 UTCidentified

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

2. 16 dicembre 2025 alle ore 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 dicembre 2025 alle ore 20:50 UTCresolved

   This incident has been resolved.

1. 5 dicembre 2025 alle ore 09:14 UTCidentified

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

2. 5 dicembre 2025 alle ore 09:41 UTCresolved

   This incident has been resolved.

1. 18 novembre 2025 alle ore 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 novembre 2025 alle ore 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 novembre 2025 alle ore 19:32 UTCresolved

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

1. 9 novembre 2025 alle ore 11:16 UTCinvestigating

   We are currently investigating this issue.

2. 9 novembre 2025 alle ore 11:34 UTCidentified

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

3. 9 novembre 2025 alle ore 11:34 UTCmonitoring

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

4. 9 novembre 2025 alle ore 11:57 UTCresolved

   This incident has been resolved.

1. 27 ottobre 2025 alle ore 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 ottobre 2025 alle ore 19:15 UTCresolved

   This incident has been resolved.

1. 21 ottobre 2025 alle ore 19:55 UTCinvestigating

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

2. 21 ottobre 2025 alle ore 20:26 UTCinvestigating

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

3. 21 ottobre 2025 alle ore 21:11 UTCinvestigating

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

4. 21 ottobre 2025 alle ore 21:32 UTCmonitoring

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

5. 21 ottobre 2025 alle ore 21:52 UTCmonitoring

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

6. 21 ottobre 2025 alle ore 22:25 UTCresolved

   The incident was resolved.

1. 20 ottobre 2025 alle ore 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 ottobre 2025 alle ore 04:59 UTCresolved

   This incident has been resolved.

1. 16 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 settembre 2025 alle ore 11:38 UTCinvestigating

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

2. 6 settembre 2025 alle ore 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 settembre 2025 alle ore 12:22 UTCidentified

   Still checking.

4. 6 settembre 2025 alle ore 12:47 UTCidentified

   Issue is fixed. Monitoring.

5. 6 settembre 2025 alle ore 13:12 UTCresolved

   This incident has been resolved.

1. 5 agosto 2025 alle ore 17:03 UTCinvestigating

   We are currently investigating an issue.

2. 5 agosto 2025 alle ore 17:32 UTCidentified

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

3. 5 agosto 2025 alle ore 18:11 UTCmonitoring

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

4. 6 agosto 2025 alle ore 14:39 UTCresolved

   This incident has been resolved

1. 5 agosto 2025 alle ore 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 agosto 2025 alle ore 17:00 UTCidentified

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

3. 5 agosto 2025 alle ore 17:00 UTCmonitoring

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

4. 5 agosto 2025 alle ore 17:07 UTCresolved

   This incident has been resolved

1. 22 luglio 2025 alle ore 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 luglio 2025 alle ore 17:05 UTCinvestigating

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

3. 22 luglio 2025 alle ore 17:56 UTCidentified

   The issue has been identified and the fix is being implemented

4. 22 luglio 2025 alle ore 18:23 UTCmonitoring

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

5. 22 luglio 2025 alle ore 19:12 UTCresolved

   This incident has been resolved.

1. 23 giugno 2025 alle ore 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 giugno 2025 alle ore 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!