Resolved -
Incident has been resolved. It appears that our default API version was switched from V1 to V3 which caused our legacy V1 API to fail if the full path `/v1/*` was not provided which some of our endpoints within our mobile app were using.
May 3, 06:25 AEST
Identified -
Issue has been identified and a fix is being pushed.
May 3, 06:03 AEST
Investigating -
We are currently investigating an increase in error rate on our V1 driver APIs
May 3, 05:44 AEST