Bringg Status

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 (eu1)

Fetching

Realtime API response time (us1)

Fetching

Realtime API response time (eu1)

Fetching

Past Incidents

Nov 14, 2019

No incidents reported today.

Nov 13, 2019

Investigating issues related to API response

Resolved - We are marking this issue as resolved, as we've identified the cause and have confirmed that it is no longer occurring. All API activity has returned to a normal state.
Nov 13, 21:32 UTC

Identified - We've identified the issue, and believe it is only affecting a specific sub-set of our clients. The majority of API activity is responding correctly. We are continuing to review.
Nov 13, 21:28 UTC

Investigating - We've received reports of issues with the Bringg API. Our team is investigating.
Nov 13, 21:14 UTC

Nov 12, 2019

No incidents reported.

Nov 11, 2019

We are experiencing cloud problems in Google Cloud, several services are in bad state. We contacted our provider in order to understand the root cause

Resolved - This incident has been resolved.
Nov 11, 14:01 UTC

Update - Next GCP update at 13:30 UTC - https://status.cloud.google.com/incident/cloud-datastore/19006
Nov 11, 12:52 UTC

Update - Next Google Cloud update will be at 13:00 UTC
Nov 11, 12:10 UTC

Update - We are continuing to monitor for any further issues.
Nov 11, 12:08 UTC

Monitoring - We are still monitoring this issue, if you want to check GCP please check https://status.cloud.google.com/
Nov 11, 11:45 UTC

Identified - We identified a degradation on Google Cloud and we are monitoring if any of our components can be impacted. Availability to them can be impacted
Nov 11, 11:23 UTC

Nov 10, 2019

No incidents reported.

Nov 9, 2019

No incidents reported.

Nov 8, 2019

No incidents reported.

Nov 7, 2019

No incidents reported.

Nov 6, 2019

No incidents reported.

Nov 5, 2019

No incidents reported.

Nov 4, 2019

No incidents reported.

Nov 3, 2019

[Scheduled] Bringg Scheduled Maintenance - Sunday, November 3, 2019

Completed - The scheduled maintenance has been completed.
Nov 3, 15:00 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 3, 11:01 UTC

Update - We will be undergoing scheduled maintenance during this time.
Oct 30, 09:35 UTC

Scheduled - MAINTENANCE DETAILS

Bringg has scheduled a short maintenance window starting on Sunday, November 3, 2019 at 11 AM UTC in order to perform a short upgrade. The Maintenance will be carried out on all servers with the following schedule:

EU1 (AWS/Amazon) : 11:00 - 15:00 UTC - 12:00 - 16:00 Paris

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.
Oct 30, 08:46 UTC

[Scheduled] Bringg Scheduled Maintenance - Sunday, November 3, 2019

Completed - The scheduled maintenance has been completed.
Nov 3, 14:00 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 3, 12:30 UTC

Update - We will be undergoing scheduled maintenance during this time.
Oct 30, 09:34 UTC

Scheduled - MAINTENANCE DETAILS

Bringg has scheduled a short maintenance window starting on Sunday, November 3, 2019 at 12:30 AM UTC in order to perform a short upgrade. The Maintenance will be carried out on all servers with the following schedule:

US1 (AWS/Amazon): 12:30 - 14:00 UTC - 07:30 - 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.
Oct 30, 12:30 UTC

[Scheduled] Bringg Scheduled Maintenance - Sunday, November 3, 2019

Completed - The scheduled maintenance has been completed.
Nov 3, 10:00 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 3, 08:30 UTC

Update - We will be undergoing scheduled maintenance during this time.
Oct 30, 09:38 UTC

Scheduled - MAINTENANCE DETAILS

Bringg has scheduled a short maintenance window starting on Sunday, November 3, 2019 at 8:30 AM UTC in order to perform a short upgrade. The Maintenance will be carried out on all servers with the following schedule:

US2 (GCP/Google) : 08:30 - 10:00 UTC - 03:30 - 05: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.
Oct 30, 08:43 UTC

[Scheduled] Bringg Scheduled Maintenance - Sunday, November 3, 2019

Completed - The scheduled maintenance has been completed.
Nov 3, 08:30 UTC

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 3, 07:00 UTC

Update - We will be undergoing scheduled maintenance during this time.
Oct 30, 09:36 UTC

Update - We will be undergoing scheduled maintenance during this time.
Oct 30, 08:40 UTC

Scheduled - MAINTENANCE DETAILS

Bringg has scheduled a short maintenance window starting on Sunday, November 3, 2019 at 7 AM UTC in order to perform a short upgrade. The Maintenance will be carried out on all servers with the following schedule:

EU2 (GCP/Google) : 11:00 - 12:00 UTC - 11:00 - 12:00 London

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.
Oct 30, 08:39 UTC

Nov 2, 2019

No incidents reported.

Nov 1, 2019

No incidents reported.

Oct 31, 2019

No incidents reported.