tag:status.bringg.com,2005:/historyBringg Status - Incident History2024-03-29T05:24:03ZBringgtag:status.bringg.com,2005:Incident/201864252024-03-07T19:46:09Z2024-03-07T19:46:09ZUS2 fleet-router-service issues<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>19:46</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>16:50</var> UTC</small><br><strong>Monitoring</strong> - The number of timeout errors related to fleet-router-service has decreased, we are monitoring the system</p><p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>16:41</var> UTC</small><br><strong>Investigating</strong> - We are seeing timeouts increase related to fleet-router-service, we are working on resolving the issue</p>tag:status.bringg.com,2005:Incident/201728572024-03-07T07:01:56Z2024-03-07T07:01:56ZBringg Scheduled Maintenance — Thursday, 7 March 2024 - US2 | Preventive maintenance in our caching infra.<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>07:01</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>07:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>05:51</var> UTC</small><br><strong>Scheduled</strong> - MAINTENANCE DETAILS<br /><br />Bringg has scheduled a maintenance window starting on Thursday, 7 March 2024 at 7 AM UTC, we are going to do preventive maintenance in our caching infra. <br />The maintenance will be carried out on the US2 Bringg server only.<br /><br />The maintenance is needed to ensure the scalability of our caching infra which is at 80% capacity and will last several seconds.<br /><br />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.<br /><br />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.<br /><br />TECHNICAL INFORMATION<br /><br />There won't be any downtime, just small hiccups during the maintenance.<br /><br />For any questions or concerns please contact support@bringg.com.</p>tag:status.bringg.com,2005:Incident/199208702024-02-25T08:00:56Z2024-02-25T08:00:56ZMaintenance on Bringg's data lake infrastructure<p><small>Feb <var data-var='date'>25</var>, <var data-var='time'>08:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'>25</var>, <var data-var='time'>07:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>15:24</var> UTC</small><br><strong>Update</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Feb <var data-var='date'>25</var>, <var data-var='time'>07:00</var> UTC</small><br><strong>Scheduled</strong> - MAINTENANCE DETAILS<br /><br />Bringg has scheduled a short maintenance window starting on Sunday, February 25, 2024 at 7 AM UTC in order to perform a short upgrade. The Maintenance will be carried out on all servers with the following schedule:<br /><br />7:00 - 8:00 UTC<br />2:00 - 3:00 New York<br />23:00 - 00:00 Los Angeles<br /><br />We anticipate that the maintenance will result in less than five (5) minutes of possible service degradation and will affect only the reporting component (Dashboard).<br /><br />We have scheduled the maintenance for a low-activity time period to ensure that your customers and operations are minimally affected, if at all, by any disruption.<br /><br />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.<br /><br />HOW TO PREPARE<br /><br />During the short maintenance window, Bringg services may become temporarily unavailable. This includes the reporting component only (Dashboard), as was previously mentioned.<br /><br />If you have any questions, please let us know at support@bringg.com.</p>tag:status.bringg.com,2005:Incident/200317612024-02-20T20:00:07Z2024-02-20T20:00:07ZEU2 Subscription-service issues<p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>20:00</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>19:08</var> UTC</small><br><strong>Update</strong> - The issue has been resolved. Monitoring to confirm that it will not resurface.</p><p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>18:59</var> UTC</small><br><strong>Monitoring</strong> - The fix is being deployed. Monitoring. Next update at 21:05 UTC</p><p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>18:57</var> UTC</small><br><strong>Identified</strong> - The issue with realtime affecting Driver app and Web has been identified.</p>tag:status.bringg.com,2005:Incident/200317182024-02-20T18:56:10Z2024-02-20T18:56:10ZUS2 Subscription-service issues<p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>18:56</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>18:52</var> UTC</small><br><strong>Monitoring</strong> - The issue has been identified and resolved on our side, we are monitoring the results<br />Next update will be at 09:00 PM UTC</p><p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>18:51</var> UTC</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Feb <var data-var='date'>20</var>, <var data-var='time'>18:50</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.bringg.com,2005:Incident/199956102024-02-16T00:05:23Z2024-02-16T00:05:23ZWebhooks service outage<p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>00:05</var> UTC</small><br><strong>Resolved</strong> - This incident has been fully resolved.<br />All systems are operational.</p><p><small>Feb <var data-var='date'>15</var>, <var data-var='time'>23:24</var> UTC</small><br><strong>Monitoring</strong> - We are monitoring the results as the services are back up and running.</p><p><small>Feb <var data-var='date'>15</var>, <var data-var='time'>23:18</var> UTC</small><br><strong>Identified</strong> - The issue has been identified and services have been restarted.</p><p><small>Feb <var data-var='date'>15</var>, <var data-var='time'>23:06</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating the issue.</p>tag:status.bringg.com,2005:Incident/199868432024-02-14T22:57:21Z2024-02-14T22:57:21ZSMS degradation: Our system has detected abnormalities in Twilio API requests and we are actively monitoring<p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>22:57</var> UTC</small><br><strong>Resolved</strong> - Update from Twilio:<br /><br />"All services impacted by the issues with the Twilio Rest API have recovered and are operating as intended. This incident has been resolved."<br /><br />This incident has been resolved.</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>22:05</var> UTC</small><br><strong>Monitoring</strong> - Update from Twilio:<br />"We're seeing recovery in the Twilio Rest API, impacting multiple Twilio services. Please see impacted services as follows:<br /><br />Taskrouter: Customers are unable to create, update, or delete via REST API<br />Flex platform: Agent Login/Inbound outbound conversation <br />Programmable Video: Unable to create and modify rooms via Rest API <br />Verify: To be determined <br />Programmable Messaging (SMS): Customers may experience 5XX errors<br /><br />We will be monitoring all services to ensure a full recovery and provide another update in 30 minutes or as soon as more information becomes available."</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>21:50</var> UTC</small><br><strong>Update</strong> - We are seeing improvements in Twilio API requests, we continue to monitor the issue</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>21:30</var> UTC</small><br><strong>Update</strong> - Update from Twilio:<br />"We are experiencing issues with the Twilio Rest API, impacting multiple Twilio services. We're seeing impact on Very, Programmable Messaging (SMS), Taksrouter and Flex agent login/inbound conversations. Our engineering team is actively working to resolve the issue. We expect to provide another update in 30 mins or as soon as more information becomes available."<br />https://status.twilio.com/incidents/dhb0hj0dm9qf</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>21:24</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>21:19</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>21:07</var> UTC</small><br><strong>Investigating</strong> - We are monitoring the abnormalities in Twilio API requests. <br />Twilio reported: <br />"We are currently investigating errors for the Twilio Rest API, impacting multiple Twilio services. Our engineering team has been alerted and is actively investigating. We will update as soon as we have more information. Feb 14, 13:04 PST"<br />https://status.twilio.com/</p>tag:status.bringg.com,2005:Incident/196567222024-01-28T12:30:38Z2024-01-28T12:30:38ZPeriodic upgrades for Bringg's server infrastructure<p><small>Jan <var data-var='date'>28</var>, <var data-var='time'>12:30</var> UTC</small><br><strong>Completed</strong> - Scheduled maintenance is completed.</p><p><small>Jan <var data-var='date'>28</var>, <var data-var='time'>09:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>28</var>, <var data-var='time'>07:00</var> UTC</small><br><strong>Update</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Jan <var data-var='date'> 9</var>, <var data-var='time'>13:25</var> UTC</small><br><strong>Scheduled</strong> - MAINTENANCE DETAILS<br /><br />Bringg has scheduled a short maintenance window starting on Sunday, January 28, 2024 at 7:00 AM UTC in order to perform a short upgrade. The maintenance will be carried out on all servers according to the following schedule:<br /><br />US regions (GCP/Google):<br />7:00 - 11:00 GMT<br />2:00 - 6:00 New York time<br />27 Jan 23:00 - 28 Jan 3:00 Los Angeles time<br /><br />We anticipate that the maintenance will result in less than five (5) minutes of possible service degradation, and may affect both real-time and API services.<br /><br />We have scheduled the maintenance for a low-activity time period to ensure that your customers and operations are minimally affected, if at all, by any disruption.<br /><br />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.<br /><br />HOW TO PREPARE<br /><br />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.<br /><br />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.<br /><br />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.<br /><br />TECHNICAL INFORMATION<br /><br />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.<br /><br />If you have any questions, please let us know at support@bringg.com.</p>tag:status.bringg.com,2005:Incident/187671782023-10-29T12:00:23Z2023-10-29T12:00:23ZBringg Scheduled Maintenance - Sunday, 29 October 2023 - US1 (AWS) migration to US3 (GCP)<p><small>Oct <var data-var='date'>29</var>, <var data-var='time'>12:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Oct <var data-var='date'>29</var>, <var data-var='time'>08:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Oct <var data-var='date'>12</var>, <var data-var='time'>16:13</var> UTC</small><br><strong>Scheduled</strong> - MAINTENANCE DETAILS<br /><br /><br />Bringg has scheduled a maintenance window starting on Sunday, October 29, 2023, at 8 AM UTC.<br />During this maintenance, our team will perform the previously planned migration of our US1 (AWS) server infrastructure to US3 under GCP.<br /><br /><br />The maintenance will be carried out on Bringg's US1 server with the following schedule:<br />08:00 AM - 12:00 PM UTC<br />01:00 AM - 05:00 AM Los Angeles<br />04:00 AM - 08:00 AM New York<br /><br /><br />We anticipate that the maintenance will result in periods of downtime and service degradation and may affect both real-time and API services during the time of the window.<br /><br /><br />We have scheduled the maintenance for a low-activity time period to ensure that your customers and operations are minimally affected.<br /><br /><br />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.<br /><br /><br />HOW TO PREPARE<br /><br /><br />During the maintenance window, Bringg services will have moments of temporary unavailability. This might include APIs, integrations, Driver Apps, associated inventory management applications (both web and mobile), and driver/delivery tracking services.<br /><br /><br />If you have activity during this period, you may want to prepare a warning statement telling your users to try your service again following the maintenance window.<br /><br /><br />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.<br /><br /><br />TECHNICAL INFORMATION<br /><br /><br />During this window, the Bringg platform may respond to requests in the following ways:<br />Administrators and dispatchers attempting to log into the Bringg Dashboard may see a message indicating that Bringg is unavailable.<br /><br /><br />API services attempting to contact our API endpoints may receive a 5XX response such as 502 Bad Gateway or 503 Service Unavailable. We will not be providing any maintenance responses via JSON.<br /><br /><br />For any questions or concerns, please contact support@bringg.com.</p>tag:status.bringg.com,2005:Incident/189234112023-10-25T14:08:56Z2023-10-25T14:08:56ZAnalytic reports cannot be downloaded or emailed<p><small>Oct <var data-var='date'>25</var>, <var data-var='time'>14:08</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Oct <var data-var='date'>25</var>, <var data-var='time'>13:26</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Oct <var data-var='date'>25</var>, <var data-var='time'>12:46</var> UTC</small><br><strong>Investigating</strong> - The issue is currently being investigated.</p>tag:status.bringg.com,2005:Incident/186297892023-09-28T11:35:43Z2023-09-28T11:35:43ZAn issue with the 'quotes-service'<p><small>Sep <var data-var='date'>28</var>, <var data-var='time'>11:35</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>28</var>, <var data-var='time'>10:58</var> UTC</small><br><strong>Update</strong> - The issue has been resolved on our side, we are monitoring the results. We will provide more information by Thursday, 2023-09-28 11:40 UTC.</p><p><small>Sep <var data-var='date'>28</var>, <var data-var='time'>10:18</var> UTC</small><br><strong>Update</strong> - We are continuing to monitor for any further issues. We will provide more information by Thursday, 2023-09-28 11:10 UTC.</p><p><small>Sep <var data-var='date'>28</var>, <var data-var='time'>09:28</var> UTC</small><br><strong>Update</strong> - We are continuing to monitor for any further issues. We will provide more information by Thursday, 2023-09-28 10:20 UTC.</p><p><small>Sep <var data-var='date'>28</var>, <var data-var='time'>08:39</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results. We will provide more information by Thursday, 2023-09-28 09:30 UTC.</p><p><small>Sep <var data-var='date'>28</var>, <var data-var='time'>08:30</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating the problem. We will provide more information by Thursday, 2023-09-28 09:10 UTC.</p>tag:status.bringg.com,2005:Incident/181864832023-08-18T17:57:22Z2023-08-18T17:57:22ZPartial outage at US-2 Aug 18.<p><small>Aug <var data-var='date'>18</var>, <var data-var='time'>17:57</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'>18</var>, <var data-var='time'>17:24</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Aug <var data-var='date'>18</var>, <var data-var='time'>17:06</var> UTC</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Aug <var data-var='date'>18</var>, <var data-var='time'>16:55</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Aug <var data-var='date'>18</var>, <var data-var='time'>16:54</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.bringg.com,2005:Incident/180011312023-07-30T09:13:38Z2023-07-30T09:13:38ZRemaing Issues from the Scheduled Maintenance to EU3 (GCP)<p><small>Jul <var data-var='date'>30</var>, <var data-var='time'>09:13</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>30</var>, <var data-var='time'>08:23</var> UTC</small><br><strong>Monitoring</strong> - All issues found were addressed and the fixes were verified from the Bringg side. <br />We will keep monitoring this incident for the next hours.</p><p><small>Jul <var data-var='date'>30</var>, <var data-var='time'>08:13</var> UTC</small><br><strong>Update</strong> - The Bringg R&D team was able to address the issue with the Customer Experience App. <br />They are still working on fixing some remaining issues on the Billing Page.<br />We will provide more information by Sunday, 2023-07-30 08:43 UTC.</p><p><small>Jul <var data-var='date'>30</var>, <var data-var='time'>07:41</var> UTC</small><br><strong>Update</strong> - The issues with Delivery Partners (fleet service) have been resolved. <br />Our team is currently working on addressing the problems with the customer experience app and the Billing Page. <br />We will provide more information by Sunday, 2023-07-30 08:12 UTC.</p><p><small>Jul <var data-var='date'>30</var>, <var data-var='time'>07:11</var> UTC</small><br><strong>Identified</strong> - Our team has identified some issues with the following Bringg product components: Fleet service, Customer Experience App, and Billing page. <br />We are currently working to fix this problem. Users might experience degraded performance in this area of the product.</p>tag:status.bringg.com,2005:Incident/179025922023-07-30T07:05:25Z2023-07-30T07:05:25ZBringg Scheduled Maintenance - Sunday, 30 July 2023 - EU1 migration to EU3 (GCP)<p><small>Jul <var data-var='date'>30</var>, <var data-var='time'>07:05</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jul <var data-var='date'>30</var>, <var data-var='time'>03:01</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jul <var data-var='date'>19</var>, <var data-var='time'>17:27</var> UTC</small><br><strong>Scheduled</strong> - MAINTENANCE DETAILS<br /><br />Bringg has scheduled a maintenance window starting on Sunday the 30th of July 2023 at 3AM UTC.<br />During this maintenance our team will perform the previously notified planned of migrating our EU1 (AWS) server infrastructure to EU3, under GCP.<br /><br />The maintenance will be carried out on Bringg's EU1 server with the following schedule:<br />03:00 AM - 07:00 AM UTC<br />04:00 AM - 08:00 AM London<br />11:00 PM - 03:00 AM New York<br /><br />We anticipate that the maintenance will result in periods of downtime and service degradation, and may affect both real-time and API services, during the time of the window.<br /><br />We have scheduled the maintenance for a low-activity time period to ensure that your customers and operations are minimally affected.<br /><br />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.<br /><br />HOW TO PREPARE<br /><br />During the maintenance window, Bringg services will have moments of temporary unavailability. This might include APIs, integrations, Driver Apps, associated inventory management applications (both web and mobile), and driver/delivery tracking services.<br /><br />If you have activity during this period, you may want to prepare a warning statement telling your users to try your service again following the maintenance window.<br /><br />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.<br /><br />TECHNICAL INFORMATION<br /><br />During this window, the Bringg platform may respond to requests in the following ways:<br />Administrators and dispatchers attempting to log into the Bringg Dashboard may see a message indicating that Bringg is unavailable.<br /><br />API services attempting to contact our API endpoints may receive a 5XX response such as 502 Bad Gateway or 503 Service Unavailable. We will not be providing any maintenance response via JSON.<br /><br />For any questions or concerns please contact support@bringg.com.</p>tag:status.bringg.com,2005:Incident/179662832023-07-26T17:21:43Z2023-07-26T17:21:43Z'Realtime' updates are not operational in eu1<p><small>Jul <var data-var='date'>26</var>, <var data-var='time'>17:21</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved. We thank you for your patience while we worked on resolving the issue.</p><p><small>Jul <var data-var='date'>26</var>, <var data-var='time'>16:16</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results. We will provide more information by Wednesday, 2023-07-26 17:30 UTC.</p><p><small>Jul <var data-var='date'>26</var>, <var data-var='time'>15:49</var> UTC</small><br><strong>Identified</strong> - Our team has stabilized Kafka, however, they are still working on improving the situation. We will provide more information by Wednesday, 2023-07-26 16:30 UTC.</p><p><small>Jul <var data-var='date'>26</var>, <var data-var='time'>15:07</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue and we do not have an ETA for mitigation at this point. We will provide more information by Wednesday, 2023-07-26 15:50 UTC.</p><p><small>Jul <var data-var='date'>26</var>, <var data-var='time'>14:32</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating an issue with Kafka which led to problems with the 'realtime' updates. We will provide more information by Wednesday, 2023-07-26 15:10 UTC.</p>tag:status.bringg.com,2005:Incident/179580772023-07-25T19:21:53Z2023-07-25T19:21:53ZHistory search returns an error<p><small>Jul <var data-var='date'>25</var>, <var data-var='time'>19:21</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved. We thank you for your patience while we worked on resolving the issue.</p><p><small>Jul <var data-var='date'>25</var>, <var data-var='time'>18:57</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results. We will provide more information by Tuesday, 2023-07-25 19:30 UTC.</p><p><small>Jul <var data-var='date'>25</var>, <var data-var='time'>18:23</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating this issue with our RnD team. The next update will be within 40 minutes.</p>tag:status.bringg.com,2005:Incident/177597542023-07-04T10:35:35Z2023-07-04T10:35:35ZElevated error rate and longer response times in EU2 region<p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>10:35</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>09:27</var> UTC</small><br><strong>Monitoring</strong> - The issue has been identified and resolved on our side, we are monitoring the results</p><p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>09:15</var> UTC</small><br><strong>Update</strong> - Our R&D team continue to investigate the issue with degraded performance of our system in EU2</p><p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>08:42</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.bringg.com,2005:Incident/175744472023-06-14T20:34:35Z2023-06-14T20:34:35ZUS2 Long time response<p><small>Jun <var data-var='date'>14</var>, <var data-var='time'>20:34</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>14</var>, <var data-var='time'>19:31</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jun <var data-var='date'>14</var>, <var data-var='time'>18:07</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.bringg.com,2005:Incident/175719832023-06-14T15:28:20Z2023-06-14T15:28:20ZUS2 Long time response<p><small>Jun <var data-var='date'>14</var>, <var data-var='time'>15:28</var> UTC</small><br><strong>Resolved</strong> - This issue has been resolved.</p><p><small>Jun <var data-var='date'>14</var>, <var data-var='time'>14:54</var> UTC</small><br><strong>Monitoring</strong> - The problem has been identified, the fix has been implemented, and we are monitoring the system.</p><p><small>Jun <var data-var='date'>14</var>, <var data-var='time'>13:35</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating service degradation issue on US2</p>tag:status.bringg.com,2005:Incident/174088092023-06-11T11:00:06Z2023-06-11T11:00:06ZBringg Scheduled Maintenance - Sunday, 11 June 2023<p><small>Jun <var data-var='date'>11</var>, <var data-var='time'>11:00</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jun <var data-var='date'>11</var>, <var data-var='time'>07:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>May <var data-var='date'>29</var>, <var data-var='time'>11:48</var> UTC</small><br><strong>Scheduled</strong> - MAINTENANCE DETAILS<br /><br />Bringg has scheduled a maintenance window starting on Sunday the 11th of June 2023 at 7AM UTC, in order to perform periodic upgrades for Bringg's server infrastructure.<br />The maintenance will be carried out on Bringg's GCP servers (US2/ EU2) with the following schedule:<br /><br />07:00 AM - 11:00 PM UTC<br />08:00 AM - 12:00 PM London<br />03:00 AM - 07:00 AM New York<br /><br />Our technical team anticipates that this maintenance should not cause any service degradation.<br /><br />In any case, we have scheduled the maintenance for a low-activity time period to ensure that your customers and operations are minimally affected, if at all, by any possible disruption.<br /><br />We will be updating the ongoing status of this activity 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.<br /><br />For any questions or concerns please contact support@bringg.com.</p>tag:status.bringg.com,2005:Incident/171829252023-05-08T18:09:04Z2023-05-08T18:09:04ZUS-2 Database Slowness Issue<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>18:09</var> UTC</small><br><strong>Resolved</strong> - The issue was resolved</p><p><small>May <var data-var='date'> 8</var>, <var data-var='time'>17:23</var> UTC</small><br><strong>Monitoring</strong> - The issue was fixed and is under monitoring process</p><p><small>May <var data-var='date'> 8</var>, <var data-var='time'>16:44</var> UTC</small><br><strong>Investigating</strong> - We're investigating the issue with slowness on US-2</p>tag:status.bringg.com,2005:Incident/169751022023-04-26T20:44:40Z2023-04-26T20:44:40ZUS2 - Issues with the Route Optimization service and AutoDispatch service<p><small>Apr <var data-var='date'>26</var>, <var data-var='time'>20:44</var> UTC</small><br><strong>Resolved</strong> - The incident has been resolved.</p><p><small>Apr <var data-var='date'>26</var>, <var data-var='time'>20:29</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.<br /><br />We will provide an update within the next 30 minutes.</p><p><small>Apr <var data-var='date'>26</var>, <var data-var='time'>20:22</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating this issue.<br /><br />We will provide an update within the next 30-40 minutes.</p>tag:status.bringg.com,2005:Incident/169638282023-04-25T17:06:46Z2023-04-25T17:06:46ZNetwork issues with our cloud provider (GCP) in US2<p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>17:06</var> UTC</small><br><strong>Resolved</strong> - The incident has been resolved by the cloud provider. More information about the problem could be found by following this link: https://status.cloud.google.com/incidents/gsr6HAk6oCUpNG4CAZ1H</p><p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>16:36</var> UTC</small><br><strong>Identified</strong> - We currently have a network issue that is related to our cloud provider. Our systems mitigated the problem automatically, however, there is a possibility for short-lived malfunctions.<br /><br />We will provide an update within the next 30-40 minutes.</p>tag:status.bringg.com,2005:Incident/169336562023-04-21T23:29:06Z2023-04-21T23:29:06ZUS2 - Issues with the Route Optimization service and AutoDispatch service<p><small>Apr <var data-var='date'>21</var>, <var data-var='time'>23:29</var> UTC</small><br><strong>Resolved</strong> - The incident has been resolved.</p><p><small>Apr <var data-var='date'>21</var>, <var data-var='time'>22:35</var> UTC</small><br><strong>Update</strong> - Our team has significantly mitigated the problem. We are continuing to monitor for any further issues.</p><p><small>Apr <var data-var='date'>21</var>, <var data-var='time'>22:10</var> UTC</small><br><strong>Update</strong> - We are continuing to monitor the situation closely.</p><p><small>Apr <var data-var='date'>21</var>, <var data-var='time'>21:13</var> UTC</small><br><strong>Monitoring</strong> - Some users report a partial outage, therefore, we keep monitoring the situation.</p>tag:status.bringg.com,2005:Incident/169323682023-04-21T20:25:45Z2023-04-21T20:25:45ZUS2 - Issues with the Route Optimization service and AutoDispatch service<p><small>Apr <var data-var='date'>21</var>, <var data-var='time'>20:25</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Apr <var data-var='date'>21</var>, <var data-var='time'>19:40</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Apr <var data-var='date'>21</var>, <var data-var='time'>18:50</var> UTC</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Apr <var data-var='date'>21</var>, <var data-var='time'>17:54</var> UTC</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Apr <var data-var='date'>21</var>, <var data-var='time'>17:36</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>