Resolved after 2 hours, on September 18, 2025.
Root Cause: A breaking change at an external partner API led to unplanned behavior in our Speeding Detection service Impact: During a 4 hour time window 20% of trackings could not be processed, 80% were processed therefor some speedings might not have been detected
Update timeline
- resolved Sep 19, 2025, 06:39 PM UTC
Root Cause: A breaking change at an external partner API led to unplanned behavior in our Speeding Detection service Impact: During a 4 hour time window 20% of trackings could not be processed, 80% were processed therefor some speedings might not have been detected
Your product runs on more than INVERS
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.