Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Jul 30, 2023 - 03:01 UTC
Scheduled
MAINTENANCE DETAILS
Bringg has scheduled a maintenance window starting on Sunday the 30th of July 2023 at 3AM UTC. During this maintenance our team will perform the previously notified planned of migrating our EU1 (AWS) server infrastructure to EU3, under GCP.
The maintenance will be carried out on Bringg's EU1 server with the following schedule: 03:00 AM - 07:00 AM UTC 04:00 AM - 08:00 AM London 11:00 PM - 03:00 AM New York
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.
We have scheduled the maintenance for a low-activity time period to ensure that your customers and operations are minimally affected.
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 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.
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.
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 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.