All Systems Operational
EU2-GCP
Operational
Access / Authentication (EU2-GCP)
?
Operational
API / Integrations (EU2-GCP)
?
Operational
Customer Experience (EU2-GCP)
?
Operational
Delivery Partners (EU2-GCP)
?
Operational
Dispatch Interface / Dashboard (EU2-GCP)
?
Operational
Driver App (EU2-GCP)
?
Operational
Geolocation / Tracking (EU2-GCP)
?
Operational
Infrastructure (EU2-GCP)
?
Operational
Inventory (EU2-GCP)
?
Operational
Notifications (EU2-GCP)
?
Operational
Planning / Optimization (EU2-GCP)
?
Operational
Reporting (EU2-GCP)
?
Operational
Billing Page (EU2 - GCP)
Operational
EU3-GCP
Operational
Access / Authentication (EU3-GCP)
?
Operational
API / Integrations (EU3-GCP)
?
Operational
Customer Experience (EU3-GCP)
?
Operational
Delivery Partners (EU3-GCP)
?
Operational
Dispatch Interface / Dashboard (EU3-GCP)
?
Operational
Driver App (EU3-GCP)
?
Operational
Geolocation / Tracking (EU3-GCP)
?
Operational
Infrastructure (EU3-GCP)
?
Operational
Inventory (EU3-GCP)
?
Operational
Notifications (EU3-GCP)
?
Operational
Planning / Optimization (EU3-GCP)
?
Operational
Reporting (EU3-GCP)
?
Operational
Billing Page (EU3-GCP)
Operational
US2-GCP
Operational
Access / Authentication (US2-GCP)
?
Operational
API / Integrations (US2-GCP)
?
Operational
Customer Experience (US2-GCP)
?
Operational
Delivery Partners (US2-GCP)
?
Operational
Dispatch Interface / Dashboard (US2-GCP)
?
Operational
Driver App (US2-GCP)
?
Operational
Geolocation / Tracking (US2-GCP)
?
Operational
Infrastructure (US2-GCP)
?
Operational
Inventory (US2-GCP)
?
Operational
Notifications (US2-GCP)
?
Operational
Planning / Optimization (US2-GCP)
?
Operational
Reporting (US2-GCP)
?
Operational
Billing Page (US2 - GCP)
Operational
US3-GCP
Operational
Access / Authentication (US3-GCP)
?
Operational
API / Integrations (US3-GCP)
?
Operational
Customer Experience (US3-GCP)
?
Operational
Delivery Partners (US3-GCP)
?
Operational
Dispatch Interface / Dashboard (US3-GCP)
?
Operational
Driver App (US3-GCP)
?
Operational
Geolocation / Tracking (US3-GCP)
?
Operational
Infrastructure (US3-GCP)
?
Operational
Inventory (US3-GCP)
?
Operational
Notifications (US3-GCP)
?
Operational
Planning / Optimization (US3-GCP)
?
Operational
Reporting (US3-GCP)
?
Operational
Billing Page (US3 - GCP)
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Periodic upgrades for Bringg's server infrastructure
Jul 28, 2024 05:00-12:00 UTC
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 on Jul 09, 2024 - 12:22 UTC
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 on Jul 09, 2024 - 12:22 UTC