API and Processing Issues
Incident Report for Bringg
Resolved
Our Infrastructure and DevOps teams have completed all remedial steps and we are now marking this issue as resolved. Since the earlier reported instances, we have not seen further occurrences of the performance issues and all indications and metrics appear to be healthy. We will continue to monitor performance and will post additional notifications here should this issue reoccur.
Posted Sep 30, 2020 - 20:18 UTC
Update
We're happy to report that all services remain stable and fully operational. We will continue to monitor performance and will provide additional updates in due course.
Posted Sep 30, 2020 - 19:59 UTC
Monitoring
All services appear to have resumed successfully and remain stable and fully operational. We will continue to monitor performance and provide periodic updates.
Posted Sep 30, 2020 - 19:27 UTC
Update
Our DevOps and Server Teams are still working to ensure that all systems and services are resumed and remain fully functional. We will continue to provide ongoing updates.
Posted Sep 30, 2020 - 19:10 UTC
Identified
Bringg's DevOps and Server Teams have identified the issue and we are currently undertaking a number of remedial steps to ensure that the resumed services remain fully functional. We will provide additional updates shortly.
Posted Sep 30, 2020 - 18:48 UTC
Investigating
We're experiencing an elevated level of API and processing errors. We are currently investigating this issue.
Posted Sep 30, 2020 - 18:30 UTC
This incident affected: 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)).