THIS IS A SCHEDULED EVENT Oct <var data-var='date'>11</var>, <var data-var='time'>07:00</var> - <var data-var='time'>08:00</var> UTC Aug <var data-var='date'> 4</var>, <var data-var='time'>08:33</var> UTC Scheduled - Bringg will be performing a planned upgrade to the infrastructure powering our reporting capabilities. This enhancement will improve the performance, accuracy, and scalability of the Report Builder and BI dashboards. To minimize customer impact, the upgrade will be rolled out gradually across environments outside of peak operating hours. Impact: During the maintenance window, the Report Builder and BI dashboards may be temporarily unavailable. There is no impact to: - Deliveries - Integrations - Dispatching and day-to-day platform operations After the Upgrade: You may notice slight changes in some reporting metrics. These are expected and result from more accurate data processing on the upgraded infrastructure, such as the removal of duplicate records. Overall, reporting data will be more reliable and consistent. If you notice any unexpected reporting behavior after the upgrade, please contact Bringg Support through your usual support channel. For more information, please see our documentation: https://help.bringg.com/docs/reporting-infrastructure-upgrade

Reporting Infrastructure Upgrade - US3

THIS IS A SCHEDULED EVENT Sep <var data-var='date'>27</var>, <var data-var='time'>07:00</var> - <var data-var='time'>08:00</var> UTC Aug <var data-var='date'> 4</var>, <var data-var='time'>08:33</var> UTC Scheduled - Bringg will be performing a planned upgrade to the infrastructure powering our reporting capabilities. This enhancement will improve the performance, accuracy, and scalability of the Report Builder and BI dashboards. To minimize customer impact, the upgrade will be rolled out gradually across environments outside of peak operating hours. Impact: During the maintenance window, the Report Builder and BI dashboards may be temporarily unavailable. There is no impact to: - Deliveries - Integrations - Dispatching and day-to-day platform operations After the Upgrade: You may notice slight changes in some reporting metrics. These are expected and result from more accurate data processing on the upgraded infrastructure, such as the removal of duplicate records. Overall, reporting data will be more reliable and consistent. If you notice any unexpected reporting behavior after the upgrade, please contact Bringg Support through your usual support channel. For more information, please see our documentation: https://help.bringg.com/docs/reporting-infrastructure-upgrade

Reporting Infrastructure Upgrade - US2

THIS IS A SCHEDULED EVENT Sep <var data-var='date'>13</var>, <var data-var='time'>07:00</var> - <var data-var='time'>08:00</var> UTC Aug <var data-var='date'> 4</var>, <var data-var='time'>08:32</var> UTC Scheduled - Bringg will be performing a planned upgrade to the infrastructure powering our reporting capabilities. This enhancement will improve the performance, accuracy, and scalability of the Report Builder and BI dashboards. To minimize customer impact, the upgrade will be rolled out gradually across environments outside of peak operating hours. Impact: During the maintenance window, the Report Builder and BI dashboards may be temporarily unavailable. There is no impact to: - Deliveries - Integrations - Dispatching and day-to-day platform operations After the Upgrade: You may notice slight changes in some reporting metrics. These are expected and result from more accurate data processing on the upgraded infrastructure, such as the removal of duplicate records. Overall, reporting data will be more reliable and consistent. If you notice any unexpected reporting behavior after the upgrade, please contact Bringg Support through your usual support channel. For more information, please see our documentation: https://help.bringg.com/docs/reporting-infrastructure-upgrade

Reporting Infrastructure Upgrade - EU2

THIS IS A SCHEDULED EVENT Sep <var data-var='date'>13</var>, <var data-var='time'>05:00</var> - <var data-var='time'>09:00</var> UTC Aug <var data-var='date'>11</var>, <var data-var='time'>13:29</var> UTC Update - We will be undergoing scheduled maintenance during this time. Aug <var data-var='date'>11</var>, <var data-var='time'>13:28</var> UTC Scheduled - Bringg has scheduled a maintenance window starting on Sunday, September 13, 2026, from 5 AM to 9 AM UTC. We are planning to do maintenance for a Kubernetes upgrade. We have scheduled the maintenance for a low-activity period to ensure that your customers and operations are minimally affected, if at all, by any disruption. We will be updating the ongoing status via Bringg's service status page at: https://status.bringg.com. We strongly encourage all customers to visit the status page and subscribe to receive email or SMS notifications. TECHNICAL INFORMATION There won't be any downtime, just small hiccups during the maintenance. For any questions or concerns, please contact us here: https://bringg.my.site.com/supportcenter/s/login/?inst=4M or via email at support@bringg.com.

Periodic upgrades for Bringg's server infrastructure - Sunday, September 13, 2026

THIS IS A SCHEDULED EVENT Aug <var data-var='date'>23</var>, <var data-var='time'>07:00</var> - <var data-var='time'>08:00</var> UTC Aug <var data-var='date'> 4</var>, <var data-var='time'>08:32</var> UTC Scheduled - Bringg will be performing a planned upgrade to the infrastructure powering our reporting capabilities. This enhancement will improve the performance, accuracy, and scalability of the Report Builder and BI dashboards. To minimize customer impact, the upgrade will be rolled out gradually across environments outside of peak operating hours. Impact: During the maintenance window, the Report Builder and BI dashboards may be temporarily unavailable. There is no impact to: - Deliveries - Integrations - Dispatching and day-to-day platform operations After the Upgrade: You may notice slight changes in some reporting metrics. These are expected and result from more accurate data processing on the upgraded infrastructure, such as the removal of duplicate records. Overall, reporting data will be more reliable and consistent. If you notice any unexpected reporting behavior after the upgrade, please contact Bringg Support through your usual support channel. For more information, please see our documentation: https://help.bringg.com/docs/reporting-infrastructure-upgrade

Reporting Infrastructure Upgrade - EU3

Aug <var data-var='date'>11</var>, <var data-var='time'>03:10</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>11</var>, <var data-var='time'>03:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>10</var>, <var data-var='time'>14:54</var> UTC Scheduled - As part of our ongoing efforts to ensure platform reliability and readiness for peak traffic periods, we will be performing preventive maintenance on our messaging queue infrastructure in the US3 region. This work is intended to further strengthen the platform’s ability to handle increased load during peak demand. Expected Impact During the maintenance window, there will be a brief service interruption of up to 5 minutes (likely much shorter) affecting all services while the infrastructure upgrade is completed. Our engineering team will actively monitor the environment throughout the maintenance to minimize the duration of the interruption and ensure services are restored as quickly as possible. No action is required from your team. We appreciate your understanding as we perform this proactive maintenance to improve platform reliability. If you have any questions, please don’t hesitate to reach out.

[US3] Preventive Maintenance - Message Queue Peak Load Readiness

Jul <var data-var='date'> 5</var>, <var data-var='time'>06:30</var> UTC Completed - The scheduled maintenance has been completed. Jul <var data-var='date'> 5</var>, <var data-var='time'>06:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'> 9</var>, <var data-var='time'>14:28</var> UTC Scheduled - We plan to perform a periodic upgrade on Bringg’s server infrastructure in the US2 & EU2 environments on July 5th. Israel: 9:00 AM – 9:30 AM IDT (UTC+3) London: 7:00 AM – 7:30 AM BST (UTC+1) New York: 2:00 AM – 2:30 AM EDT (UTC−4) Los Angeles: 11:00 PM – 11:30 PM PDT (Saturday → Sunday, UTC−7) Technical Information During the scheduled maintenance window, Bringg will perform infrastructure upgrades as part of our ongoing platform maintenance and optimization efforts. During this period, users and API consumers may experience occasional request failures while the changes are being applied. The maintenance has been scheduled during a period of low activity and volume, and any impact is expected to be minimal.

Scheduled Maintenance – Server Infrastructure Upgrade

Jun <var data-var='date'>28</var>, <var data-var='time'>13:57</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>28</var>, <var data-var='time'>12:43</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>28</var>, <var data-var='time'>12:43</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'>28</var>, <var data-var='time'>12:36</var> UTC Investigating - We are currently investigating this issue.

Quotes service - Degraded Performance

Jun <var data-var='date'>23</var>, <var data-var='time'>22:04</var> UTC Resolved - This incident has been resolved Jun <var data-var='date'>23</var>, <var data-var='time'>21:15</var> UTC Update - We are continuing to monitor system performance to ensure full recovery. Jun <var data-var='date'>23</var>, <var data-var='time'>20:39</var> UTC Update - We are monitoring service performance to confirm full recovery. The next update will be available at 21:20 UTC. Jun <var data-var='date'>23</var>, <var data-var='time'>19:58</var> UTC Monitoring - A fix has been implemented, and we are monitoring the results. The next update will be available at 20:40 UTC. Jun <var data-var='date'>23</var>, <var data-var='time'>19:23</var> UTC Update - Remediation remains underway, and we anticipate full restoration in due course. The next update will be available at 20:00 UTC. Jun <var data-var='date'>23</var>, <var data-var='time'>18:40</var> UTC Update - Work to fully resolve this incident is ongoing. The next update will be available at 19:20 UTC. Jun <var data-var='date'>23</var>, <var data-var='time'>18:05</var> UTC Update - 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. Jun <var data-var='date'>23</var>, <var data-var='time'>17:29</var> UTC Identified - 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. Jun <var data-var='date'>23</var>, <var data-var='time'>17:11</var> UTC Update - We are continuing to investigate the issue. The next update will be available at 17:55 UTC. Jun <var data-var='date'>23</var>, <var data-var='time'>16:41</var> UTC Investigating - We are currently experiencing degraded performance with our optimization services. We are investigating the problem. Next Update will be available at 17:15 UTC.

Optimization Services — Degraded Performance

Jun <var data-var='date'>15</var>, <var data-var='time'>17:43</var> UTC Resolved - The incident has been resolved. Jun <var data-var='date'>15</var>, <var data-var='time'>15:34</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>15</var>, <var data-var='time'>15:03</var> UTC Investigating - 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.

API Slowness on US2

Jun <var data-var='date'> 5</var>, <var data-var='time'>06:30</var> UTC Completed - The scheduled maintenance was cancelled. Jun <var data-var='date'> 5</var>, <var data-var='time'>06:00</var> UTC In progress - Scheduled maintenance was cancelled. Jun <var data-var='date'> 1</var>, <var data-var='time'>13:50</var> UTC Update - We will be undergoing scheduled maintenance during this time. Jun <var data-var='date'> 1</var>, <var data-var='time'>06:00</var> UTC Scheduled - We plan to perform a periodic upgrade on Bringg's server infrastructure in the US2 & EU2 environment on June 5th. Israel 9 AM – 9:30 AM IDT (UTC+3) London 7 AM – 7:30 AM BST (UTC+1) New York 2 AM – 2:30 AM EDT (UTC−4) Los Angeles 11 PM – 11:30 PM (Sat → Sun) PDT (UTC−7) TECHNICAL INFORMATION During the scheduled maintenance window, the Bringg platform may experience temporary service disruptions, intermittent errors, or degraded performance. Users and API consumers may encounter brief outages, increased response times, or occasional request failures while maintenance activities are underway. The maintenance has been scheduled during a period of low activity and volume. As a result, any impact is expected to be minimal, if any.

May <var data-var='date'> 8</var>, <var data-var='time'>13:13</var> UTC Resolved - The issue has been resolved. May <var data-var='date'> 8</var>, <var data-var='time'>13:03</var> UTC Monitoring - A fix has been implemented, and we are monitoring the results. May <var data-var='date'> 8</var>, <var data-var='time'>12:48</var> UTC Update - We are continuing to investigate the issue. Thank you for your patience. May <var data-var='date'> 8</var>, <var data-var='time'>12:17</var> UTC Investigating - 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.

OTP Code not being send to users during login

May <var data-var='date'> 5</var>, <var data-var='time'>14:37</var> UTC Resolved - The issue has been resolved. May <var data-var='date'> 5</var>, <var data-var='time'>14:08</var> UTC Monitoring - A fix has been implemented, and we are monitoring the results. May <var data-var='date'> 5</var>, <var data-var='time'>14:05</var> UTC Investigating - 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.

Bringg UI issue

Mar <var data-var='date'>24</var>, <var data-var='time'>17:13</var> UTC Resolved - The incident has been resolved. Mar <var data-var='date'>24</var>, <var data-var='time'>16:20</var> UTC Monitoring - A fix has been implemented, and we are monitoring the results. Next Update will be available at 17:15 UTC. Mar <var data-var='date'>24</var>, <var data-var='time'>16:10</var> UTC Investigating - We are currently investigating the issue. Next Update will be available at 16:50 UTC.

Partners integration service is down

Mar <var data-var='date'>22</var>, <var data-var='time'>10:00</var> UTC Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>22</var>, <var data-var='time'>06:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>22</var>, <var data-var='time'>06:00</var> UTC Scheduled - We plan to perform a periodic upgrade on Bringg’s server infrastructure in the US2 environment on March 22nd. Israel, 8 AM – 12 PM, IST (UTC+2) London, 6 AM – 10 AM, GMT (UTC+0) New York, 2 AM – 6 AM, EDT (UTC-4) Los Angeles, 11 PM – 3 AM, (Sat -> Sun) PDT (UTC-7) HOW TO PREPARE During the short maintenance window, Bringg services in the US2 environment only may become temporarily unavailable. This might include APIs, integrations, Driver Apps, associated inventory management applications (both web and mobile), and driver/delivery tracking services. If you have low activity/volume during this period, your users and customers may not even notice the maintenance. If you have higher activity/volume during this period, you may want to prepare a warning statement telling your users to try your service again following the maintenance window. If you have automated, background syncs or internal API calls, we strongly recommend pausing them during this window. Alternately, you should verify that your integration code will correctly retry API calls after the window is over. Please do not retry your API during the maintenance period. TECHNICAL INFORMATION During this maintenance window, the Bringg platform may respond differently to user and API interactions. Administrators and dispatchers trying to log into the Bringg Dashboard will be informed that the service is unavailable. For API requests, the platform will primarily respond with a 503 Service Unavailable status code, accompanied by a JSON message indicating ongoing maintenance.

Feb <var data-var='date'> 1</var>, <var data-var='time'>10:00</var> UTC Completed - The scheduled maintenance has been completed. Feb <var data-var='date'> 1</var>, <var data-var='time'>06:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'> 1</var>, <var data-var='time'>08:00</var> UTC Scheduled - We plan to perform a periodic upgrade on Bringg’s server infrastructure in the EU2 environment on February 1st. Israel 8 AM – 12 AM IST (UTC+2) London 6 AM – 10 AM GMT (UTC+0) New York 1 AM – 5 AM EST (UTC−5) Los Angeles 10 PM – 2 AM (Sat → Sun) PST (UTC−8) HOW TO PREPARE During the short maintenance window, Bringg services in the EU2 environment only may become temporarily unavailable. This might include APIs, integrations, Driver Apps, associated inventory management applications (both web and mobile), and driver/delivery tracking services. If you have low activity/volume during this period, your users and customers may not even notice the maintenance. If you have higher activity/volume during this period, you may want to prepare a warning statement telling your users to try your service again following the maintenance window. If you have automated, background syncs or internal API calls, we strongly recommend pausing them during this window. Alternately, you should verify that your integration code will correctly retry API calls after the window is over. Please do not retry your API during the maintenance period. TECHNICAL INFORMATION During this maintenance window, the Bringg platform may respond differently to user and API interactions. Administrators and dispatchers trying to log into the Bringg Dashboard will be informed that the service is unavailable. For API requests, the platform will primarily respond with a 503 Service Unavailable status code, accompanied by a JSON message indicating ongoing maintenance.

Dec <var data-var='date'>16</var>, <var data-var='time'>20:50</var> UTC Resolved - This incident has been resolved. Dec <var data-var='date'>16</var>, <var data-var='time'>20:13</var> UTC Monitoring - Roadie team has implemented a fix, and we are monitoring the results. More details can be found here: https://status.roadie.com/ Dec <var data-var='date'>16</var>, <var data-var='time'>19:45</var> UTC Identified - We are currently monitoring this incident that may be tracked here: https://status.roadie.com/

Roadie is experiencing a core platform outage

Dec <var data-var='date'> 5</var>, <var data-var='time'>09:41</var> UTC Resolved - This incident has been resolved. Dec <var data-var='date'> 5</var>, <var data-var='time'>09:14</var> UTC Identified - We are currently monitoring this incident that may be tracked here: https://www.doordashstatus.com/

DoorDash is experiencing service degradation due to a Cloudflare outage

Nov <var data-var='date'>24</var>, <var data-var='time'>20:00</var> UTC Completed - The scheduled maintenance has been completed. Nov <var data-var='date'>24</var>, <var data-var='time'>19:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Nov <var data-var='date'>24</var>, <var data-var='time'>18:50</var> UTC Scheduled - This is a preventive maintenance to ensure EU3 operations will not be impacted during peak hours. The Bringg's production team will perform a short failover of the impacted workloads, which may cause several seconds of failures. Normally, customers won't see any effect on their operations, but it is advised for the customer to perform a retry in case of any experienced issue or problem.

[EU3] Database maintenance

Nov <var data-var='date'>18</var>, <var data-var='time'>19:32</var> UTC Resolved - The Uber team has resolved the service interruption. The system is functioning normally. Nov <var data-var='date'>18</var>, <var data-var='time'>17:37</var> UTC Update - The Uber team has confirmed a related outage. We are continuing to monitor the situation and will provide updates as they become available. Nov <var data-var='date'>18</var>, <var data-var='time'>17:00</var> UTC Identified - We’re currently experiencing an outage with the Uber API. The next update will be available at 17:40 UTC.

An outage with the Uber API

Nov <var data-var='date'> 9</var>, <var data-var='time'>11:57</var> UTC Resolved - This incident has been resolved. Nov <var data-var='date'> 9</var>, <var data-var='time'>11:34</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Nov <var data-var='date'> 9</var>, <var data-var='time'>11:34</var> UTC Identified - The issue has been identified and a fix is being implemented. Nov <var data-var='date'> 9</var>, <var data-var='time'>11:16</var> UTC Investigating - We are currently investigating this issue.

Web application and driver app login issues

Nov <var data-var='date'> 2</var>, <var data-var='time'>09:00</var> UTC Completed - The scheduled maintenance has been completed. Nov <var data-var='date'> 2</var>, <var data-var='time'>05:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct <var data-var='date'>20</var>, <var data-var='time'>16:30</var> UTC Scheduled - We plan to perform a periodic upgrade on Bringg’s server infrastructure on Sunday, November 2, 2025, Israel	 7 AM – 11 AM	IST (UTC+2) London	 5 AM – 9 AM	GMT (UTC+0) New York	12 AM – 4 AM	EST (UTC−5) Los Angeles	9 PM – 1 AM (Sat → Sun)	PST (UTC−8) HOW TO PREPARE During the short maintenance window, Bringg services may become temporarily unavailable. This might include APIs, integrations, Driver Apps, associated inventory management applications (both web and mobile), and driver/delivery tracking services. If you have low activity/volume during this period, your users and customers may not even notice the maintenance. If you have higher activity/volume during this period, you may want to prepare a warning statement telling your users to try your service again following the maintenance window. If you have automated, background syncs or internal API calls, we strongly recommend pausing them during this window. Alternately, you should verify that your integration code will correctly retry API calls after the window is over. Please do not retry your API during the maintenance period. TECHNICAL INFORMATION During this maintenance window, the Bringg platform may respond differently to user and API interactions. Administrators and dispatchers trying to log into the Bringg Dashboard will be informed that the service is unavailable. For API requests, the platform will primarily respond with a 503 Service Unavailable status code, accompanied by a JSON message indicating ongoing maintenance.

Oct <var data-var='date'>28</var>, <var data-var='time'>19:15</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'>27</var>, <var data-var='time'>21:09</var> UTC Investigating - 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.

Unable to Submit Support Ticket in Bringg

Oct <var data-var='date'>21</var>, <var data-var='time'>22:25</var> UTC Resolved - The incident was resolved. Oct <var data-var='date'>21</var>, <var data-var='time'>21:52</var> UTC Update - The system is fully operational now, but we are still monitoring the situation. Oct <var data-var='date'>21</var>, <var data-var='time'>21:32</var> UTC Monitoring - The system has been restored to normal operation, and we are actively monitoring the situation to ensure continued stability. Oct <var data-var='date'>21</var>, <var data-var='time'>21:11</var> UTC Update - We are investigating the issue. We will provide an update by 21:40 PM UTC. Oct <var data-var='date'>21</var>, <var data-var='time'>20:26</var> UTC Update - We are still investigating the issue. We will provide an update by 21:10 PM UTC. Oct <var data-var='date'>21</var>, <var data-var='time'>19:55</var> UTC Investigating - We are currently investigating the issue. We will provide an update by 20:30 PM UTC.

Increased error rates associated with the quote service

Oct <var data-var='date'>21</var>, <var data-var='time'>04:59</var> UTC Resolved - This incident has been resolved. Oct <var data-var='date'>20</var>, <var data-var='time'>11:36</var> UTC Identified - 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.

Is Bringg down?

Bringg status is UP

Lastest published events

Reporting Infrastructure Upgrade - US3

Reporting Infrastructure Upgrade - US2

Reporting Infrastructure Upgrade - EU2

Bringg Services, Components and Regions

Recent Bringg events

Reporting Infrastructure Upgrade - US3

Reporting Infrastructure Upgrade - US2

Reporting Infrastructure Upgrade - EU2

Periodic upgrades for Bringg's server infrastructure - Sunday, September 13, 2026

Reporting Infrastructure Upgrade - EU3

[US3] Preventive Maintenance - Message Queue Peak Load Readiness