All Systems Operational
EU1-AWS Operational
Access / Authentication (EU1-AWS) ? Operational
API / Integrations (EU1-AWS) ? Operational
Customer Experience (EU1-AWS) ? Operational
Delivery Partners (EU1-AWS) ? Operational
Dispatch Interface / Dashboard (EU1-AWS) ? Operational
Driver App (EU1-AWS) ? Operational
Geolocation / Tracking (EU1-AWS) ? Operational
Infrastructure (EU1-AWS) ? Operational
Inventory (EU1-AWS) ? Operational
Notifications (EU1-AWS) ? Operational
Planning / Optimization (EU1-AWS) ? Operational
Reporting (EU1-AWS) ? 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
US1-AWS Operational
Access / Authentication (US1-AWS) ? Operational
API / Integrations (US1-AWS) ? Operational
Customer Experience (US1-AWS) ? Operational
Delivery Partners (US1-AWS) ? Operational
Dispatch Interface / Dashboard (US1-AWS) ? Operational
Driver App (US1-AWS) ? Operational
Geolocation / Tracking (US1-AWS) ? Operational
Infrastructure (US1-AWS) ? Operational
Inventory (US1-AWS) ? Operational
Notifications (US1-AWS) ? Operational
Planning / Optimization (US1-AWS) ? Operational
Reporting (US1-AWS) ? 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
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
API response time (us1)
Fetching
API response time (us2)
Fetching
API response time (eu1)
Fetching
API response time (eu2)
Fetching
Past Incidents
Oct 3, 2022

No incidents reported today.

Oct 2, 2022
Bringg Scheduled Maintenance — Sunday, 2 October 2022
Completed - The scheduled maintenance has been completed.
Oct 2, 14:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 2, 08:00 UTC
Scheduled - MAINTENANCE DETAILS

Bringg has scheduled a short maintenance window starting on Sunday, 2nd of October 2022 at 8AM UTC in order to perform Kubernetes API maintenance. The maintenance will be carried out on all servers (US1, US2, EU1, EU2) with the following schedule:

08:00 — 14:00 UTC
09:00 — 15:00 London
03:00 — 09:00 New York

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 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.

If you have any questions, please let us know at support@bringg.com.
Sep 14, 10:18 UTC
Oct 1, 2022

No incidents reported.

Sep 30, 2022

No incidents reported.

Sep 29, 2022

No incidents reported.

Sep 28, 2022

No incidents reported.

Sep 27, 2022

No incidents reported.

Sep 26, 2022

No incidents reported.

Sep 25, 2022

No incidents reported.

Sep 24, 2022

No incidents reported.

Sep 23, 2022

No incidents reported.

Sep 22, 2022

No incidents reported.

Sep 21, 2022

No incidents reported.

Sep 20, 2022

No incidents reported.

Sep 19, 2022

No incidents reported.

← Incident History Powered by Atlassian Statuspage