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.
Posted on
Oct 20, 2025 - 16:30 UTC