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
US4-GCP
Operational
Access / Authentication (US4-GCP)
Operational
API / Integrations (US4-GCP)
Operational
Customer Experience (US4-GCP)
Operational
Delivery Partners (US4-GCP)
Operational
Dispatch Interface / Dashboard (US4-GCP)
Operational
Driver App (US4-GCP)
Operational
Geolocation / Tracking (US4-GCP)
Operational
Infrastructure (US4-GCP)
Operational
Inventory (US4-GCP)
Operational
Notifications (US4-GCP)
Operational
Planning / Optimization (US4-GCP)
Operational
Reporting (US4-GCP)
Operational
Billing Page (US4-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
Scheduled Maintenance – Server Infrastructure Upgrade Mar 8, 2026 07:00-07:30 UTC
We plan to perform a periodic upgrade on Bringg's server infrastructure for all environments on March 8.
Israel 9 AM – 9:30 AM IST (UTC+2)
London 7 AM – 7:30 AM GMT (UTC+0)
New York 2 AM – 2:30 AM EST (UTC−5)
Los Angeles 11 AM – 11:30 AM (Sat → Sun) PST (UTC−8)
TECHNICAL INFORMATION
During the scheduled maintenance window, the Bringg platform may experience temporary service disruptions, intermittent errors, or degraded performance. Users and API consumers may encounter brief outages, increased response times, or occasional request failures while maintenance activities are underway.
The maintenance has been scheduled during a period of low activity and volume. As a result, any impact is expected to be minimal, if any.
Posted on Feb 18, 2026 - 22:48 UTC
Israel 9 AM – 9:30 AM IST (UTC+2)
London 7 AM – 7:30 AM GMT (UTC+0)
New York 2 AM – 2:30 AM EST (UTC−5)
Los Angeles 11 AM – 11:30 AM (Sat → Sun) PST (UTC−8)
TECHNICAL INFORMATION
During the scheduled maintenance window, the Bringg platform may experience temporary service disruptions, intermittent errors, or degraded performance. Users and API consumers may encounter brief outages, increased response times, or occasional request failures while maintenance activities are underway.
The maintenance has been scheduled during a period of low activity and volume. As a result, any impact is expected to be minimal, if any.
Posted on Feb 18, 2026 - 22:48 UTC
Scheduled Maintenance – Server Infrastructure Upgrade Mar 22, 2026 06:00-10:00 UTC
We plan to perform a periodic upgrade on Bringg’s server infrastructure in the US2 environment on March 22nd.
Israel, 8 AM – 12 AM, IST (UTC+2)
London, 6 AM – 10 PM, GMT (UTC+0)
New York, 2 AM – 6 PM, EDT (UTC-4)
Los Angeles, 11 PM – 3 PM, PDT (UTC-7)
HOW TO PREPARE
During the short maintenance window, Bringg services in the US2 environment only 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 Mar 22, 2026 - 06:00 UTC
Israel, 8 AM – 12 AM, IST (UTC+2)
London, 6 AM – 10 PM, GMT (UTC+0)
New York, 2 AM – 6 PM, EDT (UTC-4)
Los Angeles, 11 PM – 3 PM, PDT (UTC-7)
HOW TO PREPARE
During the short maintenance window, Bringg services in the US2 environment only 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 Mar 22, 2026 - 06:00 UTC