# WyzeCam becoming more & more unusable?

**URL:** <https://forums.wyze.com/t/wyzecam-becoming-more-more-unusable/202985>\
**Category:** Cameras\
**Tags:** video\
**Created:** [November 19, 2021, 3:08pm UTC](https://forums.wyze.com/t/wyzecam-becoming-more-more-unusable/202985 "2021-11-19T15:08:48Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Customer](https://avatars.discourse-cdn.com/v4/letter/c/e19b73/32.png) [@Customer](https://forums.wyze.com/u/Customer)\
**Post date:** [November 20, 2021, 12:57am UTC](https://forums.wyze.com/t/wyzecam-becoming-more-more-unusable/202985/8 "2021-11-20T00:57:59Z")

</div>

> [@chaz](#):
>
> are you sure they don’t route through Wyzecam servers on the way to us?

Yes. This has been discussed, described, and documented many times. There are exceptions such as some Alexa streams.

Here is one semi-official description of the P2P process. (This means that after it starts the stream goes directly from camera to viewer.)

> [@Wyze is a Big Brother? The Company Failed Us](https://forums.wyze.com/t/topic/25839/11):
>
> Below is the logic between device and TUTK servers for illustrative purpose. I intentionally use generic words to hide detail implementation. During device setup time, the device registers itself with TUTK server to let Server know where it is. This is needed for TUTK to connect phone and the device in the future. However TUTK doesn’t know anything about Wyze user name, MAC, etc. We intentionally protected that. During device boot time, it registers itself with TUTK servers. Wyze’s code used …

---

_[View the full topic](https://forums.wyze.com/t/wyzecam-becoming-more-more-unusable/202985)._
