We apologize for the SelfDryv experience disruption experienced by some[0] customers earlier this week[1]. We experienced technical difficulties during a server migration that may[2] have degraded customer experience. The server migration exposed an incorrect dependency between the SelfDryv consumer hardware the the SelfDryv cloud services[3]. We have issued a fix[4] and offer 5 miles credits to any customer who was effected.

[0] About 100%

[1] 54 hours spanning Monday through Wednesday.

[2] ^H absolutely most certainly did

[3] Turns out part of the car's A/C UI dynamically fetches JavaScript on startup and our outage stopped serving JS, so A/C module failed to load. The worker thread that spawns the rest of the car's functionality freezes if the A/C module fails to respond. I guess we never tested that, I mean our internal network is pretty reliable, you know?

[4] We moved the JavaScript to a CDN so that means 100% availability. Presumably eventually we'll rewrite the entire client stack anyway thus implicitly killing this horrible dependency.