Bringg has scheduled a short maintenance window starting on Sunday, 16th June 2019 at 7 AM UTC in order to perform a short upgrade. The Maintenance will be carried out on all servers with the following schedule:
US1 (AWS/Amazon): 07:00 - 08:00 UTC - 03:00 - 04:00 New York
EU1 (AWS/Amazon): 08:00 - 09:00 UTC - 09:00 - 10:00 London
US2 (GCP/Google) : 10:00 - 11:00 UTC - 06:00 - 07:00 New York
EU2 (GCP/Google) : 11:00 - 12:00 UTC - 12:00 - 13:00 London
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.
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.
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.
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.
During this window, the Bringg platform may respond to requests in the following ways:
Administrators and dispatchers attempting to log into the Bringg Dashboard may see a message indicating that Bringg is unavailable.
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.
If you have any questions, please let us know at email@example.com