Routific incident
API authentication errors impacting driver tracking and notification links
Resolved after 15 minutes, affecting Routific API and New Routific and 1 more, on August 25, 2026.
This incident is resolved. Between 20:15 and 20:47 UTC, API requests using older API tokens returned 401 errors, which delayed driver location updates and omitted tracking links from some delivery notifications. Notifications themselves continued to send throughout.
Affected components
Update timeline
- identified Aug 25, 2026, 08:51 PM UTC
Since approximately 30 minutes ago, a subset of API requests are failing with 401 Unauthorized errors. Requests authenticated with older, long-lived API tokens are affected; sign-ins through the web app are working normally. Customers may notice: - API integrations receiving 401 errors (including creating and polling optimizations) - Driver location updates missing from live tracking views - Delivery notifications (SMS/email) sending successfully but without their tracking links
- identified Aug 25, 2026, 08:52 PM UTC
We have identified the cause and we are fixing the affected services now.
- monitoring Aug 25, 2026, 08:53 PM UTC
The fix is complete as of now. API requests with existing tokens are authenticating normally again, and driver location updates and notification tracking links have resumed. We are monitoring error rates to confirm full recovery.
- resolved Aug 25, 2026, 09:06 PM UTC
This incident is resolved. Between 20:15 and 20:47 UTC, API requests using older API tokens returned 401 errors, which delayed driver location updates and omitted tracking links from some delivery notifications. Notifications themselves continued to send throughout.
Your product runs on more than Routific
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services