Nabla mobile applications broken
critical- Started
- Aug 3, 8:57 AM EDT
- Resolved
- Aug 3, 9:13 AM EDT
- Duration
- 16 min
Nabla's updates (2)
- identified · Aug 3, 8:57 AM EDT
The Nabla mobile applications stopped working correctly after our regular backend deployment. We've identified the issue as being CORS related, as well as the root cause change in the backend deployment. We're currently rolling out a hotfix to restore service. In addition, we'll be adding several guardrails in our backend so this issue cannot reproduce in the future.
- resolved · Aug 3, 9:13 AM EDT
The hotfix is fully rolled out. Service is fully recovered according to our metrics.
What our checks recorded
We checked Nabla 3 times from Nabla's start time to its resolution, once every five minutes. Every one of them reached Nabla's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 114 ms, against 189 ms over the 24 hours before. Nabla posted the incident at Aug 3, 8:57 AM EDT.
Updates are Nabla's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗