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.

Scheduled Maintenance – Server Infrastructure Upgrade

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.

Widespread AWS and Docker issues that are happening now are causing a significant impact on our operations

Oct <var data-var='date'>19</var>, <var data-var='time'>11:10</var> UTC Completed - The scheduled maintenance has been completed.Oct <var data-var='date'>19</var>, <var data-var='time'>11:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Oct <var data-var='date'> 1</var>, <var data-var='time'>06:26</var> UTC Scheduled - We’re scheduling maintenance on our Dynamic Delivery Slots feature on Sunday, October 19, 2025 in the environment US2. During this window, the feature may be unavailable for up to 10 minutes (we expect it to be less). What to expect: - Temporary unavailability of Dynamic Delivery Slots (up to 10 minutes) - No action required on your side If this timing poses any issues, or if you have questions, please reply to this email and we’ll work with you on options. Our support team is also available via the support portal.

Scheduled maintenance for Dynamic Delivery Slots — Sunday, October 19

Oct <var data-var='date'>17</var>, <var data-var='time'>19:28</var> UTC Resolved - 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.Oct <var data-var='date'>16</var>, <var data-var='time'>19:15</var> UTC Monitoring - 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.

DoorDash integration is down with Bringg because of the change on DoorDash side that now requires Customer's last name.

Sep <var data-var='date'> 6</var>, <var data-var='time'>13:12</var> UTC Resolved - This incident has been resolved.Sep <var data-var='date'> 6</var>, <var data-var='time'>12:47</var> UTC Update - Issue is fixed. Monitoring.Sep <var data-var='date'> 6</var>, <var data-var='time'>12:22</var> UTC Update - Still checking.Sep <var data-var='date'> 6</var>, <var data-var='time'>11:53</var> UTC Identified - The issue was compounded when the memory of scheduler-db in eu2 was increased, right now we are fixing it.Sep <var data-var='date'> 6</var>, <var data-var='time'>11:38</var> UTC Investigating - We increased the memory of scheduler-db in eu2 which created an issue. Currently we are investigating it.

Degradation of scheduled jobs in EU-2 environments

Aug <var data-var='date'>31</var>, <var data-var='time'>10:00</var> UTC Completed - The scheduled maintenance has been completed.Aug <var data-var='date'>31</var>, <var data-var='time'>06:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Aug <var data-var='date'>13</var>, <var data-var='time'>22:54</var> UTC Scheduled - Bringg has scheduled a maintenance window starting on Sunday, August 31, 2025 from 6 AM to 10 AM UTC Tel Aviv: 9:00 AM – 1:00 PM Los Angeles: 11:00 PM – 3:00 AM Sat, Aug 30 New York: 2:00 AM – 6:00 AM Sun, Aug 31 We will be performing a planned maintenance to upgrade our data infrastructure component in environments eu2, eu3, us2, and us3. We have scheduled the maintenance for a low-activity period to ensure that your operations are minimally affected, if at all, by any disruption. We will be updating the ongoing status via Bringg's service status page: https://status.bringg.com. We strongly encourage all customers to visit the status page and subscribe to receive email or SMS notifications. TECHNICAL INFORMATION During this maintenance window, some of the components will be completely unavailable for a few minutes at a time while we upgrade each environment sequentially: - History Page - Billing Portal - Report Builder - Scheduled Reports For any questions or concerns, please contact us here: https://bringg.my.site.com/supportcenter/s/login/?inst=4M or email support@bringg.com. HOW TO PREPARE If you have automated reports, scheduled exports, or background queries relying on our database, we strongly recommend pausing them during this window. Alternately, verify that your integration code correctly retries after the window is over.

data infrastructure update

Aug <var data-var='date'> 6</var>, <var data-var='time'>14:39</var> UTC Resolved - This incident has been resolvedAug <var data-var='date'> 5</var>, <var data-var='time'>18:11</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Aug <var data-var='date'> 5</var>, <var data-var='time'>17:32</var> UTC Identified - The issue has been identified and a fix is being implemented.Aug <var data-var='date'> 5</var>, <var data-var='time'>17:03</var> UTC Investigating - We are currently investigating an issue.

Degraded performance of one of Bringg services

Aug <var data-var='date'> 5</var>, <var data-var='time'>17:07</var> UTC Resolved - This incident has been resolvedAug <var data-var='date'> 5</var>, <var data-var='time'>17:00</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Aug <var data-var='date'> 5</var>, <var data-var='time'>17:00</var> UTC Update - We are continuing to work on a fix for this issue.Aug <var data-var='date'> 5</var>, <var data-var='time'>13:07</var> UTC Identified - 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.

Pickup Task Functionality Degradation

Jul <var data-var='date'>22</var>, <var data-var='time'>19:12</var> UTC Resolved - This incident has been resolved.Jul <var data-var='date'>22</var>, <var data-var='time'>18:23</var> UTC Monitoring - After implementing a fix, we see that system is back online and responsive. We are monitoring the resultsJul <var data-var='date'>22</var>, <var data-var='time'>17:56</var> UTC Identified - The issue has been identified and the fix is being implementedJul <var data-var='date'>22</var>, <var data-var='time'>17:05</var> UTC Update - Our team is continuing to investigate the issue. We’ll share updates as soon as we have more information.Jul <var data-var='date'>22</var>, <var data-var='time'>16:32</var> UTC Investigating - 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.

Partial downtime in one of our services due to increased load on the database.

Jul <var data-var='date'>18</var>, <var data-var='time'>15:21</var> UTC Resolved - The maintenance is complete.Jul <var data-var='date'>18</var>, <var data-var='time'>15:09</var> UTC Update - The maintenance is completed, we are ensuring all systems are up and working.Jul <var data-var='date'>18</var>, <var data-var='time'>15:06</var> UTC Update - Urgent maintenance in processJul <var data-var='date'>18</var>, <var data-var='time'>15:00</var> UTC Monitoring - We are performing urgent preventive maintenance to address increased load on internal infrastructure in the EU2 region. This maintenance is necessary to ensure the stability and reliability of the Bringg platform. Some Bringg services may experience brief interruptions during the maintenance. These may include delays in real-time functionality and occasional issues with API interactions. The work involves internal critical components responsible for service-to-service communication. While no full downtime is expected, short disruptions may occur as key components are restarted. We are working to complete this maintenance as quickly and smoothly as possible and appreciate your understanding. Starting at 15:00 UTC. Expected timeframe is 30 minutes.

Urgent maintenance

Jun <var data-var='date'>23</var>, <var data-var='time'>11:57</var> UTC Resolved - The issue with the Reports UI in Analytics has been resolved, and everything is now working as expected. Thank you for your patience!Jun <var data-var='date'>23</var>, <var data-var='time'>11:35</var> UTC Identified - 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.

Issue with Reports UI in Analytics

Jun <var data-var='date'>12</var>, <var data-var='time'>21:33</var> UTC Resolved - The incident has been resolved and we see all services fully operational.Jun <var data-var='date'>12</var>, <var data-var='time'>20:48</var> UTC Monitoring - We are seeing signs of recovery in our US3 region (us-central1) following the earlier disruption related to our cloud provider, Google Cloud Platform. Our team continues to monitor the situation closely to ensure full restoration of all impacted services. We are working with Google to confirm stability and will provide further updates as new information becomes available. Thank you for your patience as we work to resolve this incident. For the latest updates from Google, you can also visit the Google Cloud Status Page. https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsWJun <var data-var='date'>12</var>, <var data-var='time'>19:42</var> UTC Update - We want to inform you that the current service disruption is now isolated to our US3 region. According to the latest update from Google Cloud Platform: "All locations except us-central1 have fully recovered. us-central1 is mostly recovered. We do not have an ETA for full recovery in us-central1." If you are experiencing issues, they are likely limited to services operating in the US3 (us-central1) region. Our team continues to monitor the situation closely and is working with Google to resolve the remaining issues. For the latest updates from Google, please visit the Google Cloud Status Page. https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW Thank you for your continued patience and understanding.Jun <var data-var='date'>12</var>, <var data-var='time'>19:37</var> UTC Update - We are continuing to work on a fix for this issue.Jun <var data-var='date'>12</var>, <var data-var='time'>19:14</var> UTC Identified - The ongoing service disruption has been identified as an incident with our cloud provider, Google Cloud Platform (GCP). Our team is actively collaborating with Google to resolve the issue. You can track the progress and view the latest updates directly on the Google Cloud Status Page. https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW We will continue to monitor the situation closely and provide further updates as soon as more information becomes available. Thank you for your continued patience and understanding.Jun <var data-var='date'>12</var>, <var data-var='time'>18:58</var> UTC Update - We are continuing to investigate this issue.Jun <var data-var='date'>12</var>, <var data-var='time'>18:40</var> UTC Update - We are currently experiencing issues with some of our services due to an ongoing incident affecting our cloud provider (Google Cloud Platform). At this time, the majority of our services remain operational, including those critical to core functionality. However, some features are currently impacted, including: * Order Images * Reports * Geocoding * Maps Our team is actively working with our cloud provider to resolve the issue. We will provide an update as soon as more information becomes available, and no later than 19:30 UTC. Thank you for your patience and understanding.Jun <var data-var='date'>12</var>, <var data-var='time'>18:34</var> UTC Investigating - Due to a major incident on the Google side, we are currently experiencing some service issues. We will keep you updated.

Google Cloud Provider Issue

Apr <var data-var='date'>27</var>, <var data-var='time'>10:00</var> UTC Completed - The scheduled maintenance has been completed.Apr <var data-var='date'>27</var>, <var data-var='time'>06:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Apr <var data-var='date'>22</var>, <var data-var='time'>19:51</var> UTC Update - 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.Apr <var data-var='date'>17</var>, <var data-var='time'>12:54</var> UTC Update - We will be undergoing scheduled maintenance during this time.Apr <var data-var='date'>17</var>, <var data-var='time'>12:35</var> UTC Scheduled - Bringg has scheduled a maintenance window starting on Sunday, April 27, 2025 from 6 AM to 10 AM UTC, we are planing to-do a maintenance for 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 using email support@bringg.com.

Periodic upgrades for Bringg's server infrastructure - Sunday, April 27, 2025

Apr <var data-var='date'> 8</var>, <var data-var='time'>18:44</var> UTC Resolved - This incident has been resolved.Apr <var data-var='date'> 8</var>, <var data-var='time'>17:58</var> UTC Update - We are continuing to monitor for any further issues. Next Update will be available at 18:50 UTC.Apr <var data-var='date'> 8</var>, <var data-var='time'>17:25</var> UTC Update - We are continuing to monitor for any further issues. Next Update will be available at 18:10 UTC.Apr <var data-var='date'> 8</var>, <var data-var='time'>17:00</var> UTC Update - We are continuing to monitor for any further issues. Next Update will be available at 17:30 UTC.Apr <var data-var='date'> 8</var>, <var data-var='time'>16:08</var> UTC Update - We are continuing to monitor for any further issues. Next Update will be available at 16:45 UTC.Apr <var data-var='date'> 8</var>, <var data-var='time'>15:40</var> UTC Monitoring - We had an issue related to the BI dashboard where the results in all widgets were not shown. A fix has been implemented, and we are monitoring the results. The next Update will be available at 16:10 UTC.

BI dashboard widgets

Mar <var data-var='date'>30</var>, <var data-var='time'>07:00</var> UTC Completed - The scheduled maintenance has been completed.Mar <var data-var='date'>30</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'> 4</var>, <var data-var='time'>16:21</var> UTC Scheduled - We will be undergoing scheduled maintenance during this time. There is no downtime planned, but there may be some slowness during the process, and reports may be incomplete during a certain part of it. Tel Aviv: 8:00-9:00 Sun, 30 Mar 2025 Los Angeles: 22:00-23:00 Sat, 29 Mar 2025 New York: 1:00-2:00 Sun, 30 Mar 2025

Is Bringg down?

Bringg status is UP

Lastest published events

Partners integration service is down

Scheduled Maintenance – Server Infrastructure Upgrade

Scheduled Maintenance – Server Infrastructure Upgrade

Bringg Services, Components and Regions

Recent Bringg events

Partners integration service is down

Scheduled Maintenance – Server Infrastructure Upgrade

Scheduled Maintenance – Server Infrastructure Upgrade

Roadie is experiencing a core platform outage

DoorDash is experiencing service degradation due to a Cloudflare outage

[EU3] Database maintenance

Get your FREE account now,
5 monitors included!

Is Bringg down?

Bringg status is UP

Lastest published events

Partners integration service is down

Scheduled Maintenance – Server Infrastructure Upgrade

Scheduled Maintenance – Server Infrastructure Upgrade

Bringg Services, Components and Regions

Recent Bringg events

Partners integration service is down

Scheduled Maintenance – Server Infrastructure Upgrade

Scheduled Maintenance – Server Infrastructure Upgrade

Roadie is experiencing a core platform outage

DoorDash is experiencing service degradation due to a Cloudflare outage

[EU3] Database maintenance

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!