Wyze Associates,
On Friday morning, we had a service outage that resulted in a safety incident. Your account and over 99.75% of all Wyze accounts weren’t affected by the safety occasion, however we wished to let in regards to the incident and what we're doing to verify it doesn't occur once more.
The outage originated from our AWS associate and disabled Wyze units for a number of hours early Friday morning. When you tried to view stay cameras or occasions throughout that point, you most likely failed. We’re very sorry for the frustration and confusion this has prompted.
Whereas working to carry the cameras again on-line, we ran right into a safety problem. Some customers have reported seeing the mistaken occasion thumbnails and movies within the Occasions tab. I instantly eliminated entry to the Occasions tab and started an investigation.
We will now verify that as cameras got here again on-line, roughly 13,000 Wyze customers obtained thumbnails from cameras that weren't theirs and 1,504 customers touched them. Most faucets enlarged the thumbnail, however in some circumstances an occasion video could possibly be seen. All affected customers have been notified. Your account was not one of many affected accounts.
The incident was attributable to a third-party cache consumer library that was lately built-in into our system. This consumer library skilled unprecedented load situations attributable to units coming on-line hastily. On account of elevated demand, it blended up the machine ID and person ID mapping and linked some information to incorrect accounts.
To verify this doesn't occur once more, we've added a brand new stage of verification earlier than customers are linked to occasion movies. We've additionally modified our system to bypass caching for user-device relationship checks till we determine new consumer libraries which might be totally examined for excessive occasions like we skilled on Friday.
We all know that is very disappointing information. It doesn’t replicate our dedication to defending clients or mirror the opposite investments and actions we’ve got taken over the previous few years to make safety a high precedence at Wyze. We constructed a safety workforce, applied a number of processes, created new dashboards, maintained a bug bounty program, and underwent a number of third-party audits and penetration assessments when this occasion occurred.
We now have to do extra and be higher and we are going to. We’re very sorry for this incident and are devoted to rebuilding your belief.
In case you have questions on your account, go to assist.wyze.com.
The Wyze workforce