Periodic upgrades for Bringg's server infrastructure
Completed
The scheduled maintenance has been completed.
Posted Jul 28, 2024 - 09:40 UTC
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Jul 28, 2024 - 05:00 UTC
Scheduled
Bringg has scheduled a maintenance window starting on Sunday, Jul 28, 2024 at 5:00 AM UTC in order to perform periodic upgrades. The maintenance will be carried out on all servers according to the following schedule:
5:00 - 12:00 GMT
1:00 - 8:00 New York time
27 Jul 22:00 - 28 Jul 5:00 Los Angeles time
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.
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 Jul 09, 2024 - 12:22 UTC
This scheduled maintenance affected: EU2-GCP (Access / Authentication (EU2-GCP), API / Integrations (EU2-GCP), Customer Experience (EU2-GCP), Delivery Partners (EU2-GCP), Dispatch Interface / Dashboard (EU2-GCP), Driver App (EU2-GCP), Geolocation / Tracking (EU2-GCP), Infrastructure (EU2-GCP), Inventory (EU2-GCP), Notifications (EU2-GCP), Planning / Optimization (EU2-GCP), Reporting (EU2-GCP), Billing Page (EU2 - GCP)), US3-GCP (Access / Authentication (US3-GCP), API / Integrations (US3-GCP), Customer Experience (US3-GCP), Delivery Partners (US3-GCP), Dispatch Interface / Dashboard (US3-GCP), Driver App (US3-GCP), Geolocation / Tracking (US3-GCP), Infrastructure (US3-GCP), Inventory (US3-GCP), Notifications (US3-GCP), Planning / Optimization (US3-GCP), Reporting (US3-GCP), Billing Page (US3 - GCP)), US2-GCP (Access / Authentication (US2-GCP), API / Integrations (US2-GCP), Customer Experience (US2-GCP), Delivery Partners (US2-GCP), Dispatch Interface / Dashboard (US2-GCP), Driver App (US2-GCP), Geolocation / Tracking (US2-GCP), Infrastructure (US2-GCP), Inventory (US2-GCP), Notifications (US2-GCP), Planning / Optimization (US2-GCP), Reporting (US2-GCP), Billing Page (US2 - GCP)), and EU3-GCP (Access / Authentication (EU3-GCP), API / Integrations (EU3-GCP), Customer Experience (EU3-GCP), Delivery Partners (EU3-GCP), Dispatch Interface / Dashboard (EU3-GCP), Driver App (EU3-GCP), Geolocation / Tracking (EU3-GCP), Infrastructure (EU3-GCP), Inventory (EU3-GCP), Notifications (EU3-GCP), Planning / Optimization (EU3-GCP), Reporting (EU3-GCP), Billing Page (EU3-GCP)).